|
- I've just added a hard disk using harddrake2, and for various reasons, it's added a line to /etc/fstab for a disk partition which no longer exists
On bootup, the line "Error found in disk check, would you like to repair (Y/N), beware you can lose data". Answering either yes or no to this gives the same result: the disk check fails, and mandrake craps out to a "recovery console".
A recovery console which apparently doesn't have access to any text editors (/usr/bin is not mounted), and seems rather incapable of editing fstab.
Linux bootable business card can run okay. However, its access to /mnt/disks/parta6 or wherever fstab is, is read-only. So no luck getting anything fixed from there either.
Booting from installation CD1, and I think this is probably some sort of problem, it will go into an infinite loop of "cannot check hda8, repair? [Yes] [No]", then report an error and go back to "cannot check hda8, repair? [Yes] [No]". Ad infinitum.
Booting into "failsafe" mode is similar to the bootable CD. It runs, but it boots into it's own little world, where /etc/fstab is most definitely not the one I need to edit.
Surely there must be some more intelligent bootup sequence whose response to a disk error is not to blindly run in circles doing the same disk check again and again and again and again, but to load what disks it can, so that the errors can be recovered from?
|
