Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

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

Featured Replies

Messing with the mount and unmount script and believe I found a bug.

 

Enable a disk script, run it (it can be simple just echo $LOGFILE and $SERIAL. in my case it echos "/tmp/unassigned.devices/$LABEL.log" and $SERIAL

 

In the GUI the Script Log doesn't show anything. But, the log file seems to be written to"/tmp/$SERIAL.log"

  • Replies 11.9k
  • Views 2.1m
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • It's that self healing feature I built into UD.  It just fixes itself.

  • New release of UD.  Changes: When changing the mount point (which is also the share name), the mount point is checked for a duplicate of a user share or another UD device.  Samba cannot handle

  • Major new release of UD: "Where are the switches?"  The "Pass Through", "Read Only", "Automount", and "Share" switches have been moved to a new Edit Settings dialog.  This is also where the sc

Posted Images

  • Author
15 hours ago, shaunsund said:

Messing with the mount and unmount script and believe I found a bug.

 

Enable a disk script, run it (it can be simple just echo $LOGFILE and $SERIAL. in my case it echos "/tmp/unassigned.devices/$LABEL.log" and $SERIAL

 

In the GUI the Script Log doesn't show anything. But, the log file seems to be written to"/tmp/$SERIAL.log"

The $LOGFILE variable is the user log that your script writes to.  For example:

echo "Write to the log" > $LOGFILE

The "/tmp/$SERIAL.log" is used by UD and generally doesn't have anything of importance.  This is done so the user script log is only the information relating to the running of the script and not any UD information.

2 hours ago, dlandon said:

The $LOGFILE variable is the user log that your script writes to.  For example:


echo "Write to the log" > $LOGFILE

The "/tmp/$SERIAL.log" is used by UD and generally doesn't have anything of importance.  This is done so the user script log is only the information relating to the running of the script and not any UD information. 

Ah, in retrospect that makes sense. But should the Log icon on the main UD page show the /tmp/$SERIAL.log? I was getting the /tmp/$SERIAL.log fill with data from a script, but never saw its contents in the GUI.

hello

i have tried something else for my issue with 4TB seagate passing through USB: i have plugged it into a RAID adapter as single volume. 

Then U.D. could see my disk without any issue. I have then formatted it with XFS thanks to U.D. => works well.

I was hoping i could see it later while connected in an USB enclosure.

But no chance... issue is different that time, but U.D. is still unable to mount this drive (only when connected through USB. Please note i have tried with 2 different USB enclosures => same bad result...)

 

any advise?

 

///

Jul 30 18:59:23 Tower kernel: usb 1-1.1: USB disconnect, device number 5
Jul 30 18:59:23 Tower unassigned.devices: benchmark: shell_exec(/usr/bin/timeout 20 /bin/df '/dev/sdp1' --output=size,used,avail|/bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took 19.064277s.
Jul 30 18:59:23 Tower kernel: sd 10:0:0:0: [sdp] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
Jul 30 18:59:23 Tower kernel: sd 10:0:0:0: [sdp] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 e8 d0 00 44 00 00 00 02 00 00
Jul 30 18:59:23 Tower kernel: print_req_error: I/O error, dev sdp, sector 3905945668
Jul 30 18:59:23 Tower kernel: XFS (sdp1): metadata I/O error: block 0xe8d00004 ("xlog_iodone") error 5 numblks 64
Jul 30 18:59:23 Tower kernel: XFS (sdp1): xfs_do_force_shutdown(0x2) called from line 1232 of file fs/xfs/xfs_log.c. Return address = 0xffffffffa02b5c11
Jul 30 18:59:23 Tower kernel: XFS (sdp1): Log I/O Error Detected. Shutting down filesystem
Jul 30 18:59:23 Tower kernel: XFS (sdp1): Please umount the filesystem and rectify the problem(s)
Jul 30 18:59:23 Tower unassigned.devices: benchmark: shell_exec(/usr/bin/timeout 20 /bin/df '/dev/sdp1' --output=size,used,avail|/bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took 18.465126s.
Jul 30 18:59:23 Tower unassigned.devices: benchmark: shell_exec(/usr/bin/timeout 20 /bin/df '/dev/sdp1' --output=size,used,avail|/bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took 18.477993s.
Jul 30 18:59:23 Tower unassigned.devices: benchmark: shell_exec(/usr/bin/timeout 20 /bin/df '/dev/sdp1' --output=size,used,avail|/bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took 17.152884s.
Jul 30 18:59:23 Tower kernel: usb 1-1.1: new high-speed USB device number 6 using ehci-pci
Jul 30 18:59:23 Tower kernel: usb 1-1.1: device descriptor read/64, error -71
Jul 30 18:59:23 Tower kernel: usb 1-1.1: device descriptor read/64, error -71
Jul 30 18:59:24 Tower kernel: usb 1-1.1: new high-speed USB device number 7 using ehci-pci
Jul 30 18:59:24 Tower kernel: usb 1-1.1: device descriptor read/64, error -71
Jul 30 18:59:24 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Jul 30 18:59:24 Tower kernel: usb 1-1.1: device descriptor read/64, error -71
Jul 30 18:59:24 Tower kernel: usb 1-1-port1: attempt power cycle
Jul 30 18:59:25 Tower kernel: usb 1-1.1: new high-speed USB device number 8 using ehci-pci
Jul 30 18:59:25 Tower kernel: usb 1-1.1: device not accepting address 8, error -71
Jul 30 18:59:25 Tower kernel: usb 1-1.1: new high-speed USB device number 9 using ehci-pci
Jul 30 18:59:26 Tower kernel: usb 1-1.1: device not accepting address 9, error -71
Jul 30 18:59:26 Tower kernel: usb 1-1-port1: unable to enumerate USB device

Jul 30 19:03:12 Tower kernel: usb 1-1.1: new high-speed USB device number 10 using ehci-pci
Jul 30 19:03:12 Tower kernel: usb-storage 1-1.1:1.0: USB Mass Storage device detected
Jul 30 19:03:12 Tower kernel: usb-storage 1-1.1:1.0: Quirks match for vid 152d pid 2329: 8020
Jul 30 19:03:12 Tower kernel: scsi host11: usb-storage 1-1.1:1.0
Jul 30 19:03:13 Tower kernel: scsi 11:0:0:0: Direct-Access ST4000DM 004-2CV104 PQ: 0 ANSI: 2 CCS
Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: Attached scsi generic sg15 type 0
Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] Very big device. Trying to use READ CAPACITY(16).
Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] Write Protect is off
Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] Mode Sense: 28 00 00 00
Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] No Caching mode page found
Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] Assuming drive cache: write through
Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] Very big device. Trying to use READ CAPACITY(16).
Jul 30 19:03:13 Tower kernel: GPT:Primary header thinks Alt. header is not at the end of the disk.
Jul 30 19:03:13 Tower kernel: GPT:7811891199 != 7814037167
Jul 30 19:03:13 Tower kernel: GPT:Alternate GPT header not at the end of the disk.
Jul 30 19:03:13 Tower kernel: GPT:7811891199 != 7814037167
Jul 30 19:03:13 Tower kernel: GPT: Use GNU Parted to correct GPT errors.
Jul 30 19:03:13 Tower kernel: sdq: sdq1
Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] Very big device. Trying to use READ CAPACITY(16).
Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] Attached SCSI disk
Jul 30 19:03:14 Tower unassigned.devices: Adding disk '/dev/sdq1'...
Jul 30 19:03:14 Tower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdq1' '/mnt/disks/ST4000DM004-2CV104_ZFN15573'
Jul 30 19:03:14 Tower kernel: XFS (sdq1): Filesystem has duplicate UUID 4df411d4-f5e6-402d-85e3-463d6d5e3101 - can't mount
Jul 30 19:03:14 Tower unassigned.devices: Mount of '/dev/sdq1' failed. Error message: mount: /mnt/disks/ST4000DM004-2CV104_ZFN15573: wrong fs type, bad option, bad superblock on /dev/sdq1, missing codepage or helper program, or other error. 
Jul 30 19:03:14 Tower unassigned.devices: Partition 'ST4000DM004-2CV104_ZFN15573' could not be mounted...
Jul 30 19:03:17 Tower sSMTP[15643]: Creating SSL connection to host
Jul 30 19:03:17 Tower sSMTP[15643]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256

Jul 30 19:03:20 Tower sSMTP[15643]: Sent mail for [email protected] (221 2.0.0 closing connection y191-v6sm108132wmy.4 - gsmtp) uid=0 username=root outbytes=880
Jul 30 19:03:46 Tower kernel: usb 1-1.1: reset high-speed USB device number 10 using ehci-pci
Jul 30 19:03:46 Tower kernel: usb 1-1.1: device descriptor read/64, error -71
Jul 30 19:03:46 Tower kernel: usb 1-1.1: device descriptor read/64, error -71
Jul 30 19:03:46 Tower kernel: usb 1-1.1: reset high-speed USB device number 10 using ehci-pci
Jul 30 19:03:46 Tower kernel: usb 1-1.1: device descriptor read/64, error -71
Jul 30 19:03:46 Tower kernel: usb 1-1.1: device descriptor read/64, error -71
Jul 30 19:03:46 Tower kernel: usb 1-1.1: reset high-speed USB device number 10 using ehci-pci

Jul 30 19:03:47 Tower kernel: usb 1-1.1: device not accepting address 10, error -71
Jul 30 19:03:47 Tower kernel: usb 1-1.1: reset high-speed USB device number 10 using ehci-pci
Jul 30 19:03:47 Tower kernel: usb 1-1.1: device not accepting address 10, error -71
Jul 30 19:03:47 Tower kernel: usb 1-1.1: USB disconnect, device number 10
Jul 30 19:03:47 Tower kernel: usb 1-1.1: new high-speed USB device number 11 using ehci-pci
Jul 30 19:03:48 Tower kernel: usb 1-1.1: device descriptor read/64, error -71
Jul 30 19:03:48 Tower kernel: usb 1-1.1: device descriptor read/64, error -71
Jul 30 19:03:48 Tower kernel: usb 1-1.1: new high-speed USB device number 12 using ehci-pci
Jul 30 19:03:48 Tower kernel: usb 1-1.1: device descriptor read/64, error -71
Jul 30 19:03:48 Tower kernel: usb 1-1.1: device descriptor read/64, error -71
Jul 30 19:03:48 Tower kernel: usb 1-1-port1: attempt power cycle

Jul 30 19:03:49 Tower kernel: usb 1-1.1: new high-speed USB device number 13 using ehci-pci
Jul 30 19:03:49 Tower kernel: usb 1-1.1: device not accepting address 13, error -71
Jul 30 19:03:49 Tower kernel: usb 1-1.1: new high-speed USB device number 14 using ehci-pci
Jul 30 19:03:50 Tower kernel: usb 1-1.1: device not accepting address 14, error -71
Jul 30 19:03:50 Tower kernel: usb 1-1-port1: unable to enumerate USB device
 

tower-diagnostics-20180730-1908.zip

Edited by pegounet
email info deleted

For the Unassigned Drive plugin, can you selectively choose which shares to export and which shares to hide? It seems to be currently a global option?

 

Thanks.

1 minute ago, coolspot said:

For the Unassigned Drive plugin, can you selectively choose which shares to export and which shares to hide? It seems to be currently a global option?

 

Thanks.

Unassigned drives is independent of standard unraid User shares.     You have to sim-ly decide whether to share the whole device or not.

Just now, itimpi said:

Unassigned drives is independent of standard unraid User shares.     You have to sim-ly decide whether to share the whole device or not.

 

 

I don't have that option in my Unassigned Share screen - I can mount or unmount the NFS Share, auto mount, Log, and Script.

 

I don't have the ability to mount the drive locally and share or not share.

 

For example, if I have 10 NFS mounts, I may only want to share some and not others.

 

I don't think this is possible right - it's either share everything or nothing?

Would still be super helpful if i could see all my unused unassigned scsi SAS drives that are just chilling waiting to be added... :(

Hi in a future update, if possible could you add the read/write info like the array drives please??

  • Author
1 hour ago, DZMM said:

Hi in a future update, if possible could you add the read/write info like the array drives please??

There is not currently enough room to add the read/write info.  I won't redesign UD since LT has indicated that in will be eventually included in the base unRAID.  They can add that feature.

 

I really don't have the time or any interest in UD improvements.  I will do maintenance only.

Edited by dlandon

1 hour ago, dlandon said:

There is not currently enough room to add the read/write info.  I won't redesign UD since LT has indicated that in will be eventually included in the base unRAID.  They can add that feature.

 

I really don't have the time or any interest in UD improvements.  I will do maintenance only.

Thanks - it'll be good for LT to take it on as I agree it's become core functionality like the rest of your plugins

Hi all, i am having an issue with unassigned devices.

 

system:

-Unraid v 6.5.3

-Unassigned devices v 2018.06.01a

 

i have a WD 500gb usb external hard drive that i have plugged into my server to copy files into my array.  when i plug the usb into windows i can see the files through file explorer no problem, however when i plug the usb into the server, unassigned devices (and dolphin) show nothing on the disk.  i have formated the usb twice and tried test files, still nothing shows.  I forgot to mention that when i plug the usb into the server it auto mounts, and i cannot unmount the device.  i hope you folks can help, i am a newb so bare with me a little bit!

unassigned devices issue 1.PNG

unassigned devices issue 2.PNG

Hi,

I have 2 towers with movies on them

On tower2 I am running the binhex-Radarr docker and have added in my /media (which points to my /mnt/user/Movies share on tower2)

I also want to add a link in the docker to point to my /mnt/user/Movies share on tower1

 

So I thought I would setup a remote smb share in unassigned devices plugin. I created the map and named it TOWER_Movies

That is fine and it seems to show my movies on tower1

This mount is /mnt/disks/TOWER_Movies on tower2

I then created a /media2 link in the binhex-Radarr docker and pointed it to /mnt/

In Radarr I bulk import and add the /media2/disks/TOWER_Movie folder

This seems to work ok and it found the movies on tower1 and added them to Radarr

 

A problem I am seeing is if I update a movie that exists on the TOWER_Movies share, it seems to update the /mnt/disks/TOWER_Movies share and put the movie there  (even though it is not on the Movies share on Tower1) but it seems to also exist on tower2. Plex scans the change and finds 2 copies of the movie and adds them both. One link points to /media/ and the other to /media2/disks/TOWER_Movies

 

Am I doing this completely wrong? Is there a better way?

 

Thanks

  • Author
7 hours ago, beaner said:

Hi all, i am having an issue with unassigned devices.

 

system:

-Unraid v 6.5.3

-Unassigned devices v 2018.06.01a

 

i have a WD 500gb usb external hard drive that i have plugged into my server to copy files into my array.  when i plug the usb into windows i can see the files through file explorer no problem, however when i plug the usb into the server, unassigned devices (and dolphin) show nothing on the disk.  i have formated the usb twice and tried test files, still nothing shows.  I forgot to mention that when i plug the usb into the server it auto mounts, and i cannot unmount the device.  i hope you folks can help, i am a newb so bare with me a little bit!

unassigned devices issue 1.PNG

unassigned devices issue 2.PNG

Turn off the USB auto mount: Set "Settings->Unassigned Devices->Auto Mount USB Devices?" to "No".

 

Reboot your server and try again.  If it persists, post your diagnostics.

  • Author
16 minutes ago, Blade said:

Hi,

I have 2 towers with movies on them

On tower2 I am running the binhex-Radarr docker and have added in my /media (which points to my /mnt/user/Movies share on tower2)

I also want to add a link in the docker to point to my /mnt/user/Movies share on tower1

 

So I thought I would setup a remote smb share in unassigned devices plugin. I created the map and named it TOWER_Movies

That is fine and it seems to show my movies on tower1

This mount is /mnt/disks/TOWER_Movies on tower2

I then created a /media2 link in the binhex-Radarr docker and pointed it to /mnt/

In Radarr I bulk import and add the /media2/disks/TOWER_Movie folder

This seems to work ok and it found the movies on tower1 and added them to Radarr

 

A problem I am seeing is if I update a movie that exists on the TOWER_Movies share, it seems to update the /mnt/disks/TOWER_Movies share and put the movie there  (even though it is not on the Movies share on Tower1) but it seems to also exist on tower2. Plex scans the change and finds 2 copies of the movie and adds them both. One link points to /media/ and the other to /media2/disks/TOWER_Movies

 

Am I doing this completely wrong? Is there a better way?

 

Thanks

Your configuration is extremely confusing and I don't follow it at all.  Sounds like you have a circular configuration.  Simplify the setup.

Edited by dlandon

I thank you for taking the time to look at this....

OK - my bad - let me start slow

Hopefully I can explain it better.

Please let me know which parts do not make sense and I will try and clarify

Here we go...

 

I have 2 unraid towers (TOWER1 and TOWER2)

I have a Movies share on both towers

All dockers are running on TOWER2

I have the official PlexMediaServer and binhex-Radarr dockers running

 

In the Radarr docker I created a link (/media) that points to /mnt/user/Movies on TOWER2

I then imported all the movies on TOWER2 into the Radarr docker - that works fine

Plex also has a /media link that points to /mnt/user/Movies on TOWER2 - movies show up fine in Plex

 

I now wanted to add the movies from TOWER1

So under UD I created a remote SMB share to TOWER1 Movies share and called it TOWER_Movies

My assumption is that this creates a path on TOWER2 of /mnt/disks/TOWER_Movies (which should point to all my movies on TOWER1)

Now I want to add the TOWER1 movies to Radarr and Plex

I created another docker link in each docker called /media2 and pointed it to /mnt/disks/TOWER_Movies

I then added that /media2 path as a monitored folder to both Radarr and Plex - this seems to add all of the movies from TOWER1 to both dockers

 

OK here is where I see my problem... in Radarr say I see a new version of a movie that exists on TOWER1 which is my SMB remote share of /mnt/disks/TOWER_Movies

When I import that new movie into Radarr (after it is done downloading), the movie shows up in the /mnt/disks/TOWER_Movies share but I do not see it on my actual Movies share on TOWER1. I also seem to see it on my Movies share on TOWER2

So when plex sees this new movie, it seems to have two movie files for the movie in plex. One points to the movie on TOWER2 and the other points to the movie on /mnt/disks/TOWER_Movies

 

I really hope this makes sense or maybe I am not adding remote SMB shares properly - I am new to dockers

 

Edited by Blade

I'm experiencing an either inability to access unassigned devices or extremely long timeout when an smb device is set to mount but no longer active on the network. is there a way to lower what I assume is the timeout?

I'm having a small issue with NFS shares. I have two unraid servers, one has several shares via NFS and I'm trying to use unassigned devices on the 2nd server to mount those shares. Mounting works perfectly fine, but automounting does not. On the 2nd server, when it boots the array starts, but the NFS shares never get automounted. If I click mount, they mount without any issue at all.

 

Is there a log I could look for to see if it attempted an automount and got an error somewhere? Something I'm missing?

  • Author
11 hours ago, glave said:

I'm having a small issue with NFS shares. I have two unraid servers, one has several shares via NFS and I'm trying to use unassigned devices on the 2nd server to mount those shares. Mounting works perfectly fine, but automounting does not. On the 2nd server, when it boots the array starts, but the NFS shares never get automounted. If I click mount, they mount without any issue at all.

 

Is there a log I could look for to see if it attempted an automount and got an error somewhere? Something I'm missing?

Look at the system log.  You probably have a timing situation.  Something is not ready when the server starts, but is available when you mount manually.

2 hours ago, dlandon said:

Look at the system log.  You probably have a timing situation.  Something is not ready when the server starts, but is available when you mount manually.

I found it in the logs, but not sure why it's happening. I'm getting the error that the remote server is offline and the share cannot be mounted. That's odd because I can see in the logs that the network is definitely up, in fact a few seconds after the errors, I can see ntpd messages from it syncing. I did a few reboot tests and the results seem consistent as well, it just doesn't make much sense.

 

Is it possible to maybe delay the mount a little longer, or possible mount it from userscripts instead?

  • Author
8 hours ago, glave said:

I found it in the logs, but not sure why it's happening. I'm getting the error that the remote server is offline and the share cannot be mounted. That's odd because I can see in the logs that the network is definitely up, in fact a few seconds after the errors, I can see ntpd messages from it syncing. I did a few reboot tests and the results seem consistent as well, it just doesn't make much sense.

 

Is it possible to maybe delay the mount a little longer, or possible mount it from userscripts instead?

Read the help on the UD webpage and add the autostart command to User Scripts to start when the array is started.  It will mount any automount devices that aren't mounted.  Any devices already mounted will not be affected.

  • 2 weeks later...

I just added an NVME drive in my unassigned devices. Will unRAID's TRIM schedule pick it up automatically?

1 hour ago, remati said:

I just added an NVME drive in my unassigned devices. Will unRAID's TRIM schedule pick it up automatically?

No.

 

You can add a script to do this at regular intervals via User Scripts.

I am using unraid to smb mount a share from my solus linux desktop. It was working fine but this morning I'm getting a stale file handle? Every post I've read deals with NFS but I am not using NFS, just samba.

 

I've tried unmounting and remounting the share but it still gives the same error

 

/bin/ls: cannot access 'solus': Stale file handle

Edited by ffhelllskjdje

  • Author
3 hours ago, ffhelllskjdje said:

I am using unraid to smb mount a share from my solus linux desktop. It was working fine but this morning I'm getting a stale file handle? Every post I've read deals with NFS but I am not using NFS, just samba.

 

I've tried unmounting and remounting the share but it still gives the same error

 

/bin/ls: cannot access 'solus': Stale file handle

Do you have NFS support enabled in Settings->Unassigned Devices?

 

Post diagnostics.

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.