Let me recap to see if I understand correctly:
- the grub menu presents you with two installations, 9.2 and 10.0
- when you select 10.0 the boot begins but for some reason it hangs at some point
- when you select 9.2 grub loads 10.0 anyway (and ends up as above)
I do not think the superblock error you see is related to the above, looks more like when you installed grub something was not done right and you ended up with two entries linking to the same kernel image (10.0). The loader I use (lilo) does not have the intelligence necessary to do the switch you suggest, I assume it is the same for grub.
You could try to use the "reinstall boot loader" of the rescue disk:
1. boot from the MDK9.2 cd1
2. at the splash, type F1, then rescue
3. at the menu, select "reinstall boot loader"
This should search for existing boot images on the disk and reconstruct the lilo (or grub) loader. But, I have never done it so I cannot tell you how effective it is.
Another thing you can try is to select "mount existing partitions under /mnt" at point 3. above. This will let you access the uncorrupted partitions from the rescue disk, and then you could try to modify fstab to avoid loading the corrupt partition. But this option depends on how familiar you are with the command line, and with the linux configuration files.
I don't remember where fsck is located in the rescue disk, but I am almost sure I had e2fsck in the path. Try it out, it's the same as fsck if you are using ext2 or ext3 (the default installation).
It's not much, I hope others have better ideas.
raffaele
[EMAIL PROTECTED] wrote:
----- Original Message ----- From: "Raffaele Belardi" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 27, 2004 01:42
Subject: Re: [newbie] Bad superblock
Assuming you are using ext2 or ext3, superblock backup copies are stored in several places on the disk, mke2fs tells you where when you first create the filesystem.
If you didn't take a note, you can find out where the backup copies are by typing # mke2fs -n /dev/hdxx (note -n, does not actually create the fs, only prints what it would do).
Once you know where the backups are, you can issue # e2fsck -b <block number> /dev/hdxx to force fsck to use a different, possibly uncorrupted, superblock.
All of this can normally be done with the rescue option of the MDK9.2 install disk (i.e. insert disk 1, reboot, hit F1, type rescue), I'm surprised that it does not work for you. Could you please give more details on your problem?
Well I'll try. I installed 10.0rc1 and missed the configuration of the mouse although the mouse worked fine during the install, it didnt register that I hadnt configujred it, when I booted into the new system the mouse wouldnt even move or otherwise respond otherwise the install went well. I decided to reinstall and this time I configured the mouse. On booting into the system the mouse worked but there was another problem that requried me to correct lilo in order to boot 10.0. Well I misspelled lilo and couldnt find lilo.conf. Therefore I figured the easy way to fix lilo would be to reinstall with everything in place so I did so and selected grub instead of lilo. This worked but when I booted into 10.0 there was an error which I couldnt clear or get around so master reset was pushed to get out of the system. On rebooting to 9.2 several times I noticed scroll past on the screen a note that said bad superblock and the boot was switched to 10.0 by the computer now that is all I can boot into even though the boot process starts to boot into 9.2 it always ends up in 10.0 with the unresolvable problem. Rescue boots ok but fsck command will not execute and that is the first time I have tried to use rescue so I am at a rather sever impass. Hope this helps.
Regards; Hoyt
------------------------------------------------------------------------
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
