dlandon

I guess I was wrong. You do have an issue with this drive. There is no work around to your drive disconnecting, except to fix it. It it's a USB drive, try another UB port. Post diagnostics so we can see what is causing the disconnect.

It doesn't indicate a problem with your system, it's just a situation that UD does not handle well.

Jan 1 22:26:26 Tower unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs4' -o rw,noacl '172.27.9.90:/mnt/Skywalker/Nikki' '/mnt/remotes/172.27.9.90_Nikki' Jan 1 22:26:26 Tower unassigned.devices: NFS mount failed: 'mount: /mnt/remotes/172.27.9.90_Nikki: unknown filesystem type 'nfs4'. '. Jan 1 22:26:31 Tower unassigned.devices: Mounting Remote SMB/NFS Share '172.27.9.90:/mnt/Skywalker/Nikki'... Jan 1 22:26:31 Tower unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs4' -o rw,noacl '172.27.9.90:/mnt/Skywalker/Nikki' '/mnt/remotes/172.27.9.90_Nikki' You need 6.10 or better to mount nfs shares with NFSv4. Go to UD settings and set NFS version to use NFSv3 and your shares will mount.

I've made a fix for this in the next release of UD.

Right, now you'll need to format it.

Post another diagnostics.

It probably doesn't have a file system. Post a screen shot of the disk with all the details on that disk on UD.

You have multiple issues: Dec 31 09:43:02 Tower unassigned.devices: Cannot 'Auto Mount' Remote Shares. Network not available! The network was not available on startup so remote shares could not be auto mounted. Dec 31 09:45:31 Tower unassigned.devices: Error: Device '172.27.9.81:/mnt/Skywalker/Nikki' mount point '172.27.9.81_Nikki' - name is reserved, used in the array or by an unassigned device. Dec 31 09:45:31 Tower unassigned.devices: Remote SMB/NFS '172.27.9.81:/mnt/Skywalker/Nikki' cannot be mounted. You have another UD device with the same name. Dec 31 09:54:14 Tower unassigned.devices: Error: Device '172.27.9.81:/mnt/Skywalker/bkup' mount point '172.27.9.81_bkup' - name is reserved, used in the array or by an unassigned device. Dec 31 09:54:14 Tower unassigned.devices: Remote SMB/NFS '172.27.9.81:/mnt/Skywalker/bkup' cannot be mounted. Dec 31 09:54:16 Tower unassigned.devices: Error: Device '172.27.9.81:/mnt/Skywalker/bkup' mount point '172.27.9.81_bkup' - name is reserved, used in the array or by an unassigned device. Dec 31 09:54:16 Tower unassigned.devices: Remote SMB/NFS '172.27.9.81:/mnt/Skywalker/bkup' cannot be mounted. This one looks to be duplicated in UD. I'd remove all the NFS remote shares and re-enter them.

I wouldn't recommend doing that. UD adds additional things to the share configuration such as the recycle bin if that plugin is installed, and some entries to deal with case sensitive names, and Mac OS interoperability. It's also very easy to mess up samba shares when making manual entries. A cleaner approach would be to partition the disk with multiple partitions on a PC. When you put the disk back in Unraid, you then set each partition mount point for the share name you want, and you'll have multiple shares on one disk with all the extra things UD handles. Down side is each share is limited by the partition size for the shares. If you need more share control than that, use Unraid shares.

1) No. One disk - one share. 2) Yes.

Post the contents of the '/var/state/unassigned.devices/unasigned.devices.ini' file.

Debug logging won't help in this situation and it just clogs the syslog with messages.

You also need to go to the UD settings and set 'Debug Log Level' to 'None'. You are generating excessive log messages. This setting should only be used when requested for debugging.

Disk was not unmounted cleanly: Dec 29 14:11:38 Kyles-Lab mount.exfat: volume was not unmounted cleanly Dec 29 14:11:38 Kyles-Lab unassigned.devices: Mount of 'sdc1' failed: 'FUSE exfat 1.3.0 WARN: volume was not unmounted cleanly. fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option ' Take it to a PC and mount it, then unmount it cleanly.

Post your diagnostics.

Start by posting your diagnostics zip.

Yes, your devices are showing zero size. Dec 26 22:42:46 Tower emhttpd: device /dev/sdh has size zero Dec 26 22:42:46 Tower emhttpd: device /dev/sdg has size zero Dec 26 22:42:46 Tower emhttpd: device /dev/sdf has size zero Dec 26 22:42:46 Tower emhttpd: device /dev/sdi has size zero Dec 26 22:42:47 Tower emhttpd: device /dev/sdh has size zero What's the story on these devices? Can you give a screen shot?

Can someone with scsi attached disks with the dynamix.scsi.devices plugin installed give me the output of: ls /dev/ I think I see what might be happening with scsi disks not being recognized by UD.

This is a known issue in UD. The dynamix.scsi.devices plugin changes the disks from ata to scsi. UD should be handling this properly, but apparently something has broken it. I can't fix it until I can get some hardware to test scsi attached disks as I don't have scsi disks. The only fix for the moment is to remove the dynamix.scsi.devices plugin.

I plan on a release after the Holidays. I'm working on some issues I want resolved by the next release.

Thanks. I'd like to get this solved.

Just noting this for the poster with the concern.

UD handles the changes in sdX designations when disks are hot plugged.

I've released a new version with the ffmpeg package installed so players that don't play wma natively can play wma files.

That won't make them go away. UD is designed to leave the configured shares when it is uninstalled. So you can't delete the share at all? It sounds like the configuration file might be corrupted. You can start over by doing this: Unmount all remote shares. Delete the /flash/config/plugins/unassigned.devices/samba_mount.cfg file. Click on the double arrows in the upper right corner of the UD page. Re-enter your remote shares.