JorgeB

That's normal if you're using the default system share, since it doesn't checksum the data, so also no way to verify or fix it, that's also mentioned in the FAQ link.

That usually happens when a disk drops offline or there was another controller related issue, you should post the diags.

This will happen if that disk had the fs set to "xfs" instead of "auto", only disks set to "auto" will use the default filesystem on the disk settings, you can check by going to main and clicking on the disk .

You need to completely wipe the device, e.g., with blkdiscard, or removr the partition, if you just change the filesystem Unraid will use the existing partition when re-formatting.

Frequent ATA errors on the log, which result in freezes and can even drop devices in some cases, Asmedia is good as a 2 port controller, not good with port multipliers, for more ports get a JMB585 or an 8 port LSI HBA.

It's considered safe enough for most if running raid1 metadata, Unraid default, should not use raid5/6 for metadata, I'm running several raid5 pools for more than a year without issues, still should have backups of anything important.

Try this: https://forums.unraid.net/topic/77912-solved-cant-start-vm-after-restore/?do=findComment&comment=721029

Please don't double post, locking this one, anyone responding please use the other thread:

Did a test with a Windows VM to see if there was a difference with the new partition alignment, total bytes written after 16 minutes (VM is idling doing nothing, not even internet connected): space_cache=v1, old alignment - 7.39GB space_cache=v2, old alignment - 1.72GB space_cache=v2, new alignment - 0.65GB So that's encouraging, though I guess that unlike v2 space cache the new alignment might work better for some NVMe devices and don't make much difference for others, still worth testing IMHO, since for some it should also give better performance, for this test I used an Intel 600p.

Someone/something did, it's certainly not default, but yes you can remove it, on the main page click on flash, scroll down to Syslinux configuration, make sure it's set to "menu view" (upper right corner) and remove: xen-pciback.hide=(07:00.0)(08:00.0)(09:00.0)(0a:00.0)

As long as there are no uncorrectable errors all should be fine.

It would still be my first guess, could also be a disk, but that's not very likely and hopefully it's RAM since it would be easier to find/fix.

Barbecue of hiding the controller from Unraid with that custom command line, it will hide any controllers/cards using those IDs, HBA is currently 07:00:0

Disk is dropping offline, did you also replace the power cable? If not do that, if yes, swap that disk's SATA and power cable with another one, preferably one connected to the onboard SATA controller and post new diags if/when it fails again.

Problems with the NVMe device: Jul 14 08:32:43 Tower kernel: nvme nvme0: I/O 769 QID 1 timeout, aborting Jul 14 08:32:43 Tower kernel: nvme nvme0: I/O 698 QID 3 timeout, aborting Jul 14 08:32:43 Tower kernel: nvme nvme0: I/O 128 QID 4 timeout, aborting Jul 14 08:32:43 Tower kernel: nvme nvme0: I/O 0 QID 5 timeout, aborting Jul 14 08:32:43 Tower kernel: nvme nvme0: I/O 1 QID 5 timeout, aborting Jul 14 08:32:43 Tower kernel: nvme nvme0: I/O 2 QID 5 timeout, aborting Jul 14 08:32:43 Tower kernel: nvme nvme0: I/O 3 QID 5 timeout, aborting Jul 14 08:32:43 Tower kernel: nvme nvme0: I/O 5 QID 5 timeout, aborting Jul 14 08:33:13 Tower kernel: nvme nvme0: I/O 769 QID 1 timeout, reset controller Jul 14 08:33:44 Tower kernel: nvme nvme0: I/O 0 QID 0 timeout, reset controller This can sometimes help: Some NVMe devices have issues with power states on Linux, try this, on the main GUI page click on flash, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (on the top right) and add this to your default boot option, after "append" nvme_core.default_ps_max_latency_us=0 Reboot and see if it makes a difference.

Scrub should always output the affected filenames to the log, it won't be on the log when a checksum error is detected during a normal file read, just the error without the filename.

Again, if that was the case everyone using those NICs would have the same problem, no?

I already mentioned that: The link I posted also says what you should do.

Because of this: Jul 14 12:58:04 Interocitor kernel: Command line: BOOT_IMAGE=/bzimage xen-pciback.hide=(07:00.0)(08:00.0)(09:00.0)(0a:00.0) initrd=/bzroot

Dup:

Run a scrub, any corrupt files will be identified on the syslog during it.

Not directly, but anyone can use it if advantageous, I use a lot of reflinking on my btrfs pools.

Completely understand, can't blame a guy for asking That is indeed what I plan to use as soon as everything is working correctly with the multiple pools. P.S. I sent some beer money your way yesterday to show my appreciation for all the work you have done and continue to do on this, and encourage anyone who relies on UD to do the same.

Can't download the diags, please attach again on a new post.

Going to move this to the KVM forum, might get more help there.