Post Reply

Internal Memory issue

OP matrixzone

17th January 2014, 08:06 AM   |  #1  
matrixzone's Avatar
OP Senior Member
Thanks Meter: 785
 
2,498 posts
Join Date:Joined: Mar 2012
More
I am getting the following error while checking the internal memory of my phone. Any help will be highly appreciated


C:\android-sdk-windows\sdk\platform-tools>adb shell
~ # cat etc/fstab
cat etc/fstab
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw
~ # e2fsck -fv dev/block/mmcblk0p01
e2fsck -fv dev/block/mmcblk0p01
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open dev/block/mmcblk0p01
Possibly non-existent device?
~ # e2fsck -fv dev/block/mmcblk0p
e2fsck -fv dev/block/mmcblk0p
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open dev/block/mmcblk0p
Possibly non-existent device?
~ # cat etc/fstab
cat etc/fstab
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw
~ # e2fsck /dev/block/mmcblk0p2
e2fsck /dev/block/mmcblk0p2
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
2

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>
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes