Reply
Thread Tools
sub7's Avatar
Posts: 69 | Thanked: 10 times | Joined on Sep 2010 @ Spain
#1
Hi have hundreds of NFS file handle file errors, there any way to fix this?.
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.
 
Posts: 41 | Thanked: 23 times | Joined on Oct 2009 @ US
#2
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.

Last edited by mdl; 2011-01-02 at 01:10.
 
sub7's Avatar
Posts: 69 | Thanked: 10 times | Joined on Sep 2010 @ Spain
#3
Thanks man, my problem at first was this, http://forums.internettablettalk.com...ad.php?t=52360 but it turns out I have several broken links that can not be removed by the NFS file handle error.

I will try the kernel-power solution if I damaged the file system I have a backup done.
 
Posts: 327 | Thanked: 383 times | Joined on Aug 2010 @ alex , egypt
#4
if u installed nitdroid 0.0.9 on memory card and connected ur mobile to linux pc u will have full access to the 32 giga internal storage
 
sub7's Avatar
Posts: 69 | Thanked: 10 times | Joined on Sep 2010 @ Spain
#5
mmm that is a great idea, could be possibl repair maemo file system using a linux pc too, using this way?
 
Posts: 327 | Thanked: 383 times | Joined on Aug 2010 @ alex , egypt
#6
yes u have full access to whole memory
 
sub7's Avatar
Posts: 69 | Thanked: 10 times | Joined on Sep 2010 @ Spain
#7
Then I installed nitdroid specifically to fix these errors hahaha.

And it worked, I will explain a bit as I did in case anyone serves.

For those who have the famous Stale NFS File handle errors. Means that the file system is damaged and you have to fix that. For this you use a tool called fsck, but it can not repair a drive that is mounted, so can not be repaired from maemo.

To fix this you have to install nitdroid 0.0.9, after having installed ubuntu on a computer.

You must restart the phone with nitdroid and then connect the phone to the computer to detect it and on the phone you must enable mass storage.

after that, ubuntu automatically mount the partitions of the phone.

Now we have to disassemble to use fsck.

open a terminal and write.
Code:
$ sudo umount /dev/sdb1
$ sudo umount /dev/sdb2
then write

Code:
fsck -v /dev/sdb1
Here there were no errors
Code:
fsck -v /dev/sdb2
In my case here fsck found many errors that were repaired.

If you do not want to answer questions and that everything is done automatically write

fsck -va
This repairs the errors automatically.
or

fsck -vy
This answers all questions with a YES.

I do not know which is better, if someone with more knowledge please tell me what is wrong to correct it.

after that, you must disable the mass storage in nitdroid and restart the phone to maemo to see if it went well.

Thanks to mido.fayad for the idea, now I could repair the errors that I went out with backupmenu to make backups.

If anyone knows an easier way, please tell me.

Last edited by sub7; 2011-01-06 at 23:43.
 

The Following User Says Thank You to sub7 For This Useful Post:
sub7's Avatar
Posts: 69 | Thanked: 10 times | Joined on Sep 2010 @ Spain
#8
Originally Posted by mdl View Post
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.
I try to repair the system using this method, but not work for me.
 
sub7's Avatar
Posts: 69 | Thanked: 10 times | Joined on Sep 2010 @ Spain
#9
WARNING!!!!!

don't use external fsck, if you don't know what are you are doing, because i totaly **** up my n900, doing fsck, because it change the file system ext3 to ext2 of my n900 ;( now is on nokia care i hope they can repair it.
 
debernardis's Avatar
Posts: 2,142 | Thanked: 2,054 times | Joined on Dec 2006 @ Sicily
#10
maybe fsck.ext3 was more appropriate? But then even if ext3 -> ext2 why did it become unreadable?
 
Reply


 
Forum Jump


All times are GMT. The time now is 20:13.