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


dlandon

Recommended Posts

4 hours ago, SuberSeb said:

I have mounted NFS private shares but for some reason plugin don't ask me for password. How this can happen?

 

UD doesn't ask for the password.  Access is controlled by Linux permissions.

Link to comment
On 4/10/2021 at 11:02 AM, dlandon said:

I think this issue is related to some remote servers needing to have the version specified when mounting a CIFS mount.  I have updated UD and added a setting to possibly help with this issue.

 

Procedure:

  • Update UD plugin.
  • Unmount all SMB remote shares.
  • Go to settings and set 'Specify SMB Version when Mounting Remote Shares?' to 'Yes'.
  • Mount remote SMB shares.

Let me know if this takes care of the excessive log messages.

 

Thanks!!  I've completed the steps.  I will report back on the log status.  

Link to comment
1 hour ago, Andiroo2 said:

 

Thanks!!  I've completed the steps.  I will report back on the log status.  

Update:  still getting the error messages in the log, starting about 10 minutes later:

 

Apr 12 09:23:05 Tower unassigned.devices: Mount SMB share '//MACMINI-581918/DATA' using SMB3 protocol.
Apr 12 09:23:05 Tower unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.0,credentials='/tmp/unassigned.devices/credentials_DATA' '//MACMINI-581918/DATA' '/mnt/remotes/MACMINI-581918_DATA'
Apr 12 09:23:05 Tower kernel: CIFS: Attempting to mount //MACMINI-581918/DATA
Apr 12 09:23:06 Tower unassigned.devices: Successfully mounted '//MACMINI-581918/DATA' on '/mnt/remotes/MACMINI-581918_DATA'.
Apr 12 09:23:06 Tower unassigned.devices: Adding SMB share 'MACMINI-581918_DATA'.
Apr 12 09:24:44 Tower emhttpd: read SMART /dev/sdh
Apr 12 09:25:44 Tower emhttpd: read SMART /dev/sdk
Apr 12 09:25:53 Tower emhttpd: read SMART /dev/sdj
Apr 12 09:28:13 Tower kernel: CIFS: VFS: \\MACMINI-581918 Cancelling wait for mid 487243 cmd: 5
Apr 12 09:28:13 Tower kernel: CIFS: VFS: \\MACMINI-581918 Cancelling wait for mid 487244 cmd: 14
Apr 12 09:28:13 Tower kernel: CIFS: VFS: \\MACMINI-581918\DATA Close unmatched open for MID:76f4b
Apr 12 09:30:44 Tower kernel: CIFS: VFS: \\MACMINI-581918 Cancelling wait for mid 725165 cmd: 14
Apr 12 09:33:15 Tower kernel: CIFS: VFS: \\MACMINI-581918 Cancelling wait for mid 959576 cmd: 6

 

Link to comment
On 4/12/2021 at 10:09 AM, Andiroo2 said:

 

On 4/12/2021 at 10:09 AM, Andiroo2 said:

Update:  still getting the error messages in the log, starting about 10 minutes later:

 

To be clear, my SMB share still works perfectly.  I am transferring data to this remote share as part of a backup process weekly and it's working as expected.  I am just getting these errors spamming my Unraid logs.  

Link to comment
3 hours ago, Andiroo2 said:

To be clear, my SMB share still works perfectly.  I am transferring data to this remote share as part of a backup process weekly and it's working as expected.  I am just getting these errors spamming my Unraid logs.  

I have no idea where to look to solve these messages.  As much as I dislike just ignoring log messages, they seem to be informational and can be filtered from the log.  To do that, install the enhanced log plugin and click on the "Syslog Filter" tab and enter the following text:

"Cancelling wait for mid"
"Close unmatched open for MID"

This will filter those messages from the log.

Link to comment

So I'm having the same problem as a few others where the mount points are dropping to "0" space available. I didn't have this problem until it update to 6.9.x. My log has this over and over.

 

Apr 12 05:00:00 KRAKEN kernel: NFS: server 192.168.1.100 error: fileid changed
Apr 12 05:00:00 KRAKEN kernel: fsid 0:56: expected fileid 0x901000000000016, got 0x3000000528fe15

 

Link to comment
6 hours ago, Twitchstick said:

So I'm having the same problem as a few others where the mount points are dropping to "0" space available. I didn't have this problem until it update to 6.9.x. My log has this over and over.

 


Apr 12 05:00:00 KRAKEN kernel: NFS: server 192.168.1.100 error: fileid changed
Apr 12 05:00:00 KRAKEN kernel: fsid 0:56: expected fileid 0x901000000000016, got 0x3000000528fe15

 

Post diagnostics.

Link to comment

This is becoming unbearable 😞
All my data is on a Synology NAS connected with shares (UD) to my Unraid server (I purchased the Synology before I learned about Unraid).

Everyday my shares drops to 0 and only a reboot brings them back online.
My troubles started after the upgrade to 6.9.2 - maybe I will try to go back to 6.9.1.

It would be very much appreciated if some of you have a solution for this.

Link to comment
5 hours ago, lakr said:

This is becoming unbearable 😞
All my data is on a Synology NAS connected with shares (UD) to my Unraid server (I purchased the Synology before I learned about Unraid).

Everyday my shares drops to 0 and only a reboot brings them back online.
My troubles started after the upgrade to 6.9.2 - maybe I will try to go back to 6.9.1.

It would be very much appreciated if some of you have a solution for this.

Post diagnostics.

Link to comment
On 4/14/2021 at 12:29 PM, lakr said:

This is becoming unbearable 😞
All my data is on a Synology NAS connected with shares (UD) to my Unraid server (I purchased the Synology before I learned about Unraid).

Everyday my shares drops to 0 and only a reboot brings them back online.
My troubles started after the upgrade to 6.9.2 - maybe I will try to go back to 6.9.1.

It would be very much appreciated if some of you have a solution for this.

 

In your diagnostics, the 'df' command did not show any results and your log indicates a lot of timeouts with the 'df' command trying to get the size, free, and used status of your remote shares:

Apr 16 05:39:53 HighTower unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/LAKR_NAS_Movies' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 2s!

This is indicative of a networking issue.

 

You also have a lot of the following in your log that you need to resolve:

Apr 16 05:31:29 HighTower nginx: 2021/04/16 05:31:29 [alert] 7071#7071: worker process 9226 exited on signal 6
Apr 16 05:31:31 HighTower nginx: 2021/04/16 05:31:31 [alert] 7071#7071: worker process 9237 exited on signal 6

and

Apr 14 19:57:20 HighTower kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]
Apr 14 19:57:20 HighTower kernel: caller _nv000712rm+0x1af/0x200 [nvidia] mapping multiple BARs

I don't know enough about these issues to help, so someone else will have to chime in to help.

Link to comment
On 4/13/2021 at 11:34 PM, Twitchstick said:

So I'm having the same problem as a few others where the mount points are dropping to "0" space available. I didn't have this problem until it update to 6.9.x. My log has this over and over.

 


Apr 12 05:00:00 KRAKEN kernel: NFS: server 192.168.1.100 error: fileid changed
Apr 12 05:00:00 KRAKEN kernel: fsid 0:56: expected fileid 0x901000000000016, got 0x3000000528fe15

 

On your remote server post the contents of the "/etc/exports" directory.  I'm interested in seeing if there is a 'fsid=' parameter in the exports file. 

Link to comment

Hi everyone, I having some issues with an unassigned disk, where I cannot access some files and folders from my Mac.

I'll try to summarize it as best as I can:

  • MacOS 11.2.3 (BigSur)
    • via Finder/SMB
  • Unraid v6.8.3
  • Disk: nvme ssd (Samsung 970 EVO) with btrfs FS
    • used for Docker persistent storage
  • UD Settings:
    • Share: /mnt/disks/ua_appdata
    • SMB Security: enabled (r+w for my smb user)
    • encrypted: no

For some docker container folders, I cannot see any files and/or folders within the existing folders (e.g. /mnt/disks/ua_appdata/appdata/home-assistant/ ) when I browse the share via macOS Finder. I see all files and when I browse the Share from the Unraid Web UI, and I see all files when I browse /mnt/disks/ua_appdata/ with a krusader docker container.

I do not have this issue with "regular" shares in Unraid01, though none of them host any docker container config files.

Link to comment

[Solved] Since upgrading to 6.9 I've been unable to mount drives which I have been previously able to mount on 6.8.  Diagnostics are attached.  I have an external caddy (StarTech)  and I've tried both estata and usb connections, no luck.  BTW, the drives mount via usb (hot plug) in my Windows 10 VM. Diagnostics attached.

tower-diagnostics-20210417-1442.zip

Edited by Woodpusherghd
Link to comment
1 hour ago, 1l25kj1 said:

Hi everyone, I having some issues with an unassigned disk, where I cannot access some files and folders from my Mac.

I'll try to summarize it as best as I can:

  • MacOS 11.2.3 (BigSur)
    • via Finder/SMB
  • Unraid v6.8.3
  • Disk: nvme ssd (Samsung 970 EVO) with btrfs FS
    • used for Docker persistent storage
  • UD Settings:
    • Share: /mnt/disks/ua_appdata
    • SMB Security: enabled (r+w for my smb user)
    • encrypted: no

For some docker container folders, I cannot see any files and/or folders within the existing folders (e.g. /mnt/disks/ua_appdata/appdata/home-assistant/ ) when I browse the share via macOS Finder. I see all files and when I browse the Share from the Unraid Web UI, and I see all files when I browse /mnt/disks/ua_appdata/ with a krusader docker container.

I do not have this issue with "regular" shares in Unraid01, though none of them host any docker container config files.

I suspect that it is a permissions issue.

 

Post diagnostics.

Link to comment
18 minutes ago, Woodpusherghd said:

Since upgrading to 6.9 I've been unable to mount drives which I have been previously able to mount on 6.8.  Diagnostics are attached.  I have an external caddy (StarTech)  and I've tried both estata and usb connections, no luck.  BTW, the drives mount via usb (hot plug) in my Windows 10 VM. Diagnostics attached.

tower-diagnostics-20210417-1442.zip 223.96 kB · 0 downloads

 

Unraid/Linux is having an issue with the disk or hardware:

Apr 17 14:07:52 Tower unassigned.devices: Adding disk '/dev/sdj1'...
Apr 17 14:07:52 Tower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdj1' '/mnt/disks/TOSHIBA_HDWD110_46GRL01NS'
Apr 17 14:07:52 Tower kernel: ata1.00: failed to read SCR 1 (Emask=0x40)
Apr 17 14:07:52 Tower kernel: ata1.01: failed to read SCR 1 (Emask=0x40)
Apr 17 14:07:52 Tower kernel: ata1.00: exception Emask 0x100 SAct 0x2000 SErr 0x0 action 0x6 frozen
Apr 17 14:07:52 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 17 14:07:52 Tower kernel: ata1.00: cmd 60/01:68:40:00:00/00:00:00:00:00/40 tag 13 ncq dma 512 in
Apr 17 14:07:52 Tower kernel:         res 50/00:08:00:00:00/00:00:00:00:00/40 Emask 0x100 (unknown error)
Apr 17 14:07:52 Tower kernel: ata1.00: status: { DRDY }
Apr 17 14:07:57 Tower kernel: ata1.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Apr 17 14:07:57 Tower kernel: ata1.00: hard resetting link
Apr 17 14:07:58 Tower kernel: ata1.00: failed to resume link (SControl 0)
Apr 17 14:07:58 Tower kernel: ata1.00: SATA link down (SStatus 0 SControl 0)
Apr 17 14:07:59 Tower kernel: ata1.01: failed to resume link (SControl 0)
Apr 17 14:07:59 Tower kernel: ata1.01: SATA link down (SStatus 0 SControl 0)
Apr 17 14:08:03 Tower kernel: ata1.00: hard resetting link
Apr 17 14:08:04 Tower kernel: ata1.00: failed to resume link (SControl 0)
Apr 17 14:08:04 Tower kernel: ata1.00: SATA link down (SStatus 0 SControl 0)
Apr 17 14:08:10 Tower kernel: ata1.00: hard resetting link
Apr 17 14:08:11 Tower kernel: ata1.00: failed to resume link (SControl 0)
Apr 17 14:08:11 Tower kernel: ata1.00: SATA link down (SStatus 0 SControl 0)
Apr 17 14:08:11 Tower kernel: ata1.00: disabled
Apr 17 14:08:11 Tower kernel: sd 1:0:0:0: [sdj] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=19s
Apr 17 14:08:11 Tower kernel: sd 1:0:0:0: [sdj] tag#13 Sense Key : 0x5 [current] 
Apr 17 14:08:11 Tower kernel: sd 1:0:0:0: [sdj] tag#13 ASC=0x21 ASCQ=0x4 
Apr 17 14:08:11 Tower kernel: sd 1:0:0:0: [sdj] tag#13 CDB: opcode=0x28 28 00 00 00 00 40 00 00 01 00
Apr 17 14:08:11 Tower kernel: blk_update_request: I/O error, dev sdj, sector 64 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0
Apr 17 14:08:11 Tower kernel: ata1: EH complete
Apr 17 14:08:11 Tower kernel: ata1.00: detaching (SCSI 1:0:0:0)
Apr 17 14:08:11 Tower kernel: XFS (sdj1): SB validate failed with error -5.
Apr 17 14:08:11 Tower kernel: blk_update_request: I/O error, dev sdj, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Apr 17 14:08:11 Tower kernel: sd 1:0:0:0: [sdj] Synchronizing SCSI cache
Apr 17 14:08:11 Tower kernel: sd 1:0:0:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00
Apr 17 14:08:11 Tower kernel: sd 1:0:0:0: [sdj] Stopping disk
Apr 17 14:08:11 Tower kernel: sd 1:0:0:0: [sdj] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00
Apr 17 14:08:11 Tower unassigned.devices: Mount of '/dev/sdj1' failed. Error message: mount: /mnt/disks/TOSHIBA_HDWD110_46GRL01NS: can't read superblock on /dev/sdj1. 
Apr 17 14:08:11 Tower unassigned.devices: Partition 'TOSHIBA_HDWD110_46GRL01NS' cannot be mounted.

@JorgeB Might be able to help.

Link to comment

New release of UD.  I've implemented a CIFS mount option called 'cache=none' that disables oplocks that may be the cause of some of the issues some of you have been seeing with CIFS mounts.  Please update and see if it helps with any remote SMB.

Link to comment
14 hours ago, Woodpusherghd said:

I have an external caddy (StarTech)  and I've tried both estata and usb connections,

The eSATA includes a port multiplier:

 

Apr 17 14:05:41 Tower kernel: ata1.15: Port Multiplier 1.2, 0x197b:0x0562 r0, 2 ports, feat 0x5/0xf

 

That's my guess on what's causing the problems, not even sure the onboard AMD SATA controller suports port multipliers, Intel doesn't.

Link to comment
4 hours ago, lakr said:

Had high hopes for the updated of UD - but sadly it seems to have gotten worse.
My shares disappeard again last night and I updated UD after the reboot this morning.

 

With the new version the shares went to zero bytes within 5 minutes.

I have added the diagnostics file.

hightower-diagnostics-20210418-0734.zip 138.45 kB · 0 downloads

After updating UD, unmount and remount all your remote smb shares.  The UD change relates to the mounting of the smb devices and won't take effect until you mount the shares.

Link to comment
8 hours ago, JorgeB said:

The eSATA includes a port multiplier:

 



Apr 17 14:05:41 Tower kernel: ata1.15: Port Multiplier 1.2, 0x197b:0x0562 r0, 2 ports, feat 0x5/0xf

 

That's my guess on what's causing the problems, not even sure the onboard AMD SATA controller suports port multipliers, Intel doesn't.

That makes sense.  I tried another estata caddy that doesn't have a port multiplier and the disk mounts.  

Edited by Woodpusherghd
  • Like 1
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.