Reply
Thread Tools
Posts: 4 | Thanked: 0 times | Joined on Jan 2011
#51
Originally Posted by michaaa62 View Post
You are right very unclear
Code:
dd if=/dev/mmcblk0p1 of=/dev/mmcblk0p1 bs=512 count=1 skip=6
is the command to write the copy of the superblock back on the device
Code:
fsck -af /dev/mmcblk0p1
checks the filesystem afterwards. It might be necessary to apply some more force to the fsck command that would be
Code:
fsck -r /dev/mmcblk0p1
After you receive no more errors from fsck, you could mount the partition
Code:
mount /dev/mmcblk0p1 /home/user/MyDocs
This will be the final moment of truth, if all went well.
my n900, it not accept fsck... wat can i do now?
 
jedi's Avatar
Posts: 1,411 | Thanked: 1,330 times | Joined on Jan 2010 @ Tatooine
#52
Originally Posted by tranthao View Post
my n900, it not accept fsck... wat can i do now?
Copy/paste the output here...
__________________
May the source be with you.
 
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#53
It really is difficult to pick up, what you are trying to achieve, from those one liners you are posting.
Please try to do what jedi asked and also describe the error you were facing first.
 

The Following User Says Thank You to michaaa62 For This Useful Post:
Posts: 130 | Thanked: 24 times | Joined on Jan 2011
#54
i had the same problem abt a week ago..

http://talk.maemo.org/showthread.php...862#post979862

its all thankx to michaaa62

Last edited by hhmah; 2011-04-06 at 15:12.
 
Posts: 2 | Thanked: 0 times | Joined on May 2011
#55
Originally Posted by Temporal View Post
Ok, easier now:

1)
sudo gainroot

2)
umount /dev/mmcblk0p1

3)
fsck.vfat -f /dev/mmcblk0p1

What does each one of this report?
well i have been following this thread since i have the same problem but when i run umount/dev/mmcblk0p1 is says not found what should i do
 
anim1's Avatar
Posts: 146 | Thanked: 40 times | Joined on Jun 2010 @ philly
#56
Originally Posted by michaaa62 View Post
Yes it does.
The partition for MyDocs is not mounted, this might be often triggered by a corrupted file system due to not being safely removed from a PC.
Please try
Code:
sudo gainroot
fsck -af /dev/mmcblk0p1
If no errors occur, try to mount it
Code:
mount /dev/mmcblk0p1 /home/user/MyDocs
every time i try this, it works but when i reboot, i have to do it all over again. thanx by the way.
 
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#57
Originally Posted by anim1 View Post
every time i try this, it works but when i reboot, i have to do it all over again. thanx by the way.
Don't reboot
Well the error must be happening while closing some applications or during shutdown.
Do you use file sharing on the N900, which is reported to sometimes corrupt the file system, or do you enable mass storage mode, while charging it via USB connected to a PC?
 

The Following User Says Thank You to michaaa62 For This Useful Post:
anim1's Avatar
Posts: 146 | Thanked: 40 times | Joined on Jun 2010 @ philly
#58
Originally Posted by michaaa62 View Post
Don't reboot
Well the error must be happening while closing some applications or during shutdown.
Do you use file sharing on the N900, which is reported to sometimes corrupt the file system, or do you enable mass storage mode, while charging it via USB connected to a PC?
cant do anything because even with the temporary fix the memory still says corrupted. N900 folder appears in file manager but it is usless because i cant format or save anything to it.
 
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#59
First backup everything valuable on the partition to some external media, like external microSD or your PC.
And then apply a fresh file system to it with
Code:
sudo gainroot
umount /dev/mmcblk0p1
mkfs.vfat /dev/mmcblk0p1
mount /dev/mmcblk0p1 /home/user/MyDocs
 

The Following User Says Thank You to michaaa62 For This Useful Post:
Posts: 167 | Thanked: 204 times | Joined on Jul 2010
#60
One other semi-random thought... the only time I've had serious microSD card corruption was when I was first playing with kernel-power and experimented with the "starving" settings.

They appeared to work fine for most normal phone use and I was on the verge of replacing my microSD when I thought to check "what have I done recently?". Returning to the "ideal" voltages solved the problem and I haven't had any problems since - so, if you're doing any major undervolting, try changing that before assuming your SD card or filesystem is shot.
 

The Following User Says Thank You to magick777 For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 21:36.