Unable to mount NTSF drive

SKDMRK · 3 February 2017 12:01

Hello

I’ve had to get a new USB external harddrive, as the last one showed behavior of failing. I managed to copy most of the data over to the new one. But now I am unable to mount it. It does not automatically mount, not possible to browse it or manually add it in OSMC.

Have also tried through SSH with the root user, there are some errors given and messages indicating wrong or missing folders.

The device /dev/sda2 (2.7 TB) is the old one, while disk /dev/sda (4.6 TB) is the new one. I cannot make sense of this unfortunately.

Logs: http://paste.osmc.io/equzalucum

root@osmc:/# fdisk -l
...

Device         Boot  Start     End Sectors  Size Id Type
/dev/mmcblk0p1        2048  499711  497664  243M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      501760 3862527 3360768  1.6G 83 Linux

The backup GPT table is corrupt, but the primary appears OK, so that will be used.

**Disk /dev/sda: 4.6 TiB, 5000981078016 bytes, 1220942646 sectors**
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: F4835E06-3794-4BAE-A39B-C18EC56ED4F4

Device     Start       End   Sectors  Size Type
/dev/sda1      6     32773     32768  128M Microsoft reserved
/dev/sda2  33024 732566527 732533504  2.7T Microsoft basic data

Hope to get to mount the 4.6 TB one soon slight_smile:

These are the commands I’ve tried:

root@osmc:/# mount -t ntfs-3g /dev/sda /media/Media
NTFS signature is missing.
Failed to mount '/dev/sda': Invalid argument
The device '/dev/sda' 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?

root@osmc:/# mount -t ntfs-3g /dev/sdc1 /media/Media
ntfs-3g: Failed to access volume '/dev/sdc1': No such file or directory

root@osmc:/# su -c 'mount /dev/sda2 /media/Media'
Failed to read last sector (9767276542): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
   or it was not setup correctly (e.g. by not using mdadm --build ...),
   or a wrong device is tried to be mounted,
   or the partition table is corrupt (partition is smaller than NTFS),
   or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/sda2': Invalid argument
The device '/dev/sda2' 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?

root@osmc:/media# mount -t ntfs-3g /dev/sda2 /Media/Media
Failed to read last sector (9767276542): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
   or it was not setup correctly (e.g. by not using mdadm --build ...),
   or a wrong device is tried to be mounted,
   or the partition table is corrupt (partition is smaller than NTFS),
   or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/sda2': Invalid argument
The device '/dev/sda2' 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?

Also some other stuff I’ve tried to no avail. The disk was quick formatted with NTFS when I got it.

ActionA · 3 February 2017 12:19

sda1 and sda2 are different partitions on one drive. Your new drive should be sdb

SKDMRK · 3 February 2017 12:25

I tried by this error came

root@osmc:~# mount -t ntfs-3g /dev/sdb /media/Media
ntfs-3g: Failed to access volume '/dev/sdb': No such file or directory

ntfs-3g 2014.2.15AR.2 integrated FUSE 28 - Third Generation NTFS Driver
                Configuration type 7, XATTRS are on, POSIX ACLS are on

Copyright (C) 2005-2007 Yura Pakhuchiy
Copyright (C) 2006-2009 Szabolcs Szakacsits
Copyright (C) 2007-2014 Jean-Pierre Andre
Copyright (C) 2009 Erik Larsson

Usage:    ntfs-3g [-o option[,...]] <device|image_file> <mount_point>

Options:  ro (read-only mount), windows_names, uid=, gid=,
          umask=, fmask=, dmask=, streams_interface=.
          Please see the details in the manual (type: man ntfs-3g).

Example: ntfs-3g /dev/sda1 /mnt/windows

News, support and information:  http://tuxera.com

joakim_s · 3 February 2017 12:28

/dev/sdb is the hard drive, but you have to mount the partitions, /dev/sdb1 (sdb2,sdb3 depending on how many aprtitions there is)

SKDMRK · 3 February 2017 12:30

It is only one partition for the whole drive, this was the result:

root@osmc:~# mount -t ntfs-3g /dev/sdb1 /media/Media
ntfs-3g: Failed to access volume '/dev/sdb1': No such file or directory

ntfs-3g 2014.2.15AR.2 integrated FUSE 28 - Third Generation NTFS Driver
                Configuration type 7, XATTRS are on, POSIX ACLS are on

Copyright (C) 2005-2007 Yura Pakhuchiy
Copyright (C) 2006-2009 Szabolcs Szakacsits
Copyright (C) 2007-2014 Jean-Pierre Andre
Copyright (C) 2009 Erik Larsson

Usage:    ntfs-3g [-o option[,...]] <device|image_file> <mount_point>

Options:  ro (read-only mount), windows_names, uid=, gid=,
          umask=, fmask=, dmask=, streams_interface=.
          Please see the details in the manual (type: man ntfs-3g).

Example: ntfs-3g /dev/sda1 /mnt/windows

News, support and information:  http://tuxera.com

joakim_s · 3 February 2017 12:42

If both drives are connected to the Pi, you should have sda and sdb, if only one is connected it should be /dev/sda.

To list the partitions on the drive run this command:

fdisk -l /dev/sda

Alternative sdb if two harddisc’s are connected to Pi

ps. if you got some usb sticks connected to the pi they also take a have a “sd-device”

SKDMRK · 3 February 2017 12:43

Gave this result, also, only one drive connected

root@osmc:~# fdisk -l /dev/sda
The backup GPT table is corrupt, but the primary appears OK, so that will be used.

Disk /dev/sda: 4.6 TiB, 5000981078016 bytes, 1220942646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: F4835E06-3794-4BAE-A39B-C18EC56ED4F4

Device     Start       End   Sectors  Size Type
/dev/sda1      6     32773     32768  128M Microsoft reserved
/dev/sda2  33024 732566527 732533504  2.7T Microsoft basic data

SKDMRK · 3 February 2017 12:44

and when I tried sdb it gave me this

root@osmc:~# fdisk -l /dev/sdb
fdisk: cannot open /dev/sdb: No such file or directory

SKDMRK · 3 February 2017 12:46

thought I understood it now, but no luck

root@osmc:~# mount -t ntfs-3g /dev/sda2 /media/Media
Failed to read last sector (9767276542): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
   or it was not setup correctly (e.g. by not using mdadm --build ...),
   or a wrong device is tried to be mounted,
   or the partition table is corrupt (partition is smaller than NTFS),
   or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/sda2': Invalid argument
The device '/dev/sda2' 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?

joakim_s · 3 February 2017 12:49

Looking at it, you only got the 4gb drive connected, and there is just 2.7 Tb of partionioned space. I’m abit out of my league. How did you clone the old drive? Might been a problem with the partition data, so it isn’t recognised as a functioning NTFS or even partionioned as a dynamic drive

SKDMRK · 3 February 2017 12:53

The drive was quick formatted in windows with NTFS. Contents were copied over from old drive from a windows PC. It works perfectly when connected to Windows PC. When investigating this issue I did find that there might be problems if one has unmounted a drive without stopping it. This happened to this drive, as it could not be stopped. Quite normal in windows.

fzinken · 3 February 2017 13:59

Your GPT is corrupted which is really really bad.
My first question would be how are you Powering the drive?
After that is clarified my suggestion is to backup the data temporary and start fresh creating a single partition and formatting that

SKDMRK · 3 February 2017 14:02

The drive is powered by own supply, it’s a 3.5" 5 TB Seagate drive. As mentioned above, it works perfectly when connected to a Windows PC.

SKDMRK · 3 February 2017 23:44

Thank you fzinken, you were quite right, the GPT was corrupted and it is really bad.

sam_nazarko · 4 February 2017 00:40

Check cable, disc and caddy.

SKDMRK · 6 February 2017 08:38

So I got it resolved. The GPT was corrupt, I was unable to fix it. Luckily the broken hard drive gave up most of its data one more time. Now all is well.

Things I learned:

Name the replacement hard drive the same as the one it replaced, to keep all scraper info.
Do not try to clone the failed hard drive to new hard drive with a clone hardware machine. Most likely this which resulted in the GPT getting corrupt.
Always, even though windows cannot, stop the device and unmount in windows. reboot if necessary.