dlandon

I can't figure out why you are having the problem. Your disk is designated /dev/sdab, which was an issue until the latest release of UD where I applied a fix for four letter disk designations. I have done some testing to verify that the /dev/sdab is parsed correctly. Is there any chance you can reformat the disk? The commands to open an encrypted disk and change the UUID at the command line can be daunting.

Not true. It is being considered and will be implemented in due time. There will be some testing I will need to do to be sure it doesn't break UD remote shares. I'm sure you'd like us to be sure it doesn't cause any major issues. The stale file handle issue has been around a long time with no clear answer and we want to see if it can eventually solve the stale file handle problem.

Click on the check mark next to the partition mountpoint and see if the disk has issues. I just tried on an encrypted disk and it worked for me.

I think the problem is the password/passphrase not working. It's trying to use the Unraid password. Go to the UD settings page and set the password there for the disk. UD will then use that password to open the disk for the UUID change. You should then be able to change the UUID.

Because it is an encrypted disk, it has to be opened with cryptsetup. That command won't work at the command line. I see an issue with the luksOpen. Let me take a look.

That's a LMS log, and not the container log. Probably best to get support from the LMS developers.

Install the Unassigned Devices plugin and set up a script to run when the drive is hot plugged.

This issue would be better for @JorgeB to look at. He is the disk wizard.

Click on the check mark next to the mountpoint and see if the disk can be repaired. Looks like it may be a disk issue.

This has nothing to do with your issue. The spin down timer was being applied for older versions of Unraid and didn't apply to 6.10. Unraid overwrites the timer when it takes over the spin up/down. This is the screen shot I was asking for: Also post your diagnostics for me to have a look.

Make sure you have the latest version of UD. The previous version had an issue with changing the UUID. I wanted a screen shot of the disk on the actual UD page, not the UD settings page.

Show a screen shot of the disk on the UD page.

Look at the help on the UD page for commands to mount/unmount a disk. You could set up User Scripts on a schedule to mount and unmount the disk. You'd need one scheduled script for mount, and another for unmount.

Go to the UD settings and change the UUID for this disk.

Edit the container template and click the 'Show more settings'. Confirm that the mapping makes sense for the config folder.

Yes, it should work this way. Be sure to properly shut it down in Windows and Unraid to prevent these kinds of issues.

Yes, the drive designations can change on a reboot.

If you're talking about the container log, you can control log rotation on the Settings->Docker settings page. Turn on Advanced view, stop Docker, the enable log rotation. You can also set the size of the logs and the number of logs to maintain.

That partition doesn't show as having a file system. Post diagnostics.

Fixed in the next release.

I stopped these messages by setting "Enable Router Advertisement" to disabled in my ASUS router. There is an issue with the syslog filtering setup in rsyslog.conf. I solved the issue with the Enhanced Log plugin so it will work properly. Install the plugin and then set up the syslog filter to what you want with the plugin.

Put your drive in the Pool and Unraid will monitor disk utilization.

You need to update UD to the latest version. Then try clicking on the check mark next to the partition and see if UD can repair it, but it looks more like a cable or controller problem to me.

Your disk is having a problem: Aug 14 16:36:16 Shinagawa unassigned.devices: Mounting 'Auto Mount' Devices... Aug 14 16:36:16 Shinagawa unassigned.devices: Disk with serial 'Cruzer_Glide_3.0_4C530001290809121503', mountpoint 'SanDisk_Cruzer_Glide_3.0' is not set to auto mount. Aug 14 16:36:16 Shinagawa unassigned.devices: Adding disk '/dev/sde1'... Aug 14 16:36:16 Shinagawa unassigned.devices: No filesystem detected on '/dev/sde1'. Aug 14 16:36:16 Shinagawa unassigned.devices: Partition 'WDC_WD40EFRX-68WT0N0_WD-WCC4E3KZDDCH-part1' cannot be mounted. Aug 14 16:36:16 Shinagawa unassigned.devices: Adding disk '/dev/sde2'... Aug 14 16:36:16 Shinagawa unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o rw,auto,async,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000 '/dev/sde2' '/mnt/disks/DB6' Aug 14 16:36:20 Shinagawa kernel: ata5.00: exception Emask 0x0 SAct 0xc0000 SErr 0x0 action 0x0 Aug 14 16:36:20 Shinagawa kernel: ata5.00: irq_stat 0x40000008 Aug 14 16:36:20 Shinagawa kernel: ata5.00: failed command: READ FPDMA QUEUED Aug 14 16:36:20 Shinagawa kernel: ata5.00: cmd 60/00:90:f0:e8:63/01:00:00:00:00/40 tag 18 ncq dma 131072 in Aug 14 16:36:20 Shinagawa kernel: res 41/40:00:80:e9:63/00:00:00:00:00/40 Emask 0x409 (media error) <F> Aug 14 16:36:20 Shinagawa kernel: ata5.00: status: { DRDY ERR } Aug 14 16:36:20 Shinagawa kernel: ata5.00: error: { UNC } Aug 14 16:36:20 Shinagawa kernel: ata5.00: configured for UDMA/133 Aug 14 16:36:20 Shinagawa kernel: scsi_io_completion_action: 2 callbacks suppressed Aug 14 16:36:20 Shinagawa kernel: sd 6:0:0:0: [sde] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=3s Aug 14 16:36:20 Shinagawa kernel: sd 6:0:0:0: [sde] tag#18 Sense Key : 0x3 [current] Aug 14 16:36:20 Shinagawa kernel: sd 6:0:0:0: [sde] tag#18 ASC=0x11 ASCQ=0x4 Aug 14 16:36:20 Shinagawa kernel: sd 6:0:0:0: [sde] tag#18 CDB: opcode=0x88 88 00 00 00 00 00 00 63 e8 f0 00 00 01 00 00 00 Aug 14 16:36:20 Shinagawa kernel: print_req_error: 2 callbacks suppressed Aug 14 16:36:20 Shinagawa kernel: blk_update_request: I/O error, dev sde, sector 6547840 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Aug 14 16:36:20 Shinagawa kernel: ata5: EH complete Aug 14 16:36:24 Shinagawa kernel: ata5.00: exception Emask 0x0 SAct 0x4003fc SErr 0x0 action 0x0 Aug 14 16:36:24 Shinagawa kernel: ata5.00: irq_stat 0x40000008 Aug 14 16:36:24 Shinagawa kernel: ata5.00: failed command: READ FPDMA QUEUED Aug 14 16:36:24 Shinagawa kernel: ata5.00: cmd 60/00:b0:f0:e9:63/01:00:00:00:00/40 tag 22 ncq dma 131072 in Aug 14 16:36:24 Shinagawa kernel: res 41/40:00:f8:e9:63/00:00:00:00:00/40 Emask 0x409 (media error) <F> Aug 14 16:36:24 Shinagawa kernel: ata5.00: status: { DRDY ERR } Aug 14 16:36:24 Shinagawa kernel: ata5.00: error: { UNC } Aug 14 16:36:24 Shinagawa kernel: ata5.00: configured for UDMA/133 Aug 14 16:36:24 Shinagawa kernel: sd 6:0:0:0: [sde] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=6s Aug 14 16:36:24 Shinagawa kernel: sd 6:0:0:0: [sde] tag#22 Sense Key : 0x3 [current] Aug 14 16:36:24 Shinagawa kernel: sd 6:0:0:0: [sde] tag#22 ASC=0x11 ASCQ=0x4 Aug 14 16:36:24 Shinagawa kernel: sd 6:0:0:0: [sde] tag#22 CDB: opcode=0x88 88 00 00 00 00 00 00 63 e9 f0 00 00 01 00 00 00 Aug 14 16:36:24 Shinagawa kernel: blk_update_request: I/O error, dev sde, sector 6547960 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0 Aug 14 16:36:24 Shinagawa kernel: ata5: EH complete and Aug 14 16:37:32 Shinagawa unassigned.devices: Mount of '/dev/sde2' failed: 'ntfs_attr_pread_i: ntfs_pread failed: Input/output error Failed to read NTFS : Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details. ' Aug 14 16:37:32 Shinagawa unassigned.devices: Partition 'DB6' cannot be mounted.

Post diagnostics.