I haven't been able to transfer files to my N900 for a while so yesterday I did some Googling and found this post - http://talk.maemo.org/showthread.php?t=38837

So I followed the instructions and here I am, 24 hours later, watching a load of jibber jabber scrolling down the screen.

I don't mean it's technical when I say "jibber jabber". I mean they're strange looking characters. The bits I can make out are

"/QDATAM/"

and each one has a line like:

"FSCKXXXX.XXX"

The X has been incrementing since it started. It started at FSCK0001.001 and is now on FSCK0160.887.

It runs through 999 times before incrementing the number after "FSCK".

I hope that makes sense and could somebody advise me on whether this will actually finish.

Thanks in advance,

I'd be more inclined to use fsck.vfat or dosfsck and see how that works out instead.

/dev/mmcblk0p1 on /home/user/MyDocs type vfat

fsck on its own is for ext type file systems, hopefully you haven't killed your partition : )

I've run plain fsck before on my partitions and it always detected the partition type correctly.

Edit: Just did a successful fsck of the MicroSD with:

sudo gainroot
umount /media/mmc1
fsck /dev/mmcblk1p1

I have just tried this with 'fsck.vfat -a /dev/mmcblk0p1' and it's stuck in the same process as mentioned above

I don't have an MMC card. Only the in-built memory chip.

"umount: cannot unount /media/mmc1: invalid argument"

Try this:

sudo gainroot
umount /home/user/MyDocs
fsck /dev/mmcblk0p1

That's what I originally tried, with -a parameter though. Do you think removing -a may solve this problem? Reason I ask is that I've just used the -f option and it's doing things it didn't do before and I don't want to cancel this to try your suggestion otherwise.

Thanks,

I don't see why -a should make a difference...

Then I've already tried your suggestion and it takes over 24 hours to fix the file system.