JorgeB

sdj1 (and md11) are missing from that list, it confirms something damaged the superblocks (and possibly more) on that disk, other that using a file recovery util the only other thing that comes to mind is to see if the superblock is correctly emulated by parity, but to do that you'd need to disable disk11, stop array, unassign disk11, start array, post new diags, leave actual disk11 untouched so you can later use a file recovery util if needed.

Partition is there, now post the output of: blkid

It's x4 only, so link is correct:

Error suggests superblock is damaged in one ore more devices, try the safe recovery options described here first: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490

No valid filesystem is being detected in that disk, please post output of: fdisk -l /dev/sdj

Should be faster than that, I assume you're using the bottom slot, which is x4 only, still should give you around 100MB/s with 16 drives, check the current link speed/width with lspci -vv -s 05:00.0

Diags after array start please.

Still seems a little on the low side for that CPU, this is with a D2700, it is faster but not my much (passmark of 492 vs 423): dd if=/dev/zero bs=1M count=1k | md5sum 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 4.70252 s, 228 MB/s I would expect it to be 10 or 20% faster on this test, not twice as fast, might be worth checking the BIOS to make sure CPU cache is enable and/or reset CMOS to optimal defaults. Some more comparison tests, though as already mentioned a low end CPU can always limit your performance, especially when using user shares, but it also shouldn't be that slow, source disk is a 500GB 2.5" HDD: dd if=/mnt/disk2/test/1.mp4 bs=1M count=1k | md5sum 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 12.1803 s, 88.2 MB/s dd if=/mnt/user/test/1.mp4 bs=1M count=1k | md5sum 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 16.5119 s, 65.0 MB/s Reading from a client computer over SMB I get around 110MB/s when using a disk share and around 65MB/s with a user share.

Looks more like a power/connection problem, check/replace/swap cables on parity2.

2022-05-15 19:19:39.627+0000: 14471: error : virQEMUFileOpenAs:11519 : Failed to open file '/mnt/disks/2139E5D6640F/Windows 10/vdisk1.img': No such file or directory You need to mount the NVMe device, and check that mountpoint (or the VM path) is correct. May 15 21:19:15 Tower unassigned.devices: Disk with ID 'CT1000P2SSD8_2139E5D6640F (nvme0n1)' is not set to auto mount. P.S. this indicates that one of the cache devices dropped offline in the past: May 15 21:19:14 Tower kernel: BTRFS info (device sde1): bdev /dev/sde1 errs: wr 441362, rd 1149, flush 10893, corrupt 1529, gen 0 You should run a scrub and monitor for more issues, more info below: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582

You can add a notification to the go file, e.g.: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & /usr/local/emhttp/webGui/scripts/notify -i normal -s "Boot complete"

Try to disconnect every USB cable/device (except the Unraid flash drive) to see if it goes way. Because of that there might be some data corruption on the rebuild disk4, unless by luck the error sectors corresponded to empty space there. Cache filesystem is fully allocated, you need to run a balance: https://forums.unraid.net/topic/62230-out-of-space-errors-on-cache-drive/?do=findComment&comment=610551

Unraid currently doesn't support share quotas, you more or less accomplish what you want if the share fits in a single disk, set the share to use that disk only and set the minimum free space accordingly, e.g., lets say disk 1 is 4TB, set the "Test" share to only use disk1 and set minimum free space for that share to 3500GB.

That's a MegaRAID controller with no IT mode option, you can use it but it's not recommended, there will likely be several issues, like not possible to connect the devices to a different controller if that one fails without doing a new config or possibly rebuilding all the disks in the array, no spin down, possibly no SMART and temps, etc

Please post the diagnostics after upgrading.

It might, though I never found it, still I would prefer to risk that that having disks overheating due to for example a failed fan and being notified half an hour later, when it already might be too late, disks in a close space like in a 5in3 cage or similar can overheat very quick if a fan stops or gets blocked.

Yes, I agree, default should be much lower.

Are you doing this? https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606

1 or 2 secs would probably be nonsense, I've been using 60 or 120 secs for years without issues.

Turns out this can also occur between two servers running v6.10-rc, so lets see if someone has an idea on what's causing this, or you can create a bug report.

Because of have the GUI updating at the default 1800secs, that's 30 minutes, change that to a more reasonable 60 or 120secs. Settings -> Disk Settings -> Poll Attributes.

VM page uses binary units, rest of the GUI uses SI units, 226GiB is 243GB so it looks about right.

Try creating the folder manually: mkdir /mnt/cache/domains

blkdiscard /dev/sdX or blkdiscard -f /dev/sdX depending on the Unraid version.