Re: bootable raid 1

2000-12-27 Thread Charles Wilkins
21.5 or later for the bootable raid 1. Here is my lilo.conf for your reference. boot=/dev/md1 map=/boot/map install=/boot/boot.b prompt timeout=50 default=vmlinux vga=normal keytable=/boot/us.klt message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinux label=vmlinux root=/dev/md0 append

Re: bootable raid 1

2000-12-21 Thread Danilo Godec
On Wed, 20 Dec 2000, Michael wrote: > This is an issue with the firmware on the drive itself. Intrestingly > enough, I have 2 identical (??) 20 gig drives purchased at the same > time that report differently to the kernel at boot. When probed, one > reports CHS and the other reports LBA values. I

Re: bootable raid 1

2000-12-21 Thread Charles Wilkins
el" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, December 21, 2000 3:05 AM Subject: Re: bootable raid 1 > On Wed, 20 Dec 2000, Michael wrote: > > > This is an issue with the firmware on the drive itself. Intrestingly > > enough, I have 2 identica

Re: bootable raid 1

2000-12-20 Thread Michael
> I am not 100% certain, but this is the only change > that I implemented that made the difference. It might explain why > when both drives were installed that the system booted, but when > either was removed, it would not boot. > > Using LBA translation method in both the BIOS and with fdisk us

bootable raid 1

2000-12-19 Thread Charles Wilkins
Thank you both for your help with this matter. I am pleased that I have overcome this issue and here are my conclusions. My previous raid configuration was set up using CHS method for harddisk geometry. There was no reason for doing this other than it was a part of the diagnostic procedure for a

Re: bootable raid 1

2000-12-18 Thread Godfrey Livingstone
gt; > vga=normal > > default=vmlinux > > keytable=/boot/us.klt > > prompt > > timeout=50 > > message=/boot/message > > menu-scheme=wb:bw:wb:bw > > image=/boot/vmlinuz > > label=vmlinuz > > root=/dev/md0 > > append=" ide3=autotu

Re: bootable raid 1

2000-12-18 Thread Godfrey Livingstone
ot/vmlinuz > label=vmlinuz > root=/dev/md0 > append=" ide3=autotune ide1=autotune ide2=autotune hdh=ide-scsi" > read-only > image=/boot/vmlinux > label=vmlinux > root=/dev/md0 > append=" ide3=autotune ide1=autotune ide2=autotune hdh=ide-scsi" > read-o

Re: bootable raid 1

2000-12-18 Thread Charles Wilkins
ide-scsi" read-only image=/boot/vmlinux label=vmlinux root=/dev/md0 append=" ide3=autotune ide1=autotune ide2=autotune hdh=ide-scsi" read-only - Original Message - From: "Luca Berra" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 18,

Re: bootable raid 1

2000-12-18 Thread Luca Berra
On Mon, Dec 18, 2000 at 09:15:51AM -0500, Charles Wilkins wrote: > I am currently doing bootable raid 1 with all of the latest patches for > 2.2.18 and then some. > When I try to boot the system with either drive removed, I get a bunch of > 010101010's in an endless loop. > Y

bootable raid 1

2000-12-18 Thread Charles Wilkins
I am currently doing bootable raid 1 with all of the latest patches for 2.2.18 and then some. When I try to boot the system with either drive removed, I get a bunch of 010101010's in an endless loop. Yet, when both drives are in, the system comes up fine. What am I doing wrong? Using lilo