Jump to content
dlandon

Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

3484 posts in this topic Last Reply

Recommended Posts

Getting th following error while trying to install.

 

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 ... done

Warning: simplexml_load_file(): /tmp/plugins/unassigned.devices.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): /tmp/plugins/unassigned.devices.plg:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193
plugin: xml parse error

Share this post


Link to post

I updated to the latest version (thanks dlandon for updating this)

 

I am converting drives from RFS to XFS, and I added a drive to the array, formatted it XFS and then pulled it out of the array and connected it via this plugin.  This newly formatted XFS drive will not mount at all when connected to my Areca card, but when moved back to the motherboard port, it will mount fine.

 

I have an Areca 1280 with a bunch of 3tb drives on it and it works fine with unRaid.  Other Areca connected RFS drives mount fine with this unassigned devices plugin too.  But this newly formatted 3TB WD EZRS drive would not.

 

You have not said you rebooted or just plugged the drive in.  If you didn't reboot, it may be a hot plug problem.

 

The best way to see if a drive is recognized by unraid and subsequently by unassigned devices is to go to the 'Dashboard' and look at the row labeled 'Unassigned".  You will see the disks that unraid sees as unassigned.  If it does not show there, unassigned devices will not recognize it.

 

Drive was always showing in the list of drives recognized by unassigned devices, you could change the mount name without problems, but pressing mount just brought it back to the same screen without any results.

 

I did reboot the server and it (newly formatted XFS drive)  is now mounted on a motherboard port without issue as un unassigned device.  Perhaps mounting and unmounting multiple times from multiple ports gets things in a mishmash that only a reboot can cure???

 

What can we do to test the Areca mount issue?

Share this post


Link to post

I have found a problem (bug?).

 

I have a disk, mounted as /mnt/disks/SABDrive.

 

SMB setting in UD are : (see pic capture1.png)

 

I have access through the admin_user to the disk.  I can create/delete files/dirs.

 

However, when I use windows to create a new dir on the disk, the user uid is not correct. I just created a "New folder" on the disk and the user is admin_user instead of nobody. (see capture2.png)

 

I can just delete this folder from windows.

 

If I use newparms on the drive then the admin_user becomes nobody. I can then still delete the file from the drive.

 

Is something broken on my setup, or is this a bug? Using UD v 2016.01.26a .

 

Thanks

 

 

Capture2.PNG.51ec35b41e60f765f78971f95d2dacd6.PNG

Capture1.PNG.ade067d606e6f5c26271b3c49b44d06b.PNG

Share this post


Link to post

I updated to the latest version (thanks dlandon for updating this)

 

I am converting drives from RFS to XFS, and I added a drive to the array, formatted it XFS and then pulled it out of the array and connected it via this plugin.  This newly formatted XFS drive will not mount at all when connected to my Areca card, but when moved back to the motherboard port, it will mount fine.

 

I have an Areca 1280 with a bunch of 3tb drives on it and it works fine with unRaid.  Other Areca connected RFS drives mount fine with this unassigned devices plugin too.  But this newly formatted 3TB WD EZRS drive would not.

 

You have not said you rebooted or just plugged the drive in.  If you didn't reboot, it may be a hot plug problem.

 

The best way to see if a drive is recognized by unraid and subsequently by unassigned devices is to go to the 'Dashboard' and look at the row labeled 'Unassigned".  You will see the disks that unraid sees as unassigned.  If it does not show there, unassigned devices will not recognize it.

 

Drive was always showing in the list of drives recognized by unassigned devices, you could change the mount name without problems, but pressing mount just brought it back to the same screen without any results.

 

I did reboot the server and it (newly formatted XFS drive)  is now mounted on a motherboard port without issue as un unassigned device.  Perhaps mounting and unmounting multiple times from multiple ports gets things in a mishmash that only a reboot can cure???

 

What can we do to test the Areca mount issue?

 

Check the log after a mount that doesn't succeed and it should have the error from the mount command.

 

If the drive shows on the Dashboard as "Unassigned", then it will be available to unassigned devices to mount.  If it doesn't, then unassigned devices cannot mount it.

 

In order for unassigned devices to recognize a drive it has to be recognized by unraid Linux.  It's my understanding that hot plug is supported by Linux, but not by unraid.

Share this post


Link to post

Getting th following error while trying to install.

 

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 ... done

Warning: simplexml_load_file(): /tmp/plugins/unassigned.devices.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): /tmp/plugins/unassigned.devices.plg:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193
plugin: xml parse error

 

The plugin manager has a bug when a file is not downloaded, it is created and is empty.  Because it exists when the next attempt at installing the plugin, it is not re-downloaded and the plugin installation fails.

 

Best way for now to deal with it is to delete the /flash/config/plugins/unassigned.devices/packages/ folder and try installing the plugin again.

Share this post


Link to post

Getting th following error while trying to install.

 

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 ... done

Warning: simplexml_load_file(): /tmp/plugins/unassigned.devices.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): /tmp/plugins/unassigned.devices.plg:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193
plugin: xml parse error

 

The plugin manager has a bug when a file is not downloaded, it is created and is empty.  Because it exists when the next attempt at installing the plugin, it is not re-downloaded and the plugin installation fails.

 

Best way for now to deal with it is to delete the /flash/config/plugins/unassigned.devices/packages/ folder and try installing the plugin again.

 

That worked, thank you.

Share this post


Link to post

I have found a problem (bug?).

 

I have a disk, mounted as /mnt/disks/SABDrive.

 

SMB setting in UD are : (see pic capture1.png)

 

I have access through the admin_user to the disk.  I can create/delete files/dirs.

 

However, when I use windows to create a new dir on the disk, the user uid is not correct. I just created a "New folder" on the disk and the user is admin_user instead of nobody. (see capture2.png)

 

I can just delete this folder from windows.

 

If I use newparms on the drive then the admin_user becomes nobody. I can then still delete the file from the drive.

 

Is something broken on my setup, or is this a bug? Using UD v 2016.01.26a .

 

Thanks

 

The share permissions are controlled by unraid.  Unassigned devices can't change that.

Share this post


Link to post

Release 2016.01.28 is now available.  There are two changes.

 

- The samba host lookup has been changed so it should work on more systems.  It was not working on either of my servers and is now working.  The change shouldn't affect any systems where it was working before.

 

- Mount points are now limited to /mnt/disks/.  If you change the mount point name it will be set to /mnt/disks/ regardless of whether or not you try to change the mount point directory.  You can just enter the name of the mount point you want and it will be set to /mnt/disks/.

Share this post


Link to post

Check the log after a mount that doesn't succeed and it should have the error from the mount command.

 

If the drive shows on the Dashboard as "Unassigned", then it will be available to unassigned devices to mount.  If it doesn't, then unassigned devices cannot mount it.

 

In order for unassigned devices to recognize a drive it has to be recognized by unraid Linux.  It's my understanding that hot plug is supported by Linux, but not by unraid.

 

I never had a problem with the drive showing on the unassigned list.  Whether using the motherboard ports or the Areca ports both always showed up.  After rebooting the server, I had no problems mounting with the drive connected to the Areca.  So problem solved with a reboot.

 

Confession time: 

The previous problems followed uninstalling the gfardjim unassigned devices plugin, and then reinstalling your newer version without doing a reboot.  It sort of worked, but not with this drive.  Here are the log entries from around that time that you might find interesting as I was hot plugging drives in and out.  Sometimes Areca ports and sometimes motherboard ports are being used in the list below.  The drive in question is a WDC WD30EZRS, and I was also working with a Hitachi and a WD 2tb EARS both RFS formatted and connected to the Areca.

 

Jan 27 16:25:34 Kim kernel: XFS (sdp1): Unmounting Filesystem
Jan 27 16:26:06 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove unassigned.devices.plg
Jan 27 16:26:06 Kim logger: plugin: running: anonymous
Jan 27 16:26:29 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/hd_parm down sdp
Jan 27 16:26:34 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/hd_parm up sdp
Jan 27 16:26:45 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sdp
Jan 27 16:27:55 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg
Jan 27 16:27:55 Kim logger: plugin: running: anonymous
Jan 27 16:27:55 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/unassigned.devices-2016.01.26a.tgz - downloading from URL https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices-2016.01.26a.tgz
Jan 27 16:27:56 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/unassigned.devices-2016.01.26a.tgz - MD5
Jan 27 16:27:56 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/ntfs-3g-2015.3.14-x86_64-1.txz - downloading from URL http://slackbuilds.org/mirror/slackware/slackware64-current/slackware64/a/ntfs-3g-2015.3.14-x86_64-1.txz
Jan 27 16:28:02 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/ntfs-3g-2015.3.14-x86_64-1.txz - MD5
Jan 27 16:28:02 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/ntfs-3g-2015.3.14-x86_64-1.txz
Jan 27 16:28:02 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/exfat-utils-1.1.1-x86_64-1_SBo.txz - downloading from URL https://github.com/dlandon/unassigned.devices/raw/master/packages/exfat-utils-1.1.1-x86_64-1_SBo.txz
Jan 27 16:28:03 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/exfat-utils-1.1.1-x86_64-1_SBo.txz - MD5
Jan 27 16:28:03 Kim logger: plugin: running: anonymous
Jan 27 16:28:03 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/fuse-exfat-1.1.0-x86_64-1_SBo.txz - downloading from URL https://github.com/dlandon/unassigned.devices/raw/master/packages/fuse-exfat-1.1.0-x86_64-1_SBo.txz
Jan 27 16:28:04 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/fuse-exfat-1.1.0-x86_64-1_SBo.txz - MD5
Jan 27 16:28:04 Kim logger: plugin: running: anonymous
Jan 27 16:28:04 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz - downloading from URL http://slackware.org.uk/slacky/slackware64-14.1/system/hfsprogs/332.25/hfsprogs-332.25-x86_64-2sl.txz
Jan 27 16:28:06 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz - MD5
Jan 27 16:28:06 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz
Jan 27 16:28:06 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/libbsd-0.6.0-x86_64-1sl.txz - downloading from URL http://slackware.org.uk/slacky/slackware64-14.1/libraries/libbsd/0.6.0/libbsd-0.6.0-x86_64-1sl.txz
Jan 27 16:28:08 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/libbsd-0.6.0-x86_64-1sl.txz - MD5
Jan 27 16:28:08 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/libbsd-0.6.0-x86_64-1sl.txz
Jan 27 16:28:08 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/parted-3.1-x86_64-1.txz - downloading from URL http://slackware.osuosl.org/slackware64-14.1/slackware64/l/parted-3.1-x86_64-1.txz
Jan 27 16:28:09 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/parted-3.1-x86_64-1.txz - MD5
Jan 27 16:28:09 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/parted-3.1-x86_64-1.txz
Jan 27 16:28:09 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz - downloading from URL http://slackware.osuosl.org/slackware64-14.1/slackware64/l/libnl-1.1.4-x86_64-1.txz
Jan 27 16:28:09 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz - MD5
Jan 27 16:28:09 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz
Jan 27 16:28:09 Kim logger: plugin: running: anonymous
Jan 27 16:29:35 Kim kernel: XFS (sdp1): Mounting V5 Filesystem
Jan 27 16:29:36 Kim kernel: XFS (sdp1): Ending clean mount
Jan 27 16:42:03 Kim kernel: ata1: exception Emask 0x50 SAct 0x0 SErr 0x40d0800 action 0xe frozen
Jan 27 16:42:03 Kim kernel: ata1: irq_stat 0x00400040, connection status changed
Jan 27 16:42:03 Kim kernel: ata1: SError: { HostInt PHYRdyChg CommWake 10B8B DevExch }
Jan 27 16:42:03 Kim kernel: ata1: hard resetting link
Jan 27 16:42:04 Kim kernel: ata1: SATA link down (SStatus 0 SControl 300)
Jan 27 16:42:09 Kim kernel: ata1: hard resetting link
Jan 27 16:42:09 Kim kernel: ata1: SATA link down (SStatus 0 SControl 300)
Jan 27 16:42:09 Kim kernel: ata1: limiting SATA link speed to 1.5 Gbps
Jan 27 16:42:14 Kim kernel: ata1: hard resetting link
Jan 27 16:42:15 Kim kernel: ata1: SATA link down (SStatus 0 SControl 310)
Jan 27 16:42:15 Kim kernel: ata1.00: disabled
Jan 27 16:42:15 Kim kernel: ata1: EH complete
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: [sdp] killing request
Jan 27 16:42:15 Kim kernel: blk_update_request: I/O error, dev sdp, sector 2930276939
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: XFS (sdp1): metadata I/O error: block 0xaea87a0b ("xlog_iodone") error 5 numblks 64
Jan 27 16:42:15 Kim kernel: XFS (sdp1): xfs_do_force_shutdown(0x2) called from line 1180 of file fs/xfs/xfs_log.c.  Return address = 0xffffffff81275cff
Jan 27 16:42:15 Kim kernel: XFS (sdp1): Log I/O Error Detected.  Shutting down filesystem
Jan 27 16:42:15 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:42:15 Kim kernel: XFS (sdp1): Please umount the filesystem and rectify the problem(s)
Jan 27 16:42:15 Kim kernel: ata1.00: detaching (SCSI 2:0:0:0)
Jan 27 16:42:15 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Synchronizing SCSI cache
Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00
Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Stopping disk
Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00
Jan 27 16:42:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:43:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:43:18 Kim kernel: scsi 1:0:0:7: Direct-Access     WDC      WD30EZRS-00J99B0 R001 PQ: 0 ANSI: 5
Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] physical block alignment offset: 3276288
Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: Attached scsi generic sg16 type 0
Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Write Protect is off
Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Mode Sense: cb 00 00 08
Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 27 16:43:18 Kim kernel: sds: sds1
Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Attached SCSI disk
Jan 27 16:43:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:44:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:44:16 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount
Jan 27 16:44:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:44:37 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount
Jan 27 16:45:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:45:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:46:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:46:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:47:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:47:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:48:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:48:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:49:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:49:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): found reiserfs format "3.6" with standard journal
Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): using ordered data mode
Jan 27 16:49:51 Kim kernel: reiserfs: using flush barriers
Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): journal params: device sdr1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): checking transaction log (sdr1)
Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): Using r5 hash to sort names
Jan 27 16:50:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:50:14 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount
Jan 27 16:50:23 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount
Jan 27 16:50:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:51:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:51:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:51:38 Kim apcupsd[11285]: Power failure.
Jan 27 16:51:40 Kim apcupsd[11285]: Power is back. UPS running on mains.
Jan 27 16:52:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:52:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:53:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:53:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:54:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:54:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:55:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:55:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:56:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:56:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:56:38 Kim kernel: sd 1:0:0:7: [sds] Synchronizing SCSI cache
Jan 27 16:57:01 Kim kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
Jan 27 16:57:01 Kim kernel: ata1: irq_stat 0x00000040, connection status changed
Jan 27 16:57:01 Kim kernel: ata1: SError: { CommWake DevExch }
Jan 27 16:57:01 Kim kernel: ata1: hard resetting link
Jan 27 16:57:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:57:07 Kim kernel: ata1: link is slow to respond, please be patient (ready=0)
Jan 27 16:57:11 Kim kernel: ata1: COMRESET failed (errno=-16)
Jan 27 16:57:11 Kim kernel: ata1: hard resetting link
Jan 27 16:57:17 Kim kernel: ata1: link is slow to respond, please be patient (ready=0)
Jan 27 16:57:17 Kim kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Jan 27 16:57:17 Kim kernel: ata1.00: ATA-8: WDC WD30EZRS-00J99B0,      WD-WCAWZ0361944, 80.00A80, max UDMA/133
Jan 27 16:57:17 Kim kernel: ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Jan 27 16:57:17 Kim kernel: ata1.00: configured for UDMA/133
Jan 27 16:57:17 Kim kernel: ata1: EH complete
Jan 27 16:57:17 Kim kernel: scsi 2:0:0:0: Direct-Access     ATA      WDC WD30EZRS-00J 0A80 PQ: 0 ANSI: 5
Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: Attached scsi generic sg16 type 0
Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] 4096-byte physical blocks
Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Write Protect is off
Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Mode Sense: 00 3a 00 00
Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 27 16:57:17 Kim kernel: sds: sds1
Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Attached SCSI disk
Jan 27 16:57:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:57:51 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount
Jan 27 16:58:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:58:11 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount
Jan 27 16:58:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:59:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:59:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 17:00:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 17:00:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.

Share this post


Link to post

Check the log after a mount that doesn't succeed and it should have the error from the mount command.

 

If the drive shows on the Dashboard as "Unassigned", then it will be available to unassigned devices to mount.  If it doesn't, then unassigned devices cannot mount it.

 

In order for unassigned devices to recognize a drive it has to be recognized by unraid Linux.  It's my understanding that hot plug is supported by Linux, but not by unraid.

 

I never had a problem with the drive showing on the unassigned list.  Whether using the motherboard ports or the Areca ports both always showed up.  After rebooting the server, I had no problems mounting with the drive connected to the Areca.  So problem solved with a reboot.

 

Confession time: 

The previous problems followed uninstalling the gfardjim unassigned devices plugin, and then reinstalling your newer version without doing a reboot.  It sort of worked, but not with this drive.  Here are the log entries from around that time that you might find interesting as I was hot plugging drives in and out.  Sometimes Areca ports and sometimes motherboard ports are being used in the list below.  The drive in question is a WDC WD30EZRS, and I was also working with a Hitachi and a WD 2tb EARS both RFS formatted and connected to the Areca.

 

Jan 27 16:25:34 Kim kernel: XFS (sdp1): Unmounting Filesystem
Jan 27 16:26:06 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove unassigned.devices.plg
Jan 27 16:26:06 Kim logger: plugin: running: anonymous
Jan 27 16:26:29 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/hd_parm down sdp
Jan 27 16:26:34 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/hd_parm up sdp
Jan 27 16:26:45 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sdp
Jan 27 16:27:55 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg
Jan 27 16:27:55 Kim logger: plugin: running: anonymous
Jan 27 16:27:55 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/unassigned.devices-2016.01.26a.tgz - downloading from URL https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices-2016.01.26a.tgz
Jan 27 16:27:56 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/unassigned.devices-2016.01.26a.tgz - MD5
Jan 27 16:27:56 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/ntfs-3g-2015.3.14-x86_64-1.txz - downloading from URL http://slackbuilds.org/mirror/slackware/slackware64-current/slackware64/a/ntfs-3g-2015.3.14-x86_64-1.txz
Jan 27 16:28:02 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/ntfs-3g-2015.3.14-x86_64-1.txz - MD5
Jan 27 16:28:02 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/ntfs-3g-2015.3.14-x86_64-1.txz
Jan 27 16:28:02 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/exfat-utils-1.1.1-x86_64-1_SBo.txz - downloading from URL https://github.com/dlandon/unassigned.devices/raw/master/packages/exfat-utils-1.1.1-x86_64-1_SBo.txz
Jan 27 16:28:03 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/exfat-utils-1.1.1-x86_64-1_SBo.txz - MD5
Jan 27 16:28:03 Kim logger: plugin: running: anonymous
Jan 27 16:28:03 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/fuse-exfat-1.1.0-x86_64-1_SBo.txz - downloading from URL https://github.com/dlandon/unassigned.devices/raw/master/packages/fuse-exfat-1.1.0-x86_64-1_SBo.txz
Jan 27 16:28:04 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/fuse-exfat-1.1.0-x86_64-1_SBo.txz - MD5
Jan 27 16:28:04 Kim logger: plugin: running: anonymous
Jan 27 16:28:04 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz - downloading from URL http://slackware.org.uk/slacky/slackware64-14.1/system/hfsprogs/332.25/hfsprogs-332.25-x86_64-2sl.txz
Jan 27 16:28:06 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz - MD5
Jan 27 16:28:06 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz
Jan 27 16:28:06 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/libbsd-0.6.0-x86_64-1sl.txz - downloading from URL http://slackware.org.uk/slacky/slackware64-14.1/libraries/libbsd/0.6.0/libbsd-0.6.0-x86_64-1sl.txz
Jan 27 16:28:08 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/libbsd-0.6.0-x86_64-1sl.txz - MD5
Jan 27 16:28:08 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/libbsd-0.6.0-x86_64-1sl.txz
Jan 27 16:28:08 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/parted-3.1-x86_64-1.txz - downloading from URL http://slackware.osuosl.org/slackware64-14.1/slackware64/l/parted-3.1-x86_64-1.txz
Jan 27 16:28:09 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/parted-3.1-x86_64-1.txz - MD5
Jan 27 16:28:09 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/parted-3.1-x86_64-1.txz
Jan 27 16:28:09 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz - downloading from URL http://slackware.osuosl.org/slackware64-14.1/slackware64/l/libnl-1.1.4-x86_64-1.txz
Jan 27 16:28:09 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz - MD5
Jan 27 16:28:09 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz
Jan 27 16:28:09 Kim logger: plugin: running: anonymous
Jan 27 16:29:35 Kim kernel: XFS (sdp1): Mounting V5 Filesystem
Jan 27 16:29:36 Kim kernel: XFS (sdp1): Ending clean mount
Jan 27 16:42:03 Kim kernel: ata1: exception Emask 0x50 SAct 0x0 SErr 0x40d0800 action 0xe frozen
Jan 27 16:42:03 Kim kernel: ata1: irq_stat 0x00400040, connection status changed
Jan 27 16:42:03 Kim kernel: ata1: SError: { HostInt PHYRdyChg CommWake 10B8B DevExch }
Jan 27 16:42:03 Kim kernel: ata1: hard resetting link
Jan 27 16:42:04 Kim kernel: ata1: SATA link down (SStatus 0 SControl 300)
Jan 27 16:42:09 Kim kernel: ata1: hard resetting link
Jan 27 16:42:09 Kim kernel: ata1: SATA link down (SStatus 0 SControl 300)
Jan 27 16:42:09 Kim kernel: ata1: limiting SATA link speed to 1.5 Gbps
Jan 27 16:42:14 Kim kernel: ata1: hard resetting link
Jan 27 16:42:15 Kim kernel: ata1: SATA link down (SStatus 0 SControl 310)
Jan 27 16:42:15 Kim kernel: ata1.00: disabled
Jan 27 16:42:15 Kim kernel: ata1: EH complete
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: [sdp] killing request
Jan 27 16:42:15 Kim kernel: blk_update_request: I/O error, dev sdp, sector 2930276939
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device
Jan 27 16:42:15 Kim kernel: XFS (sdp1): metadata I/O error: block 0xaea87a0b ("xlog_iodone") error 5 numblks 64
Jan 27 16:42:15 Kim kernel: XFS (sdp1): xfs_do_force_shutdown(0x2) called from line 1180 of file fs/xfs/xfs_log.c.  Return address = 0xffffffff81275cff
Jan 27 16:42:15 Kim kernel: XFS (sdp1): Log I/O Error Detected.  Shutting down filesystem
Jan 27 16:42:15 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:42:15 Kim kernel: XFS (sdp1): Please umount the filesystem and rectify the problem(s)
Jan 27 16:42:15 Kim kernel: ata1.00: detaching (SCSI 2:0:0:0)
Jan 27 16:42:15 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Synchronizing SCSI cache
Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00
Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Stopping disk
Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00
Jan 27 16:42:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:43:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:43:18 Kim kernel: scsi 1:0:0:7: Direct-Access     WDC      WD30EZRS-00J99B0 R001 PQ: 0 ANSI: 5
Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] physical block alignment offset: 3276288
Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: Attached scsi generic sg16 type 0
Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Write Protect is off
Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Mode Sense: cb 00 00 08
Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 27 16:43:18 Kim kernel: sds: sds1
Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Attached SCSI disk
Jan 27 16:43:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:44:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:44:16 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount
Jan 27 16:44:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:44:37 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount
Jan 27 16:45:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:45:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:46:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:46:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:47:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:47:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:48:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:48:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:49:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:49:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): found reiserfs format "3.6" with standard journal
Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): using ordered data mode
Jan 27 16:49:51 Kim kernel: reiserfs: using flush barriers
Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): journal params: device sdr1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): checking transaction log (sdr1)
Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): Using r5 hash to sort names
Jan 27 16:50:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:50:14 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount
Jan 27 16:50:23 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount
Jan 27 16:50:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:51:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:51:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:51:38 Kim apcupsd[11285]: Power failure.
Jan 27 16:51:40 Kim apcupsd[11285]: Power is back. UPS running on mains.
Jan 27 16:52:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:52:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:53:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:53:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:54:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:54:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:55:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:55:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:56:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:56:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:56:38 Kim kernel: sd 1:0:0:7: [sds] Synchronizing SCSI cache
Jan 27 16:57:01 Kim kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
Jan 27 16:57:01 Kim kernel: ata1: irq_stat 0x00000040, connection status changed
Jan 27 16:57:01 Kim kernel: ata1: SError: { CommWake DevExch }
Jan 27 16:57:01 Kim kernel: ata1: hard resetting link
Jan 27 16:57:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:57:07 Kim kernel: ata1: link is slow to respond, please be patient (ready=0)
Jan 27 16:57:11 Kim kernel: ata1: COMRESET failed (errno=-16)
Jan 27 16:57:11 Kim kernel: ata1: hard resetting link
Jan 27 16:57:17 Kim kernel: ata1: link is slow to respond, please be patient (ready=0)
Jan 27 16:57:17 Kim kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Jan 27 16:57:17 Kim kernel: ata1.00: ATA-8: WDC WD30EZRS-00J99B0,      WD-WCAWZ0361944, 80.00A80, max UDMA/133
Jan 27 16:57:17 Kim kernel: ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Jan 27 16:57:17 Kim kernel: ata1.00: configured for UDMA/133
Jan 27 16:57:17 Kim kernel: ata1: EH complete
Jan 27 16:57:17 Kim kernel: scsi 2:0:0:0: Direct-Access     ATA      WDC WD30EZRS-00J 0A80 PQ: 0 ANSI: 5
Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: Attached scsi generic sg16 type 0
Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] 4096-byte physical blocks
Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Write Protect is off
Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Mode Sense: 00 3a 00 00
Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 27 16:57:17 Kim kernel: sds: sds1
Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Attached SCSI disk
Jan 27 16:57:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:57:51 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount
Jan 27 16:58:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:58:11 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount
Jan 27 16:58:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:59:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 16:59:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 17:00:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.
Jan 27 17:00:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.

 

The log I meant was the unassigned devices log.  It is more useful to me in these cases.

 

Just taking a guess here, it looks like the drive was not unmounted properly before it was mounted.

 

Jan 27 16:58:11 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount

 

Or, hot plug didn't work and Linux thought there were two drives with the same UUID?

Share this post


Link to post

The log I meant was the unassigned devices log.  It is more useful to me in these cases.

 

Just taking a guess here, it looks like the drive was not unmounted properly before it was mounted.

 

Jan 27 16:58:11 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount

 

Or, hot plug didn't work and Linux thought there were two drives with the same UUID?

 

Here is the current log, but I don't find the one for the time before the reboot. 

 

You can see I hot plugged another drive.  An old Array xfs drive LAFX and it shows an error, but this is different.  This drive was showing errors

 

Jan 28 9:31:30 Disk 'ST3000DM001 9YN166 W1F0N4JK' not mounted, cannot unmount...
Jan 28 9:31:30 Command not available, skipping.
Jan 28 9:31:30 Unmounting disk 'Samsung SSD 840 EVO 120GB S1D5NEAD803955A'...
Jan 28 9:31:30 Unmounting '/dev/sdp1'...
Jan 28 9:31:31 Successfully unmounted '/dev/sdp1'
Jan 28 9:31:31 Disk 'Samsung SSD 840 EVO 120GB S1D5NEAD803955A' removed successfully.
Jan 28 9:31:31 Disk 'Areca ARC1280V2' not mounted, cannot unmount...
Jan 28 9:31:31 Disk 'Hitachi HDS5C3030ALA630' not mounted, cannot unmount...
Jan 28 9:31:31 Disk 'WDC WD20EARS 00MVWB0' not mounted, cannot unmount...
Jan 28 9:31:31 Disk 'WDC WD30EZRS 00J99B0' not mounted, cannot unmount...
Jan 28 9:38:39 Disk with serial 'ST3000DM001-9YN166_W1F0N4JK' auto mount is disabled, not mounted.
Jan 28 9:38:39 Disk with serial 'ST3000DM001-9YN166_W1F11605' auto mount is disabled, not mounted.
Jan 28 9:38:39 Disk with serial 'ARC1280V1_0000003002536795' auto mount is disabled, not mounted.
Jan 28 9:38:39 Disk with serial 'HDS5C3030ALA630_MJ1323YNG1UKKC' auto mount is disabled, not mounted.
Jan 28 9:38:39 Disk with serial 'WD20EARS-00MVWB0_WD-WMAZA3919347' auto mount is disabled, not mounted.
Jan 28 10:03:29 Adding disk '/dev/sdo1'...
Jan 28 10:03:29 Mount drive command: mount -t reiserfs -o auto,async,noatime,nodiratime '/dev/sdo1' '/mnt/disks/ST1605'
Jan 28 10:03:29 Successfully mounted '/dev/sdo1' on '/mnt/disks/ST1605'
Jan 28 10:03:29 Defining share 'ST1605' on file '/etc/samba/unassigned-shares/ST1605.conf'
Jan 28 10:03:29 Adding share 'ST1605' to '/boot/config/smb-extra.conf'
Jan 28 10:03:29 Reloading Samba configuration...
Jan 28 10:03:29 Directory '/mnt/disks/ST1605' shared successfully.
Jan 28 10:03:29 Command not available, skipping.
Jan 28 10:19:37 Disk with serial 'ST3000DM001-9YN166_W1F0LAFX' auto mount is disabled, not mounted.
Jan 28 10:24:54 Adding disk '/dev/sds1'...
Jan 28 10:24:54 Mount drive command: mount -t xfs -o rw,noatime,nodiratime '/dev/sds1' '/mnt/disks/STLAFX'
Jan 28 10:24:54 Mount of '/dev/sds1' failed. Error message: mount: wrong fs type, bad option, bad superblock on /dev/sds1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


Jan 28 10:25:02 Adding disk '/dev/sds1'...
Jan 28 10:25:02 Mount drive command: mount -t xfs -o rw,noatime,nodiratime '/dev/sds1' '/mnt/disks/STLAFX'
Jan 28 10:25:02 Mount of '/dev/sds1' failed. Error message: mount: wrong fs type, bad option, bad superblock on /dev/sds1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


Share this post


Link to post

The log I meant was the unassigned devices log.  It is more useful to me in these cases.

 

Just taking a guess here, it looks like the drive was not unmounted properly before it was mounted.

 

Jan 27 16:58:11 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount

 

Or, hot plug didn't work and Linux thought there were two drives with the same UUID?

 

Here is the current log, but I don't find the one for the time before the reboot. 

 

You can see I hot plugged another drive.  An old Array xfs drive LAFX and it shows an error, but this is different.  This drive was showing errors and that is why it got pulled from the array.

 

Jan 28 9:31:30 Disk 'ST3000DM001 9YN166 W1F0N4JK' not mounted, cannot unmount...
Jan 28 9:31:30 Command not available, skipping.
Jan 28 9:31:30 Unmounting disk 'Samsung SSD 840 EVO 120GB S1D5NEAD803955A'...
Jan 28 9:31:30 Unmounting '/dev/sdp1'...
Jan 28 9:31:31 Successfully unmounted '/dev/sdp1'
Jan 28 9:31:31 Disk 'Samsung SSD 840 EVO 120GB S1D5NEAD803955A' removed successfully.
Jan 28 9:31:31 Disk 'Areca ARC1280V2' not mounted, cannot unmount...
Jan 28 9:31:31 Disk 'Hitachi HDS5C3030ALA630' not mounted, cannot unmount...
Jan 28 9:31:31 Disk 'WDC WD20EARS 00MVWB0' not mounted, cannot unmount...
Jan 28 9:31:31 Disk 'WDC WD30EZRS 00J99B0' not mounted, cannot unmount...
Jan 28 9:38:39 Disk with serial 'ST3000DM001-9YN166_W1F0N4JK' auto mount is disabled, not mounted.
Jan 28 9:38:39 Disk with serial 'ST3000DM001-9YN166_W1F11605' auto mount is disabled, not mounted.
Jan 28 9:38:39 Disk with serial 'ARC1280V1_0000003002536795' auto mount is disabled, not mounted.
Jan 28 9:38:39 Disk with serial 'HDS5C3030ALA630_MJ1323YNG1UKKC' auto mount is disabled, not mounted.
Jan 28 9:38:39 Disk with serial 'WD20EARS-00MVWB0_WD-WMAZA3919347' auto mount is disabled, not mounted.
Jan 28 10:03:29 Adding disk '/dev/sdo1'...
Jan 28 10:03:29 Mount drive command: mount -t reiserfs -o auto,async,noatime,nodiratime '/dev/sdo1' '/mnt/disks/ST1605'
Jan 28 10:03:29 Successfully mounted '/dev/sdo1' on '/mnt/disks/ST1605'
Jan 28 10:03:29 Defining share 'ST1605' on file '/etc/samba/unassigned-shares/ST1605.conf'
Jan 28 10:03:29 Adding share 'ST1605' to '/boot/config/smb-extra.conf'
Jan 28 10:03:29 Reloading Samba configuration...
Jan 28 10:03:29 Directory '/mnt/disks/ST1605' shared successfully.
Jan 28 10:03:29 Command not available, skipping.
Jan 28 10:19:37 Disk with serial 'ST3000DM001-9YN166_W1F0LAFX' auto mount is disabled, not mounted.
Jan 28 10:24:54 Adding disk '/dev/sds1'...
Jan 28 10:24:54 Mount drive command: mount -t xfs -o rw,noatime,nodiratime '/dev/sds1' '/mnt/disks/STLAFX'
Jan 28 10:24:54 Mount of '/dev/sds1' failed. Error message: mount: wrong fs type, bad option, bad superblock on /dev/sds1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


Jan 28 10:25:02 Adding disk '/dev/sds1'...
Jan 28 10:25:02 Mount drive command: mount -t xfs -o rw,noatime,nodiratime '/dev/sds1' '/mnt/disks/STLAFX'
Jan 28 10:25:02 Mount of '/dev/sds1' failed. Error message: mount: wrong fs type, bad option, bad superblock on /dev/sds1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


Share this post


Link to post

Release 2016.01.28 is now available.  There are two changes.

- Mount points are now limited to /mnt/disks/.  If you change the mount point name it will be set to /mnt/disks/ regardless of whether or not you try to change the mount point directory.  You can just enter the name of the mount point you want and it will be set to /mnt/disks/.

 

What happens if I upgrade but don't have the mount points in the disks folder? Will it try and remap them?

Share this post


Link to post

I have noticed that I only seem to be able to click on a drive in the Unassigned Devices tab to get its SMART attibutes if I first mount it.    Is there any reason why I cannot get them for drives that are not mounted?

Share this post


Link to post

Release 2016.01.28 is now available.  There are two changes.

- Mount points are now limited to /mnt/disks/.  If you change the mount point name it will be set to /mnt/disks/ regardless of whether or not you try to change the mount point directory.  You can just enter the name of the mount point you want and it will be set to /mnt/disks/.

 

What happens if I upgrade but don't have the mount points in the disks folder? Will it try and remap them?

 

No.  Only if you make a change to the mount point.

Share this post


Link to post

I have noticed that I only seem to be able to click on a drive in the Unassigned Devices tab to get its SMART attibutes if I first mount it.    Is there any reason why I cannot get them for drives that are not mounted?

 

There is a special case when the Drive is not mounted and the script is deleted, the drive will show spun down and the smart report is not available.

Share this post


Link to post

Release 2016.01.28 is now available.  There are two changes.

- Mount points are now limited to /mnt/disks/.  If you change the mount point name it will be set to /mnt/disks/ regardless of whether or not you try to change the mount point directory.  You can just enter the name of the mount point you want and it will be set to /mnt/disks/.

 

What happens if I upgrade but don't have the mount points in the disks folder? Will it try and remap them?

 

No.  Only if you make a change to the mount point.

 

But it shows them as being changed.....  I use the ZFS plugin and its setup to mount "appdisk" in /mnt (/mnt/appdisk) - but the plugin is displaying the path wrong - /mnt/disks/appdisk

 

Myk

 

Share this post


Link to post

Release 2016.01.28 is now available.  There are two changes.

- Mount points are now limited to /mnt/disks/.  If you change the mount point name it will be set to /mnt/disks/ regardless of whether or not you try to change the mount point directory.  You can just enter the name of the mount point you want and it will be set to /mnt/disks/.

 

What happens if I upgrade but don't have the mount points in the disks folder? Will it try and remap them?

 

No.  Only if you make a change to the mount point.

 

But it shows them as being changed.....  I use the ZFS plugin and its setup to mount "appdisk" in /mnt (/mnt/appdisk) - but the plugin is displaying the path wrong - /mnt/disks/appdisk

 

Myk

 

The mount point is not changed until you edit it by clicking on it when the drive is unmounted.  It appears you may have edited the mount points.

Share this post


Link to post

@dlandon,

 

i just found this plugin and i think it would be usefull to me, however, i'm left with some questions:

 

[*]Would this allow me to export the disk with NFS?

[*]Is it possible to create a Raid10 array with 4 disks outside the array?

 

I would like to reduce my 24/7 running systems, and therefore it would be extremely useful if I could create on the same box UnRaid and a fast Raid10 array for VM's and TV Recordings (recording multiple HD streams and watching live HD streams at the same time is just too much for a single HDD)

 

Thanks in advance.

Share this post


Link to post

@dlandon,

 

i just found this plugin and i think it would be usefull to me, however, i'm left with some questions:

 

[*]Would this allow me to export the disk with NFS?

[*]Is it possible to create a Raid10 array with 4 disks outside the array?

 

I would like to reduce my 24/7 running systems, and therefore it would be extremely useful if I could create on the same box UnRaid and a fast Raid10 array for VM's and TV Recordings (recording multiple HD streams and watching live HD streams at the same time is just too much for a single HDD)

 

Thanks in advance.

 

1. Yes.

2. Don't know.

Share this post


Link to post

[*]Would this allow me to export the disk with NFS?

[*]Is it possible to create a Raid10 array with 4 disks outside the array?

There is no support for RAID 10 in unRAID, but if you have a disk controller that presents the RAID array to unRAID as if it is a single large disk (i.e. the RAID 10 aspects are all handled at the hardware level) then it will work.

Share this post


Link to post

@dlandon,

 

i just found this plugin and i think it would be usefull to me, however, i'm left with some questions:

 

[*]Would this allow me to export the disk with NFS?

[*]Is it possible to create a Raid10 array with 4 disks outside the array?

 

I would like to reduce my 24/7 running systems, and therefore it would be extremely useful if I could create on the same box UnRaid and a fast Raid10 array for VM's and TV Recordings (recording multiple HD streams and watching live HD streams at the same time is just too much for a single HDD)

 

Thanks in advance.

How many streams are you recording simultaneously?

How many can you do recording to the array or a single disk outside the array?

 

I'm not sure how many recordings I've had, but I would think up to 6 without any problems. That is to the array, but no parity.

Share this post


Link to post

Is there a way to prevent a disk from powering down?

 

The plugin sets a 15 minute idle time with 'hdparm -S180' to the device when it is mounted.  You could issue a no idle time to the device in the script when it is mounted with 'hdparm -S0'.  This tells the drive to never go to the idle (spin down) mode.  The script will look like this:

#!/bin/bash
PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin
## Available variables: 
# AVAIL      : available space
# USED       : used space
# SIZE       : partition size
# SERIAL     : disk serial number
# ACTION     : if mounting, ADD; if unmounting, REMOVE
# MOUNTPOINT : where the partition is mounted
# FSTYPE     : partition filesystem
# LABEL      : partition label
# DEVICE     : partition device, e.g /dev/sda1
# OWNER      : "udev" if executed by UDEV, otherwise "user"

case $ACTION in
  'ADD' )
    // do your stuff here
    echo "Added"
    hdparm -S0 $DEVICE 
;;

  'REMOVE' )
    // do your stuff here
    echo "Removed"
  ;;
esac

 

You'll have to do the same thing on unmount if you want the drive to not enter the idle mode.

 

This won't work until the next release because currently the sleep time is set after the drive script is executed.  I changed this to be before the drive script is executed in the next release.

 

Caveat: The drive has to accept the 'hdparm -S0' command.

Share this post


Link to post

Release 2016.01.30 is available.  The major change is the scripts.  All scripts have been put together into one script named rc.unassigned.  This is consistent with unraid standards.

 

If you were using the unassigned devices mount and umount scripts you will have to make some changes.

 

/usr/local/sbin/unassigned_mount [device,'all'] =====> /usr/local/rc.unassigned mount [device,'auto']

 

/usr/local/sbin/unassigned_umount [device,'all'] =====> /usr/local/rc.unassigned umount [device,'auto']

 

'all' has been changed to 'auto' to better describe the operation.  'auto' means auto mounted devices.

 

'all' now means unmount all devices when used with 'rc.unassigned umount all'.

 

I have changed the sample script in the OP to reflect this change.

 

I won't be making any more structural changes, I will only be fixing bugs at this point.  If nothing major comes up in the next week, I'll take this plugin out of beta.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.