How do I mount my External HDD with filesystem type errors?

Posted by Snuggie on Ask Ubuntu See other posts from Ask Ubuntu or by Snuggie
Published on 2013-11-08T02:33:34Z Indexed on 2013/11/08 4:19 UTC
Read the original article Hit count: 271

Filed under:
|

I am a relatively new Ubuntu user and I am having some difficulty mounting my external 2TB HDD. When I first installed Linux my external HDD was working just fine, however, it has stopped working and I have a lot of important files on there that I need.

Before my HDD would automatically mount and no worries. Now, however, it doesn't automatically mount and when I try to manually mount it I keep running into filesystem type errors that I can't seem to get past.

Below are images that depict my step by step process of how I am trying to mount my HDD along with the errors I am receiving. If anybody has any idea what I am doing wrong or how to correct the issue I would greatly appreciate it.

Step 1) Ensure the computer recognizes my external HDD.

pj@PJ:~$ dmesg

...

[ 5790.367910] scsi 7:0:0:0: Direct-Access WD My Passport 0748 1022 PQ: 0 ANSI: 6

[ 5790.368278] scsi 7:0:0:1: Enclosure WD SES Device 1022 PQ: 0 ANSI: 6

[ 5790.370122] sd 7:0:0:0: Attached scsi generic sg2 type 0

[ 5790.370310] ses 7:0:0:1: Attached Enclosure device

[ 5790.370462] ses 7:0:0:1: Attached scsi generic sg3 type 13

[ 5792.971601] sd 7:0:0:0: [sdb] 3906963456 512-byte logical blocks: (2.00 TB/1.81 TiB)

[ 5792.972148] sd 7:0:0:0: [sdb] Write Protect is off

[ 5792.972162] sd 7:0:0:0: [sdb] Mode Sense: 47 00 10 08

[ 5792.972591] sd 7:0:0:0: [sdb] No Caching mode page found

[ 5792.972605] sd 7:0:0:0: [sdb] Assuming drive cache: write through

[ 5792.975235] sd 7:0:0:0: [sdb] No Caching mode page found

[ 5792.975249] sd 7:0:0:0: [sdb] Assuming drive cache: write through

[ 5792.987504] sdb: sdb1

[ 5792.988900] sd 7:0:0:0: [sdb] No Caching mode page found

[ 5792.988911] sd 7:0:0:0: [sdb] Assuming drive cache: write through

[ 5792.988920] sd 7:0:0:0: [sdb] Attached SCSI disk

Step 2) Check if it mounted properly (it does not)

pj@PJ:~$ df -ah

Filesystem Size Used Avail Use% Mounted on

/dev/sda1 682G 3.9G 644G 1% /

proc 0 0 0 - /proc

sysfs 0 0 0 - /sys

none 0 0 0 - /sys/fs/fuse/connections

none 0 0 0 - /sys/kernel/debug

none 0 0 0 - /sys/kernel/security

udev 2.9G 4.0K 2.9G 1% /dev

devpts 0 0 0 - /dev/pts

tmpfs 1.2G 928K 1.2G 1% /run

none 5.0M 0 5.0M 0% /run/lock

none 2.9G 156K 2.9G 1% /run/shm

gvfs-fuse-daemon 0 0 0 - /home/pj/.gvfs

Step 3) Try mounting manually using NTFS and VFAT (both as SDB and SDB1)

pj@PJ:~$ sudo mount /dev/sdb /media/Passport/

NTFS signature is missing.

Failed to mount '/dev/sdb': Invalid argument

The device '/dev/sdb' doesn't seem to have a valid NTFS.

Maybe the wrong device is used? Or the whole disk instead of a

partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

pj@PJ:~$ sudo mount /dev/sdb1 /media/Passport/

NTFS signature is missing.

Failed to mount '/dev/sdb1': Invalid argument

The device '/dev/sdb1' doesn't seem to have a valid NTFS.

Maybe the wrong device is used? Or the whole disk instead of a

partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

pj@PJ:~$ sudo mount -t ntfs /dev/sdb /media/Passport/

NTFS signature is missing.

Failed to mount '/dev/sdb': Invalid argument

The device '/dev/sdb' doesn't seem to have a valid NTFS.

Maybe the wrong device is used? Or the whole disk instead of a

partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

pj@PJ:~$ sudo mount -t vfat /dev/sdb /media/Passport/

mount: wrong fs type, bad option, bad superblock on /dev/sdb,

   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try

   dmesg | tail  or so

pj@PJ:~$ sudo mount -t ntfs /dev/sdb1 /media/Passport/

NTFS signature is missing.

Failed to mount '/dev/sdb1': Invalid argument

The device '/dev/sdb1' doesn't seem to have a valid NTFS.

Maybe the wrong device is used? Or the whole disk instead of a

partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

pj@PJ:~$ sudo mount -t vfat /dev/sdb1 /media/Passport/

mount: wrong fs type, bad option, bad superblock on /dev/sdb1,

   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try

   dmesg | tail  or so

© Ask Ubuntu or respective owner

Related posts about mount

  • 12.10 update breaks NFS mount

    as seen on Ask Ubuntu - Search for 'Ask Ubuntu'
    I've just upgraded to the latest 12.10 beta. Rebooted twice. The problem is with the NFS folders not mounting, here's a verbose log. # mount -v myserver:/nfs_shared/tools /tools/ mount: no type was given - I'll assume nfs because of the colon mount.nfs: timeout set for Mon Oct 1 11:42:28 2012 mount… >>> More

  • Mount SMB / AFP 13.10

    as seen on Ask Ubuntu - Search for 'Ask Ubuntu'
    I cannot seem to get Ubuntu to mount a mac share via SMB or AFP. I've tried the following... AFP: apt-get install afpfs-ng-utils mount_afp afp://user:password@localip/share /mnt/share Error given: "Could not connect, never got a reponse to getstatus, Connection timed out". Which is odd as I can… >>> More

  • Mount Return Code for CIFS mount

    as seen on Server Fault - Search for 'Server Fault'
    When I run the following command (as root or via sudo) from a bash script I get an exit status (or return code in mount man page parlance) of 1: mount -v -t cifs //nasbox/volume /tmpdir/ --verbose -o credentials=/root/cifsid & /tmp/mylog It outputs the following into the myflog file: parsing… >>> More

  • Disable raid member check upon mount to mount damaged nvidia raid1 member

    as seen on Server Fault - Search for 'Server Fault'
    Hi, A friend of mine destroyed his Nvidia RAID1 array somehow and in trying to fix it, he ended up with a non-working array. Because of the RAID metadata, the actual disk data was stored at an offset from the beginning. I was able to identify this offset with dd and a hexeditor and then I used losetup… >>> More

  • Network shares do not mount.

    as seen on Super User - Search for 'Super User'
    My network shares were mounting fine yesterday.. suddenly they are not. They were mounting fine for the last two weeks or however long since I added them. When I run sudo mount -a I get the following error: topsy@monolyth:~$ sudo mount -a mount error(12): Cannot allocate memory Refer to the mount… >>> More

Related posts about hard-drive