Unable to mount NTFS drive

[Nicodem]

I have two NTFS drives with files backup, both are 12TB, same hardware and formatted in same way (my assumption, I do not really remember..) under Windows 11. 

One of them is visible in Unraid, second - no, only FORMAT option visible in unassigned devices.

 

How I can mount it? Need to copy large amount of data and I do not have in this network Windows machine that can see this and copy via network. Wanted to copy via USB enclosure.

How I can mount it?

 

Tried with two different UNRAID based systems - all can see other disk, this one is not visible.

Windows 11 open this flawlessly.

[ChatNoir]

Mounting drives outside of the Array and Pools is handled by the Unassigned Devices plugin.

You should look for assistance on it's support thread :

 

https://forums.unraid.net/topic/92462-unassigned-devices-managing-disk-drives-and-remote-shares-outside-of-the-unraid-array/#comments

 

[Nicodem]

Tried there - no answer. How I can install NTFS-3G directly on Unraid, without use of unassigned devices?

Unassigned do not see this drive which is 100% usable under Windows.

[SimonF]

1 minute ago, Nicodem said:

Tried there - no answer. How I can install NTFS-3G directly on Unraid, without use of unassigned devices?

Unassigned do not see this drive which is 100% usable under Windows.

Do you have any errors related to the disk in the log?

[Nicodem]

Log:

Dec  1 08:44:16 QNAP453D kernel: usb-storage 2-1:1.0: USB Mass Storage device detected
Dec  1 08:44:16 QNAP453D kernel: scsi host1: usb-storage 2-1:1.0
Dec  1 08:44:17 QNAP453D kernel: scsi 1:0:0:0: Direct-Access     WD       Elements 25A3    1030 PQ: 0 ANSI: 6
Dec  1 08:44:17 QNAP453D kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Dec  1 08:44:17 QNAP453D kernel: sd 1:0:0:0: [sdb] Spinning up disk...
Dec  1 08:44:37 QNAP453D kernel: ...................ready
Dec  1 08:44:37 QNAP453D kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Dec  1 08:44:37 QNAP453D kernel: sd 1:0:0:0: [sdb] 23437705216 512-byte logical blocks: (12.0 TB/10.9 TiB)
Dec  1 08:44:37 QNAP453D kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Dec  1 08:44:37 QNAP453D kernel: sd 1:0:0:0: [sdb] Write Protect is off
Dec  1 08:44:37 QNAP453D kernel: sd 1:0:0:0: [sdb] Mode Sense: 47 00 10 08
Dec  1 08:44:37 QNAP453D kernel: sd 1:0:0:0: [sdb] No Caching mode page found
Dec  1 08:44:37 QNAP453D kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
Dec  1 08:44:37 QNAP453D kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Dec  1 08:44:41 QNAP453D  emhttpd: WD_Elements_25A3_35504B394C393345-0:0 (sdb) 512 23437705216
Dec  1 08:44:41 QNAP453D  emhttpd: read SMART /dev/sdb

 

And in unassigned what I see:

[JorgeB]

Post the output of

blkid

and

fdisk -l /dev/sdb

 

[Nicodem]

This time (after reboot) its sdf so:

blkid:

/dev/sdf: PTTYPE="PMBR"

 

FDISK:

Disk /dev/sdf: 10.91 TiB, 12000105070592 bytes, 23437705216 sectors
Disk model: Elements 25A3   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start        End    Sectors Size Id Type
/dev/sdf1           1 4294967295 4294967295   2T ee GPT

Partition 1 does not start on physical sector boundary.

 

 

[JorgeB]

It's missing the NTFS type signature, that's why UD doesn't recognize the file system and there's no mount option, you can see if it mounts manually by specifying the fs:
 

mkdir /x
mount -t ntfs /dev/sdf1 /x

 

[Nicodem]

No, it does not mount.

Any way to add this signature (dont know why windows didnt done it...) WITHOUT loosing data?

 

[JorgeB]

2 minutes ago, Nicodem said:

Any way to add this signature (dont know why windows didnt done it...) WITHOUT loosing data?

Nope, only way I know would be to re-format the disk.

[Nicodem]

stupid windows thing... 

So I have to now mount it to some windows machine and copy over LAN. Can do but its way more complicated and slower in my case then just copy from USB directly.

 

Thanks for help. F U Microsoft..

 

[Knights21]

On 12/1/2022 at 12:40 PM, JorgeB said:

It's missing the NTFS type signature, that's why UD doesn't recognize the file system and there's no mount option, you can see if it mounts manually by specifying the fs:
 

mkdir /x
mount -t ntfs /dev/sdf1 /x

 

I'm having the same problem with a 1TB NTFS USB drive, Uassisgned devices see the disk but not the FS and only offers 'pool' as an option. 

Mount reported:

The disk contains an unclean file system (0, 0).
The file system wasn't safely closed on Windows. Fixing.
ntfs-3g-mount: failed to access mountpoint /x: No such file or directory
This worked (\x):

mount -t ntfs /dev/sdh \x

Now I can enter cd \x and run ls to see the contents at the command line.

I found 'X' in \root, just need a nice dual window file manager now to make movements easy.

Edited August 16, 2023 by Knights21