Reply
Thread Tools
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#21
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
 

The Following 4 Users Say Thank You to michaaa62 For This Useful Post:
Temporal's Avatar
Posts: 323 | Thanked: 189 times | Joined on Oct 2010 @ Brazil
#22
Originally Posted by devildriven View Post
Comes back with...

/home/user # fsck -af /dev/mmcnlk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
fsck.ext2: No such file or directory while trying to open /dev/mmcnlk0p1
/dev/mmcnlk0p1:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

Should i now try...

mount /dev/mmcblk0p1 /home/user/MyDocs



Thanks so much for the help guys, i hope the end is in sight and i can get this fixed!
Ok, easier now:

1)
sudo gainroot

2)
umount /dev/mmcblk0p1

3)
fsck.vfat -f /dev/mmcblk0p1

What does each one of this report?
__________________
Love and Goodness are not a property. Are not a franchising. They are present in each one of us, and must be cultivated with KNOWLEDGE.
 

The Following User Says Thank You to Temporal For This Useful Post:
Temporal's Avatar
Posts: 323 | Thanked: 189 times | Joined on Oct 2010 @ Brazil
#23
If the last one is giving you too muck questions, you can try what michaaa62 said insted of my number 3:

fsck.vfat -af /dev/mmcblk0p1

this will automatically try to fix without the need to you read anything (mostly).
__________________
Love and Goodness are not a property. Are not a franchising. They are present in each one of us, and must be cultivated with KNOWLEDGE.
 

The Following User Says Thank You to Temporal For This Useful Post:
Temporal's Avatar
Posts: 323 | Thanked: 189 times | Joined on Oct 2010 @ Brazil
#24
auch! This is big... Was it working ok up to the time before you plugging it to the PC? What did happen then?
__________________
Love and Goodness are not a property. Are not a franchising. They are present in each one of us, and must be cultivated with KNOWLEDGE.
 
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#25
If you have anything really, really important on the partition you should make a clone copy of the device /dev/mmcblk0p1 to some external storage. From a linux system, either Live-CD or installed system with at least 28 GB free storage available, it would be as root
Code:
mount /dev/SomePartition /mnt
dd if=/dev/YourN900'sFirstPartition of=/mnt/SomeClearName.dd_image bs=4096
If things are saved, or you still have the files already copied before, this would write a copy of the superblock of a FAT32 filesystem only back
Code:
dd if=/dev/mmcblk0p1 of=/dev/mmcblk0p1 bs=512 count=1 skip=6
Note: If that is failing [check with the above fsck code] there is no way back but to rewrite the image your before took, or to knowingly wipe the partition and format it.
 

The Following 4 Users Say Thank You to michaaa62 For This Useful Post:
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#26
Heres what i got...

/home/user # umount /dev/mmcblk0p1
umount: cannot umount /dev/mmcblk0p1: Invalid argument
/home/user # fsck.vfat -f /dev/mmcblk0p1
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Cluster size is zero.
/home/user #
This actually means your partition superblock is wiped. After assuring yourself that is safe to proceed, do as i told you to copy the backup of the superblock to the device. There might be the necessarity to apply the -r option to fsck to really repair the filesystem later on.
EDIT: Nothing lost yet!
 

The Following 2 Users Say Thank You to michaaa62 For This Useful Post:
Temporal's Avatar
Posts: 323 | Thanked: 189 times | Joined on Oct 2010 @ Brazil
#27
Well, that it usually means that the main sector got corrupted, and that still there's a hope that the backup is still alive, but I have never tried that.

You should do what michaaaa62 just said. Make a image copy, of all your internal drive, (first command) then copy the backup cluster (6) to the main (0) (second commnad) and hope for the best |:/

@Michaaa62:
Are you sure that you are copying the sec 6 to the 0 with this command? Shouldn't I try to copy to the sec 6 somewhere else and then try to copy it to sec 0? I don't know much, but looks like you are copying the 6 to the 6 again, am I wrong?

EDIT:I was wrong. I got it!
__________________
Love and Goodness are not a property. Are not a franchising. They are present in each one of us, and must be cultivated with KNOWLEDGE.

Last edited by Temporal; 2011-02-01 at 14:29.
 

The Following User Says Thank You to Temporal For This Useful Post:
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#28
Originally Posted by Temporal View Post
Well, that it usually means that the main sector got corrupted, and that still there's a hope that the backup is still alive, but I have never tried that.

You should do what michaaaa62 just said. Make a image copy, of all your internal drive, (first command) then copy the backup cluster (6) to the main (0) (second commnad) and hope for the best |:/

@Michaaa62:
Are you sure that you are copying the sec 6 to the 0 with this command? Shouldn't I try to copy to the sec 6 somewhere else and then try to copy it to sec 0? I don't know much, but looks like you are copying the 6 to the 6 again, am I wrong?
of=/dev/mmcblk0p1 does start at zero, writing one block [count=1] to it after skipping 6, actually writes the seventh block, back to the device. Also please note that in windows they count from one, while in linux, they count from zero. Please don't ask me why, may be some patent trolls on Linus' shoulder, i don't know.
 

The Following 2 Users Say Thank You to michaaa62 For This Useful Post:
Temporal's Avatar
Posts: 323 | Thanked: 189 times | Joined on Oct 2010 @ Brazil
#29
Originally Posted by devildriven View Post
If there are any amendments to the code you posted would you be so kind as to post them?

Could you really spoon feed me what the final code i should be running is as to avoid messing up my device further please?

Once again i am very thankful for all of you help.
You should be perfectly fine with the code michaaa62 did:

Code:
dd if=/dev/mmcblk0p1 of=/dev/mmcblk0p1 bs=512 count=1 skip=6

the -r option is for after, to the fsck that will be needed after this.
__________________
Love and Goodness are not a property. Are not a franchising. They are present in each one of us, and must be cultivated with KNOWLEDGE.

Last edited by Temporal; 2011-02-01 at 14:32.
 

The Following User Says Thank You to Temporal For This Useful Post:
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#30
Originally Posted by devildriven View Post
Thanks for all your help, i really appreciate it!

So i should run?...

dd if=/dev/mmcblk0p1 of=/dev/mmcblk0p1 bs=512 count=1 skip=6

Is that the full code? Where would the -r option come in? After i have run this? Thanks again, hopefully its going to be fixable this way!
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.
 

The Following 5 Users Say Thank You to michaaa62 For This Useful Post:
Reply

Thread Tools

 
Forum Jump


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