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


dlandon

Recommended Posts

I am on the 2020.12.10a release and 6.9 RC1 and it seems that my QNAP share is not getting passed through to the Dockers. I can browse all the files like normal when clicking the mount point but for whatever reason dockers (including in the Docker config window within unraid) can’t see the files or the mount point. I tried reinstalling the plugin but had no luck.

  • Like 1
Link to comment
38 minutes ago, Mirano said:

After updating unassigned devices i get the following error on my radarr docker:

 

[Warn] RadarrErrorPipeline: Invalid request Validation failed:
-- Path: Folder is not writable by user abc

 

I've tried alot, which is noted here:

 

Radarr thinks he has no write access while it does · Issue #125 · linuxserver/docker-radarr (github.com)

https://github.com/linuxserver/docker-radarr/issues/125

 

Read the recommended post at the top of this forum to see if that applies to you.

Link to comment
13 minutes ago, Whiskey90 said:

I am on the 2020.12.10a release and 6.9 RC1 and it seems that my QNAP share is not getting passed through to the Dockers. I can browse all the files like normal when clicking the mount point but for whatever reason dockers (including in the Docker config window within unraid) can’t see the files or the mount point. I tried reinstalling the plugin but had no luck.

Read the recommended post at the top of this forum to see if it applies to you.

Link to comment

After the latest update I had the same problem with the mounts - but after recreating i am now getting some mounts not automounting and the option is checked - any ideas?

 

logs show that these mounts are offline when they are not.  
 

especially when the same server is hosting multiple shares, and some auto mount and others don’t. 

Edited by cferra
Link to comment
7 minutes ago, cferra said:

After the latest update I had the same problem with the mounts - but after recreating i am now getting some mounts not automounting and the option is checked - any ideas?

 

logs show that these mounts are offline when they are not.  
 

especially when the same server is hosting multiple shares, and some auto mount and others don’t. 

You should post your entire diagnostics file.

Link to comment

I keep getting my new disk disabled after UD throws the error "Dec 11 13:02:03 Gerwig unassigned.devices: Disk with serial 'ST12000VN0008-XXXXX', mountpoint 'ST12000VN0008-XXXXXXXXX' is not set to auto mount and will not be mounted."

 

I add a new disk to the array in safe mode, rebuilds fine, reboot in normal mode, then after some time it disables thee drive. I've tried with 2 new drives and it happens to both.

Edited by ddwag1
Link to comment
6 minutes ago, ddwag1 said:

I keep getting my new disk disabled after UD throws the error "Dec 11 13:02:03 Gerwig unassigned.devices: Disk with serial 'ST12000VN0008-2PH103_ZS8008MQ', mountpoint 'ST12000VN0008-2PH103_ZS8008MQ' is not set to auto mount and will not be mounted."syslog.txt

 

I add a new disk to the array in safe mode, rebuilds fine, reboot in normal mode, then after some time it disables thee drive. I've tried with 2 new drives and it happens to both.

Your disk went offline and the back online:

Dec 11 13:01:57 Gerwig kernel: sd 7:0:1:0: attempting task abort! scmd(00000000b8fc9a6f)
Dec 11 13:01:57 Gerwig kernel: sd 7:0:1:0: [sdc] tag#2292 CDB: opcode=0x85 85 06 20 00 d8 00 00 00 00 00 4f 00 c2 00 b0 00
Dec 11 13:01:57 Gerwig kernel: scsi target7:0:1: handle(0x000a), sas_address(0x50030480010d2f0d), phy(13)
Dec 11 13:01:57 Gerwig kernel: scsi target7:0:1: enclosure logical id(0x50030480010d2f3f), slot(1) 
Dec 11 13:01:57 Gerwig kernel: sd 7:0:1:0: device_block, handle(0x000a)
Dec 11 13:01:59 Gerwig kernel: sd 7:0:1:0: device_unblock and setting to running, handle(0x000a)
Dec 11 13:01:59 Gerwig kernel: sd 7:0:1:0: [sdc] Synchronizing SCSI cache
Dec 11 13:01:59 Gerwig kernel: sd 7:0:1:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Dec 11 13:02:00 Gerwig kernel: scsi 7:0:1:0: task abort: SUCCESS scmd(00000000b8fc9a6f)
Dec 11 13:02:00 Gerwig kernel: mpt2sas_cm0: removing handle(0x000a), sas_addr(0x50030480010d2f0d)
Dec 11 13:02:00 Gerwig kernel: mpt2sas_cm0: enclosure logical id(0x50030480010d2f3f), slot(1) 
Dec 11 13:02:03 Gerwig kernel: scsi 7:0:15:0: Direct-Access     ATA      ST12000VN0008-2P SC61 PQ: 0 ANSI: 6
Dec 11 13:02:03 Gerwig kernel: scsi 7:0:15:0: SATA: handle(0x000a), sas_addr(0x50030480010d2f0d), phy(13), device_name(0x0000000000000000)
Dec 11 13:02:03 Gerwig kernel: scsi 7:0:15:0: enclosure logical id (0x50030480010d2f3f), slot(1) 
Dec 11 13:02:03 Gerwig kernel: scsi 7:0:15:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)

-> Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: Power-on or device reset occurred

Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: Attached scsi generic sg2 type 0
Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: [sdp] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB)
Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: [sdp] 4096-byte physical blocks
Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: [sdp] Write Protect is off
Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: [sdp] Mode Sense: 7f 00 10 08
Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: [sdp] Write cache: enabled, read cache: enabled, supports DPO and FUA
Dec 11 13:02:03 Gerwig kernel: sdp: sdp1
Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: [sdp] Attached SCSI disk

I'm not a disk or controller expert, so I can't help with the problem you are having.  Maybe @JorgeB can help.  He is the disk and controller guru.

Link to comment
On 12/5/2020 at 9:08 PM, JorgenK said:

A few months ago I added a 2.5" 500GB drive with unassigned devices. When naming the mount point I was thinking that it would prevent me from using forbidden characters and HGST 500GB 2.5" was tried. I didn't think that it would be used directly without modification. The name was accepted, but would not mount and it can not be renamed. When clicking on it in the gui nothing happens.

 

I have seen fixes which seem to prevent mistakes like this, but nothing has allowed me to rename the mount point.

 

When removing the mount point and then formatting the drive the same mount point is used.

 

Is there a way to solve this?

 

On 12/5/2020 at 9:55 PM, dlandon said:

When you add the drive, the mount point has the quote?

 

Sorry for the delay.

Yes, the quote was included. I expected that it would be caught if it was not allowed. 

Link to comment
25 minutes ago, JorgenK said:

Sorry for the delay.

Yes, the quote was included. I expected that it would be caught if it was not allowed. 

It is now.  UD will remove the quote character.  If a quote is entered in the mount point, UD will replace it with an underline.

Edited by dlandon
Link to comment
2 minutes ago, Dent_ said:

I seem to be having the same issue as cferra and squid. I can see the full network share if I click on the mount point, but I can only see one folder inside the docker (should be two) and none of the subfolders. I also updated UD to 2020.10.21.

unraid-diagnostics-20201211-1710.zip 162.87 kB · 0 downloads

Read the recommended topic at the top of this forum.  The remote shares mount point has changed.

Link to comment
1 hour ago, dlandon said:

It is now.  UD will remove the quote character and replace it with an underline.

I must be missing something. Is there a way to solve the problem after the fact? If it's to complicated I can replace the drive at a later time to be able to start from scratch. The only reason I fitted the 2.5" drive is to let the security cameras write to a silent drive. 

 

If I remove the partition and choose format I still get the same name and when it is mounted it's still at: /mnt/disks/HGST 500GB 2.5"

 

The entry /etc/samba/unassigned-shares is named HGST_500GB_2.5".conf and contains:

[HGST 500GB 2.5"]
        path = /mnt/disks/HGST 500GB 2.5"
        read only = No
        guest ok = Yes
        vfs objects = 

 

I don't see a reference to /etc/samba/unassigned-shares/HGST_500GB_2.5".conf in the .conf files in the /etc/samba directory

 

The symptoms is that i can't see a share when browsing the server from a windows machine. I have not diagnosed it further.

Edited by JorgenK
Link to comment
1 minute ago, JorgenK said:

I must be missing something. Is there a way to solve the problem after the fact? If it's to complicated I can replace the drive at a later time to be able to start from scratch. The only reason I fitted the 2.5" drive is to let the security cameras write to a silent drive. 

 

If I remove the partition and choose format I still get the same name and when it is mounted it's still at: /mnt/disks/HGST 500GB 2.5"

 

The entry /etc/samba/unassigned-shares is named HGST_500GB_2.5".conf and contains:

[HGST 500GB 2.5"]
        path = /mnt/disks/HGST 500GB 2.5"
        read only = No
        guest ok = Yes
        vfs objects = 

 

I don't see a reference to /etc/samba/unassigned-shares/HGST_500GB_2.5" in the .conf files in the /etc/samba directory

 

The symptoms is that i can't see a share when browsing the server from a windows machine. I have not diagnosed it further.

I just added the block for the quote.  It comes from the information supplied by the drive when it is installed.  I'll update UD in a few minutes to fix this,  Remove the drive and then delete it from the Historical devices.  If you can't remove it from the Historical devices, post back here and I'll explain how to force its removal.

 

Once it is removed, then update UD and re-install the drive.

Link to comment
37 minutes ago, dlandon said:

Read the recommended topic at the top of this forum.  The remote shares mount point has changed.

Yup, missed that some how, removed and recreated the SMB share but sailed right past the remotes folder instead of the disks folder. I think what got me is that the original folder under disks is still there so I just automatically thought there it is lol.  

Edited by Dent_
Link to comment
1 minute ago, Dent_ said:

Yup, missed that some how, removed and recreated the SMB share but sailed right past the remotes folder instead of the disks folder.

You didn't need to recreate the remote share.  All you needed to do was unmount and remount it after setting the UD setting for legacy mount point.  It will mount to the /mnt/remotes/ mount point automatically.

  • Like 1
Link to comment
21 minutes ago, dlandon said:

I just added the block for the quote.  It comes from the information supplied by the drive when it is installed.  I'll update UD in a few minutes to fix this,  Remove the drive and then delete it from the Historical devices.  If you can't remove it from the Historical devices, post back here and I'll explain how to force its removal.

 

Once it is removed, then update UD and re-install the drive.

Thanks a lot! It works now. I guess that just unplugging the drive an removing it from historical devices would have solved the problem I had.

Link to comment
1 minute ago, dlandon said:

Not really.  You also needed the UD update so the quote character would be blocked.

It's the original drive from an Apple Mini and the name was APPLE_HDD_HTS545050A7E362_TNS5193T15ML6H. I need to take credit for using the quote in the name when I didn't want a long name like that. I clearly remember wondering if the spaces and the quote was acceptable in the name and was a bit surprised when it was accepted. The Ohh shit, moment came minutes later.

Link to comment
3 minutes ago, JorgenK said:

It's the original drive from an Apple Mini and the name was APPLE_HDD_HTS545050A7E362_TNS5193T15ML6H. I need to take credit for using the quote in the name when I didn't want a long name like that. I clearly remember wondering if the spaces and the quote was acceptable in the name and was a bit surprised when it was accepted. The Ohh shit, moment came minutes later.

Spaces are not a problem.  The quote obviously was.

Link to comment

I'm wanting to remove UD so I can test out 6.9 RC1.

I'm on 6.8.3, I removed UD + UD Extra. Restarted unraid.

I confirmed no install on the startup but I still have the "Unassigned Disk" tab on the main unraid page.

Can see below, it shows the tab and a drive but cant really do much with it.. I wold have expected the tab to not be there anymore?

firefox_2020-12-11_20-51-46[1].png

Edited by zoggy
Link to comment
16 minutes ago, zoggy said:

I'm wanting to remove UD so I can test out 6.9 RC1.

I'm on 6.8.3, I removed UD + UD Extra. Restarted unraid.

I confirmed no install on the startup but I still have the "Unassigned Disk" tab on the main unraid page.

Can see below, it shows the tab and a drive but cant really do much with it.. I wold have expected the tab to not be there anymore?

firefox_2020-12-11_20-51-46[1].png

That's the stock Unassigned Devices page.  It is not the UD plugin page.

Link to comment

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.