Active Topics

 


Reply
Thread Tools
Posts: 915 | Thanked: 3,209 times | Joined on Jan 2011 @ Germany
#11
Did fsck produce any error messages? If so, which ones?

(question to others: Does Maemo's fsck produce any error messages at all?)
 

The Following User Says Thank You to sulu For This Useful Post:
Posts: 23 | Thanked: 9 times | Joined on Sep 2010
#12
Originally Posted by michaaa62 View Post
Testdisk and Photorec (do not use it , until you really have to!) are fine tools, but they are quite time consuming. First try to get the partition back to default.
Do you get any error messages (copy and paste them), if you try to fsck the partition?

Please no conky, images or vague description, just shell output.

Code:
#fsck /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Logical sector size is zero.
 
Posts: 124 | Thanked: 105 times | Joined on Jul 2010
#13
I assume you've rebooted your phone??
What is the error you're getting trying to mount?
Is it mounted already? (run mount to find out)
 

The Following 2 Users Say Thank You to nman For This Useful Post:
Posts: 23 | Thanked: 9 times | Joined on Sep 2010
#14
Originally Posted by michaaa62 View Post
Testdisk and Photorec (do not use it , until you really have to!) are fine tools, but they are quite time consuming. First try to get the partition back to default.
Do you get any error messages (copy and paste them), if you try to fsck the partition?

Please no conky, images or vague description, just shell output.
Code:
#umount /dev/mmcblk0p1
umount: cannot umount /dev/mmcblk0p1: Invalid argument
Code:
#mount /dev/mmcblk0p1 /home/user/MyDocs
mount: mounting /dev/user/MyDocs failed: Invalid argument
And of course I did reboot my phone...
 
Posts: 23 | Thanked: 9 times | Joined on Sep 2010
#15
Okay... I flashed my phone (not the 27GB part). Now I can connect the phone to my pc again, but Windows says the volume is damaged. I'm trying now to recover my files with a Windows tool. But no files found so far...
Thanks anyway for your help.
 
misterc's Avatar
Posts: 1,625 | Thanked: 998 times | Joined on Aug 2010
#16
Originally Posted by lpdv74 View Post
Code:
#umount /dev/mmcblk0p1
umount: cannot umount /dev/mmcblk0p1: Invalid argument
Code:
#mount /dev/mmcblk0p1 /home/user/MyDocs
mount: mounting /dev/user/MyDocs failed: Invalid argument
And of course I did reboot my phone...
apologies not having gotten back to you earlier
was busy sending an important e-mail
if it is not mounted because of an error it can't be unmounted of course.

BEFORE screwing it up even more w/ m@ke$$h!t LostDOS, try following (after disconnecting it from your PC)

Code:
root
fsck /dev/mmcblk0p1
and post the output of that command.
(you should be able to open this thread with the microb browser on your N900)
 
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#17
#fsck /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Logical sector size is zero.
This error makes recovery of files nearly impossible, because even testdisk might need some kind of file system information for the data it should try to get from the partition.

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 2 Users Say Thank You to michaaa62 For This Useful Post:
Posts: 23 | Thanked: 9 times | Joined on Sep 2010
#18
Originally Posted by michaaa62 View Post
This error makes recovery of files nearly impossible, because even testdisk might need some kind of file system information for the data it should try to get from the partition.

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.
I've one really important file on it... How can I make a clone copy of mmcblk0p1? I'm running out of time for today, I will be back tomorrow...
 
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#19
You might try to get that file with testdisk faster than with a clone copy of the whole device. Here is some basic info on testdisk usage: http://talk.maemo.org/showpost.php?p...8&postcount=16
 

The Following User Says Thank You to michaaa62 For This Useful Post:
Posts: 23 | Thanked: 9 times | Joined on Sep 2010
#20
YESSSS!!! I've everything back, thnx to Testdisk and the help of you all.
Thank you very much!!!
 
Reply


 
Forum Jump


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