Hi I'm new to unRAID and new to the forum, I'm just beginning to explore the possibilities of unRAID and it's very exciting! However just encountering a few small bugs that I'm not sure how to get past. 

 

A problem I'm having is that I'm unable to write to my unassigned devices that're formatted as NTFS. They're just USB Hard Drives I wish to mount separately from my array. I'm able to read from it no problem, but writing and deleting files on the drives via network shares or Krusader proves that I lack the write permission. I tried searching and seems that there's a "ntfs-3g" driver thing? That was a really old post and config seems quite complex. 

 

Please let me know how I should diagnose this. Appreciate the help! unRAID OS version 6.5.3.

You should be able to write to any unassigned ntfs device, it would be better to post on the UD thread and make sure you post your diagnostics.

Yes I know I should be, but I can't and that's why I'm trying to find out why. I'm unaware that there's a Unassigned Devices thread (can't find it). If there is admin please move me there. 

 

Attached my diagnostic s - 

homeserver-diagnostics-20180817-1305.zip

 

Thanks

read/write mount failed, so it was then mounted read only:

 

Aug 15 16:56:46 HomeServer unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sde2' '/mnt/disks/Kevin'
Aug 15 16:56:46 HomeServer unassigned.devices: Mount failed with error: ntfs-3g-mount: mount failed: Device or resource busy
Aug 15 16:56:46 HomeServer unassigned.devices: Mounting ntfs drive read only.
Aug 15 16:56:46 HomeServer unassigned.devices: Mount drive ro command: /sbin/mount -t ntfs -ro auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sde2' '/mnt/disks/Kevin'

 

3 minutes ago, JustKev85 said:

I'm unaware that there's a Unassigned Devices thread (can't find it)

 

Thanks! How do I read/write mount it? 

3 hours ago, JustKev85 said:

I'm unaware that there's a Unassigned Devices thread (can't find it).

 

For future reference, you can always get to the support thread for any addon (plugin or docker) from its support link Community Applications.

Looks like something else was using the disk, but I don't have experience with using ntfs disks with unRAID, try again after rebooting and if the same happens post on the UD thread.

10 hours ago, trurl said:

For future reference, you can always get to the support thread for any addon (plugin or docker) from its support link Community Applications.

Oh that is perfect, very convenient. Will do that thanks! 

 

And thanks Johnnie, I'll try that! 

On 8/18/2018 at 1:07 AM, JustKev85 said:

Yes I know I should be, but I can't and that's why I'm trying to find out why. I'm unaware that there's a Unassigned Devices thread (can't find it). If there is admin please move me there. 

 

Attached my diagnostic s - 

homeserver-diagnostics-20180817-1305.zip 83.96 kB · 4 downloads

 

Thanks

this came up higher when trying to google the same issue. any massive thread is useless when trying to search for one answer.

How I just solves this issue:

 

I first tried using Unassigned Devices (Plus) which did not mount in Read-Write mode. Looking at the Disk Log Information on the Main tab it told me: ntfs-3g[60028]:

Mounted /dev/sdf1 (Read-Only, label "MY-LABEL", NTFS 3.1)

Attempting to manually mount the partition following this guide I was able to get some more information on why RW failed and it defaulted to Read-Only:

The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Falling back to read-only mount because the NTFS partition is in an
unsafe state. Please resume and shutdown Windows fully (no hibernation
or fast restarting.)

Following a suggestion from here I attempted to repair the file system using ntfsfix. Using it looked like this in my case:

root@MYSERVER: ~# ntfsfix /dev/sdc1
Mounting volume... The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
FAILED
Attempting to correct errors... 
Processing $MFT and $MFTMirr...
Reading $MFT... OK
Reading $MFTMirr... OK
Comparing $MFTMirr to $MFT... OK
Processing of $MFT and $MFTMirr completed successfully.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sdc1 was processed successfully.

After that I could successfully mount the partition with Unassigned Devices.

 

Hope this helps anyone finding this in the future.

Edited February 15, 20242 yr by DesertCookie
typo

I realize that this is years later, but thanks for the ntfsfix tip. That worked perfectly for me as well.