dlandon

You really have to give me more information. What is 'MAIN' page? What is 'loaded stats'? Is this when you are on the unassigned webpage? How do you know it is unassigned devices?

OK. So the unassigned drives show on the main page. However it does not recognise the NTFS partitions and consequently won't mount the drives. I can see the ntfs package is in the unassigned plugin folder. Any ideas? Thanks Check the log. Found the log button and checked it out. This is the error I'm getting Mon Jan 18 10:29:04 PST 2016: Adding disk ... Mon Jan 18 10:29:04 PST 2016: Mounting drive with command: mount -t ntfs -o auto,async,nodev,nosuid,umask=000 '/dev/sdd2' '/mnt/disks/New_Volume' Mon Jan 18 10:29:04 PST 2016: Mount of /dev/sdd2 failed. Error message: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Failed to mount '/dev/sdd2': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option. So I must have not cleanly shut down windows when i removed these disks. Read only is fine as I only want to pull the information from it. I tried to ssh in and use the following command "mount -t ntfs -ro auto,async,nodev,nosuid,umask=000 '/dev/sdd2' '/mnt/disks/New_Volume" All i got was a chevron after pressing enter. I guess im not doing it correctly. My linux knowledge is very limited. Do I need to boot these drives under windows to clear the mounting problem? Only issue is I no longer have a windows machine as I have moved from windows based flexraid to unraid. Thanks I've just made a change to unassigned devices so an unsafe ntfs partition can be mounted read only. If an ntfs partition doesn't mount, unassigned devices will mount it read only so files can be taken off the drive. The log will indicate the mount status. EDIT: Will be in the next release.

Where in unassigned devices do you see the cache? If it's in historical devices then click the remove button. I believe unassigned devices picked it up when it saw a new drive not assigned to the array. In order to format a drive you need to enable the destructive mode setting in the unassigned devices settings.

Turn on unRaid nfs and nfs export in unassigned devices in settings and share the unassigned device.

New release 2016.01.18 should fix the nfs export. See if it works for you.

OK. So the unassigned drives show on the main page. However it does not recognise the NTFS partitions and consequently won't mount the drives. I can see the ntfs package is in the unassigned plugin folder. Any ideas? Thanks Check the log. Found the log button and checked it out. This is the error I'm getting Mon Jan 18 10:29:04 PST 2016: Adding disk ... Mon Jan 18 10:29:04 PST 2016: Mounting drive with command: mount -t ntfs -o auto,async,nodev,nosuid,umask=000 '/dev/sdd2' '/mnt/disks/New_Volume' Mon Jan 18 10:29:04 PST 2016: Mount of /dev/sdd2 failed. Error message: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Failed to mount '/dev/sdd2': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option. So I must have not cleanly shut down windows when i removed these disks. Read only is fine as I only want to pull the information from it. I tried to ssh in and use the following command "mount -t ntfs -ro auto,async,nodev,nosuid,umask=000 '/dev/sdd2' '/mnt/disks/New_Volume" All i got was a chevron after pressing enter. I guess im not doing it correctly. My linux knowledge is very limited. Do I need to boot these drives under windows to clear the mounting problem? Only issue is I no longer have a windows machine as I have moved from windows based flexraid to unraid. Thanks If unraid can't mount it, you'll need to get it to a Windows machine and clean up the disk.

OK. So the unassigned drives show on the main page. However it does not recognise the NTFS partitions and consequently won't mount the drives. I can see the ntfs package is in the unassigned plugin folder. Any ideas? Thanks Check the log.

You can edit that name. Unmount the drive, then click on the identification, then click on the name and you can edit it. That would keep this from happening again.

I will look into this, but I don't use NFS shares so I don't know much about it. Do you have NFS shares enabled under Network Settings?

Nope, yours just makes things pretty, I could manage without it.... Dan's powerdown stops me breaking stuff..... You're not having fun unless you break stuff.

I don't know. I think that was one of the things gfjardim was working on in a later version. I will take a look when I get some time.

That's a bug in one of the earlier releases today. I got rid of it by updating and a reboot.

The sleep time is set to 15 minutes. I have a WD red that spins down just fine. The sleep time is set by unassigned devices using: hdparm -S180. Your drive has to be able to respond to this command.

Please update to version 2016.01.17c. I fixed what I broke in unassigned_umount.

I don't know. I will have a look.

I can reproduce the issue and will work on it. Do you happen to have the Recycle Bin plugin installed? No, I have not installed the Recycle Bin Plugin BTW, thanks for all your work!!! Fixed in latest version 2016.01.17a.

I can reproduce the issue and will work on it. Do you happen to have the Recycle Bin plugin installed?

I tried to install this plugin using the PLG provided and when the install dialog comes up it just shows the following plugin: installing: https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg plugin: downloading https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg plugin: downloading: https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg ... After I click on done and check the installed plugins "unassigned devices" is not there. I have also checked the plugins folder and nothing has been created there. This is on a fresh install of the latest unraid version. I have a bunch of NTFS drives I need to copy over and would appreciate any help. Thanks I updated the plugin this morning and you may have caught it partially updated. Look at your log and see if there is any indication of why it did not work there. Delete the folder /flash/config/plugins/unassigned_devices and try again. If it still doesn't work, copy the script output when the plugin is installed and post it.

Did it work in the latest gfjardim version?

Just my own opinion: Automount for me would mean that the drive mounts as soon as possible when the server boots up, and the drives get unmounted just before the server shuts down. In other words, the drives are also mounted when the array is stopped. Compare it with an entry in fstab, mount as soon as possible while booting up, unmount just before the server powers down... Yes. That's exactly what I have implemented in the newest version. It's just that there is a command line command "unassigned_umount all" that can be used by a user that is not working as I think it should.

I have fixed the SMB potentially not unmounting on an array shutdown. It seems that any device mounted with the auto mount switch off would not unmount when the array was being shutdown. I also found the auto mount switch on an SMB device was not working. There is a quirk (feature) in the unmounting of unassigned devices that I don't fully understand. The command "unassigned_unmount all" would unmount only devices that were set to auto mount. Devices that were not auto mounted would not be unmounted. I could see this possibly being useful if a person wanted a disk to stay mounted with the array stopped. I can't see why one would want to do this though because there would not be any shares. I don't like keeping a device mounted because the array would potentially not shutdown cleanly or hang during shutdown. I added a parameter to the unassigned_umount as a special case when the array is stopped. When the array is stopped, the command "unassigned_umount shutdown" is issued and all devices are unmounted so the array can shutdown regardless of the auto mount switch. I'm looking for feedback from anyone who knows why gfjardim would do the unmount like this. I am thinking it is so the "unassigned_umount all" command from the command line would only unmount devices set to auto mount. I'm actually thinking is this is a wanted feature, it really should be the other way around. My thinking is that any auto mounted device should stay mounted with the "unassigned_umount all", and only be unmounted when the array is stopped. Thoughts? EDIT: I have convinced myself that the opposite logic makes sense for 'unassigned_umount all". If a device is auto mounted, it should not be unmounted unless the array is shutting down. When the "unassigned_umount all" is executed, all devices not set to auto mount will be unmouned.

The removal of the older unassigned devices leaves packages behind that can interfere with an update or new install of the older versions. I have changed the way the gui files are installed and it is not a problem now. You can remove the existing plugin and then install my version from ca and it will be clean. Your settings will be kept.

Thanks for the fix dlandon, was looking into this plugin to see if my files were still on a disk I didn't want to include in the array and have rebuilt yet. I can help with testing this but I am new to UNRAID and can't find the log to check for the extra entries. Also with the other issue you mentioned, does the SMB mounted device need to be setup in any particular way? If you can guide me through what info you need reported and what needs to be done, will be happy to help. Click on the Help button on the main menu bar and you'll see the line about the log. The issue with the smb unmount is when stopping the array. It was posted in another thread about this. Mount an smb device and thn stop the array and see if the array stops. You should be prepared to go to a command line to shutdown if necessary. A better way might be to install the open files plugin and use it to manage the array stop.

Ever see this? Yes. What version of unassigned devices do you have installed?

I've made my version of unassigned devices available as a beta on ca.