Re: Problem with FSCK
 

Did you connect the N900 to the PC while switched on in Maemo system and did you export the device in 'mass storage mode'?
The problem is the setup of Maemo itself, because it does not care for file system corruption and will always just create these folders in MyDocs, even if the partition is not available. This causes testdisk to produce this error, because of the exact same names of the folders.

Please install 'BackupMenu', it is capable to export the device and all of the other partitions to your PC without Maemo running, and thus not interacting with the export in any way.

Re: Problem with FSCK
 

yes, it was connected while maemo was running, and in mass storage mode.

many thanks, I will try this.


Edit ---

many thanks for the help, again. my problem is not solved yet, but I keep trying.

so, when BackupMenu starts, the following messages are written:

"UDev started.
1
2
Error with: cp /lib/libacl.so.1 /tmp/disk/lib/ Code:1
cp: cannot stat '/lib/libacl.so.1': No such file or directory
Press any key to continue...
Error with: cp /lib/libattr.so.1.1.0 /tmp/disk/lib/ Code:1
cp: cannot stat '/lib/libattr.so.1.1.0': No such file or directory
Press any key to continue...
3.
4"

then it loads, and works fine. I press "w" to mass storage mode, then connect it to my ubuntu laptop. it sees (I mean I can see it in nautilus) the "ot a boot d" named phone (before using fsck and accidental deletion the phone name was "n900") with its 27 Gig storage, and the other 2 Gig partition (I assume the "/home" folder). so I ran testdisk and it does find partitions with the "Intel" partition table, but the listed partitions (after deeper search) are only the "ot a boot d", "Linux" (this is the 2 Gig partition), "Linux swap", and another "Linux" partition which also too small to be the lost partition. I'm a bit stucked now. my only idea is to run GParted on my ubuntu laptop to gain access to the n900's partitions...

(I don't know if I'm right, but I read that BackupMenu can do backup only from my rootFS and optFS, but not from my MyDocs folder which contains the .documents. and I don't know how to backup my lost partitions with it)

I ran Photorec too before installing BackupMenu, so it went through the process while maemo was running, and with Non-partitioned table (I connected it to my ubuntu laptop, so the recup folders were saved to the laptop - to the Desktop), and it does restored many lost files from the device, but not all of them I think, and I do no want to sort them one by one... (: (it is a nightmare...) and some of the .doc files can not be opened with OpenOffice (for example)...

Re: Problem with FSCK
 

The errors while starting BackupMenu are minor! You might in the long run just install libacl1 and libattr1 to get rid of the errors.

Yes Photorec is some kind of an application :eek: Only for professionals i think. Testdisk is the better in terms of usability of the two.
Nevertheless it might be your only chance to use it, because of the weird automatic behavior to create the dot.folders in My Docs, this might just have overwritten the descriptors(pointers) to the files and folders, you had in the folders with the same names before.

The 'ot a boot d'-named partition should be your desired 'MyDocs' partition. All kind of problems might get the label or name of a partition to get screwed.

You might want to create a clone copy of MyDocs, aka. 'ot a boot d', on your laptopPlease adapt the path to the partition and to the folder, where you want to store the image, to your needs.
You might use Photorec or Testdisk on the image as well and could just reformat the MyDocs partition and carry on.

Re: Problem with FSCK
 

hmm... I don't know... I wish it would be my desired MyDocs folder...

I tried to make a clone copy and the following happened:

1. in the /dev/disk/by-label folder I only see a "@ot\x20a\x20boot\x20d" named file, which is unaccessable.

2. so I typed "dd if=/media/'ot a boot d' of=/home/my_user_name/MyDocs.dd.img bs=4096. the following message emerged: ""dd: /media/ot a boot d" reading: this is a directory
0+0 read record
0+0 wrote record
0 bit (0B) copied, 0.000507397 sec, 0.0 kB/sec"

another thing is that in ubuntu's /media folder I can see the 2 Gig partition which also have a MyDocs folder in its /user folder... (now I connect my phone using BackupMenu)

and one more thing: in ubuntu's /media folder I can see the /ot a boot d folder which has .documents, .videos, .sounds etc. folders (empty of course) and a /MyDocs folder

Re: Problem with FSCK
 

The default setup in Maemo for the MyDocs folder in /home/user is not very robust against misuse. In the not so rare case of severe file system corruption, where the device is not mounted at all, the folder will get used by the Maemo system instead of the large partition, which should be mounted there.This is the right place for this folder, this should be empty by default, but i would make sure it really is empty...
Thats strange, you should only see the content of the MyDocs partition. What is inside the MyDocs folder?Do not mount the device, try to get an image of the raw device, therefore from the /dev/disk/by-label/@ot\x20a\x20boot\x20d device.

Re: Problem with FSCK
 

Hey michaaaa,

Is there any help that you can render me over this issue??

refer to this post: http://talk.maemo.org/showpost.php?p...postcount=4121

thanks in advance.

Re: Problem with FSCK
 

1. The file system is "ext2" and not "ext3" - run fsck without assuming anything as long as you are not certain you want to kick a thing in place.
2. The files are <bo>not</bo> deleted, just moved to a directory $HOME/.Trash

The Nokia File Manager does not allow you to see the .Trash directory, but mount it on another Linux device and tick of "Hidden fiiles" and pop comes the weasel. Well, of course you may do:
Use the Terminal:
> cd $HOME/.Tras*
> ls -al | more
> rm <whatever file you really want to remove/delete>

Re: Problem with FSCK
 

Ok: "dd" is "device dump" that starts on block 0, sector 0 and produce a file - that in this case is unusable for anything. The command will work even if the file system has gone completely belly-up, and allow someone competent to fix it.

Use the correct command, "tape archiving" may sound strange but here every file is copied, symbolic and hard links are managed. You may also compress the tar archive as it is produced.

A special use of "dd" is "dd if=/dev/zero of /dev/hd..."
This will wipe out everything, and place zero where there used to be data. Call it a quick format of a mounted device.

Re: Problem with FSCK
 

Read the system documentation!
Backup will back-up contacts, appointments, your settings and bookmark and a list of installed applications. This is held in a system directory, but can be linked to "MyDocs". This is NOT Windows. You should backup to your SD memory.
Windows does not have user protection and does not have any "x" bit to indicate that a file is "executable" - e.g. as a shell script. So, if you use FAT32 on the /rootfs - there is no way anything here can start executing, so this is used where really nothing should be executable, so just keep the executable in a directory that is linked into the FAT32 file system.
There is no way you can check, verify and repair the FAT.
Please, read the documentation, and shoud you happen to know Windows and Microsoft, please understand that this was made to fix most of the problems that Microsoft skipped, and require more than a Sunday School course to muck around with. Scrap the wizards and try to understand because here things can be explained and they make sense - curses and wizards gets you nowhere.

Re: Problem with FSCK
 

In linux, and justmemory referred to Ubuntu, you might mount this image of a device as a loopback device and use it.

The application is indeed called BackupMenu, you might want to search the forum for it. It is a fine tool, that nearly is a recovery console.
nourgomaa had a broken emmc, which he also reported in his blog some time ago.