dlandon

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.

It's two sentences. Equal sign added in the latest version. Will publish fixes to these.

Done.

You didn't do the command correctly: /usr/local/sbin/rc.unassigned spindown devX' - spin down a disk. The devX is the device name in the UD page. If the device name is 'Dev 1', then use dev1 as the device to spin down. SSDs will not spin down. Use devX, not sdX. Besides being incorrect for rc.unassigned, the sdX can change after a reboot and you'd reference the wrong disk. The spin down of UD disks was changed in a later version of 6.9rc.

You can't spin the disk down that way. Unraid controls the spin up/down of the disk in later versions of 6.9 and 6.10. You are confusing Unraid. Go to the UD web page and look at the help you'll see a command to spin down the disk using the UD script that uses the Unraid api. Unraid then knows the proper spin status.

Let me give this some thought.

Use UD and install one at a time Set the the mount point you want, and click the three gears icon and set the disk to auto mount. Do the same for the other disk. Then just plug in a disk when you want to back up.

It's a known issue (not unique to 6.10) and the only solutions are: - Disable hard links. - Don't use cache on the share. - Use SMB, and not NFS for remote shares. It's a limitation of NFS and Unraid has no control over the issue.

Sometimes it will be suggested to post on the forum that is appropriate for the issue being presented so the user can get a quicker answer.

If you update to the latest version of UD, the format button will be enabled and when you click it you will see a dialog explaining what needs to be done to format the disk.

Click on the three gears 'Settings' icon and turn off 'Passed Through".

Yes, but don't install or mount them both at the same time.

Your disk has a problem: Aug 7 09:36:05 Tower unassigned.devices: Formatting disk '/dev/sdf' with 'xfs' filesystem. Aug 7 09:36:06 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s Aug 7 09:36:06 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 38 5a f0 00 00 f0 00 Aug 7 09:36:06 Tower kernel: print_req_error: 2 callbacks suppressed Aug 7 09:36:06 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976771824 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0 Aug 7 09:36:06 Tower emhttpd: read SMART /dev/sdf Aug 7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s Aug 7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e1 10 00 00 f0 00 Aug 7 09:36:08 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976871696 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0 Aug 7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s Aug 7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e2 00 00 00 f0 00 Aug 7 09:36:08 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976871936 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0 Aug 7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s Aug 7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e2 f0 00 00 f0 00 Aug 7 09:36:08 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976872176 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0 Aug 7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s Aug 7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e3 e0 00 00 f0 00 Aug 7 09:36:08 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976872416 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0 Aug 7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s Aug 7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e4 d0 00 00 f0 00 Aug 7 09:36:08 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976872656 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0 Aug 7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s Aug 7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e5 c0 00 00 f0 00 Aug 7 09:36:08 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976872896 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0 Aug 7 09:36:09 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s Aug 7 09:36:09 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e6 b0 00 00 80 00 Aug 7 09:36:09 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976873136 op 0x1:(WRITE) flags 0x0 phys_seg 16 prio class 0 Aug 7 09:36:09 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s Aug 7 09:36:09 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e7 30 00 00 f0 00 Aug 7 09:36:09 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976873264 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0 Aug 7 09:36:09 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s Aug 7 09:36:09 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e8 20 00 00 f0 00 Aug 7 09:36:09 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976873504 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0 Aug 7 09:36:09 Tower kernel: floppy: error 10 while reading block 0 ### [PREVIOUS LINE REPEATED 5 TIMES] ### I wouldn't use the disk until you sort this out.