+ Eduard Bloch <[EMAIL PROTECTED]> [19.06.02 10:57]:
> The current md driver is broken-by-design in the autodetection issue.
> You have to compile the driver into the kernel and mark the partition as
> type 0xFD to make it autodetecteable. When using modules, you will be
> forced to reconstruct the
+ Thomas -Balu- Walter <[EMAIL PROTECTED]> [19.06.02 11:14]:
> + George Karaolides <[EMAIL PROTECTED]> [19.06.02 10:18]:
> > Have you got it all working normally before simulating failures? Can you
> > boot into the RAID from either disk, using the BIOS setup to sele
+ George Karaolides <[EMAIL PROTECTED]> [19.06.02 10:18]:
> Before we go into your message, which kernel version are you using?
kernel-image-2.4.18-686
[bios=0x80]
> When you install an MBR on a disk using lilo, lilo will use the BIOS ID
> currently lilo thinks is currently assigned to the disk.
Thanks George, I am getting closer :)
+ George Karaolides <[EMAIL PROTECTED]> [18.06.02 11:23]:
[...]
> # Better use the first BIOS ID for the disk we'll boot from;
> # we'll use the BIOS setup to boot from this
> disk=/dev/hdc
> bios=0x80
What exactly does that do?
[...]
> You don't need
I've read different HOWTOs, Hints, Tipps and tricks on this subject, but
none helped (and this is the first problem since 5 years that I am going
to despair on :-])
I am trying to set up a debian (woody) system running the
debian-packaged 2.4.18-686-kernel that boots from "root=/dev/md1" (and
uses
5 matches
Mail list logo
