Marcos,
> My boot partition is on sda1 and that is on that partition.
What do you mean by this? What is on that partition? Is /dev/sda1 mounted on
/boot with all the normal /boot files on it? If so, your setup sounds fine.
Assuming the setup is OK, you have 2 alternatives. Kill klogd, as you suggest.
But you presumably have this running for a reason. So if you don't want to do
this, the other alternative would be to leave /dev/sda1 on /boot for now. Edit
/mnt/newroot/etc/lilo.conf so that you have an image section which selects your
root-RAID array as root (e.g. root=/dev/md?). Delete the files you copied to
/mnt/newroot/boot (you want it to be an empty mount-point). Make sure
/mnt/newroot/etc/fstab shows / on your root-RAID device and /boot still on
/dev/sda1. Now run lilo -C /mnt/newroot/etc/lilo.conf. If you now reboot and
select the RAID image section at the boot prompt, everything should be working.
Note to Jakob: The advice to move the boot device to /mnt/newroot/boot and
running lilo with the -r option is more confusing than it needs to be. Why not
simply make sure that lilo.conf includes a RAID section as above (where
root=/dev/md?)? You don't need the boot device to be on /mnt/newroot/boot. All
the files which lilo references are in the same physical place, whether it is
mounted on /boot or /mnt/newroot/boot. You could replace the section beginning
"Now, unmount the current /boot filesystem" and ending with "complete with no
errors" with a simple instruction to run lilo without parameters, as long as you
insert an item before the filesystem is copied across to the effect of:
* Edit /etc/lilo.conf to add an image section which points to the root-RAID
array as the root device (i.e. use "root=/dev/md?" where ? is the device number
of your root RAID array).
(We do this before the filesystem is copied so that /etc/lilo.conf matches
/mnt/newroot/etc/lilo.conf, so we don't even have to use -C with lilo to pass it
the new lilo.conf address.) I think this would be a good change to make as the
unnecessary complication of moving the boot device seems to be tripping a lot of
people up.
Cheers,
Bruno Prior [EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Marcos Lopez
> Sent: 25 October 1999 19:09
> To: [EMAIL PROTECTED]
> Subject: Root RAID and unmounting /boot
>
>
> I am attempting to get my system to run RAID 1 for /, /usr, /var, /home
>
> I have moved over all except for / and it works fine.
>
> After reading the howto "Root file system on RAID. by - Jakob
> OEstergaard" I have decided to take the first approach, unfortunately I
> can not umount \boot. even after performing a umount -f \boot. I also
> performed a lsof | grep /boot to see what was being used and it returned
> the following.
> syslogd 378 root 5w REG 9,1 8548 192396
> /var/log/boot.log
> klogd 389 root 2r REG 8,1 191102 12
> /boot/System.map-2.2.12-20
>
> Is it safe to kill these?
>
> Also i would be quite grateful if someone could explain to me why I must
> unmount /boot inorder for the lilo -r /mnt/newroot to work?
>
> My boot partition is on sda1 and that is on that partition. I actually
> had to copy my /boot to my /mnt/newroot/boot else there would be no
> files there. An explanation here would really be grand.
>
> What happens when i run lilo -r /mnt/newroot? How will this affect the
> current /boot as it is never touched as far as I can see.. Hehe, i am
> kinda confused :-)
>
> thanks
> -marcos
>
