ort84

As requested, diagnostics attached and screenshot. I see this in the dashboard. centaurus-diagnostics-20260527-0849.zip

Hi, I'm having an interesting issue. Running 7.3 with a ZFS Pool (RaidZ-2) 8 12TB drives. I had a drive die completely, not a problem I had a spare on hand. Stopped the array, removed the drive from the zfs pool slot and shut down the server. Swapped out the drives and booted back up. Resilvering started immediately once the array was up, all expected behavior. But I had a "random" drive come up showing Active and Can't Open. Never seen that before... Shut down the machine, rechecked all cables and ensured everything was plugged in correctly and nothing was loose. Booted back up and that drive no longer had the Can't Open issue but now another "random" drive (confirmed different drive via serial number) had the Can't Open status. At this point I've decided to just let the resilvering process complete before attempting anything else. Is this a hardware fault with maybe the mini-sas to sata cables, the HBA or is this a 7.3 bug? Thanks!

Great! Thanks!

Is the ZFS bug fixed? The one where if your pool is ZFS only you randomly lost the ability to write to it in 7.2?

I was going mad trying to figure out why this was happening to me. Did what you said and now the problem went away. How in the heck was such a major bug missed especially after a long RC period of testing...

Thank you! So if I'm understanding correctly, does that mean there will be no "parity" information of the existing data on the new drive? Only whatever new data is added from when the additional drive is added?

I think there is a mis-understanding of my question? If I add a drive to an existing RaidZ2 for example, does Unraid start almost like a resilvering process so the data is across all drives in that RaidZ2 Vdev?

Does anyone know if the ZFS expansion option now available in 7.2 distributes the data evenly amongst the disk when you add a drive?

Hi, just wondering if/when this image will be updated to the just released 4.9 version?

Hi, Been an Unraid user for a little over a year now and never had an issue with Community Apps until today... I'm running Unraid 7.1.4 and Community Apps stopped working this morning. I see this in the php logs: [18-Sep-2025 09:29:08 America/New_York] PHP Fatal error: Uncaught TypeError: trim(): Argument #1 ($string) must be of type string, array given in /usr/local/emhttp/plugins/community.applications/include/exec.php:311 Any help would be appreciated. Thanks!