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

dlandon · February 1

6 hours ago, wacko37 said:

Any ideas? Has something changed of recent?

Yes, I made a change that broke the script execution. If you go to the Tools->PHP Settings, you will see a php error. It will be fixed in the next release.

wacko37 · February 1

1 hour ago, dlandon said:

Yes, I made a change that broke the script execution. If you go to the Tools->PHP Settings, you will see a php error. It will be fixed in the next release.

As always @dlandon thankyou for all that you do for the Unraid community.

I never knew Tools->PHP existed until now.... Always learning.

I look forward to the next release, thanks

dlandon · February 1

27 minutes ago, wacko37 said:

I never knew Tools->PHP existed until now.... Always learning.

When Unraid updated to PHP 8.0, we had to track down all the warnings in php. Php 8.0 throws warnings about everything now that it used to ignore.

27 minutes ago, wacko37 said:

I look forward to the next release, thanks

It should be ready soon. I've been rewriting a lot of old code that is difficult to read and maintain, and finding a few code mistakes as I do that. I have to test it all.

wacko37 · February 1

16 minutes ago, dlandon said:

When Unraid updated to PHP 8.0, we had to track down all the warnings in php. Php 8.0 throws warnings about everything now that it used to ignore.

I have attached a screenshot of the PHP logs, hope it helps somewhat.

Edited February 1 by wacko37
remove details from image

dlandon · February 1

2 minutes ago, wacko37 said:

I have attached a screenshot of the PHP logs, hope it helps somewhat.

I was able to reproduce the error and that's how I found it - from the log.

TheFullTimer · February 2

Just wanted to pop in here. I have a file named mounts which was created today in the `/mnt` directory around the time I updated Unassigned Devices. Would this be related to the two updates today (02-02-2024 EST)? If so, keep or delete?

Edited February 2 by TheFullTimer

dlandon · February 2

29 minutes ago, TheFullTimer said:

Just wanted to pop in here. I have a file named mounts which was created today in the `/mnt` directory around the time I updated Unassigned Devices. Would this be related to the two updates today (02-02-2024 EST)? If so, keep or delete?

Be sure to have the latest version 2024.02.02a and that file will no longer be created. It's harmless and will go away after a reboot, or if your OCD kicks in, just do a 'rm /mnt/mounts'.

dlandon · February 2

I encourage anyone holding back on updating UD to update to the latest version. Several things have changed that I believe are worth updating now:

Cut down on the number of system command calls used to get mount status, read only status, and file system type of a disk device.
Cut down on code that was redundant and being executed in the wrong places wasting time.
Cached some information like mount status to make checking for mounted/unmounted status and read only a lot faster.
Removed the nchan messaging to be sure UD does not interfere with core Unraid. Changed to a Java Script timer.
Reworked the mount/unmount status on the 'Mount' button so it would better show mounting and unmounting status.
Fixed a lot of issues with Device Settings that didn't work properly - like being able to choose a pre-existing device script and delete not deleting the proper script file.
Reworked the remote share online check to verify that the SMB or NFS port is open to the server. Ping is no longer used to do this. Now you will see the online status not just on the server, but on shares. For example, a server is online and SMB is enabled but NFS is turned off, any SMB shares on that server will show online, but the NFS shares will show offline.
Improved the server scan to be faster and better at finding servers on the LAN.
Fixed a situation where the scan for servers would go out of control and peg CPUs in an endless scan.
Added "vfs object = dirsort" to help with SMB listings in network listings.

The bottom line is I believe you will find UD a lot more responsive and operation in general a lot cleaner.

EDIT: Feedback encouraged as I don't hear much about things that aren't bugs.

wacko37 · February 2

@dlandon Thanks for the update mate, Device Scripts are working as per normal.

nukecat · February 3

image.png.73020629cbb37115c9194802981ec16e.png

how do I delete this 「user-pool.Endurance」 share?I created it with old vsersion of UD

dlandon · February 3

8 hours ago, nukecat said:

how do I delete this 「user-pool.Endurance」 share?I created it with old vsersion of UD

What does the GUI show?

thedman · February 3

I have a strange issue that has started happening the last few months, I always update unraid and plugins weekly. I have a 12 TB usd drive that I use through unassigned devices and use as an on system backup to my main media array. It seems to mount fine on new boot or reboot to sda1, but after some time it tries to remount to sdi1. I am not sure what causes this. Then it fails and just shows a greyed out reboot icon in the plugin. Rebooting fixes again for a while but then it happens again. Attached are the logs from the mounts. Just looking for some assistance on where to look to try and fix. Thanks.

--------------------------------------

text error warn system array login

Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB)
Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Mode Sense: 2f 00 00 00
Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 1 09:52:52 dserver kernel: sda: sda1
Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 1 09:53:10 dserver emhttpd: TOSHIBA_MG07ACA12TE_2040A0BQFDUG (sda) 512 23437770752
Feb 1 09:53:10 dserver emhttpd: read SMART /dev/sda
Feb 1 09:53:22 dserver unassigned.devices: Mounting partition 'sda1' at mountpoint '/mnt/disks/Backupdp'...
Feb 1 09:53:22 dserver unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime '/dev/sda1' '/mnt/disks/Backupdp'
Feb 1 09:53:22 dserver kernel: XFS (sda1): Mounting V5 Filesystem
Feb 1 09:53:23 dserver kernel: XFS (sda1): Starting recovery (logdev: internal)
Feb 1 09:53:23 dserver kernel: XFS (sda1): Ending recovery (logdev: internal)
Feb 1 09:53:23 dserver unassigned.devices: Successfully mounted '/dev/sda1' on '/mnt/disks/Backupdp'.

** Press ANY KEY to close this window **

After about 45 minutes....

text error warn system array login

Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] Very big device. Trying to use READ CAPACITY(16).
Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB)
Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] 4096-byte physical blocks
Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] Write Protect is off
Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] Mode Sense: 2f 00 00 00
Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 1 13:07:08 dserver kernel: sdi: sdi1
Feb 1 13:07:08 dserver kernel: sd 9:0:0:0: [sdi] Attached SCSI disk
Feb 1 13:07:10 dserver unassigned.devices: Error: Device '/dev/sdi1' mount point 'Backupdp' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb 1 13:08:57 dserver kernel: sd 9:0:0:0: [sdi] Synchronizing SCSI cache
Feb 1 13:08:57 dserver kernel: sd 9:0:0:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Very big device. Trying to use READ CAPACITY(16).
Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB)
Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] 4096-byte physical blocks
Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Write Protect is off
Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Mode Sense: 2f 00 00 00
Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 1 13:08:58 dserver kernel: sdi: sdi1
Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Attached SCSI disk
Feb 1 13:09:01 dserver unassigned.devices: Error: Device '/dev/sdi1' mount point 'Backupdp' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb 1 14:03:39 dserver kernel: sd 9:0:0:0: [sdi] Synchronizing SCSI cache
Feb 1 14:03:39 dserver kernel: sd 9:0:0:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] Very big device. Trying to use READ CAPACITY(16).
Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB)
Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] 4096-byte physical blocks
Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] Write Protect is off
Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] Mode Sense: 2f 00 00 00
Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 1 14:03:51 dserver kernel: sdi: sdi1
Feb 1 14:03:51 dserver kernel: sd 9:0:0:0: [sdi] Attached SCSI disk
Feb 1 14:03:52 dserver unassigned.devices: Error: Device '/dev/sdi1' mount point 'Backupdp' - name is reserved, used in the array or a pool, or by an unassigned device.

thedman · February 3

I think it eventually must fill up some logs, and the entire unraid system becomes unassailable, the last thing on the console says file system error shutdown on sdi1, and I can't do anything but to hard power off.

dlandon · February 3

6 minutes ago, thedman said:

I have a strange issue that has started happening the last few months, I always update unraid and plugins weekly. I have a 12 TB usd drive that I use through unassigned devices and use as an on system backup to my main media array. It seems to mount fine on new boot or reboot to sda1, but after some time it tries to remount to sdi1. I am not sure what causes this. Then it fails and just shows a greyed out reboot icon in the plugin. Rebooting fixes again for a while but then it happens again. Attached are the logs from the mounts. Just looking for some assistance on where to look to try and fix. Thanks.

--------------------------------------

text error warn system array login

Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB)
Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Mode Sense: 2f 00 00 00
Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 1 09:52:52 dserver kernel: sda: sda1
Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 1 09:53:10 dserver emhttpd: TOSHIBA_MG07ACA12TE_2040A0BQFDUG (sda) 512 23437770752
Feb 1 09:53:10 dserver emhttpd: read SMART /dev/sda
Feb 1 09:53:22 dserver unassigned.devices: Mounting partition 'sda1' at mountpoint '/mnt/disks/Backupdp'...
Feb 1 09:53:22 dserver unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime '/dev/sda1' '/mnt/disks/Backupdp'
Feb 1 09:53:22 dserver kernel: XFS (sda1): Mounting V5 Filesystem
Feb 1 09:53:23 dserver kernel: XFS (sda1): Starting recovery (logdev: internal)
Feb 1 09:53:23 dserver kernel: XFS (sda1): Ending recovery (logdev: internal)
Feb 1 09:53:23 dserver unassigned.devices: Successfully mounted '/dev/sda1' on '/mnt/disks/Backupdp'.

** Press ANY KEY to close this window **

After about 45 minutes....

text error warn system array login

Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] Very big device. Trying to use READ CAPACITY(16).
Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB)
Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] 4096-byte physical blocks
Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] Write Protect is off
Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] Mode Sense: 2f 00 00 00
Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 1 13:07:08 dserver kernel: sdi: sdi1
Feb 1 13:07:08 dserver kernel: sd 9:0:0:0: [sdi] Attached SCSI disk
Feb 1 13:07:10 dserver unassigned.devices: Error: Device '/dev/sdi1' mount point 'Backupdp' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb 1 13:08:57 dserver kernel: sd 9:0:0:0: [sdi] Synchronizing SCSI cache
Feb 1 13:08:57 dserver kernel: sd 9:0:0:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Very big device. Trying to use READ CAPACITY(16).
Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB)
Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] 4096-byte physical blocks
Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Write Protect is off
Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Mode Sense: 2f 00 00 00
Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 1 13:08:58 dserver kernel: sdi: sdi1
Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Attached SCSI disk
Feb 1 13:09:01 dserver unassigned.devices: Error: Device '/dev/sdi1' mount point 'Backupdp' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb 1 14:03:39 dserver kernel: sd 9:0:0:0: [sdi] Synchronizing SCSI cache
Feb 1 14:03:39 dserver kernel: sd 9:0:0:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] Very big device. Trying to use READ CAPACITY(16).
Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB)
Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] 4096-byte physical blocks
Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] Write Protect is off
Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] Mode Sense: 2f 00 00 00
Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 1 14:03:51 dserver kernel: sdi: sdi1
Feb 1 14:03:51 dserver kernel: sd 9:0:0:0: [sdi] Attached SCSI disk
Feb 1 14:03:52 dserver unassigned.devices: Error: Device '/dev/sdi1' mount point 'Backupdp' - name is reserved, used in the array or a pool, or by an unassigned device.

Please post your complete diagnostics. It sounds like the disk is going offline and then back online. That's why it is showing 'Reboot' on the mount button. Is it USB?

thedman · February 3

It is usb. I will post diagnostics. It had been running fine for over a year, so maybe some new spin down or power saving on the drive?

thedman · February 3

Diagnostics attached.

dserver-diagnostics-20240203-1210.zip

dlandon · February 3

2 hours ago, thedman said:

Diagnostics attached.

dserver-diagnostics-20240203-1210.zip 122.4 kB · 0 downloads

There is a problem with your disk:

Feb  3 12:10:11 dserver unassigned.devices: Mounting partition 'sdh1' at mountpoint '/mnt/disks/Backupdp'...
Feb  3 12:10:11 dserver unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime '/dev/sdh1' '/mnt/disks/Backupdp'
Feb  3 12:10:11 dserver kernel: XFS (sdh1): Mounting V5 Filesystem
Feb  3 12:10:11 dserver kernel: XFS (sdh1): Starting recovery (logdev: internal)
Feb  3 12:10:11 dserver kernel: XFS (sdh1): Ending recovery (logdev: internal)
Feb  3 12:10:12 dserver unassigned.devices: Successfully mounted '/dev/sdh1' on '/mnt/disks/Backupdp'.
Feb  3 12:10:12 dserver unassigned.devices: Warning: Unassigned Devices are not set to be shared with SMB.
Feb  3 12:10:16 dserver kernel: usb 2-4: USB disconnect, device number 2
Feb  3 12:10:16 dserver kernel: device offline error, dev sdh, sector 10737746976 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2
Feb  3 12:10:16 dserver kernel: XFS (sdh1): log I/O error -19
Feb  3 12:10:16 dserver kernel: XFS (sdh1): Filesystem has been shut down due to log error (0x2).
Feb  3 12:10:16 dserver kernel: XFS (sdh1): Please unmount the filesystem and rectify the problem(s).

It mounts and then shuts itself off and UD does not know that. UD does detect that the device has an issue and marks it "Reboot" because it has detected that it dropped offline.

Click on the check mark by the mount point when the disk is unmounted and see if the disk can be fixed. If not, then maybe one of the disk experts can help you with the problem.

thedman · February 3

Thanks for the help, I will take a look.

When it is unmounted and has the greyed out reboot icon. The check mark does not respond to any clicks. I can only look at the logs. Can I do any unmount/fix via the console? Thanks again for your and anyone else's help.

Edited February 3 by thedman

Goldmaster · February 3

Will you add an option to automatically delete historical devices after a set a period of time, and maybe add a whitelist of devices not to be removed? please.

Akshunhiro · February 3

I just updated but now get this error:

Quote

Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 340

I'm on 6.11.4

EDIT: Fixed by updating to 6.12.6 - Had been putting it off due to TrueNAS ZFS pool but it's working fine

Edited February 4 by Akshunhiro
have teh dumb

nukecat · February 4

14 hours ago, dlandon said:

What does the GUI show?

I solved this problem,kind of,I guess。

I unmounted 「Shares-Pools」and deleted it in main page,and created a new root share named 「user-pool.Endurance」.

Mounted and unmounted this 「user-pool.Endurance」 share then delete it.Now no root shares exist in /mnt/rootshare.

So I guess problem solved and created a new rootshare afterwards

Edited February 4 by nukecat

dlandon · February 4

3 minutes ago, nukecat said:

I solved this problem,kind of,I guess。

I unmounted 「Shares-Pools」and deleted it in main page,and created a new root share named 「user-pool.Endurance」.

Mounted and unmounted this 「user-pool.Endurance」 share then delete it.Now no root shares exist in /mnt/rootshare.

So I guess problem solved and created a new rootshare afterwards

That works. There is an easier way though. Just unmount the root share and rename the mount point to 'user-pool.Endurance'. It would have immediately showed it as mounted.

dlandon · February 4

1 hour ago, Akshunhiro said:

I just updated but now get this error:

I'm on 6.11.4

EDIT: Fixed by updating to 6.12.6 - Had been putting it off due to TrueNAS ZFS pool but it's working fine

That code could not have been executed unless you had the zfs plugin installed. I did make a fix to prevent that php warning just in case someone else runs into it.

RoboWatch · February 5

I was hoping someone could help. Last month I attached an external QNAP RAID box for additional redundancy and let mounted it. Everything was working find until I noticed today that the mount wasn't working.

Clicking on the disk log information opened the terminal and I can see these entries for last night

Feb 4 22:01:00 Tower kernel: sd 14:0:0:0: [sdi] Very big device. Trying to use READ CAPACITY(16).
Feb 4 22:01:00 Tower kernel: sd 14:0:0:0: [sdi] 31255953408 512-byte logical blocks: (16.0 TB/14.6 TiB)
Feb 4 22:01:00 Tower kernel: sd 14:0:0:0: [sdi] 4096-byte physical blocks
Feb 4 22:01:00 Tower kernel: sd 14:0:0:0: [sdi] Write Protect is off
Feb 4 22:01:00 Tower kernel: sd 14:0:0:0: [sdi] Mode Sense: 47 00 00 08
Feb 4 22:01:00 Tower kernel: sd 14:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 4 22:01:00 Tower kernel: sdi: sdi1
Feb 4 22:01:00 Tower kernel: sd 14:0:0:0: [sdi] Attached SCSI disk
Feb 4 22:01:02 Tower unassigned.devices: Error: Device '/dev/sdi1' mount point 'QNAP_TR-004_DISK00' - name is reserved, used in the array or a pool, or by an unassigned device.

My setup is 2x parity and 3x storage, 1x cache and there are no other mounts.

In the terminal I can see the mount point is still in /mnt/disks/QNAP_TR-004_DISK00 but if I try to list it then I get an Input/Output error.

I've attached an image of what's showing in the web console but I'm not sure what to do next to try to force it to unmount and remount. I've tried switching off the external box and then powering it backup but that makes no difference.

I'm avoiding restarting unraid completely at the moment as I figured there should be a way to resolve this. The only recent change was the latest update to the unassigned devices plugin

Kilrah · February 5

3 hours ago, RoboWatch said:

In the terminal I can see the mount point is still in /mnt/disks/QNAP_TR-004_DISK00 but if I try to list it then I get an Input/Output error.

Seems like the unit disconnected unexpectedly without being unmounted, leaving the orphan mount point. You need to reboot to clear it as it says.

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

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

dlandon

dlandon

dlandon

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation