file system (superblock) corrupted?
Hi,
I saw a strange thing in my /home directory. When I did #ls -l mp3, it returned many ?s in the places for the file permissions, owners, size, and date. so, all directories looked something like this: d?????? ? ???? ???? ??? ???????????? jazz d?????? ? ???? ???? ??? ???????????? pops ... I thought my filesystem was corrupted, so I unmounted the /home directory and tried to run fsck on /dev/hdb2. Then it returned this message: [snip]--- bash-3.1# fsck /dev/hdb2 fsck 1.40.8 (13-Mar-2008) e2fsck 1.40.8 (13-Mar-2008) /sbin/e2fsck: Filesystem revision too high while trying to open /dev/hdb2 The filesystem revision is apparently too high for this version of e2fsck. (Or the filesystem superblock is corrupt) 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> ---[snip] I did mke2fs to look for alternative superblock and ran: #e2fsck -f -b 98304 /dev/hdb2 Then it returned this message: [snip]--- e2fsck 1.40.8 (13-Mar-2008) e2fsck: Device or resource busy while trying to open /dev/hdb2 Filesystem mounted or opened exclusively by another program? ---[snip] How come? I did umount on /home and /dev/hdb2 and nothing should be accessing the filesystem. fuser doesn't return anything either. Could you help me to run fsck on /dev/hdb2 at least so that I can go forward investigating the problem? /dev/hdb2 should be ext3 as described in /etc/fstab /dev/hdb2 /home ext3 defaults 1 2 Thanks in advance, gibb |
Quote:
The first thing to do is run: fsck -y -t ext3 /dev/hdb2 against a umounted /dev/hdb2. If you need to try a superblock other than the first then try: fsck -b 32768 -y -t ext3 /dev/hdb2 ------------------ Steve Stites |
Thank you for your reply jailbait.
At first, I ran fsck.ext3 and I got the same message as I ran fsck /dev/hdb2, suggesting me to try with e2fsck -b 8193 <device>. After reading your post, I ran the commands with -t ext3 option but I got the same result. Does this mean it's really messed up and not recovable? I don't know why it keeps telling me that /dev/hdb2 is busy. I executed the cmd in single-user mode and no luck. Any idea? Thanks in advance, gibb |
Hi,
You did boot into single? You could use your Slackware 12.1 install cd/dvd to insure that there won't be conflicts. Code:
excerpt from 'man e2fsck'; |
Hi onebuck,
I booted up with the slackware installation cd and ran #fsck -f -t ext3 /dev/hdb2. #fsck -f -t ext3 /dev/hdb2 fsck 1.40.8 (13-Mar-2008) fsck: fsck.ext4: not found fsck: Error 2 while executing fsck.ext4 for /dev/hdb2 hmm... it's recognizing the filesystem as ext4 while the /etc/fstab says ext3. Is this because /dev/hdb2 is about 150GB in size? I'm more interested in fixing/recovering this un-mountable filesystem than inn recovering the data in it. I just don't understand why the system keeps telling me the filesystem is busy while it is unmounted and no services should be accessing it. Or is there any way to find out? I can just format/recreate the partition and get going but I really would like to know how to fix this type of problem. Any suggestion is welcome. Thanks in advance, gibb |
Hi,
Once you boot the install cd/dvd. Do the 'e2fsck -b 8192 /dev/your_device'. What happens? |
Hi,
I executed the command after booting up with the installation cd and got the same result: e2fsck 1.40.8 (13-Mar-2008) e2fsck: Device or resource busy while trying to open /dev/hdb2 Filesystem mounted or opened exclusively by another program? hmm... why??? thanks in advance, gibb |
From the CD, what do these produce ???
Code:
fdisk -l |
Hi,
Code:
bash-3.1# fdisk -l so here is the output from the konsole: Code:
bash-3.1# file -sL /dev/hdb2 Thanks in advance, gibb |
uhmm... after rebooting the system, I lost the partition table for /dev/hdb. fdisk -l tells me "Disk /dev/hdb doesn't contain a valid partiton table." I think this drive is pretty messed up.
I'm going to rebuild this derive and start over. Thank you all for your help! gibb |
All times are GMT -5. The time now is 08:35 PM. |