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.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

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

dlandon
in Plugin Support

Featured Replies

  • Author

New release 2016.03.12 to deal with second parity drive showing up as unassigned in 6.2.

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

    Top Posters In This Topic

    Popular Days

    Most Popular Posts

    • dlandon
      dlandon

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

    • dlandon
      dlandon

      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

    • dlandon
      dlandon

      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

    New release 2016.03.12 to deal with second parity drive showing up as unassigned in 6.2.

     

    That was quick!! ????

  • Quote

    where do I get my hands on the 6.2 beta?

  • Quote
    • Author

    New release 2016.03.12 to deal with second parity drive showing up as unassigned in 6.2.

     

    That was quick!! ????

     

    Very easy fix.  I don't have a system that I can set up two parity disks, so let me know if it worked.

  • Quote

    New release 2016.03.12 to deal with second parity drive showing up as unassigned in 6.2.

     

    That was quick!! ????

     

    Very easy fix.  I don't have a system that I can set up two parity disks, so let me know if it worked.

     

    Like a charm. Let me know if you need anything else 6.2 related you need testing. No important data, pure test setup.

     

    Screen_Shot_2016_03_12_at_10_30_35_PM.png

  • Quote
    • Author

    I haven't seen anything else with 6.2 beta yet except that NFS is not starting so remote NFS mounts will not work.

  • Quote

    I am trying to use UD to mount an USB harddrive to copy off some files from to server for backup purposes. unRAID see the USB hard drive get plugged in but it never shows up on UD. Every time I click refresh disks I get the following message: Any thoughts on why it isn't showing up?

     

    Mar 13 20:56:38 Pithos kernel: usb 1-1.6: new high-speed USB device number 12 using ehci-pci
Mar 13 20:56:38 Pithos kernel: usb-storage 1-1.6:1.0: USB Mass Storage device detected
Mar 13 20:56:38 Pithos kernel: scsi host9: usb-storage 1-1.6:1.0
Mar 13 20:56:39 Pithos kernel: scsi 9:0:0:0: Direct-Access WD My Book 1230 1065 PQ: 0 ANSI: 6
Mar 13 20:56:39 Pithos kernel: sd 9:0:0:0: Attached scsi generic sg9 type 0
Mar 13 20:56:39 Pithos kernel: scsi 9:0:0:1: Enclosure WD SES Device 1065 PQ: 0 ANSI: 6
Mar 13 20:56:39 Pithos kernel: sd 9:0:0:0: [sdj] Unit Not Ready
Mar 13 20:56:39 Pithos kernel: sd 9:0:0:0: [sdj] Sense Key : 0x4 [current] 
Mar 13 20:56:39 Pithos kernel: sd 9:0:0:0: [sdj] ASC=0x30 <<vendor>>ASCQ=0x89 
Mar 13 20:56:39 Pithos kernel: scsi 9:0:0:1: Attached scsi generic sg10 type 13
Mar 13 20:57:03 Pithos udevd[2433]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [2485] terminated by signal 7 (Bus error)
Mar 13 20:58:09 Pithos udevd[4029]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4073] terminated by signal 7 (Bus error)
Mar 13 20:58:09 Pithos udevd[4031]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4079] terminated by signal 7 (Bus error)
Mar 13 20:58:09 Pithos udevd[4028]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4072] terminated by signal 7 (Bus error)
Mar 13 20:58:09 Pithos udevd[4036]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4082] terminated by signal 7 (Bus error)
Mar 13 20:58:09 Pithos udevd[4035]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4080] terminated by signal 7 (Bus error)
Mar 13 20:58:09 Pithos udevd[4033]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4077] terminated by signal 7 (Bus error)
Mar 13 20:58:09 Pithos udevd[4034]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4084] terminated by signal 7 (Bus error)
Mar 13 20:58:09 Pithos udevd[4026]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4081] terminated by signal 7 (Bus error)
Mar 13 20:59:39 Pithos kernel: sd 9:0:0:0: timing out command, waited 180s

     

    SCSI Devices

     

    [0:0:0:0]    disk             Patriot Memory   PMAP  /dev/sda 
[1:0:0:0]    disk    ATA      WDC WD40EZRX-00S 0A80  /dev/sdb 
[2:0:0:0]    disk    ATA      TOSHIBA DT01ACA2 ABB0  /dev/sdc 
[3:0:0:0]    disk    ATA      WDC WD50EZRZ-32G 0A80  /dev/sdd 
[4:0:0:0]    disk    ATA      WDC WD7500BPKX-0 1A01  /dev/sde 
[5:0:0:0]    disk    ATA      WDC WD40EZRX-00S 0A80  /dev/sdf 
[6:0:0:0]    disk    ATA      Samsung SSD 840  BB0Q  /dev/sdg 
[7:0:0:0]    disk    ATA      WDC WD10EACS-00Z 1B01  /dev/sdh 
[8:0:0:0]    disk    ATA      WDC WD30EFRX-68E 0A80  /dev/sdi 
[9:0:0:0]    disk    WD       My Book 1230     1065  -        
[9:0:0:1]    enclosu WD       SES Device       1065  -   

     

  • Quote

    Please disregard the above post. Turned out to be the "enclosure" I was trying to use. Switched to a different one and works just fine.

  • Quote

    2016.03.13

    Add: File browse for iso file selection.

     

    This is great dlandon, thanks!

  • Quote
    • Author

    Release 2016.03.16 available.  You can now format a ntfs drive in UD and Windows will recognize and mount the drive.  Thanks to gfjardim for this fix.

  • Quote

    Release 2016.03.16 available.  You can now format a ntfs drive in UD and Windows will recognize and mount the drive.  Thanks to gfjardim for this fix.

     

    Nice  :)

  • Quote

    It just gets better  :)

     

    I have a question about the Historical Devices section, though. It seems that as new devices are seen by UD and then removed they are added to this list, up to a maximum of eight. You can toggle the Automount feature in case they should be connected again in the future and you can remove them from the list. But it seems that once eight have been seen no more are added to the list. I've been pre-clearing disks for use in another server so they are very unlikely to be seen again by this server. Once the list reached eight and didn't grow any further I started removing entries. It now stands at four but new disks aren't being added to it. Is that how it's supposed to work?

  • Quote

    It just gets better  :)

     

    I have a question about the Historical Devices section, though. It seems that as new devices are seen by UD and then removed they are added to this list, up to a maximum of eight. You can toggle the Automount feature in case they should be connected again in the future and you can remove them from the list. But it seems that once eight have been seen no more are added to the list. I've been pre-clearing disks for use in another server so they are very unlikely to be seen again by this server. Once the list reached eight and didn't grow any further I started removing entries. It now stands at four but new disks aren't being added to it. Is that how it's supposed to work?

     

    Not every disk gets added, only those you change any of the configuration options, like Auto Mount/Share/Script.

  • Quote

    It just gets better  :)

     

    I have a question about the Historical Devices section, though. It seems that as new devices are seen by UD and then removed they are added to this list, up to a maximum of eight. You can toggle the Automount feature in case they should be connected again in the future and you can remove them from the list. But it seems that once eight have been seen no more are added to the list. I've been pre-clearing disks for use in another server so they are very unlikely to be seen again by this server. Once the list reached eight and didn't grow any further I started removing entries. It now stands at four but new disks aren't being added to it. Is that how it's supposed to work?

     

    Not every disk gets added, only those you change any of the configuration options, like Auto Mount/Share/Script.

     

    Ah, right. Thanks. I think some of the default actions have changed - I remember toggling off Automout in the past (which would have added the disk to the list). Now Automount is off by default so I don't need to change that setting (which is why disks are no longer being added). I'll have a play with it.

     

  • Quote

    can't upgrade to 2016.03.16.

     

    plugin: downloading: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz ... failed (Network failure)

    plugin: wget: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz download failure (Network failure)

     

    except network is fine.

     

    I tried going there manually, and appears there is a resolving host error.

     

    mirrors.kingrst.com’s server DNS address could not be found.

     

    is there another way to update it?

  • Quote

    Hi guys.

     

    Since unRAID 6.2beta19, we have a workaround to that odd behavior that prevents Docker containers to access disks mounted after the Docker service starts. It's called Slave Mounts, and it permits the host to share it's mounts with Docker containers.

     

    To enable the workaround, you must set the "/mnt/disks" path's mode to RW/Slave, like this:

     

    8C7EOlL.png

     

    After saving the container, you should be able to see every disks mounted using Unassigned Devices.

     

    A special thanks to Lime Technologies for being open minded about this.

  • Quote

    can't upgrade to 2016.03.16.

     

    plugin: downloading: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz ... failed (Network failure)

    plugin: wget: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz download failure (Network failure)

     

    except network is fine.

     

    I tried going there manually, and appears there is a resolving host error.

     

    mirrors.kingrst.com’s server DNS address could not be found.

     

    is there another way to update it?

     

    waited a few days, this repository appears to still be broken.

  • Quote

    can't upgrade to 2016.03.16.

     

    plugin: downloading: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz ... failed (Network failure)

    plugin: wget: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz download failure (Network failure)

     

    except network is fine.

     

    I tried going there manually, and appears there is a resolving host error.

     

    mirrors.kingrst.com’s server DNS address could not be found.

     

    is there another way to update it?

     

    waited a few days, this repository appears to still be broken.

     

    Try this one:

     

    http://linorg.usp.br/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz

  • Quote
    • Author

    can't upgrade to 2016.03.16.

     

    plugin: downloading: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz ... failed (Network failure)

    plugin: wget: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz download failure (Network failure)

     

    except network is fine.

     

    I tried going there manually, and appears there is a resolving host error.

     

    mirrors.kingrst.com’s server DNS address could not be found.

     

    is there another way to update it?

     

    waited a few days, this repository appears to still be broken.

     

    Works for me.  I click on the link in your post and it downloads.

  • Quote

    can't upgrade to 2016.03.16.

     

    plugin: downloading: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz ... failed (Network failure)

    plugin: wget: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz download failure (Network failure)

     

    except network is fine.

     

    I tried going there manually, and appears there is a resolving host error.

     

    mirrors.kingrst.com’s server DNS address could not be found.

     

    is there another way to update it?

     

    waited a few days, this repository appears to still be broken.

     

    Works for me.  I click on the link in your post and it downloads.

     

    Probably your mirror is different from his.

  • Quote

    can't upgrade to 2016.03.16.

     

    plugin: downloading: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz ... failed (Network failure)

    plugin: wget: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz download failure (Network failure)

     

    except network is fine.

     

    I tried going there manually, and appears there is a resolving host error.

     

    mirrors.kingrst.com’s server DNS address could not be found.

     

    is there another way to update it?

     

    waited a few days, this repository appears to still be broken.

     

    Works for me.  I click on the link in your post and it downloads.

    Why not host the packages in your github repo? Would eliminate the possibility of any broken links.

  • Quote

    can't upgrade to 2016.03.16.

     

    plugin: downloading: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz ... failed (Network failure)

    plugin: wget: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz download failure (Network failure)

     

    except network is fine.

     

    I tried going there manually, and appears there is a resolving host error.

     

    mirrors.kingrst.com’s server DNS address could not be found.

     

    is there another way to update it?

     

    waited a few days, this repository appears to still be broken.

     

    Works for me.  I click on the link in your post and it downloads.

    Why not host the packages in your github repo? Would eliminate the possibility of any broken links.

     

    No need. Oregon State University is rock solid: http://slackware.osuosl.org/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz

  • Quote

    can't upgrade to 2016.03.16.

     

    plugin: downloading: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz ... failed (Network failure)

    plugin: wget: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz download failure (Network failure)

     

    except network is fine.

     

    I tried going there manually, and appears there is a resolving host error.

     

    mirrors.kingrst.com’s server DNS address could not be found.

     

    is there another way to update it?

     

    waited a few days, this repository appears to still be broken.

     

    Works for me.  I click on the link in your post and it downloads.

    Why not host the packages in your github repo? Would eliminate the possibility of any broken links.

     

    No need. Oregon State University is rock solid: http://slackware.osuosl.org/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz

    If the package versions or build versions get updated in slackware current the link would be broken. I've seen the same package name and md5 changed later because the package was updated and not the name.

  • Quote

    can't upgrade to 2016.03.16.

     

    plugin: downloading: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz ... failed (Network failure)

    plugin: wget: http://mirrors.slackware.com/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz download failure (Network failure)

     

    except network is fine.

     

    I tried going there manually, and appears there is a resolving host error.

     

    mirrors.kingrst.com’s server DNS address could not be found.

     

    is there another way to update it?

     

    waited a few days, this repository appears to still be broken.

     

    Try this one:

     

    http://linorg.usp.br/slackware/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz

     

    You'll have to forgive me, but i have no idea how to change it. When i hit the update button next to the version in the plug in tab, i don't exactly have the option of changing the mirror it's pulling from. it just keeps pulling from the same one.

     

  • Quote

    • 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...
    Go to topic listing

    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.