Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Can't mount NTFS Drives

Featured Replies

I'm having difficulty mounting some NTFS drives in my server so that I can transfer the data to the array.

 

I have 2 NTFS drives phsyically installed in the server. In SNAP for UNRAID 5, it says "No FS" (no filesystem) for both of the drives. I've also tried manually mounting following the instructions on this page:

http://lime-technology.com/wiki/index.php/Copy_files_from_a_NTFS_drive

 

I've tried both the first method and the second method using the Read/Write driver that is supposed to work for drives over 2.2tb (formatted with GPD rather than MBR).

 

Can anyone advise me what I am doing wrong or how to troubleshoot this?

 

Many thanks!

  • 1 month later...

Bump, I'm more or less in the same boat. Really don't want to copy 10 or so TB over gigabit...

I've tried both the first method and the second method using the Read/Write driver that is supposed to work for drives over 2.2tb (formatted with GPD rather than MBR).

Do you mean that you have installed the ntfs-3g driver (as this is required for drives over 2.2TB)?  If so, perhaps you should give more details of the mount command that is failing.

... Really don't want to copy 10 or so TB over gigabit...

Why, if I may ask? From my (limited) experience it wouldn't be much, if at all, slower, even with parity disabled on unRAID.

... Really don't want to copy 10 or so TB over gigabit...

Why, if I may ask? From my (limited) experience it wouldn't be much, if at all, slower, even with parity disabled on unRAID.

 

Because it involves moving drives from machine to machine (already set in the server, just don't have the SATA connected), and going over the network requires me to use two machines when I could just use one. Plus I already brought parity online... and I only have a 60 GB cache SSD, so not sure if the mover will start moving the files over from cache when it's full or just freak the hell out and crash losing data (rather not do that... again, just had a 4x3TB RAID 5 failure, still recovering/sorting, thus my move to unRAID).

I agree with PKN, I had to move 18TB over from my NTFS drives to unRAID and was going to mount them in my rack mount and move the files over but I then found out Midnight Commander sometimes produced issues with unusual filenames so I decided to mount them in my USB docking station plugged into my macbook pro and transfer the data without parity over the wired network. It took me a week to do it, but Im glad I done it this way as I could decide which files went on which disk and it transferred each 3TB of data in around 20 hours. I just let each drive copy overnight and when it had finished copying all my NTFS data and I was happy with everything I added the parity drive. Yes its a risk as I transferred 3 drives then precleared them before adding them into the array, but I would do it again and now I have an offsite backup of my data I really have no major worries anymore.

I agree with PKN, I had to move 18TB over from my NTFS drives to unRAID and was going to mount them in my rack mount and move the files over but I then found out Midnight Commander sometimes produced issues with unusual filenames so I decided to mount them in my USB docking station plugged into my macbook pro and transfer the data without parity over the wired network. It took me a week to do it, but Im glad I done it this way as I could decide which files went on which disk and it transferred each 3TB of data in around 20 hours. I just let each drive copy overnight and when it had finished copying all my NTFS data and I was happy with everything I added the parity drive. Yes its a risk as I transferred 3 drives then precleared them before adding them into the array, but I would do it again and now I have an offsite backup of my data I really have no major worries anymore.

 

Well, given how much ntfs-3g isn't working, it looks like I will be doing this as well... only my usb dock doesn't like my 3TB drives, it shows them as uninitialized... connect directly to MB? works fine.

Yes I had this with my first docking station, in the end I brought a Startech USB2/ESATA dual dock with clone facility and its great, my friend also has the Startech USB3 version without the clone facility which also works with 3 and 4TB drives. Its paid for itself very fast.

Well, given how much ntfs-3g isn't working, it looks like I will be doing this as well... only my usb dock doesn't like my 3TB drives, it shows them as uninitialized... connect directly to MB? works fine.

I have never had any problems handling NTFS drives as long as I had ntfs-3g loaded.  However if there are issues on your motherboard and/or USB adaptor with handling large drives then that could explain your symptoms.

 

Are you sure you are specifying the correct partition when trying to mount the NTFS drive?  If it has been set up as an extended partition rather than a primary one it will be partition 5 rather than partition 1.

relevant excerpt from cat /proc/partition
   8      160 2930266584 sdk
   8      161     131072 sdk1
   8      162 2930134016 sdk2

 

I've tried 1, 2, and even 5, using this (modified for 1,2,5, none):

 

mount -r -t ntfs-3g -o umask=111,dmask=000 /dev/sdk2 /mnt/temp

 

Aaaand... just 'cause:

 

fdisk -l /dev/sdk

WARNING: GPT (GUID Partition Table) detected on '/dev/sdk'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdk: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdk1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

 

I'd really like to get this working because copy speeds are about 5-6 MB/s... which means this is going to take a long, long time...

That seems crazy low speeds, I get 20mb/s transferring files over my wi-fi network with a parity drive in place.

That seems crazy low speeds, I get 20mb/s transferring files over my wi-fi network with a parity drive in place.

 

Thus, the desire for on system cp... that said, if I'm not doing two copies (different target drives), Teracopy is reporting 10-13 MB/s... which is still way slower than the 30-40 I should see on system.

I've tried 1, 2, and even 5, using this (modified for 1,2,5, none):

 

mount -r -t ntfs-3g -o umask=111,dmask=000 /dev/sdk2 /mnt/temp

 

Looking at the fdisk output it looks as if the data should be on /dev/sdk2.  When I mount my drives I leave of all the options, so my mount command would be of the form

mount  /dev/sdk2 /mnt/temp

The format then gets auto-recognised and the drive mounted with default options.    Not sure why any of the other parameter options should cause an issue though.

 

The only other thing I can think of is that when the NTFS drive was partitioned/formatted it was not set up as a 'simple volume' as I know the others can compromise portability.  I always use that option, so not sure what the effect would be of selecting a different one.

Looking at the fdisk output it looks as if the data should be on /dev/sdk2.  When I mount my drives I leave of all the options, so my mount command would be of the form

mount  /dev/sdk2 /mnt/temp

The format then gets auto-recognised and the drive mounted with default options.    Not sure why any of the other parameter options should cause an issue though.

 

The only other thing I can think of is that when the NTFS drive was partitioned/formatted it was not set up as a 'simple volume' as I know the others can compromise portability.  I always use that option, so not sure what the effect would be of selecting a different one.

 

I will try this with the ntfs-3g since the drive is 3TB and -r for read only, as I do not want to accidentally delete something.

Well, still a no go with seeing the partition.

 

Plus I just realized this in the 5.x forum and I'm running 6.0 beta 6... so I may not be able to use any of the existing instructions.

Well, still a no go with seeing the partition.

 

Plus I just realized this in the 5.x forum and I'm running 6.0 beta 6... so I may not be able to use any of the existing instructions.

The only thing that should hange for 6b6 is the need to use a 64-bit version of the ntfs-3g driver.

Well, still a no go with seeing the partition.

 

Plus I just realized this in the 5.x forum and I'm running 6.0 beta 6... so I may not be able to use any of the existing instructions.

The only thing that should hange for 6b6 is the need to use a 64-bit version of the ntfs-3g driver.

 

Bingo, found a 64 bit driver... and I'm suddenly good to go... now if my preclear would just go faster I'd be up and running in no time at all.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.