No longer able to mount a partition

elarsen · 01-04-2012, 06:24 PM

I was playing my mp3 files. When banshe crashed. I restarted the pc, and I'm unable to mount the partition.

When I use mount /dev/sda2 /storage I get:

Code:

mount: wrong fs type, bad option, bad superblock on /dev/sda2,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

When I do dmesg | tail:

Code:

[177757.276624] sd 2:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[177757.276629] sd 2:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor]
[177757.276635] Descriptor sense data with sense descriptors (in hex):
[177757.276639]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
[177757.276651]         2e e8 60 20 
[177757.276656] sd 2:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed
[177757.276663] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 2e e8 60 20 00 00 08 00
[177757.276675] end_request: I/O error, dev sda, sector 786980896
[177757.276683] Buffer I/O error on device sda2, logical block 83886084
[177757.276713] ata3: EH complete

When I do fsck:

Code:

fsck from util-linux-ng 2.17.2
fsck.jfs version 1.1.12, 24-Aug-2007
processing started: 1/4/2012 18.1.51
Using default parameter: -p
The current device is:  /dev/sda2
Block size in bytes:  4096
Filesystem size in blocks:  229703936
**Phase 0 - Replay Journal Log
ujfs_rw_diskblocks: read 0 of 4096 bytes at offset 343597400064
logredo failed (rc=-242).  fsck continuing.
**Phase 1 - Check Blocks, Files/Directories, and  Directory Entries
ujfs_rw_diskblocks: read 0 of 16384 bytes at offset 343597400064
Unrecoverable error reading M from /dev/sda2.  CANNOT CONTINUE.

hydraMax · 01-04-2012, 06:55 PM

Maybe drive is going bad? You could try (as root):

Code:

smartctl -H /dev/sda

And maybe a long test:

Code:

smartctl -t long /dev/sda
(when done)
smartctl --all /dev/sda

elarsen · 01-05-2012, 09:15 PM

The test result says passed. So The hard drive is good.

hydraMax · 01-06-2012, 12:46 AM

Can you reformat the partition? If your drive is really fine (and the controller) that should fix the problem. (Of course, the old data will get wiped.)

elarsen · 01-06-2012, 04:57 PM

Sun of a bees wax. That is what I am trying to prevent. This would be the third time I lost data, because of similar issues. What file system would be the best for my back up partition. I basicly use my mint pc as a file server. I currently have that partition as jfs and the partition with mint is ext3.

wagscat123 · 01-06-2012, 07:59 PM

Try:

[CODE] badblocks -nvs /dev/sda2 [CODE]
on a Live CD.
Also, see if it mounts on the Live CD.

elarsen · 01-10-2012, 05:16 PM

Finally done. The out put of badblocks is :

Quote:

sudo badblocks -nvs /dev/sda2
Checking for bad blocks in non-destructive read-write mode
From block 0 to 918815743
Checking for bad blocks (non-destructive read-write test)
Testing with random pattern: 335544320one, 28:35:53 elapsed
335544336one, 28:36:24 elapsed
335544337one, 28:36:40 elapsed
335544338one, 28:36:55 elapsed
335544339one, 28:37:11 elapsed
done
Pass completed, 5 bad blocks found.

Would the program mark the blocks so nothing will be written to it? I received the same error before and after badblocks.

custangro · 01-10-2012, 05:22 PM

Quote:

Originally Posted by elarsen

Finally done. The out put of badblocks is :

Would the program mark the blocks so nothing will be written to it? I received the same error before and after badblocks.

Have you done an fsck from the live cd?

-C

elarsen · 01-10-2012, 06:27 PM

Yes I have and it comes up with the same thing.

custangro · 01-11-2012, 10:27 AM

Quote:

Originally Posted by elarsen

Yes I have and it comes up with the same thing.

Just so that we have more information...what is the output of

Code:

 dumpe2fs /dev/sda1

elarsen · 01-12-2012, 04:24 PM

Well the output of /dev/sda1:

Code:

dumpe2fs 1.41.14 (22-Dec-2010)
dumpe2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1
Couldn't find valid filesystem superblock.

Output of /dev/sda2 (one that has issue)

Code:

dumpe2fs 1.41.14 (22-Dec-2010)
dumpe2fs: Bad magic number in super-block while trying to open /dev/sda2
Couldn't find valid filesystem superblock

custangro · 01-12-2012, 05:42 PM

It looks like you have a bad superblock...try the following

Code:

dumpe2fs /dev/sda2 |grep -i superblock

Then try repairing the disc with one of the backup superblocks

Code:

fsck -f -b <Backup superblock number>  /dev/sda2

NOTE:
If dumpe2fs doesn't work try getting the backup superblock with...

Code:

mkfs.ext4 -n /dev/sda2

-C

elarsen · 01-12-2012, 08:35 PM

when I do the fsck I get:

Code:

sudo fsck -f -b 32768 /dev/sda2
fsck from util-linux-ng 2.17.2
fsck.jfs version 1.1.12, 24-Aug-2007
processing started: 1/13/2012 2.31.55
fsck.jfs: invalid option -- 'b'

Usage:  fsck.jfs [-afnpvV] [-j journal_device] [--omit_journal_replay] [--replay_journal_only] device

Emergency help:
 -a                 Automatic repair.
 -f                 Force check even if file system is marked clean.
 -j journal_device  Specify external journal device.
 -n                 Check read only, make no changes to the file system.
 -p                 Automatic repair.
 -v                 Be verbose.
 -V                 Print version information only.
 --omit_journal_replay    Omit transaction log replay.
 --replay_journal_only    Only replay the transaction log.

so I remove the -b and get:

Code:

fsck from util-linux-ng 2.17.2
fsck.jfs version 1.1.12, 24-Aug-2007
processing started: 1/13/2012 2.32.9

Error: Device not specified or command format error

Usage:  fsck.jfs [-afnpvV] [-j journal_device] [--omit_journal_replay] [--replay_journal_only] device

Emergency help:
 -a                 Automatic repair.
 -f                 Force check even if file system is marked clean.
 -j journal_device  Specify external journal device.
 -n                 Check read only, make no changes to the file system.
 -p                 Automatic repair.
 -v                 Be verbose.
 -V                 Print version information only.
 --omit_journal_replay    Omit transaction log replay.
 --replay_journal_only    Only replay the transaction log.

elarsen · 01-30-2012, 04:33 PM

Well since no one can help, and I can't find anything online that will work. I am going to reformat that partition. Should I do jfs again. Or is another file system better like ReiserFS.

custangro · 01-30-2012, 06:16 PM

Quote:

Originally Posted by elarsen

Well since no one can help, and I can't find anything online that will work. I am going to reformat that partition. Should I do jfs again. Or is another file system better like ReiserFS.

Any specific reason why you are doing something other than EXT4?