|
2011-01-02
, 01:03
|
Posts: 41 |
Thanked: 23 times |
Joined on Oct 2009
@ US
|
#2
|
|
2011-01-02
, 01:25
|
|
Posts: 69 |
Thanked: 10 times |
Joined on Sep 2010
@ Spain
|
#3
|
|
2011-01-02
, 01:34
|
Posts: 327 |
Thanked: 383 times |
Joined on Aug 2010
@ alex , egypt
|
#4
|
|
2011-01-02
, 01:42
|
|
Posts: 69 |
Thanked: 10 times |
Joined on Sep 2010
@ Spain
|
#5
|
|
2011-01-02
, 01:56
|
Posts: 327 |
Thanked: 383 times |
Joined on Aug 2010
@ alex , egypt
|
#6
|
|
2011-01-06
, 23:40
|
|
Posts: 69 |
Thanked: 10 times |
Joined on Sep 2010
@ Spain
|
#7
|
$ sudo umount /dev/sdb1 $ sudo umount /dev/sdb2
fsck -v /dev/sdb1
fsck -v /dev/sdb2
The Following User Says Thank You to sub7 For This Useful Post: | ||
|
2011-01-06
, 23:45
|
|
Posts: 69 |
Thanked: 10 times |
Joined on Sep 2010
@ Spain
|
#8
|
I had this problem a few days ago. In theory, the solution is to run fsck on /dev/mmcblk0p2. But the problem is fourfold: there is no way to unmount this partition while the N900 is running, there is no option to run force fsck at boot, one cannot access this partition via USB prior to booting, and this partition is mounted very early on because it contains many of the "optified" packages.
Here's the official bug report, which IMO was somewhat prematurely marked WONTFIX:
https://bugs.maemo.org/show_bug.cgi?id=7572
There are a couple of solutions posted at the bottom of the bug report. I would avoid the experimental one requiring the power kernel, which is detailed here.
I tried the power kernel method but it ran fsck on a mounted partition, resulting in insulting messages in the log ("some bonehead is running fsck on a mounted partition"), causing further damage, and forcing me to reflash my device. Perhaps the bootmenu.sh method mentioned in the bug report will work.
I wish I could be more helpful.
|
2011-01-13
, 12:31
|
|
Posts: 69 |
Thanked: 10 times |
Joined on Sep 2010
@ Spain
|
#9
|
|
2011-01-13
, 13:02
|
|
Posts: 2,142 |
Thanked: 2,054 times |
Joined on Dec 2006
@ Sicily
|
#10
|
Because i have as 200 broken links on /.thumbnails/cropped/ and I can not remove it that I get this error.
even with rm -f is not possible.
Also when I do a backup with backupmenu i get this errors.
Anyone know how they can correct the NFS file handle error in some way?
Last edited by sub7; 2011-01-02 at 00:34.