---
Running DevFS daemon Started device management daemon V1.3.25 for /dev
unknown group: "video", defaulting to GID=0
** CRITICAL **: unknown class "dri" at line 80 in /etc/security/console.perms
Unmounting initrd:
Loading default keymap: /etc/rc.d/rc.sysinit:
line 265: /dev/tty0: No such file or directory
Checking root filesystem
fsck.ext3/dev/hda8:
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>
No such file or directory while trying to open /dev/hda8 Failed to check filesystem. Do you want to repair the errors (Y/N) (beware, you can lose data) ---
I've tried answering both yes and no to the "do you want to repair" prompt, but both times it drops me back to the shell saying it can't find /dev/hda8.
I tried running: e2fsck -b 8193 /dev/hda8 and e2fsck -b 32768 /dev/hda8 but got the same message. "can't find /dev/hda8"
I tried mke2fs -n /dev/hda8 same message: "can't find /dev/hda8"
I also booted from the CD in "rescue" mode, and tried: [EMAIL PROTECTED] /]# lsparts hda1: 3,702 MBytes, type <0x7> (NTFS (or HPFS)) hda5: 8,150 MBytes, type <0x7> (NTFS (or HPFS)) hda6: 8,573 MBytes, type <0x7> (NTFS (or HPFS)) hda7: 5,004 MBytes, type <0x7> (NTFS (or HPFS)) hda8: 5,992 MBytes, type <0x83> (Ext2) hda9: 494 MBytes, type <0x82> (Linux Swap) hda10: 6,243 MBytes, type <0x83> (Ext2)
Unfortunately, "Rescue" mode isn't very useful to me (yet), because I don't know *how* to rescue the partition...
I've tried reinstalling from CD with the "upgrade existing installation" option, and that seemed to run through everything fine, but made no difference when I rebooted.
I'm wondering if I have two problems here, because a few days ago I installed the NVidia drivers for Linux, and one of the instructions was to remove the line from /etc/security/console.perms which started with "dri". I didn't actually remove the line, but I commented it out (in case I needed to restore it later), as follows:
... <gpm>=/dev/gpmctl # <dri>=/dev/nvidia* /dev/3dfx* <mainboard>=/dev/apm_bios ...
The system has worked fine since I made that change, including shutting down and rebooting several times (though I hadn't booted into Windows until last night). Should I have removed the line completely, perhaps ?
I'm suspicious of Diskeeper 7 though, my Windows defragger. It ran for a couple of minutes while I was in Windows last night, before I noticed it and shut it down (not for Mandrake's sake, but for what I was doing at the time). I'd originally used Partition Magic 7 to create a blank space at the end of the drive, which I told Mandrake to install itself in using it's default partitioning, and when I ran Partition Magic again after Mandrake was installed, it complained about the boot sector being in the wrong place (or something similar, I don't recall the exact message). I didn't let it change anything though, as everything was working. Maybe Diskeeper shifted or overwrote something it shouldn't have.
Many of the posts I've read while Googling have basically said, "sorry dude, you're gonna have to reinstall from scratch". While this isn't a major catastrophe (I've only being using Linux for just over a month, and all I'll really lose is a few weeks emails, and some programs I've installed), I'd ideally like to get it back to where it was.
Does anybody have any bright ideas ? I'm not at home right now, so I can't try anything until I get back tonight.
Thanks for your time, Dave
-- Cunningly disguised as a responsible adult
