JorgeB

Jul 10 19:41:27 HedonistMedia kernel: BTRFS: device fsid 735f5a28-a992-4be9-b621-47603518b082 devid 1 transid 202666812 /dev/sdc1 scanned by udevd (1059) Jul 10 19:41:27 HedonistMedia kernel: BTRFS: device fsid 735f5a28-a992-4be9-b621-47603518b082 devid 2 transid 202683889 /dev/sdf1 scanned by udevd (1179) Jul 10 19:41:27 HedonistMedia kernel: BTRFS: device fsid 735f5a28-a992-4be9-b621-47603518b082 devid 3 transid 202683889 /dev/sdj1 scanned by udevd (1200) I assume the old deceive is sdc? Did you replace or add new device and the remove the other one? Either way something went wrong since the old device is still part of the filesystem, fiscally disconnect the old device (I'd like to avoid wiping it for now) and if the pool mounts, if it doesn't post new diags

Disk look OK and problem happened right after spin up, rebuild the disk and if it happens again I would either connect that disk to a different controller, like the Intel SATA ports or disable spin down.

If nomodeset helps just add that to syslinux.cfg, click on the flash drive and scroll down to "syslinux configuration":
 

 
Save and reboot.
 

NIC is being passed-through to the VM:
 
-device vfio-pci,host=0000:05:00.0,id=hostdev0,bus=pci.0,addr=0x8 \  
05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 11)  
 
 
 
 

Unraid tracks devices by serial number, not by filesystem UUID, once you assign the new disk Unraid only cares about that one.

Update to 6.10.3 and they will work.

Jul 5 09:39:17 Tower kernel: ahci 0000:03:00.0: AHCI controller unavailable!  
Problems with the Marvell controller, and all devices connected there dropped, Marvell controllers are not recommended for Unraid, first thing I would recommend is replacing it with a recommended controller, once that's done (or if you don't want to do that for now just power cycle the server) run a scrub on the pool and post new diags.

Click the minus to hide the partition, you can also set to show or hide partitions by default for each device by clicking on its settings, and next time or if you have more questions please use the existing plugin support thread.
 
 

Yes, it does look like a power/connection problem, disk 1 also showing similar issues, replace cables and rebuild.

Jul 6 21:38:14 kunraid kernel: BTRFS: device fsid 0ecc5969-4afc-4b9a-a299-3fab30cf63d9 devid 1 transid 153079 /dev/sdb1 scanned by udevd (1244) Jul 6 21:38:14 kunraid kernel: BTRFS: device fsid 0ecc5969-4afc-4b9a-a299-3fab30cf63d9 devid 2 transid 147224 /dev/sdc1 scanned by udevd (1234)  
devid 2 is on an older generation than devid 1, this can sometimes fix it:
 
btrfs-select-super -s 1 /dev/sdc1  
If you rebooted since the diags check that ssdcache2 is still sdc, then reboot and if it still doesn't mount post new diags.

https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

Yes, it won't affect the rebuild, check filesystem on disk2 when it's done.

https://wiki.unraid.net/The_parity_swap_procedure

There was a QEMU related crash:
 
Jul 4 17:06:42 Tower kernel: qemu-event[9717]: segfault at 0 ip 0000148e82990396 sp 0000148e7e03d930 error 4 in libvirt.so.0.6005.0[148e82846000+1f6000]  
Rebooting should fix it, if it doesn't post new diags.

Start by running memtest, also a good idea to replace that old JMB controller, it's causing ATA errors on both connected devices.

Apple and Samba..., several Samba errors in the log, see if disabling the SMB macOS specific options helps or not.

Try with just one DIMM at a time and see if those hardware errors go away.

Try a different NIC if available, ideally an Intel one.

Problem with the controller:
 
Jul 2 04:16:27 CMNSVR01 kernel: smartpqi 0000:0b:00.0: controller is offline: status code 0x1111 Jul 2 04:16:27 CMNSVR01 kernel: smartpqi 0000:0b:00.0: controller offline  
Power cycle the server and if the controller comes online, and it should, post new diags after array start.

Not a network guy but pretty sure you should only have one gateway, remove the gateway from eth1 and try again.

Some strange crashes, including the Unraid driver, rebooting should fix the problem for now.

You'll need to replace the flash drive, to get the array up see here:
 
https://wiki.unraid.net/Manual/Changing_The_Flash_Device#What_to_do_if_you_have_no_backup_and_do_not_know_your_disk_assignments

As expected no fs detected, but since current cache is xfs lets assume old one was the same, so try this:
 
xfs_repair -v /dev/sdb1  
This will take some time while it looks for a backup superblock.

Jul 3 11:49:01 Darkness kernel: kernel BUG at fs/btrfs/extent-tree.c:1107! Btrfs crashed during the balance, this suggests there are fs issues, reboot, force it you have to, and try again, though most likely the same will happen, if yes best bet is to mount the pool read only, backup and re-format.

If you think the device was wiped the correct command would be:
 
btrfs-select-super -s 1 /dev/nvme1n1p1