On Monday 08 July 2002 9:23 pm, Mads Martin Joergensen wrote:
Relax, all your data is ok. Problem is the kernel cannot find the init binary and execute it. Probably b/c the partitions got another order now.
Spot on, Mads! Clever.
Say your /etc/fstab says / is on /dev/hda1 and it now b/c of reordering became /dev/hda7. Then the kernel cannot find the init binary, and since the kernel have to pass execution to something, it panics.
Indeed, fstab says / is on hda11, but it is now on hda9. Ditto for lilo.conf.
Might be you've to rerun LILO if changes in /etc/lilo.conf are needed, but wait with that until you know.
Presumably this is needed, but how do I do this from the Rescue option?
HTH,
Indeed it does - a few small grains of knowledge have now trickled into my head! But, a deeper question. How come SuSE installed onto hda11 even if there was a discrepancy in the HD partition table (and ran fine)? What caused the discrepancy, do you think - did Partition Magic do something wrong in the initial partitioning, or SuSE in the install? I still tend to approach partitioning as if it's some sort of voodoo, I'm afraid :-) Thanks Kevin