You can create an emergency boot disk (minus modules) very easily with:
cat /vmlinuz >/dev/fd0
That will be identical to booting off your hard drive. I used to use that
until lilo started recognizing RAID and I still keep one around in case the
boot gets hosed.
________________________________________
Michael D. Black Principal Engineer
[EMAIL PROTECTED] 321-676-2923,x203
http://www.csihq.com Computer Science Innovations
http://www.csihq.com/~mike My home page
FAX 321-676-2355
----- Original Message -----
From: "Diegmueller, Jason (I.T. Dept)" <[EMAIL PROTECTED]>
To: "'Mike Black'" <[EMAIL PROTECTED]>; "Marco Shaw" <[EMAIL PROTECTED]>;
"Dimitri SZAJMAN" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, June 23, 2000 11:23 AM
Subject: RE: I'm installling a system
After installation you can:
: #1 - Add new hard drive (two for RAID5)
: #2 - Create failed disk RAID1 or RAID5
: #3 - Create file system on RAID1 or RAID5
: #4 - Boot from rescue disk (must have RAID kernel on it)
: #5 - Copy old non-RAID to new RAID using afio or cpio
: #6 - Reboot to new RAID (change fstab and rdev your kernel)
: #7 - raidhotadd old disk
Perhaps I live on the wild side, but I don't even boot from a
rescue disk.
I created the file system on the RAID1, cp -a'd the data over,
modified the /new/etc/fstab, whipped up my /mnt/boot1/etc/lilo.conf
and /mnt/boot2/etc/lilo.confs (/mnt/boot1 and /mnt/boot2 are
non-RAIDed, 16MB ext2fs partitions I use to boot from), then booted
straight to the new, degraded raid. THEN I performed your step 7 ..
.. of course, one of these days I'll botch up the lilo.conf
and be unable to boot, but hey, that's half the fun of playing with
this stuff. =)
