JorgeB

You don't need to use that adapter.

Both things are perfectly normal, sdX change are not important since disks are tracked by serial number, and when adding new hardware you might change the IOMMU groups and need to edit your VM settings.

It should work fine.

It's an old bug, average speed is calculated based on parity size, not disk rebuilt size.

No, I have one myself.

If you don't want to use the x16 slot you can used Asmedia based controllers on the x1 slot, e.g. SYBA SY-PEX40039 , they are 2 port controllers though, AFAIK 4 port x1 controllers only Marvell, based on the 9315 chipset and not really recommended, but they do work for some.

VMs -> Edit -> click on + to add a second vdisk You'll then need to go to disk management in Windows to partition and format it, and for the new vdisk to be detected you might need to reboot (not power down) your VM first if using Windows 8/10.

Since one of the last updates, possibly the last one, every time I reboot unRAID fans goto max before rebooting and stay at max after rebooting, this is on an X11SMM-F, I need to disable and re-enable fan control, and sometimes that isn't enough and need to change and then change back some other setting like fan minimum speed to get it working, let me know if you need anymore info.

You can use rsync with --remove-source-files, this way it will remove the already existing files on the destination, it would work best if the share or folder you're syncing fits on the destination, or rsync will abort possibly leaving a couple of dupes.

I believe so, there were previous btrfs related call traces and the last one was when trying to unmount cache.

You have a problem with your cache pool, it's failing to add a second device. Jun 10 11:38:02 Tower kernel: BTRFS info (device sdq1): relocating block group 1821087105024 flags data Jun 10 11:38:03 Tower kernel: BTRFS info (device sdq1): found 1412 extents Jun 10 11:38:05 Tower kernel: BTRFS info (device sdq1): found 1412 extents Jun 10 11:38:05 Tower kernel: BTRFS info (device sdq1): relocating block group 1820013363200 flags metadata Jun 10 11:38:07 Tower kernel: BTRFS: Transaction aborted (error -28) Usually easiest to backup and redo the pool, you can use this thread if you need help with the backup. You're also having issues with your NVMe device: Jun 10 11:07:39 Tower kernel: nvme nvme0: I/O 768 QID 7 timeout, aborting Jun 10 11:07:39 Tower kernel: nvme nvme0: I/O 769 QID 7 timeout, aborting Jun 10 11:07:39 Tower kernel: nvme nvme0: I/O 770 QID 7 timeout, aborting Jun 10 11:07:39 Tower kernel: nvme nvme0: I/O 771 QID 7 timeout, aborting Jun 10 11:07:39 Tower kernel: nvme nvme0: I/O 772 QID 7 timeout, aborting Jun 10 11:08:09 Tower kernel: nvme nvme0: I/O 768 QID 7 timeout, reset controller Jun 10 11:08:40 Tower kernel: nvme nvme0: I/O 16 QID 0 timeout, reset controller Jun 10 11:10:11 Tower kernel: nvme nvme0: Device not ready; aborting reset Jun 10 11:10:11 Tower kernel: nvme nvme0: Abort status: 0x7 Jun 10 11:10:11 Tower kernel: nvme nvme0: Abort status: 0x7 Jun 10 11:10:11 Tower kernel: nvme nvme0: Abort status: 0x7 Jun 10 11:10:11 Tower kernel: nvme nvme0: Abort status: 0x7 Jun 10 11:10:11 Tower kernel: nvme nvme0: Abort status: 0x7 Jun 10 11:11:12 Tower kernel: nvme nvme0: Device not ready; aborting reset Jun 10 11:11:12 Tower kernel: nvme nvme0: Removing after probe failure status: -19 Jun 10 11:11:12 Tower kernel: nvme0n1: detected capacity change from 1024209543168 to 0

Anyone using btrfs can also just setup regular snapshots, they can be read-only so a good protection against ransomware.

Try the cable first, if it's not that then the cage is the next most likely candidate.

Because disk18 still has more free space than disk19.

Your key is missing, check that is there and there are no filesystem issues on the flash drive.

It does need some airflow around it, remember these controllers are designed for servers with excellent ventilation, I usually have a 120mm or larger side case fan blowing air on them.

No, current cache needs to be btrfs like it says on the notes. Yes, unless something goes wrong, that's way it's always good to backup any important data. Yes.

Those are hardware errors and a general support problem, not a bug report, use the Nerdpack plugin to install mcelog, it may give some more info.

https://lime-technology.com/forums/topic/46802-faq-for-unraid-v6/?do=findComment&comment=545988

That should be cache "yes", not cache "prefer".

When a share is created it creates the folder on the first disk configured for that share, did you delete it?

I believe so but I never had to update mine, as it was already 2.something, also I believe you need an HP controller to do the update.

No such limit when crossflashed to LSI IT mode, LSI firmware limit is 256 non raid devices.

Correct, use the 2 Intel SATA3 ports for the SSDs, SATA2 is enough for HDDs.

Post your diags and we can see.