[SOLVED] Unknown memory format. FAT32 dir status starts with a bad cluster - maemo.org

K9999 | # 1 | 2012-05-19, 09:36 | Report

Hi all,,
posting this thread came after 4 days of trying different methods (except re-flashing).
I ran into a corrupted memory after unplugging the USB from the office PC. now the internal memory is not shown in filebox or manager. the files exist after checking them with TestDisk.
I've tried few codes of mounting and this is what I get:

PHP Code:


			
BusyBox v1.20.0 (Debian 1.20.0power1) built-in shell (ash) 

Enter 'help' for a list of built-in commands. 



~ $ root 





BusyBox v1.20.0 (Debian 1.20.0power1) built-in shell (ash) 

Enter 'help' for a list of built-in commands. 



Nokia-N900:~# umount /dev/mmcblk0p1 

umount: can't umount /dev/mmcblk0p1: Invalid argument 

Nokia-N900:~# fsck -a /dev/mmcblk0p1 

fsck 1.41.3.maemo0 (12-Oct-2008) 

dosfsck 2.11, 12 Mar 2005, FAT32, LFN 

There are differences between boot sector and its backup. 

Differences: (offset:original/backup) 

65:01/00 

Copying backup to original 

Cluster 5 out of range (251658240 > 442378). Setting to EOF. 

/ 

Contains a free cluster (2). Assuming EOF. 

FAT32 root dir starts with a bad cluster! 

Nokia-N900:~#

the memory format is unknown,, I can't browse it from PC or phone and I'm not willing to re-flash until I copy my stuff 1st,, if it's the only way.

Any idea guys?

Thanx in advance,

Last edited by K9999; 2012-05-23 at 15:26.

anthonie | # 2 | 2012-05-19, 10:05 | Report

Has your partition been unmounted correctly, or not? The sequence of he commands you pasted suggests not. If that' s the case, I' d try first:

Code:

Nokia-N900:~# umount-f /dev/mmcblk0p1

Then run fsck again.

michaaa62 | # 3 | 2012-05-19, 12:02 | Report

What does sfdisk think about the memory card?

Code:

sudo gainroot
sfdisk -l

Do you have a backup of the data?
If yes, just reassign a fresh new file system

Code:

mkfs.vfat -n MyDocs /dev/mmcblk0p1

If no, try the -af option for fsck first, then try -r option, or try to get as much information from fsck as possible by using the -nv option

Code:

fsck -af /dev/mmcblk0p1
fsck -r /dev/mmcblk0p1
fsck -n -v /dev/mmcblk0p1

Please give the full error messages here for further debugging.

K9999 | # 4 | 2012-05-19, 14:08 | Report

Originally Posted by anthonie View Post

Has your partition been unmounted correctly, or not? The sequence of he commands you pasted suggests not. If that' s the case, I' d try first:

Code:

Nokia-N900:~# umount-f /dev/mmcblk0p1

Then run fsck again.

it produces the same error

Code:

Nokia-N900:~# umount -f /dev/mmcblk0p1
umount: can't forcibly umount /dev/mmcblk0p1: Invalid argument
Nokia-N900:~#

Originally Posted by michaaa62 View Post

What does sfdisk think about the memory card?

Code:

sudo gainroot
sfdisk -l

Do you have a backup of the data?
If yes, just reassign a fresh new file system

Code:

mkfs.vfat -n MyDocs /dev/mmcblk0p1

If no, try the -af option for fsck first, then try -r option, or try to get as much information from fsck as possible by using the -nv option

Code:

fsck -af /dev/mmcblk0p1
fsck -r /dev/mmcblk0p1
fsck -n -v /dev/mmcblk0p1

Please give the full error messages here for further debugging.

Code:

/home/user # sfdisk -l

Disk /dev/mmcblk1: 60352 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/mmcblk1p1          0+  47999   48000-   1535999+   c  W95 FAT32 (LBA)
/dev/mmcblk1p2      48000   60351   12352     395264   83  Linux
/dev/mmcblk1p3          0       -       0          0    0  Empty
/dev/mmcblk1p4          0       -       0          0    0  Empty

Disk /dev/mmcblk0: 977024 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/mmcblk0p1          1  884864  884864   28315648    c  W95 FAT32 (LBA)
/dev/mmcblk0p2     884865  950400   65536    2097152   83  Linux
/dev/mmcblk0p3     950401  974976   24576     786432   82  Linux swap / Solaris
/dev/mmcblk0p4          0       -       0          0    0  Empty
/home/user #

Code:

/home/user # fsck -af /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offset:original/backup)
  65:01/00
Copying backup to original
Cluster 5 out of range (251658240 > 442378). Setting to EOF.
/
  Contains a free cluster (2). Assuming EOF.
FAT32 root dir starts with a bad cluster!
/home/user # 
/home/user # 
/home/user # fsck -r /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offset:original/backup)
  65:01/00
Copying backup to original
Cluster 5 out of range (251658240 > 442378). Setting to EOF.
/
  Contains a free cluster (2). Assuming EOF.
FAT32 root dir starts with a bad cluster!
/home/user # 
/home/user # fsck -n -v /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 2.11 (12 Mar 2005)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Checking we can access the last sector of the filesystem
There are differences between boot sector and its backup.
Differences: (offset:original/backup)
  65:01/00
Copying backup to original
Boot sector contents:
System ID "Maemo"
Media byte 0xf8 (hard disk)
       512 bytes per logical sector
     65536 bytes per cluster
       126 reserved sectors
First FAT starts at byte 64512 (sector 126)
         2 FATs, 32 bit entries
   1769984 bytes per FAT (= 3457 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 3604480 (sector 7040)
    442377 data clusters (28991619072 bytes)
32 sectors/track, 64 heads
         0 hidden sectors
  56631296 sectors total
Cluster 5 out of range (251658240 > 442378). Setting to EOF.
/
  Contains a free cluster (2). Assuming EOF.
FAT32 root dir starts with a bad cluster!
/home/user #

All codes end up with the same error. and yea I haven't created a backup yet. and that is to be created to...?

michaaa62 | # 5 | 2012-05-19, 15:00 | Report

Did you ever try windows to check the file system or to mount it. There are chances that windows has a different thinking about the MyDocs partition than Linux or Maemo.

You better try to get a backup from the partition with testdisk before you try any other step, just to be on the safe side. You might as well use some exterior hard disk to make an image of the partition

The Following User Says Thank You to michaaa62 For This Useful Post:
K9999

K9999 | # 6 | 2012-05-20, 08:05 | Report

damn it I came home last night with a disconnected internet,, gotta wait till Monday :\

hmmmm I haven't tried that with windows. will give it a shot after backing up my stuff. Urmm yea, about the backup, I haven't done it with TestDisk before. Does it do like what FTK imager does?

michaaa62 | # 7 | 2012-05-20, 08:13 | Report

No, testdisk is a data recovery tool.
Where no other tool might access the disk any more due to corruption to partition table or file system, it has a heuristic to assume patterns of file type as well as the data on the disk itself. Here is a short walkthrough of that, may be long, depends on the amount of data, procedure: http://talk.maemo.org/showpost.php?p...8&postcount=16

The Following User Says Thank You to michaaa62 For This Useful Post:
K9999

K9999 | # 8 | 2012-05-20, 08:20 | Report

Owhh,, I've gone through that post of yours before but dump of me I just thought it is used to retrieve the missing files or the deleted ones. didn't think of it as a backup method..
Thanx mate,, will do the backup and I think I'll just reassign a new fresh file system if windows trick didn't do the trick.

peterleinchen | # 9 | 2012-05-20, 14:41 | Report

Be sure to copy to another partition (as writing on same may screw it up more worse).
But I am afraid, that you will have use that method, as it seem your FAT table is corrupt. And also Windows will not detect that partition's FAT anymore.
But using testdisk to copy all detected files (maybe do not recover deleted, depending on what testdisk detects) to a SD card is a nice trick.
Let us know how it goes...

The Following User Says Thank You to peterleinchen For This Useful Post:
K9999

K9999 | # 10 | 2012-05-23, 15:23 | Report

Thanx guys,, thanx michaaa62.
I did backup everything using TestDisk,, and reassigned a fresh file system using the code

Originally Posted by michaaa62 View Post

just reassign a fresh new file system

Code:

mkfs.vfat -n MyDocs /dev/mmcblk0p1

it went well after the restart. I'm copying back my data into my N900 as I write this. thanx guys,,, Really.