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

dlandon · March 12, 2023

3 hours ago, Jclendineng said:

version="6.11.5"

Im running pre-clear from the plugin, and clicking the disk log on the pre-clear page, under "Identification" beside the disk, not the pre-clear log, but the actual disk log.

That's the disk log in the preclear plugin. This will be fixed in the next release of the preclear pliugin. In the meantime, use the UD page disk log.

Jclendineng · March 13, 2023

2 hours ago, dlandon said:

That's the disk log in the preclear plugin. This will be fixed in the next release of the preclear pliugin. In the meantime, use the UD page disk log.

Awesome, figured Id throw it out there since I didn't see anything recent on the forums Much appreciated.

sonofdbn · March 14, 2023

On 3/2/2023 at 12:10 AM, sonofdbn said:

I have had a similar problem to what @csendre reported a few posts above, as described in the thread above. I followed the suggestion in that thread of removing the SSD that I had as an Unassigned Device (removed virtually) and now everything looks fine except that of course I can't use the SSD.

Briefly: I had the animated logo problem as well as some page fault errors. For me, it turns out that the problem was actually some component that qbittorrent relies on, and not a bug in the UD plug-in. The link to the discussion is below. I rolled back to qbittorrent 4.3.9-2-01* and now everything has been working fine for more than 24 hours. Previously the crash came after a few hours, so I'm calling it fixed.

*Please read the thread above - rolling back might lead to some loss of configuration settings.

smick · March 15, 2023

On 3/9/2023 at 9:45 AM, itimpi said:

@comet424 Have you checked on your Main server that Settings->Unassigned Devices->SMB Security is set to something other than No? If set to No then it cannot be accessed over the network.

Thanks! This was my problem. My rootshare was working and all of a sudden stopped. Somehow the SMB security setting must have changed.

mattalat · March 15, 2023

Format failed with new SATA HD in a USB enclosure. Logs below. Any ideas? Thanks.

Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 ASC=0x3 ASCQ=0x0 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 08 08 00 00 00 80 00 00
Mar 14 21:28:30 Wyse kernel: I/O error, dev sdd, sector 2056 op 0x1:(WRITE) flags 0x800 phys_seg 16 prio class 0
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 Sense Key : 0x3 [current] 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 ASC=0x3 ASCQ=0x0 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 08 88 00 00 04 b0 00 00
Mar 14 21:28:30 Wyse kernel: I/O error, dev sdd, sector 2184 op 0x1:(WRITE) flags 0x800 phys_seg 150 prio class 0
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 Sense Key : 0x3 [current] 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 ASC=0x3 ASCQ=0x0 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 0d 38 00 00 02 58 00 00
Mar 14 21:28:30 Wyse kernel: I/O error, dev sdd, sector 3384 op 0x1:(WRITE) flags 0x800 phys_seg 75 prio class 0
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 Sense Key : 0x3 [current] 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 ASC=0x3 ASCQ=0x0 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 0f 90 00 00 00 70 00 00
Mar 14 21:28:30 Wyse kernel: I/O error, dev sdd, sector 3984 op 0x1:(WRITE) flags 0x800 phys_seg 14 prio class 0
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 Sense Key : 0x3 [current] 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 ASC=0x11 ASCQ=0x0 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
Mar 14 21:28:30 Wyse kernel: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 Sense Key : 0x3 [current] 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 ASC=0x11 ASCQ=0x0 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
Mar 14 21:28:30 Wyse kernel: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 14 21:28:30 Wyse kernel: ldm_validate_partition_table(): Disk read failed.
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 Sense Key : 0x3 [current] 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 ASC=0x11 ASCQ=0x0 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
Mar 14 21:28:30 Wyse kernel: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 14 21:28:30 Wyse kernel: sdd: unable to read partition table
Mar 14 21:28:30 Wyse unassigned.devices: Clear partition result: 1+0 records in 1+0 records out 2097152 bytes (2.1 MB, 2.0 MiB) copied, 0.298422 s, 7.0 MB/s
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 Sense Key : 0x3 [current] 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 ASC=0x11 ASCQ=0x0 
Mar 14 21:28:30 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 be 00 00 00 00 08 00 00
Mar 14 21:28:30 Wyse kernel: critical medium error, dev sdd, sector 7814036992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Mar 14 21:28:32 Wyse unassigned.devices: Reloading disk '/dev/sdd' partition table.
Mar 14 21:28:32 Wyse kernel: ldm_validate_partition_table(): Disk read failed.
Mar 14 21:28:32 Wyse kernel: sdd: unable to read partition table
Mar 14 21:28:32 Wyse unassigned.devices: Reload partition table result: /dev/sdd:  re-reading partition table
Mar 14 21:28:32 Wyse unassigned.devices: Creating Unraid compatible gpt partition on disk '/dev/sdd'.
Mar 14 21:28:32 Wyse kernel: ldm_validate_partition_table(): Disk read failed.
Mar 14 21:28:32 Wyse kernel: sdd: unable to read partition table
Mar 14 21:28:33 Wyse kernel: ldm_validate_partition_table(): Disk read failed.
Mar 14 21:28:33 Wyse kernel: sdd: unable to read partition table
Mar 14 21:28:33 Wyse kernel: ldm_validate_partition_table(): Disk read failed.
Mar 14 21:28:33 Wyse kernel: sdd: unable to read partition table
Mar 14 21:28:33 Wyse kernel: ldm_validate_partition_table(): Disk read failed.
Mar 14 21:28:33 Wyse kernel: sdd: unable to read partition table
Mar 14 21:28:33 Wyse kernel: ldm_validate_partition_table(): Disk read failed.
Mar 14 21:28:33 Wyse unassigned.devices: Create gpt partition table result: Creating new GPT entries in memory. 
Mar 14 21:28:33 Wyse kernel: sdd: unable to read partition table
Mar 14 21:28:35 Wyse unassigned.devices: Reloading disk '/dev/sdd' partition table.
Mar 14 21:28:35 Wyse kernel: scsi_io_completion_action: 44 callbacks suppressed
Mar 14 21:28:35 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 14 21:28:35 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 Sense Key : 0x3 [current] 
Mar 14 21:28:35 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 ASC=0x11 ASCQ=0x0 
Mar 14 21:28:35 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
Mar 14 21:28:35 Wyse kernel: blk_print_req_error: 44 callbacks suppressed
Mar 14 21:28:35 Wyse kernel: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 14 21:28:35 Wyse kernel: buffer_io_error: 539 callbacks suppressed
Mar 14 21:28:35 Wyse kernel: Buffer I/O error on dev sdd, logical block 0, async page read
Mar 14 21:28:35 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 14 21:28:35 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 Sense Key : 0x3 [current] 
Mar 14 21:28:35 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 ASC=0x11 ASCQ=0x0 
Mar 14 21:28:35 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
Mar 14 21:28:35 Wyse kernel: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 14 21:28:35 Wyse kernel: Buffer I/O error on dev sdd, logical block 0, async page read
Mar 14 21:28:35 Wyse kernel: ldm_validate_partition_table(): Disk read failed.
Mar 14 21:28:35 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 14 21:28:35 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 Sense Key : 0x3 [current] 
Mar 14 21:28:35 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 ASC=0x11 ASCQ=0x0 
Mar 14 21:28:35 Wyse kernel: sd 3:0:0:0: [sdd] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
Mar 14 21:28:35 Wyse kernel: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 14 21:28:35 Wyse kernel: Buffer I/O error on dev sdd, logical block 0, async page read
Mar 14 21:28:35 Wyse kernel: sdd: unable to read partition table
Mar 14 21:28:35 Wyse unassigned.devices: Reload partition table result: /dev/sdd:  re-reading partition table
Mar 14 21:28:35 Wyse unassigned.devices: Formatting disk '/dev/sdd' with 'xfs' filesystem.
Mar 14 21:28:35 Wyse unassigned.devices: Format drive command: /sbin/mkfs.xfs -f '/dev/sdd1' 2>&1
Mar 14 21:28:36 Wyse unassigned.devices: Format disk '/dev/sdd' with 'zfs' filesystem failed: Error accessing specified device /dev/sdd1: No such file or directory Usage: mkfs.xfs /* blocksize */#011#011[-b size=num] /* config file */#011[-c options=xxx] /* metadata */#011#011[-m crc=0|1,finobt=0|1,uuid=xxx,rmapbt=0|1,reflink=0|1, #011#011#011    inobtcount=0|1,bigtime=0|1] /* data subvol */#011[-d agcount=n,agsize=n,file,name=xxx,size=num, #011#011#011    (sunit=value,swidth=value|su=num,sw=num|noalign), #011#011#011    sectsize=num /* force overwrite */#011[-f] /* inode size */#011[-i perblock=n|size=num,maxpct=n,attr=0|1|2, #011#011#011    projid32bit=0|1,sparse=0|1] /* no discard */#011[-K] /* log subvol */#011[-l agnum=n,internal,size=num,logdev=xxx,version=n #011#011#011    sunit=value|su=num,sectsize=num,lazy-count=0|1] /* label */#011#011[-L label (maximum 12 characters)] /* naming */#011#011[-n size=num,version=2|ci,ftype=0|1] /* no-op info only */#011[-N] /* prototype file */#011[-p fname] /* quiet */#011#011[-q] /* realtime subvol */#011[-r extsize=num,size=num,rtdev=xxx] /* sectorsize */#011[-s size=num] /* version */#011#011[-V] #011#011#011devicename <d

dlandon · March 16, 2023

On 3/14/2023 at 9:42 PM, mattalat said:

Format failed with new SATA HD in a USB enclosure. Logs below. Any ideas? Thanks.

Try formatting it connected directly to a motherboard sata port.

architektur23 · March 16, 2023

Hey guys, I'm out of ideas...

I want to share a folder from my pc and mount it in unraid, one folder works, but not the one i want even so they are in the same location with the same permissions...
The Output Folder, share "Out" is no problem to mount, but with the same settings the dropbox folder ("Drop") isnt able to mount
Can someone pls help me understand why that is?

dlandon · March 16, 2023

4 minutes ago, architektur23 said:

Can someone pls help me understand why that is?

Looks like a credentials problem. Be careful using special characters in your password.

architektur23 · March 16, 2023

19 minutes ago, dlandon said:

Looks like a credentials problem. Be careful using special characters in your password.

its the same password and online has 4 digits, that cant be it... and i tried it like 10 times, also with the whole hard drive which also wouldnt work
but any other folder of that hard drive works...

Kilrah · March 16, 2023

Is it the dropbox folder you're trying to share?

AFAIK that's kind of a "virtual" folder created by the dropbox app, not a real folder so it might cause issues...

Or it might have different underlying permissions at the filesystem level (unrelated to what you set in the sharing tab). Maybe can be changed with the Security tab, might break the Dropbox app though...

dlandon · March 16, 2023

20 minutes ago, architektur23 said:

its the same password and online has 4 digits, that cant be it... and i tried it like 10 times, also with the whole hard drive which also wouldnt work
but any other folder of that hard drive works...

Return code -13 is a credentials issue: https://access.redhat.com/solutions/450913

DSPhoto · March 16, 2023

Hey, I'm trying to move a large amount of files from an external SSD exFat through usb connection. I've installed UD and UD+ but am seeing no Unassigned Drives. I've tried rebooting the server and switching the drive to a different USB port. I've got to be doing something wrong. Can anyone offer some guidance? Thanks!

Kilrah · March 16, 2023

36 minutes ago, DSPhoto said:

Hey, I'm trying to move a large amount of files from an external SSD exFat through usb connection. I've installed UD and UD+ but am seeing no Unassigned Drives. I've tried rebooting the server and switching the drive to a different USB port. I've got to be doing something wrong. Can anyone offer some guidance? Thanks!

Open the syslog window, if nothing scrolls by when plugging the drive then the hardware isn't even seeing it. If something does post the relevant output.

Edited March 16, 2023 by Kilrah

DSPhoto · March 16, 2023

1 hour ago, Kilrah said:

Open the syslog window, if nothing scrolls by when plugging the drive then the hardware isn't even seeing it. If something does post the relevant output.

Yeah, it looks like the hardware isn't even seeing it. I've got it plugged into an onboard USB port, right next to the bootable flash drive which is obviously working. I'm not sure what to try next.

Kilrah · March 17, 2023

Does it work no another machine? Tried a different cable?

Mogo · March 17, 2023

Not sure what happened, but my unassigned device (external ssd drive) does not show up in windows explorer any more. I can still access the drive through krusader and terminal. Krusader just gets in but all files are missing. Terminal can get in and see all files. It just does not show up in windows and is not accessible through there. Any ideas?

Fixed the issue by doing this:
Enable SMB Security? Public instead of No

Edited March 17, 2023 by Mogo

mattalat · March 18, 2023

Can't get disk share to work - the "share" toggle is enabled for both the drive and partition, but it's not showing up. Interestingly, when I hover over the settings cogwheel for both, they each say "Share: No" despite the slider being enabled in settings. Any ideas? Thanks.

dlandon · March 18, 2023

5 hours ago, mattalat said:

Can't get disk share to work - the "share" toggle is enabled for both the drive and partition, but it's not showing up. Interestingly, when I hover over the settings cogwheel for both, they each say "Share: No" despite the slider being enabled in settings. Any ideas? Thanks.

What's not showing up?

Try:

Click the doublw arrows icon on the upper right of the UD page and see if the "Share" in the tooltip shows up correctly.
Look at the post above yours and see if that is your issue. If not, then post diagnostics.

itimpi · March 18, 2023

7 hours ago, mattalat said:

Can't get disk share to work - the "share" toggle is enabled for both the drive and partition, but it's not showing up. Interestingly, when I hover over the settings cogwheel for both, they each say "Share: No" despite the slider being enabled in settings. Any ideas? Thanks.

Have you checked that you do not have Settings->Unassigned Devices->SMB Security set to No? If so that will stop the share being visible over SMB despite setting the Share option on the drive itself.

Erich · March 18, 2023

I have an external drive plugged into my Unraid server. However, the external drive does not show up in my Network connections in windows. If I try to connect to the external drive (named "Ext_Disk") from a windows 10 machine, I get an error message saying that Windows cannot access or find this location. I am trying to connect by using "\\Phoenix\Ext_Disk".

In Unraid, I have tried setting "Enable SMB Security?" to Yes and/or Private, but it still is not working.

The external drive is mounted and I do see my Unraid server, "Phoenix" on the Windows 10 machine and can access all of its shares, just not the external, unassigned hard drive.

How can I connect to the external drive on Unraid from my Windows 10 machine?

phoenix-diagnostics-20230318-1111.zip

mattalat · March 19, 2023

17 hours ago, dlandon said:

What's not showing up?

Try:

Click the doublw arrows icon on the upper right of the UD page and see if the "Share" in the tooltip shows up correctly.

Look at the post above yours and see if that is your issue. If not, then post diagnostics.

I'm just not able to see the disk under "Disk Shares" - basically trying to make an SMB share of the drive.

Tried refreshing the disks and configuration (double arrows), and tooltip still shows Share: No. Also confirmed that SMB Security is set to Public in the UD settings.

Diagnostics attached

wyse-diagnostics-20230318-2050.zip

Edited March 19, 2023 by mattalat

mattalat · March 19, 2023

15 hours ago, itimpi said:

Have you checked that you do not have Settings->Unassigned Devices->SMB Security set to No? If so that will stop the share being visible over SMB despite setting the Share option on the drive itself.

I have confirmed that it is set to Public.

dlandon · March 19, 2023

6 hours ago, mattalat said:

I have confirmed that it is set to Public.

The device is not set to share as you have said from the tooltip:

Mar 17 20:13:49 Wyse unassigned.devices: Device '/dev/sdb1' is not set to be shared.

Show a screen shot of the device settings.

Erich · March 19, 2023

22 hours ago, Erich said:

I have an external drive plugged into my Unraid server. However, the external drive does not show up in my Network connections in windows. If I try to connect to the external drive (named "Ext_Disk") from a windows 10 machine, I get an error message saying that Windows cannot access or find this location. I am trying to connect by using "\\Phoenix\Ext_Disk".

In Unraid, I have tried setting "Enable SMB Security?" to Yes and/or Private, but it still is not working.

The external drive is mounted and I do see my Unraid server, "Phoenix" on the Windows 10 machine and can access all of its shares, just not the external, unassigned hard drive.

How can I connect to the external drive on Unraid from my Windows 10 machine?

phoenix-diagnostics-20230318-1111.zip 132.92 kB · 0 downloads

Is there anyone who can help me with this?

SimonF · March 19, 2023

5 minutes ago, Erich said:

Is there anyone who can help me with this?

Have you enabled sharing in UD of the device via the cog and then slider in options?

Edited March 19, 2023 by SimonF

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