On Tuesday 18 March 2008 00:23:23 [EMAIL PROTECTED] wrote: > Try the super grub disk if you can get a copy. It should let you boot > the system. > > Heracles > > [EMAIL PROTECTED] wrote: > | I have LinuxMint KDE 4.0.44 installed > | > | My system has suddenly decided not to boot, giving the following error > | from /var/log/fsck/checkfs:- > | > | Log of fsck -C -R -A -a > | Fri Mar 14 23:43:10 2008 > | > | fsck 1.40.2 (12-Jul-2007) > | /dev/hda3: clean, 6800/1376256 files, 1585688/2749123 blocks > | fsck.ext3: No such file or directory while trying to open /dev/hdb1 > | /dev/hdb1: > | The superblock could not be read or does not describe a correct ext2 > | filesystem. If the device is valid and it really contains an ext2 > | filesystem (and not swap or ufs or something else), then the superblock > | is corrupt, and you might try running e2fsck with an alternate > | superblock: e2fsck -b 8193 <device>
The pain of the sudo paradigism is when, during boot it says 'fsck error enter root password to manually ...' I think that (a) boot any cd you are familiar with (b) run fsck and mount the target partitions If you can't do this then climb the tower, the more valuable the data the higher, and jump dagger clutched in teeth ... If all is well then you can reinstall grub (if need be) mount the partition containing /boot on (say) /mnt (say) this is /dev/sda1 now grub-install --root-directory /mnt /dev/sda will fix every thing James -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
