LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (http://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   ext4 partition failed to mount after unsuccessful unmounting (http://www.linuxquestions.org/questions/linux-hardware-18/ext4-partition-failed-to-mount-after-unsuccessful-unmounting-4175460176/)

saeedit 04-30-2013 12:40 PM

ext4 partition failed to mount after unsuccessful unmounting
 
Hello guys.
Here is the some info about my USB2 external hard disk.

500 G Portable Hard Disk

sdb1 315G ext4 label: Personal
sdb2 contains sdb5 and sdb6
sdb5 50G ext4 label: Private
sdb6 100G ntfs


After a unsuccessful unmounting the hard disk, in next try to mount it, my two ext4 partition failed to mount.
It causes to show these two error messages.


Personal ext4

Error mounting /dev/sdb1 at /media/saeed/Saeed ext4: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb1" "/media/saeed/Saeed ext4"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


Private ext4

Error mounting /dev/sdb5 at /media/saeed/Private ext4: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb5" "/media/saeed/Private ext4"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb5,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


#####################################

#dmesg | tail
[ 1647.421612] sd 4:0:0:0: >[sdb] No Caching mode page present
[ 1647.421623] sd 4:0:0:0: >[sdb] Assuming drive cache: write through
[ 1647.488164] sdb: sdb1 sdb2 < sdb5 sdb6 >
[ 1647.490858] sd 4:0:0:0: >[sdb] No Caching mode page present
[ 1647.490870] sd 4:0:0:0: >[sdb] Assuming drive cache: write through
[ 1647.490878] sd 4:0:0:0: >[sdb] Attached SCSI disk
[ 1648.285466] EXT4-fs error (device sdb5): ext4_ext_check_inode:459: inode #8: comm mount: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[ 1648.285486] EXT4-fs (sdb5): no journal found
[ 1648.285957] EXT4-fs error (device sdb1): ext4_ext_check_inode:459: inode #8: comm mount: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[ 1648.285964] EXT4-fs (sdb1): no journal found


#####################################

How can i fix it?
this [fsck.ext4 -cDfty -C 0 /dev/sdb5] does not work :-/


thanks...

cortman 04-30-2013 01:19 PM

It would appear that you have corrupted partitions. Try the procedures given here.

saeedit 05-01-2013 08:50 AM

Hi cortman,

#dumpe2fs /dev/sdb1 | grep superblock
it does not work for me.
its output: dumpe2fs: Corrupt extent header while reading journal superblock


But, after few search, i found these two commands and my partition info recovered after trying them.

#fsck.ext4 -v /dev/sdb1
#e2fsck -b 32768 /dev/sdb5

Thanks dude.

cortman 05-01-2013 11:31 AM

Glad I was able to at least point you in the right direction. :)
Glad it's solved!


All times are GMT -5. The time now is 02:11 PM.