dlandon

Hopefully you unmount the disks before you unplug them. Based on your log, it appears you are not unmounting first: Jul 28 22:33:47 Tower ntfs-3g[22374]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Jul 28 22:33:47 Tower ntfs-3g[22374]: Failed to read index block: Input/output error Jul 28 22:33:47 Tower kernel: Buffer I/O error on dev sdx2, logical block 36561612, async page read Jul 28 22:33:47 Tower ntfs-3g[23876]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Jul 28 22:33:47 Tower ntfs-3g[23876]: Failed to read index block: Input/output error Jul 28 22:33:47 Tower kernel: Buffer I/O error on dev sdaa2, logical block 73, async page read Jul 28 22:33:47 Tower ntfs-3g[23763]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Jul 28 22:33:47 Tower ntfs-3g[23763]: Failed to read index block: Input/output error Jul 28 22:33:47 Tower kernel: Buffer I/O error on dev sdab2, logical block 173, async page read Jul 28 22:33:47 Tower ntfs-3g[22458]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Jul 28 22:33:47 Tower ntfs-3g[22458]: Failed to read index block: Input/output error Jul 28 22:33:47 Tower kernel: Buffer I/O error on dev sdy2, logical block 126, async page read Jul 28 22:33:47 Tower ntfs-3g[22326]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Jul 28 22:33:47 Tower ntfs-3g[22326]: Failed to read index block: Input/output error Jul 28 22:33:47 Tower kernel: Buffer I/O error on dev sdv2, logical block 720961, async page read Jul 28 22:33:47 Tower ntfs-3g[22407]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Jul 28 22:33:47 Tower ntfs-3g[22407]: Failed to read index block: Input/output error Jul 28 22:33:47 Tower kernel: Buffer I/O error on dev sdw2, logical block 14178, async page read Jul 28 22:33:47 Tower ntfs-3g[24003]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Jul 28 22:33:47 Tower ntfs-3g[24003]: Failed to read index block: Input/output error Jul 28 22:33:47 Tower kernel: Buffer I/O error on dev sdz1, logical block 1467255154, async page read Or, the disks are dropping off line and creating a lot of ntfs issues.

Please post diagnostics so we can investigate this. We haven't been able to reproduce it yet.

I suggest several things: Update all your dockers as they are out of date. Upgrade to 6.12.3. A docker stopping issue has been fixed that might be what's happening to you. Check the Settings->Docker "Docker stop timeouot" and see if that is enough time to shut down your dockers.

Your issue is a DNS issue. That's why you can ping google, but cannot 'connect' to the Internet. There is a bug in the network settings related to the Static/Automatic DNS setting. You'll see on your page it says Automatc, and yet you have entered 1.1.1.1. Be sure the setting is Static and then enter the DNS setting. I suspect the Automatic is taken as the setting. You may have to apply the settings a few times to get them to 'take'.

No. I thought you were doing a network copy. Disk to disk should be affected by NIC speed.

There is ram disk caching that can collect a lot of information and then writes to the disk which can look like it holds back the transfer. That cache can be by default very large. You have a lot of ram. Install the Tips and Tweaks plugin and adjust it to see if it can help. I don't see this situation causing a 36 hour slow down though. You might want to look at some other tweaks in the Tips and Tweaks plugin like on your NICs.

The reason this showed up is that you had a PC with the UD GUI open and apparently your server was working very hard. The command that timed out is UD trying to read the mounts file to determine mounted status of the UD devices. Reading that file should not take longer than 1 second. I will increase the time out a bit to try to keep this from happening, but it is harmless other than to show UD could potentially be hanging. UD will catch up on the mounted status at the next background scan. Maybe ask the plugin author if they can adjust the priority.

What share are you copying to? I only see the isos share set up for a cache. Set up all your shares with the cache. Also, turn off mover logging. It can flood the syslog making it hard to read.

Can you post diagnostics so I can see why UD got hung?

Do you have 'Enhanced macOS interoperability:' set to 'Yes'? Post diagnostics.

Can you see the files with the built in file browser?

Post diagnostics.

That drive is having issues: Jul 26 15:58:52 srvr kernel: XFS (sdb1): Mounting V5 Filesystem Jul 26 15:58:52 srvr kernel: ata3.00: exception Emask 0x10 SAct 0x80000008 SErr 0x480101 action 0x6 frozen Jul 26 15:58:52 srvr kernel: ata3.00: irq_stat 0x08000000, interface fatal error Jul 26 15:58:52 srvr kernel: ata3: SError: { RecovData UnrecovData 10B8B Handshk } Jul 26 15:58:52 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 26 15:58:52 srvr kernel: ata3.00: cmd 61/00:18:fc:a5:21/06:00:1d:00:00/40 tag 3 ncq dma 786432 out Jul 26 15:58:52 srvr kernel: res 40/00:18:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error) Jul 26 15:58:52 srvr kernel: ata3.00: status: { DRDY } Jul 26 15:58:52 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 26 15:58:52 srvr kernel: ata3.00: cmd 61/00:f8:fc:9b:21/0a:00:1d:00:00/40 tag 31 ncq dma 1310720 ou Jul 26 15:58:52 srvr kernel: res 40/00:18:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error) Jul 26 15:58:52 srvr kernel: ata3.00: status: { DRDY } Jul 26 15:58:52 srvr kernel: ata3: hard resetting link Jul 26 15:58:53 srvr kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 26 15:58:53 srvr kernel: ata3.00: supports DRM functions and may not be fully accessible ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jul 26 15:58:53 srvr kernel: ata3.00: configured for UDMA/133 Jul 26 15:58:53 srvr kernel: ata3: EH complete Jul 26 15:58:53 srvr kernel: ata3.00: exception Emask 0x10 SAct 0xc000 SErr 0x400101 action 0x6 frozen Jul 26 15:58:53 srvr kernel: ata3.00: irq_stat 0x0c000000, interface fatal error Jul 26 15:58:53 srvr kernel: ata3: SError: { RecovData UnrecovData Handshk } Jul 26 15:58:53 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 26 15:58:53 srvr kernel: ata3.00: cmd 61/00:70:fc:9b:21/0a:00:1d:00:00/40 tag 14 ncq dma 1310720 ou Jul 26 15:58:53 srvr kernel: res 40/00:78:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error) Jul 26 15:58:53 srvr kernel: ata3.00: status: { DRDY } Jul 26 15:58:53 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 26 15:58:53 srvr kernel: ata3.00: cmd 61/00:78:fc:a5:21/06:00:1d:00:00/40 tag 15 ncq dma 786432 out Jul 26 15:58:53 srvr kernel: res 40/00:78:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error) Jul 26 15:58:53 srvr kernel: ata3.00: status: { DRDY } Jul 26 15:58:53 srvr kernel: ata3: hard resetting link Jul 26 15:58:53 srvr kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 26 15:58:53 srvr kernel: ata3.00: supports DRM functions and may not be fully accessible ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jul 26 15:58:53 srvr kernel: ata3.00: configured for UDMA/133 Jul 26 15:58:53 srvr kernel: ata3: EH complete Jul 26 15:58:53 srvr kernel: ata3.00: exception Emask 0x10 SAct 0xc000 SErr 0x400101 action 0x6 frozen Jul 26 15:58:53 srvr kernel: ata3.00: irq_stat 0x08000000, interface fatal error Jul 26 15:58:53 srvr kernel: ata3: SError: { RecovData UnrecovData Handshk } Jul 26 15:58:53 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 26 15:58:53 srvr kernel: ata3.00: cmd 61/00:70:fc:a5:21/06:00:1d:00:00/40 tag 14 ncq dma 786432 out Jul 26 15:58:53 srvr kernel: res 40/00:78:fc:9b:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error) Jul 26 15:58:53 srvr kernel: ata3.00: status: { DRDY } Jul 26 15:58:53 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 26 15:58:53 srvr kernel: ata3.00: cmd 61/00:78:fc:9b:21/0a:00:1d:00:00/40 tag 15 ncq dma 1310720 ou Jul 26 15:58:53 srvr kernel: res 40/00:78:fc:9b:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error) Jul 26 15:58:53 srvr kernel: ata3.00: status: { DRDY } Jul 26 15:58:53 srvr kernel: ata3: hard resetting link Jul 26 15:58:53 srvr kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 26 15:58:53 srvr kernel: ata3.00: supports DRM functions and may not be fully accessible ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jul 26 15:58:53 srvr kernel: ata3.00: configured for UDMA/133 Jul 26 15:58:53 srvr kernel: ata3: EH complete Jul 26 15:58:53 srvr kernel: ata3: limiting SATA link speed to 3.0 Gbps Jul 26 15:58:53 srvr kernel: ata3.00: exception Emask 0x10 SAct 0x6 SErr 0x400101 action 0x6 frozen Jul 26 15:58:53 srvr kernel: ata3.00: irq_stat 0x08000000, interface fatal error Jul 26 15:58:53 srvr kernel: ata3: SError: { RecovData UnrecovData Handshk } Jul 26 15:58:53 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 26 15:58:53 srvr kernel: ata3.00: cmd 61/00:08:fc:9b:21/0a:00:1d:00:00/40 tag 1 ncq dma 1310720 ou Jul 26 15:58:53 srvr kernel: res 40/00:10:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error) Jul 26 15:58:53 srvr kernel: ata3.00: status: { DRDY } Jul 26 15:58:53 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 26 15:58:53 srvr kernel: ata3.00: cmd 61/00:10:fc:a5:21/06:00:1d:00:00/40 tag 2 ncq dma 786432 out Jul 26 15:58:53 srvr kernel: res 40/00:10:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error) Jul 26 15:58:53 srvr kernel: ata3.00: status: { DRDY } Jul 26 15:58:53 srvr kernel: ata3: hard resetting link Jul 26 15:58:54 srvr kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jul 26 15:58:54 srvr kernel: ata3.00: supports DRM functions and may not be fully accessible ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jul 26 15:58:54 srvr kernel: ata3.00: configured for UDMA/133 Jul 26 15:58:54 srvr kernel: ata3: EH complete Jul 26 15:58:54 srvr kernel: ata3.00: exception Emask 0x10 SAct 0x60 SErr 0x400100 action 0x6 frozen Jul 26 15:58:54 srvr kernel: ata3.00: irq_stat 0x08000000, interface fatal error Jul 26 15:58:54 srvr kernel: ata3: SError: { UnrecovData Handshk } Jul 26 15:58:54 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 26 15:58:54 srvr kernel: ata3.00: cmd 61/00:28:fc:a5:21/06:00:1d:00:00/40 tag 5 ncq dma 786432 out Jul 26 15:58:54 srvr kernel: res 40/00:30:fc:9b:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error) Jul 26 15:58:54 srvr kernel: ata3.00: status: { DRDY } Jul 26 15:58:54 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 26 15:58:54 srvr kernel: ata3.00: cmd 61/00:30:fc:9b:21/0a:00:1d:00:00/40 tag 6 ncq dma 1310720 ou Jul 26 15:58:54 srvr kernel: res 40/00:30:fc:9b:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error) Jul 26 15:58:54 srvr kernel: ata3.00: status: { DRDY } Jul 26 15:58:54 srvr kernel: ata3: hard resetting link Jul 26 15:58:54 srvr kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jul 26 15:58:54 srvr kernel: ata3.00: supports DRM functions and may not be fully accessible ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jul 26 15:58:54 srvr kernel: ata3.00: configured for UDMA/133 Jul 26 15:58:54 srvr kernel: ata3: EH complete Jul 26 15:58:54 srvr kernel: ata3.00: exception Emask 0x10 SAct 0x300 SErr 0x400101 action 0x6 frozen Jul 26 15:58:54 srvr kernel: ata3.00: irq_stat 0x08000000, interface fatal error Jul 26 15:58:54 srvr kernel: ata3: SError: { RecovData UnrecovData Handshk } Jul 26 15:58:54 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 26 15:58:54 srvr kernel: ata3.00: cmd 61/00:40:fc:9b:21/0a:00:1d:00:00/40 tag 8 ncq dma 1310720 ou Jul 26 15:58:54 srvr kernel: res 40/00:48:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error) Jul 26 15:58:54 srvr kernel: ata3.00: status: { DRDY } Jul 26 15:58:54 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 26 15:58:54 srvr kernel: ata3.00: cmd 61/00:48:fc:a5:21/06:00:1d:00:00/40 tag 9 ncq dma 786432 out Jul 26 15:58:54 srvr kernel: res 40/00:48:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error) Jul 26 15:58:54 srvr kernel: ata3.00: status: { DRDY } Jul 26 15:58:54 srvr kernel: ata3: hard resetting link Jul 26 15:58:54 srvr kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jul 26 15:58:54 srvr kernel: ata3.00: supports DRM functions and may not be fully accessible ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jul 26 15:58:54 srvr root: mount: /mnt/cache: can't read superblock on /dev/sdb1. Check your cables and interface.

Not sure without reviewing all the changes since then, buit you should update to all the latest versions.

Were any of the disks removed before being unmounted? That could cause problems.

Jul 26 07:37:36 DT310 unassigned.devices: Partition 'sde1' does not have a file system and cannot be mounted. The disk has no file system. You might want to check cables. Jul 26 07:37:36 DT310 unassigned.devices: Warning: shell_exec(/bin/df '/mnt/disks/ugg' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 10s! This might be an indication of other issues. Looks like your reboot was a hard reboot? Jul 26 07:37:25 DT310 kernel: FAT-fs (sdd1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Your remote server doesn't seem to be on line when UD tries to mount the remote shares: Jul 25 19:48:38 DellRaid unassigned.devices: Remote Server 'DARKNUX' is offline and share '//DARKNUX/Unraid' cannot be mounted. There is timer you can set to delay auto mounting remote shares. Go to UD Settings and set the time delay to mount remote shares to what you think is a reasonable value. The default is 5 seconds.

Try this command: /usr/local/emhttp/plugins/unassigned.devices/event/stopping_svcs This is what UD uses to unmount all devices when shutting down. Downside is it will unmount all your UD devices.

You should probably reseat the nvme disk. Some users have reported this issue and reseating the nvme disk resolved it.

Do the new drives show in the BIOS? Sounds like you might have a BIOS setup issue.

Are you talking about array shares or UD shares?

Yes, there is an issue with the calculation. I'll issue an update today.

Just did a test and it looks like the 'Format' button is not disabled when destructive mode is disabled. Fix will be in the next release of UD. If you click the 'Format' button it will tell you that you can't format the disk with destructive mode disabled.

I just noticed your screen shot. If the disk is passed through to a VM, don't mount it. You will cause corruption. Why is the disk 'Dev 1' showing 'Mount' and not 'Passed'? This is destructive mode:

Something else is going on here. The button will not be orange if the destructive mode is disabled. I've never seen a situation where it would be if destrctive mode is disabled.