![]() |
2011-09-19
, 06:07
|
|
Posts: 62 |
Thanked: 16 times |
Joined on Jul 2010
@ Pune, India
|
#2
|
![]() |
2011-09-19
, 06:58
|
Posts: 2,102 |
Thanked: 1,937 times |
Joined on Sep 2008
@ Berlin, Germany
|
#3
|
sudo gainroot dumpe2fs /dev/mmcblk0p2 | grep -i superblock
[1|root@Nokia-N900|~]dumpe2fs /dev/mmcblk0p2 | grep -i superblock
dumpe2fs 1.41.3.maemo0 (12-Oct-2008)
Primary superblock at 0, Group descriptors at 1-1
Backup superblock at 32768, Group descriptors at 32769-32769
Backup superblock at 98304, Group descriptors at 98305-98305
Backup superblock at 163840, Group descriptors at 163841-163841
Backup superblock at 229376, Group descriptors at 229377-229377
Backup superblock at 294912, Group descriptors at 294913-294913
Backup superblock at 819200, Group descriptors at 819201-819201
Backup superblock at 884736, Group descriptors at 884737-884737
fsck -b 294912 -af /dev/mmcblk0p2
![]() |
2011-09-19
, 12:34
|
Posts: 80 |
Thanked: 1 time |
Joined on Aug 2011
@ Egypt
|
#4
|
Try fsck with a backup superblock, that might give you a fair chance.
To list the backups of the superblock created during initial make of the file system do:
You will receive a table containing your superblocks. They are different than my example:Code:sudo gainroot dumpe2fs /dev/mmcblk0p2 | grep -i superblock
Then pick up one of the superblocks and hand it with the -b option to fsck. From my example it would beHope it get you further on that problematic partition.Code:fsck -b 294912 -af /dev/mmcblk0p2
![]() |
2011-09-19
, 15:19
|
Posts: 2,102 |
Thanked: 1,937 times |
Joined on Sep 2008
@ Berlin, Germany
|
#5
|
sudo gainroot sfdisk -l > partitiontable.txt
![]() |
2011-09-20
, 21:29
|
Posts: 80 |
Thanked: 1 time |
Joined on Aug 2011
@ Egypt
|
#6
|
I want to encourage you to not write down the error messages or to describe them, but copy and paste them please, because these error messages are meaningful!
If you are somehow unable to paste things here please redirect the output of the commands to a file and attach it here. The redirection writes nothing to the screen, so every command seems to die silently, but it is writing the output to a file.
Example:The first command works as usual, the second one creates the file partitiontable.txt and redirects the output of the 'sfdisk -l' command to it.Code:sudo gainroot sfdisk -l > partitiontable.txt
Please attach the partitiontable.txt from the above example here!
![]() |
2011-09-21
, 06:56
|
Posts: 2,102 |
Thanked: 1,937 times |
Joined on Sep 2008
@ Berlin, Germany
|
#7
|
sudo gainroot fsck -b 294912 -af /dev/mmcblk0p2
![]() |
2011-09-21
, 11:44
|
Posts: 80 |
Thanked: 1 time |
Joined on Aug 2011
@ Egypt
|
#8
|
Now try to runto check the file system with one of the backup superblocks.Code:sudo gainroot fsck -b 294912 -af /dev/mmcblk0p2
![]() |
2011-09-21
, 12:24
|
Posts: 2,102 |
Thanked: 1,937 times |
Joined on Sep 2008
@ Berlin, Germany
|
#9
|
![]() |
2011-09-21
, 20:21
|
Posts: 80 |
Thanked: 1 time |
Joined on Aug 2011
@ Egypt
|
#10
|
Sorry to ask again!
Could you please attach the partition table as in post #5 above?
Also try to format the partition again, IF no data is on that partition, that would be destroyed.
I posted many threads in this forum for two months explaining that i've problem with my EMMC, However i could see the original size of it "27GB MyDocs and 5GB Applicable memory"
I think i know where's the problem now
After i applied this thread on wiki :http://wiki.maemo.org/Repartitioning..._compatible.29
I entered this command line and i got this error "mounting /dev/mmcblk0p2 on /mnt failed: Invalid argument"
I tried this "mount -t ext3 /dev/mmcblk0p2 /mnt"
Gave me "Invalid argument"
I tried this "fsck -af /dev/mmcblk0p2"
and it gave me "unable to set superlock flags on /dev/mmcblk0p2"
I saw this error while restoring backupmenu image too.
Any help?