Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    [help] MyDocs partion not seen by file manager

    Reply
    c4rl05 | # 1 | 2012-10-15, 17:43 | Report

    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

    Edit | Forward | Quote | Quick Reply | Thanks

     
    c4rl05 | # 2 | 2012-10-15, 19:21 | Report

    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
    ~ $

    Edit | Forward | Quote | Quick Reply | Thanks

     
    saponga | # 3 | 2012-10-15, 19:47 | Report

    Originally Posted by c4rl05 View Post
    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

    Edit | Forward | Quote | Quick Reply | Thanks

     
    c4rl05 | # 4 | 2012-10-15, 20:03 | Report

    Originally Posted by saponga View Post
    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
    Originally Posted by
    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
    ~ $ 
    ~ $

    Edit | Forward | Quote | Quick Reply | Thanks

     
    pichlo | # 5 | 2012-10-15, 20:36 | Report

    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.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to pichlo For This Useful Post:
    c4rl05

     
    saponga | # 6 | 2012-10-15, 20:59 | Report

    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 !

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to saponga For This Useful Post:
    c4rl05

     
    knuthf | # 7 | 2012-10-15, 22:56 | Report

    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. Good luck!

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to knuthf For This Useful Post:
    c4rl05

     
    c4rl05 | # 8 | 2012-10-16, 14:48 | Report

    THANKS GUYS, TEST DISK DID THE JOB, now i got MyDocs partion working with all my data.

    THANKS AGAIN

    Edit | Forward | Quote | Quick Reply | Thanks

     
vBulletin® Version 3.8.8
Normal Logout