JorgeB

You can assign one if you like, this is normal, it will always show that slot with the array stopped. You can also assign an extra disk there, you can reduce the slot count to 11 to not show that.

Since this thread is still active, and to avoid confusion, please start a new one and post the diagnostics.

Even after typing that?

This may be a bug, but you can ignore, it's just a display issue. @SimonF any idea how to check what is causing that error?

I don't see the Connect icon, try this, open a terminal window and copy/paste unraid-api plugins install unraid-api-plugin-connect Then refresh the GUI and see if the icon shows

Looks like the sparse bundle got corrupt: fruit_get_bandsize: Didn't find band-size key in .../Info.plist fruit_tmsize_do_dirent: Processing sparsebundle failed The best bet is to delete the TM backup bundle for that Mac and start a new one.

I have a Windows 2022 server VM with 8 vCPUs, don't notice any lag, but I'm not using encryption, not sure if that adds any latency. I'm also using a zfs zvol, which in my test performed better than an image on zfs.

Please post the diagnostics and a screenshot of where you see that "can't open" error.

With the plugin installed, it's in the API settings Tab

Just the image, without containers?

Can you retest without passing through any PCI devices to the VM? Also, do you have ACS override enabled?

You need to install the Connect plugin for that.

Looks like a drive problem to me, it cannot even get the capacity. May 26 21:10:52 HomeServer kernel: sd 9:0:3:0: [sdh] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK May 26 21:10:52 HomeServer kernel: sd 9:0:3:0: [sdh] Sense Key : 0x2 [current] [descriptor] May 26 21:10:52 HomeServer kernel: sd 9:0:3:0: [sdh] ASC=0x4 ASCQ=0x22 May 26 21:10:52 HomeServer kernel: sd 9:0:3:0: [sdh] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK May 26 21:10:52 HomeServer kernel: sd 9:0:3:0: [sdh] Sense Key : 0x2 [current] [descriptor] May 26 21:10:52 HomeServer kernel: sd 9:0:3:0: [sdh] ASC=0x4 ASCQ=0x22 May 26 21:10:52 HomeServer kernel: sd 9:0:3:0: [sdh] 0 512-byte logical blocks: (0 B/0 B) May 26 21:10:52 HomeServer kernel: sd 9:0:3:0: [sdh] 0-byte physical blocks May 26 21:10:52 HomeServer kernel: sd 9:0:3:0: [sdh] Test WP failed, assume Write Enabled May 26 21:10:52 HomeServer kernel: sd 9:0:3:0: [sdh] Asking for cache data failed May 26 21:10:52 HomeServer kernel: sd 9:0:3:0: [sdh] Assuming drive cache: write through May 26 21:10:52 HomeServer kernel: sd 9:0:3:0: [sdh] Preferred minimum I/O size 4096 bytes not a multiple of physical block size (0 bytes) May 26 21:10:52 HomeServer kernel: sd 9:0:3:0: [sdh] Attached SCSI disk And not even the SMART report is working: === START OF INFORMATION SECTION === Vendor: SEAGATE Product: ST6000NM0034 Revision: NE03 Compliance: SPC-4 LU is fully provisioned Rotation Rate: 7200 rpm Form Factor: 3.5 inches Logical Unit id: 0x5000c500854ad603 Serial number: Z4D4CVS00000R632V7WW Device type: disk Transport protocol: SAS (SPL-4) Local Time is: Tue May 26 22:25:39 2026 EDT device is NOT READY (e.g. spun down, busy)

Where is it showing extra devices? Also note that RAID controllers are not recommended with Unraid.

That should be OK; better to disable Docker and VM services before starting.

If the containers are not set to autostart, you can start the service and then start them one by one. If they are, you would need to remove that first, don't remember how it's done, but searching the forum should have some results. Worst case, recreate the Docker image and restore the apps one by one.

If the client is SMB capable, it may also be worth changing it since NFS tends to me more problematic, mostly meaning not as well tested.

If the 2TB was originally in the pool, and its capacity is still being limited by that device, you can use it to replace the missing one, but only using the CLI, the GUI will not allow it since that is the only small device. I can post the steps if you like.

Apr 8 05:18:21 Tower mcelog: Corrected memory errors on page 1ba04a000 exceed threshold 2 in 24h: 2 in 24h Looks like there's a bad RAM stick, but since it's EEC, it's been correct, but it should still be replaced. SEL on the BIOS may have additional information on which is the affected one.

That looks normal to me. Does Kodi connect again if you downgrade back to 7.2.4?

The 2TB device is too small to use in the existing pool, not sure if I understand if you want to recreate the pool with just the two 4TB devices. Is that what you want? All data in the pool will be deleted.

As long as it has 7.3.0 and you don't mind overwriting the old config it's fine, because you should still sync the current config to that flash, or it will also be out of date after creating the new boot pool.

Scrubbing the pool won't change anything; it's just to confirm Click the first pool device, then RESET in the "pool device status" section; no need to reboot.

Don't see any obvious issues on the Unraid side; post the output from exportfs -v

Pools were not monitored pre 7.3, so the issues were already there; you just weren't notified. Scrub the pool, and if there are no uncorrectable errors, reset the stats and keep monitoring. The current errors suggest one of the devices dropped offline in the past, most often due to a power/connection issue.