Hi,

Don't really know what happened, I decided to reboot my N900 yesterday and after the reboot background was just black. Everything else is ok and works fine, but can't change wallpapers, it doesn't give any info why it can't change wallpaper.

With dmesg I found these error messages coming up, every time I try to browse photos or change backgrounds:

[ 4000.711730] EXT3-fs error (device mmcblk1p2): ext3_add_entry: bad entry in directory #24727: directory entry across blocks - offset=0, inode=4294967295, rec_len=65536, name_len=255
[ 4000.807769] EXT3-fs error (device mmcblk1p2): ext3_add_entry: bad entry in directory #24727: directory entry across blocks - offset=0, inode=4294967295, rec_len=65536, name_len=255
[ 4000.900451] EXT3-fs error (device mmcblk1p2): ext3_add_entry: bad entry in directory #24727: directory entry across blocks - offset=0, inode=4294967295, rec_len=65536, name_len=255


Any suggestions what to do?


Regards,
Jarkko

That does look rather stuffed. Non-N900 specific suggestion would be to open a terminal, unmount the filesystem, run fsck on it. I see no reason in principle why that wouldn't work here too.

unable to umount filesystem busy



Not te easiest... I wish we had a kernel with an initramfs for such cases. Or a decent bootloader.

hm won't be easy to unmount /home (= mmcblk1p2)

according to lsof, tons of stuff is open on that partition, by various system apps like tracker, modest and so on. maybe if you killed all these apps you could umount /home and run fsck, but i'm not feeling adventurous enough to actually try that now
also, you'd probably need a user with a home directory on another partition.

WARNING: The following is untested and could seriously stuff up your N900.

You could edit /etc/init.d/rcS to do a fsck (with autorepair) before mounting /home, then reboot.

welcome to club...
Look this bug and you can vote for this:
https://bugs.maemo.org/show_bug.cgi?id=7572

> You could edit /etc/init.d/rcS to do a fsck (with autorepair) before mounting /home, then reboot.

If you make any error in file you will have to reflush device, like me...

And this bug: https://bugs.maemo.org/show_bug.cgi?id=7571

Maybe try mount -o remount,ro /home to remount it read-only? You should be able to fsck then... (this will only work if no files are open for writing)

After making a backup and transferring everything important to PC I forced umount to /home and runned fsck to /dev/mmcblk1p2 after that (yeah, I rebooted the device after fsck..) the N900 was bricked (as I expected..). It kept telling me that it can't send or receive SMS messages and when I received SMS messages they disappeared after reading them and returning to desktop. Oh, and contacts was empty too and there were some other 'small' problems too.

After that I flashed my N900 and everything is OK (for) now...

mikhmv: Have you managed to force fsck check on boot or do you know if anyone has done it?

I would like to check my file system(s). As normal user n900 doesn't recognize fsck command but as sudo gainroot it gives fsck version number. Exactly what command i have to write to get it just check my file systems/partitions.

How do i now what partitions i have? fdisk doesnt work an neither fstab.