First try to reboot after the successful fsck to see if things went really successful.

Maemo always creates some of the mentioned folders anyway, because Nokia in their .... wisdom never
thought about the possibility, that vfat is a sensible file-system to been mishandled by PCs. Those other folders are created by MacOS.

I rebooted - no apparent effect.

Last night I looked a the creation dates of the files on a Windows computer (N900 tethered in mass storage mode) and found that these files where created while I was sitting in a train to the airport reading the latest news on the N9 via 3G. I am not aware of any event that could have triggered the creation of a new file system (or the loss of my old MyDocs). However, it happened.

Now I discovered further strange behaviour: when tried to restore some old data from an OVI suite backup (what I made only early April, blame me) the data was neither complete nor stored where it was. Instead, a "dev" file within MyDocs was created that now contains some data including a futher .sounds and .documents file.

At least the Easy Debian image was there and I had to move it to MyDocs in order the have it in proper place

When I then started Easy Debian hoping it would work I received the following notice:

EZ-CHROOT ERROR

Mount failure!

/home/user/MyDocs/debian-m5-v3d.img.ext2.lzma failed to mount on loop0

mount: mounting /dev/loop0 on /.debian failed: invalid argument

Meanwhile I come accustomed to the fact that part of my files are lost. So, now it is all about recreating a reliable device.

Did you try testdisk in both modes, like Fat Undelete hidden in Advanced and Analyse?

How do I activate these modes? To answer your question: no, I did not, because I do not know how.

BTW, battery drain is tremendous now like operating hours is now maybe less than 6 hours whereas it used to be more than 30 hours (with almost no use, off course)

Testdisk is an data recovery tool fittingly from the recovery-tools package, you will get it here http://maemo.org/downloads/product/M...ecovery-tools/ or by May be you have to enable extras-testing and/or extras-devel repositories.
You will find a short walkthrough here http://talk.maemo.org/showpost.php?p...3&postcount=46

I have used testdisk because I found your instructions in some other thread two days ago. However, I do not know how to use testdisk in both modes, like Fat Undelete hidden in Advanced and Analyse. With advanced, I found a file that I have intentionally deleted myself the other day.

I could not see any of my "old" files. I suspect that is because there is a "new" data structure ("new" MyDocs) so I can not get to my "old" MyDocs in a regular manner.

Considering the overall strange behaviour of what used to be my favourite tool I am now contemplating reflashing the device. However, I learned that this does not neccessarily leads to a clean MyDocs.

Did you make a new filesystem after you lost access to the files?
Let testdisk analyse your device with quickly, then hit enter and choose 'Deeper Search', afterwards let it show you the files and folders on the first partition with 'p' . Good luck!

At the end of a day, well, i think there are different series of the N900 around. There are rocksolid devices, where it really is difficult to get your file-system borked, and there is, ahem, yours and some others.... It is the same for overclocking.

To be fair: I can not blame the N900 for any true failure. Maybe it was a bit immature when it was released. I am now using it way more than a year oftentimes 2 or 3 hours a day incl. Citrix under Easy Debian etc.

And I poked allot around with it - only semi competent (if at all). The kids are tossing it around and do many thinks I later do not really understand. And I never lost anything - until Tuesday.

My old iMac was much wore in that respect (terribly unreliable) and any Windows machine I owned or used is the same. Compared to Apple or Microsoft, the N900 is really reliable (that is why I did so little backups :-( )

This makes me think of what I expect from a pocket device (not calling it a phone): I enjoy the freedom to play around on every level and I am willing to take the risk to thereby brake something. I see the drawback (some inconsistency included) but prefer it over a closed device like otherwise elegant iPhone.

To continue off topic: that is the reason I put some hopes on Meego.

Back to the topic: I run Testdisk as described and learned that the disk is to small because it is smaller than some 35000000 TB. And some of the Linux partitions can not be recovered. I assume that the relates to now disfunctional Easy Debian, which is not a problem.

I will now try some forensic tool and will report.

Hi All,

i am new to this site. I am unable to access internal memory on N900. It shows 'Memory is corrupted'. the phone is not even detected when i connect to PC vis USB using mass storage mode.

Well I did a blunder by executing KILLALL in X-terminal yesterday. all my personal stuff that I had saved in my internal 32 gb is lost.

Experts - do you think my internal memory is corrupted due to KILLALL command. is there anyway to have it back with my personal stuff.

Thanks in advance for your support.

Tushar.

You need rootsh from extras repository installed to get this working.
If you want to retrieve the data on the phone, check and repair the file-system
This might be sufficient to get your data back, but depending of the actual corruption additional steps might be necessary.