[help] MyDocs partion not seen by file manager - maemo.org

Active Topics

List of well performing apps on Leste (34)
to Maemo 7 / Leste by biketool - 1 hr, 48 mins ago
Maemo repository (5)
to Community by dredlok706 - 1 day, 20 hrs ago
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 1 day, 23 hrs ago
Porting apps to Leste (41)
to Maemo 7 / Leste by Arno_11 - 2 days, 17 hrs ago
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 4 days, 5 hrs ago
more...

Thread Tools

c4rl05	2012-10-15 , 17:43
Posts: 91 \| Thanked: 11 times \| Joined on Apr 2012	#1

i recently connected my n900 to a cmputer which i think it had viruses ( a window machine of course) because after i connected it, MyDocs partion didnt showed up with a normal mass storage icon instead it had a normal file icon, after i removed it i didnt looked it up on file manager ( i was busy doing a certain work), and i took it to another pc which had an antivirus ( the massage of Norton came up but i didnt bother i just cancelled them), but when i selected mass storage only my MMC showed up and MyDocs partition didnt showed up, i unpluged it from a pc and went to file manager but only MMC was there and not myDocs, i rebooted the phone but the same problem cant find it on neither file manager nor on filebox on mmc can seen, i dont know whats is the problem, when i viewed on xterminal i can see myDocs directory but it contains nothing.
Can somebody help me to bring myDocs partition back with its data

Quote & Reply |

c4rl05	2012-10-15 , 19:21
Posts: 91 \| Thanked: 11 times \| Joined on Apr 2012	#2

this is the output i get when i try to mount or umount it, via xterminal

~ $ sudo umount /dev/mmcblk0p1
umount: can't umount /dev/mmcblk0p1: Invalid argument
~ $ sudo mount /dev/mmcblk0p1 /home/user/MyDocs
mount: mounting /dev/mmcblk0p1 on /home/user/MyDocs failed: Invalid argument
~ $

Quote & Reply |

saponga	2012-10-15 , 19:47
Posts: 432 \| Thanked: 917 times \| Joined on Jun 2011	#3

Originally Posted by c4rl05

this is the output i get when i try to mount or umount it, via xterminal

~ $ sudo umount /dev/mmcblk0p1
umount: can't umount /dev/mmcblk0p1: Invalid argument
~ $ sudo mount /dev/mmcblk0p1 /home/user/MyDocs
mount: mounting /dev/mmcblk0p1 on /home/user/MyDocs failed: Invalid argument
~ $

try

Code:

sudo mount -t vfat /dev/mmcblk0p1 /home/user/MyDocs

what do you get with

Code:

sudo fdisk -l

Quote & Reply |

c4rl05	2012-10-15 , 20:03
Posts: 91 \| Thanked: 11 times \| Joined on Apr 2012	#4

Originally Posted by saponga

try

Code:

sudo mount -t vfat /dev/mmcblk0p1 /home/user/MyDocs

i get:

Code:

 $ sudo mount -t vfat /dev/mmcblk0p1 /home/user/MyDocs
mount: mounting /dev/mmcblk0p1 on /home/user/MyDocs failed: Invalid argument

what do you get with
Code:
sudo fdisk -l

i get :

Code:

~ $ sudo fdisk -l

Disk /dev/mmcblk1: 8054 MB, 8054112256 bytes
4 heads, 16 sectors/track, 245792 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

        Device Boot      Start         End      Blocks  Id System
/dev/mmcblk1p1               1      245792     7865336   b Win95 FAT32

Disk /dev/mmcblk0: 32.0 GB, 32015122432 bytes
4 heads, 16 sectors/track, 977024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

        Device Boot      Start         End      Blocks  Id System
/dev/mmcblk0p1               2      884865    28315648   c Win95 FAT32 (LBA)
/dev/mmcblk0p2          884866      950401     2097152  83 Linux
/dev/mmcblk0p3          950402      974977      786432  82 Linux swap
~ $ 
~ $

Quote & Reply |

	pichlo	2012-10-15 , 20:36
	Posts: 6,453 \| Thanked: 20,983 times \| Joined on Sep 2012 @ UK	#5

So the partition is there but the file system is corrupt. It looks to me like a result of an unclean unmount. Try:

Code:

dosfsck /dev/mmcblk0p1

Another option is connect to a Windows PC and run checkdisk. I've read amazing stories on this forum of people with similar problems who fixed it by a simple checkdisk.

Quote & Reply |

The Following User Says Thank You to pichlo For This Useful Post:
c4rl05

saponga	2012-10-15 , 20:59
Posts: 432 \| Thanked: 917 times \| Joined on Jun 2011	#6

If fsck don't work, check that thread out http://talk.maemo.org/showthread.php?t=82049 and maybe you could get your data back.
Good lucky !

Quote & Reply |

The Following User Says Thank You to saponga For This Useful Post:
c4rl05

	knuthf	2012-10-15 , 22:56
	Posts: 74 \| Thanked: 42 times \| Joined on Apr 2011 @ Oslo - around	#7

Install "TestDisk" - this does the above and more.
The usual virus will try to change the MBR, but "MyDocs" runs "ext2" that is fully journalled. Load the journal, and scan the entire filesystem.

Drop Windows - this does not know about the file system, it can easily destroy it.
If the MBR has been modified, loading the previous value is the only way forward You loose the last second or two... The typical error is that the file system tye is unknown. List the types - look for "ext2" - which should be used.
If you just get hold of the journal master block, TestDisk will restore your entire "MyDocs" - also the ._Trashes directory. Use your PC to learn aout Linux / Unix commands.