Soenke Lange writes:
> Hi,
>
> I've some problems with lilo and the root device.
> My lilo.conf:
> boot=/dev/md0
> install=/boot/boot.b
> map=/boot/map
> vga=normal
> delay=20
>
> image=/mnt/boot/bzImage-2.0.38
> root=/dev/md0
> label=li
> read-only
>
>
Bruno Prior writes:
> I don't understand this part of your message. Are you trying to use the
> "/boot=/dev/md?" line which was suggested in an earlier thread? I don't see how
> this works. Going back to Dirk Lutzebaeck's problem with this, he used
> "boot=/dev/md0". /dev/md0 is a mirror of /d
dr. Eduard Werner (Edward Wornar) writes:
> I think the point is to a certain degree that *IF* the whole thing fails
> people will think "Ah, you shouldn't use Linux, since Solaris has much more
> experience with RAID ..."
Exactly. What about hardware support? Can I get a turnaround of let's
s
Niklas Paulsson writes:
> The lack of a journaling fs is also a major show stopper at our site,
> once we have a relaible journaling fs that works well together with sw
> (and hw) raid , we will begin thinking of a migration path to linux on
> our big boxes. But that belongs on another list...
Theo Van Dinter writes:
> On Wed, 27 Oct 1999, Bruno Prior wrote:
>
> BP> (a) Getting the latest patched lilo from RedHat or applying the lilo.raid1 patch
> BP> and rebuilding it yourself (if /dev/md0 is RAID-1)
> BP> (b) Providing lilo with the geometry of one of the devices in the array (a
Thomas Waldmann writes:
> Strange: I "only" got about the same value with 4 IBM DNES UW SCSI disks.
> A single DNES disk gives about 17MB/s bonnie - about 50% (?) more than the
> older DDRS disk can do - so I had expected a transfer rate of >35MB/s (the
> SCSI channels theoretically could prov
Jochen Haeberle writes:
> If there is the problem you describe, why is lilo then able to
> install a working boot sector on one of
> the disks???
I looked at the strace output:
stat("/tmp/dev.0", 0xbfffde70) = -1 ENOENT (No such file or directory)
mknod("/tmp/dev.0", S_IFBLK|0600, m
Jochen Haeberle writes:
> Although lilo.raid accepts my lilo.conf and shows two parts of adding
> configs, only the first disk in the raid seems bootable.
> The only sign of failure I get is a line saying "open /tmp/dev.0: No
> suitable device found" after adding the configs to the boot reco
