Reply
Thread Tools
Posts: 863 | Thanked: 213 times | Joined on Feb 2012 @ Goa
#1
my filesystem became Read-only so i used these commands below but its not solving the problem

/home/user # umount /home/user/MyDocs
/home/user # fsck -a /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offsetriginal/backup)
65:01/00
Not automatically fixing this.
/opt/preenv/usr/palm/applications/com.ea.app.nfshp.pre.na/published/models
Contains a free cluster (3246758). Assuming EOF.
/opt/preenv/usr/palm/applications/com.ea.app.nfshp.pre.na/published/objects
Contains a free cluster (3249777). Assuming EOF.
/opt/preenv/usr/palm/applications/com.ea.app.nfshp.pre.na/published/scenes
Contains a free cluster (3249784). Assuming EOF.
/opt/preenv/usr/palm/applications/com.ea.app.nfshp.pre.na/published/sounds
Contains a free cluster (3249788). Assuming EOF.
Unable to create unique name
/home/user #
 
stickymick's Avatar
Posts: 1,079 | Thanked: 1,019 times | Joined on Mar 2010
#2
At a guess, from things I've read in the past, I'd say you've got a corrupt file somewhere and from the info you've supplied I'd gather it's something to do with preenv or nfshp.
I'd guess there was a problem writing/saving a file and the file system has reverted to read only to prevent further damage.

In the past I've had the same problem when transfering media files, images, mp3s or videos. Just a case of identifying the culprit and manualy deleting it. Not too sure how you'd go about that in your case, but I guess you've now got a few pointers.
__________________
Mick has just punched the cr@p out of the "Unlike" button on the Official Nokia Facebook Page.
 
Posts: 177 | Thanked: 152 times | Joined on Oct 2011
#3
Try this
root
umount /dev/mmcblk0p1
fsck.vfat -r /dev/mmcblk0p1
mount /dev/mmcblk0p1 /home/user/MyDocs
 
Posts: 863 | Thanked: 213 times | Joined on Feb 2012 @ Goa
#4
boot loop and now i gave it to repair
 
Ken-Young's Avatar
Posts: 387 | Thanked: 1,700 times | Joined on Feb 2010 @ Cambridge, MA, USA
#5
Originally Posted by seanmcken View Post
boot loop and now i gave it to repair
Reflashing the phone is really quite easy. There's no need to send it for repair if you've just got a reboot loop.
 

The Following User Says Thank You to Ken-Young For This Useful Post:
Posts: 863 | Thanked: 213 times | Joined on Feb 2012 @ Goa
#6
i mean i dont hav pc cuz i lost in some crazy experiment so i gave to my friend to repair.
 

The Following User Says Thank You to seanmcken For This Useful Post:
azad1top's Avatar
Posts: 84 | Thanked: 11 times | Joined on Aug 2012 @ iran
#7
hi all

plz help

I have the same problems



Code:
BusyBox v1.20.2 (Debian 1.20.2power5+thumb0) built-in shell (ash) 
Enter 'help' for a list of built-in commands. 

~ $ sudo gainroot 
Root shell enabled 


BusyBox v1.20.2 (Debian 1.20.2power5+thumb0) built-in shell (ash) 
Enter 'help' for a list of built-in commands. 

/home/user # umount /dev/mmcblk0p1 
/home/user # fsck -af /dev/mmcblk0p1 
fsck 1.41.3.maemo0 (12-Oct-2008) 
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN 
There are differences between boot sector and its backup. 
Differences: (offset:original/backup) 
65:01/00 
Not automatically fixing this. 
/.recorder 
Contains a free cluster (153391). Assuming EOF. 
/.prismicwm/db/local.db 
Contains a free cluster (95616). Assuming EOF. 
Unable to create unique name 
/home/user #

ama.....


Code:
BusyBox v1.20.2 (Debian 1.20.2power5+thumb0) built-in shell (ash) 
Enter 'help' for a list of built-in commands. 

~ $ r 
In The Name Of God 
use ( about-k ) for know more about this app. 


BusyBox v1.20.2 (Debian 1.20.2power5+thumb0) built-in shell (ash) 
Enter 'help' for a list of built-in commands. 

Nokia-N900:~# umount /dev/mmcblk0p1 
umount: can't umount /home/user/MyDocs: Device or resource busy 
Nokia-N900:~# fsck -a /dev/mmcblk0p1 
fsck 1.41.3.maemo0 (12-Oct-2008) 
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN 
/dev/mmcblk0p1: 2645 files, 77150/344085 clusters 
Nokia-N900:~# mount /dev/mmcblk0p1 
mount: mounting /dev/mmcblk0p1 on /home/user/MyDocs failed: Device or resource busy 
Nokia-N900:~# exit 
~ $ 
~ $ 
~ $ 
~ $ root 


BusyBox v1.20.2 (Debian 1.20.2power5+thumb0) built-in shell (ash) 
Enter 'help' for a list of built-in commands. 

Nokia-N900:~# umount /dev/mmcblk0p1 
umount: can't umount /home/user/MyDocs: Device or resource busy 
Nokia-N900:~# fsck.vfat -r /dev/mmcblk0p1 
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN 
/dev/mmcblk0p1: 2645 files, 77150/344085 clusters 
Nokia-N900:~# mount /dev/mmcblk0p1 /home/user/MyDocs 
mount: mounting /dev/mmcblk0p1 on /home/user/MyDocs failed: Device or resource busy 
Nokia-N900:~#
my filesystem Read-only

not solving the problem

plz help!
 
Posts: 115 | Thanked: 49 times | Joined on Sep 2012
#8
Originally Posted by seanmcken View Post
my filesystem became Read-only so i used these commands below but its not solving the problem

/home/user # umount /home/user/MyDocs
/home/user # fsck -a /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offsetriginal/backup)
65:01/00
Not automatically fixing this.
/opt/preenv/usr/palm/applications/com.ea.app.nfshp.pre.na/published/models
Contains a free cluster (3246758). Assuming EOF.
/opt/preenv/usr/palm/applications/com.ea.app.nfshp.pre.na/published/objects
Contains a free cluster (3249777). Assuming EOF.
/opt/preenv/usr/palm/applications/com.ea.app.nfshp.pre.na/published/scenes
Contains a free cluster (3249784). Assuming EOF.
/opt/preenv/usr/palm/applications/com.ea.app.nfshp.pre.na/published/sounds
Contains a free cluster (3249788). Assuming EOF.
Unable to create unique name
/home/user #
when i face same error i connect my n900 with windows7 pc and click on scan and recover for disc error and bad sector.after scaning,every thing is working fine
__________________
need mods for a dead F O R U Mpm me if you can help
¢яαzяу ค๒๏ยt ʎɹzɐɹɔ ƬΣXƬ
 

The Following User Says Thank You to sunyakram For This Useful Post:
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#9
Use the -r option to do the repair manually like you tried
Code:
sudo gainroot
umount /dev/mmcblk0p1
fsck -r /dev/mmcblk0p1
But make sure the umount command really unmounts the device. Did you notice that you got an error during the first try...
May be try rebooting to get the state of the MyDocs partition reset to some sane state. Then try the fsck process again.
 
azad1top's Avatar
Posts: 84 | Thanked: 11 times | Joined on Aug 2012 @ iran
#10
Originally Posted by michaaa62 View Post
Use the -r option to do the repair manually like you tried
Code:
sudo gainroot
umount /dev/mmcblk0p1
fsck -r /dev/mmcblk0p1
But make sure the umount command really unmounts the device. Did you notice that you got an error during the first try...
May be try rebooting to get the state of the MyDocs partition reset to some sane state. Then try the fsck process again.
Thank you michaaa62

2O 20
 
Reply


 
Forum Jump


All times are GMT. The time now is 17:55.