On Saturday 27 August 2005 10:26 am, nordi wrote:
I agree on /boot, although for a different reason. A friend of mine had a Suse system. One time it crashed and after that not even grub would start! Turned out his file system for / had some corruptions cause by the crash that prevented grub from reading /boot/grub/menu.lst. As a result, he couldn't even start windows! With /boot on a seperate partition this could not happen, since /boot is hardly ever written to.
Right on Stefan. I've been using LILO for about 5 years and about 2 months ago I switched to GRUB. I've been having he same problem you are describing (in more than one occasion). It is because of the fact that now I'm running GRUB and I don't have a separate partition for /boot. I've been having some electrical problems (on my house) causing my system to suddenly shut down. When I boot up, not even GRUB starts. I have to insert the SUSE cd and go into recovery mode in order to perform a reiserfsck on my root partition. After that it works. This never happened before with LILO, as I guess most of the stuff LILO needs to boot my system is stored on the MBR wheras GRUB needs some files from the filesystem to load its second stage (after loading first stage on MBR). I have one of three conclusions: 1- I need to buy an UPS ;) or 2- Go back to LILO or 3- Keep using GRUB but then I need to create a partition for /boot (the one I plan to mount read-only) to avoid the problems discussed here. Jorge