dlandon

This is the issue: Oct 6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/Anime' cannot be mounted. Oct 6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/TV Shows' cannot be mounted. Oct 6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/docker' cannot be mounted. Oct 6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/Movies' cannot be mounted. Oct 6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/Workout' cannot be mounted. Oct 6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/Music' cannot be mounted. Oct 6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/Books' cannot be mounted. Oct 6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/Video' cannot be mounted. Oct 6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/transcode' cannot be mounted. Oct 6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/Photo' cannot be mounted. Because you can mount the NFS shares manually, the issue is that the Unraid network is not ready when the shares are auto mounted. I try to have the auto mount of remote shares occur as late as possible in the startup process to give the network enough time to be ready, but in your case it is taking a bit longer.

Always post diagnostics. How can we figure out what is wrong by just being told it doesn't work? Please everyone, post your diagnostics each time you ask for help. It's delays a resolution to your issue if we have to ask every time for diagnostics. Support on the forum is mostly provided by volunteers like myself and it's not respectful of the time we donate to help. Limetech has made the gathering of diagnostics very easy and obscures any private information so it is not exposed. It's not difficult and goes a long way to providing the information needed to diagnose a problem.

I can't help you with a text snippet from the UD page. I asked for a screen shot of the UD page so I can see the file system type, the partitioning of the disks, and the other information shown on the complete UD page.

I'm not an expert with disk controllers, but it appears your disk controller caused Linux to have trouble assigning drive designations for Unraid and Unraid assigned the wrong designations to the array disks. UD checks the vars for the disks not assigned to the array and designates any that are not as unassigned disks. In this case all disks look to UD to be unassigned. Oct 4 17:57:13 Tower emhttpd: Device inventory: Oct 4 17:57:13 Tower emhttpd: HUS724020ALS641_P5GPZ54V (sdm) 512 3907029168 Oct 4 17:57:13 Tower emhttpd: device /dev/sdj problem getting id Oct 4 17:57:13 Tower emhttpd: device /dev/sdk problem getting id Oct 4 17:57:13 Tower emhttpd: device /dev/sdh problem getting id Oct 4 17:57:13 Tower emhttpd: device /dev/sdg problem getting id Oct 4 17:57:13 Tower emhttpd: device /dev/sdd problem getting id Oct 4 17:57:13 Tower emhttpd: HUH72808CLAR8000_VJGT1S8X (sdt) 4096 1953506646 Oct 4 17:57:13 Tower emhttpd: device /dev/sde problem getting id Oct 4 17:57:13 Tower emhttpd: KINGSTON_SA400S37120G_50026B768240E4F0 (sdb) 512 234441648 Oct 4 17:57:13 Tower emhttpd: HUS724040ALS640_PCKJBP8X (sdr) 512 7814037168 Oct 4 17:57:13 Tower emhttpd: device /dev/sdf problem getting id Oct 4 17:57:13 Tower emhttpd: device /dev/sdc problem getting id Oct 4 17:57:13 Tower emhttpd: HUS724040ALS640_PCJGNY0X (sds) 512 7814037168 Oct 4 17:57:13 Tower emhttpd: HUS724040ALS640_PCJGET8X (sdn) 512 7814037168 Oct 4 17:57:13 Tower emhttpd: HUS724040ALS640_PCKJMT2X (sdq) 512 7814037168 Oct 4 17:57:13 Tower emhttpd: HUH72808CLAR8000_VJGS29MX (sdo) 4096 1953506646 Oct 4 17:57:13 Tower emhttpd: HUS724020ALS641_P6JV08ZV (sdl) 512 3907029168 Oct 4 17:57:13 Tower emhttpd: device /dev/sdi problem getting id Oct 4 17:57:13 Tower emhttpd: HUS724040ALS640_PCKJ6ZBX (sdp) 512 7814037168 Oct 4 17:57:13 Tower emhttpd: Kingston_DataTraveler_2.0_1C1B0D65F648B421496A204F-0:0 (sda) 512 30240768 Oct 4 17:57:13 Tower kernel: mdcmd (1): import 0 sdt 64 7814026532 0 HUH72808CLAR8000_VJGT1S8X Oct 4 17:57:13 Tower kernel: md: import disk0: (sdt) HUH72808CLAR8000_VJGT1S8X size: 7814026532 Oct 4 17:57:13 Tower kernel: mdcmd (2): import 1 sdr 64 3907018532 0 HUS724040ALS640_PCKJBP8X Oct 4 17:57:13 Tower kernel: md: import disk1: (sdr) HUS724040ALS640_PCKJBP8X size: 3907018532 Oct 4 17:57:13 Tower kernel: mdcmd (3): import 2 sds 64 3907018532 0 HUS724040ALS640_PCJGNY0X Oct 4 17:57:13 Tower kernel: md: import disk2: (sds) HUS724040ALS640_PCJGNY0X size: 3907018532 Oct 4 17:57:13 Tower kernel: mdcmd (4): import 3 sdq 64 3907018532 0 HUS724040ALS640_PCKJMT2X Oct 4 17:57:13 Tower kernel: md: import disk3: (sdq) HUS724040ALS640_PCKJMT2X size: 3907018532 Oct 4 17:57:13 Tower kernel: mdcmd (5): import 4 sdp 64 3907018532 0 HUS724040ALS640_PCKJ6ZBX Oct 4 17:57:13 Tower kernel: md: import disk4: (sdp) HUS724040ALS640_PCKJ6ZBX size: 3907018532 Oct 4 17:57:13 Tower kernel: mdcmd (6): import 5 sdn 64 3907018532 0 HUS724040ALS640_PCJGET8X Oct 4 17:57:13 Tower kernel: md: import disk5: (sdn) HUS724040ALS640_PCJGET8X size: 3907018532 Oct 4 17:57:13 Tower kernel: mdcmd (7): import 6 sdm 64 1953514552 0 HUS724020ALS641_P5GPZ54V Oct 4 17:57:13 Tower kernel: md: import disk6: (sdm) HUS724020ALS641_P5GPZ54V size: 1953514552 Oct 4 17:57:13 Tower kernel: mdcmd (8): import 7 sdl 64 1953514552 0 HUS724020ALS641_P6JV08ZV Oct 4 17:57:13 Tower kernel: md: import disk7: (sdl) HUS724020ALS641_P6JV08ZV size: 1953514552 This isn't really a UD issue. UD is doing exactly what it is supposed to do. I would report this in the 6.8.3 support forum.

Post the complete diagnostics.zip. I'm needing to see the vars so I can see how Unraid has assigned the disks.

Post diagnostics.

Parsing problem with df output.

You said when you tried to run a SMART test, it said the disk was spun down. That's what I addressed. USB enclosures are a problem with UD because of the way they present the disk serial numbers to UD. I'm not very hopeful that you can do what you want with the enclosure and UD.

You have multiple issues going on here. I found that you have a nvme disk mounted with UD and UD was issuing a spin down command. That's fixed in the latest release. You have one of the mount points on a disk set to 'disks'. That is not a good choice of mount point names. Please post a screen shot of the UD page so I can see the particulars of the disks and partitions. Be sure that you set the 'None' switch to show 'All' so I can see the partitions.

Just released a fix.

I see several issues. Oct 4 18:32:55 UnRaid unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime,discard '/dev/sdk1' '/mnt/disks/SAMSUNG_SSD512GB' Oct 4 18:32:55 UnRaid kernel: XFS (sdk1): mounting with "discard" option, but the device does not support discard Go to UD settings and turn off 'Mount SSDs with 'discard' option?'. Your SSDs don't support it. This is a minor issue. Your disk controller is really struggling. Oct 4 19:41:20 UnRaid kernel: mpt2sas_cm1: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Oct 4 19:41:20 UnRaid kernel: sd 2:0:0:0: [sdj] tag#8976 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Oct 4 19:41:20 UnRaid kernel: sd 2:0:0:0: [sdj] tag#8976 CDB: opcode=0x28 28 00 00 42 5e 98 00 01 00 00 Oct 4 19:41:20 UnRaid kernel: print_req_error: I/O error, dev sdj, sector 4349592 Oct 4 19:41:20 UnRaid kernel: mpt2sas_cm1: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Oct 4 19:41:20 UnRaid kernel: sd 2:0:0:0: [sdj] tag#8975 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Oct 4 19:41:20 UnRaid kernel: sd 2:0:0:0: [sdj] tag#8975 CDB: opcode=0x28 28 00 00 42 5d 98 00 01 00 00 Oct 4 19:41:20 UnRaid kernel: print_req_error: I/O error, dev sdj, sector 4349336 Oct 4 19:41:20 UnRaid kernel: mpt2sas_cm1: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Oct 4 19:41:20 UnRaid kernel: sd 2:0:0:0: Power-on or device reset occurred ### [PREVIOUS LINE REPEATED 1 TIMES] ### Oct 4 19:42:10 UnRaid kernel: ata6: SATA link down (SStatus 0 SControl 300) Oct 4 19:42:10 UnRaid kernel: ata6.00: link offline, clearing class 1 to NONE Oct 4 19:42:10 UnRaid kernel: sd 2:0:0:0: device_block, handle(0x0009) Oct 4 19:42:12 UnRaid kernel: sd 2:0:0:0: device_unblock and setting to running, handle(0x0009) Oct 4 19:42:12 UnRaid kernel: sd 2:0:0:0: [sdj] Synchronizing SCSI cache Oct 4 19:42:12 UnRaid kernel: XFS (sdj1): metadata I/O error in "xfs_buf_iodone_callback_error" at daddr 0x80 len 32 error 5 Oct 4 19:42:12 UnRaid kernel: ata6: COMRESET failed (errno=-32) Oct 4 19:42:12 UnRaid kernel: ata6: reset failed (errno=-32), retrying in 8 secs Oct 4 19:42:13 UnRaid kernel: sd 2:0:0:0: [sdj] tag#5541 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 Oct 4 19:42:13 UnRaid kernel: sd 2:0:0:0: [sdj] tag#5541 CDB: opcode=0x28 28 00 00 82 11 98 00 01 00 00 Oct 4 19:42:13 UnRaid kernel: print_req_error: I/O error, dev sdj, sector 8524184 Oct 4 19:42:13 UnRaid kernel: mpt2sas_cm1: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Oct 4 19:42:13 UnRaid kernel: print_req_error: I/O error, dev sdj, sector 8524440 Oct 4 19:42:13 UnRaid kernel: sd 2:0:0:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 The log is full of thiese entries. Maybe one of the experts on disk controllers can jump in here and help.

Applied another fix. Try the latest release.

Go to a command prompt and enter the folowing: cat /var/log/samba/log.smbd | grep unlink You should see the samba log entries for deleted files.

I was able to reproduce the other poster's issue and confirm a fix, so there is another issue that might be related to your setup. You also said in your case it applied to all UD devices. What I fixed was related to one device and the output from the df command. A screen shot of your UD page would go a long way to helping find the issue, since you are relctant to post diagnostics.

Restart the recycle bin.

There is a delay in the update of the used and free. Wait a few minutes and then refresh UD.

Try again in a few minutes. I had a file name issue.

@Danno93093 supplied me with the diagnostics I needed to find and resolve the issue. This is why I ask for the diagnostics. I found an extra space character from some disks information in the df command that was causing a parsing problem. Problem fixed in the latest release.

If you didn't unplug the USB enclosure, but just kept changing disks, UD would have issues. Reboot and see if it clears things up.

Show the output of the following command: cat /var/state/unassigned.devices/df_status.json

Unplug the enclosure from the USB port, change the disk, then plug the enclosure back into the USB port.

I think your additions to the smb-extra.conf file is causing some issues.

If you post diagnostics, we can help further. I have no issues with the logging.

Check the Syslog. No. UD manages the mounting and unmounting of disk drives and has no control over the disk or file operations. There are some controllers that have some issues with Unraid. Post diagnostics for further help.

The log entry is only when the file is initially deleted, not when it is removed from the recycle bin.