Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've no idea what I did to make this happen, which probably makes it even worse.
Last night when I booted, I got the following:
.
.
.
Running DevFs daemon Started device management daemon v1.3.2.5 for /dev
unknown group: "video", defaulting to GID=0
**CRITICAL**: unknown class "dri" at line 80 in /etc/security/console.perms
.
.
.
Loading default keymap: etc/rc.d/rc.sysinit: line 248: /dev/tty0: no such file or directory
fsck.ext2/dev/hda5:
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 alternative superblock:
e2fsck -b 8193 <device>
: No such file or directory while trying to open /dev/hda5
Failed to check filesystem. Do you want to repair?
Doesn't matter if I answer yes or no, I get prompted for a root password and it wants me to do something. Not much I can do, the /dev/ directory seems to be practically empty, I can't access the other drives or anything. I tried running Partition Magic on the drive and it found an error with the superblock, but can't fix it. But browsing the drive from Partition Magic shows all the data correctly, as far as I can tell.
So, at least I've got a way of saving some of my data before reinstalling. But before I do I thought I'd ask here to see if there is a way to recover the drive, or at least if someone could tell me what I might have done so I don't do it again in the future. I've no idea what it could be...
Originally posted by Bjornkri I've no idea what I did to make this happen, which probably makes it even worse.
Last night when I booted, I got the following:
.
.
.
Running DevFs daemon Started device management daemon v1.3.2.5 for /dev
unknown group: "video", defaulting to GID=0
**CRITICAL**: unknown class "dri" at line 80 in /etc/security/console.perms
.
.
.
Loading default keymap: etc/rc.d/rc.sysinit: line 248: /dev/tty0: no such file or directory
fsck.ext2/dev/hda5:
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 alternative superblock:
e2fsck -b 8193 <device>
: No such file or directory while trying to open /dev/hda5
Failed to check filesystem. Do you want to repair?
Doesn't matter if I answer yes or no, I get prompted for a root password and it wants me to do something. Not much I can do, the /dev/ directory seems to be practically empty, I can't access the other drives or anything. I tried running Partition Magic on the drive and it found an error with the superblock, but can't fix it. But browsing the drive from Partition Magic shows all the data correctly, as far as I can tell.
So, at least I've got a way of saving some of my data before reinstalling. But before I do I thought I'd ask here to see if there is a way to recover the drive, or at least if someone could tell me what I might have done so I don't do it again in the future. I've no idea what it could be...
Put in the root username, and run fsck like it says, using an alternate superblock. The reason it appears to be empty is that the the data describing the directory is now corrupt. Replacing the superblock should repair that. Don't lose hope, it's not anything serious.
Distribution: Fedora, Debian, OpenSuSE and Android
Posts: 1,820
Rep:
You can get a low level format utility from the drives manufaturer. It can be dangerous (can ruin the drive) but it will go over every square inch of the drive and afterwards you won't have bad superblocks. Just a last resort though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.