jrmcmillan

Thank you. That worked!

Everything is working ok, but it now gives me an error message regarding the cache pool after upgrading from 7.2.6 -> 7.3.0. The cache pool appears to work fine. mini12-diagnostics-20260514-1051.zip

I turned off docker (including table readmore.js) and vms. And, I could stop the array and restart it! So, I guess my procedure going forward is to turn those things off before stopping the array. Thanks for the hint!

Circular discussion. I don't want to sound impatient, but you just described what I originally posted. I'm looking for a potential solution, not a restatement of what's already been documented.

No, that's not what happens. The array will never stop. It gets hung up and will sit there for a zillion hours, stuck. SSD is inaccessible as well.

It never hits this timer. It gets stuck waiting for something...and I think it has to do with closing files as "shutdown -f" works.

I get that...the issue is what does Unraid expect that it's not getting from the array (inside the usb enclosure) when trying to shut it down? And, is that something I can configure in Unraid so it doesn't get stuck looking for it?

From my way of thinking, Unraid is looking for something from the disks when shutting down the array which it's not getting, hence it just gets stuck waiting (forever). The only way to recover at that point is to power off the server. As I understand it, "reboot -f" tells Unraid not to look for anything, just reboot - which is why that works - but with the unclean shutdown flag set.

I know for sure the main array causes a problem with the shutdown/reboot - e.g., the 5-bay causes a problem because at one point, I had the cache (4-bay ssd) off. I do not know whether the 4-bay is a problem or not.

My setup is a mini-pc, an Orico 5-bay usb enclosure for the array (4 bays populated) and an Orico 4-bay ssd enclosure for the cache (all bays populated). The system performs perfectly with one exception, I cannot shutdown the array (or reboot, or just turn it off). It gets hung (forever). What I've determined is when I need to do one of those 3 things, I have to "reboot -f". I'm always careful to stop docker/vms before doing this so there is no file activity going on. However, Unraid always detects an unclean shutdown so it always starts a parity check. It's no big deal the turn that off. However, I'm wondering if there's a better way...If the answer is "don't use usb drives" that's not really an option for me, so I might just have to put up with the inconvenience. In any event, is there a config parameter or something else that might fix this? mini12-diagnostics-20260116-1615.zip

Not upgrading the pool was the problem. Pool upgraded and 4th ssd added successfully. Thanks for the help.

mini12-diagnostics-20260105-1332.zip These diagnostics were done after trying to add the 4th cache disk and I got the "wrong pool state" error.

RAIDZ1, yes.

I currently have a 3-ssd zfs cache living in a 4-bay usb Orico ssd enclosure. It works perfectly and has been for over a year. I decided to try to expand the cache pool to 4 disks using the new zfs 7.2.3 expansion functionality. I can add the 4th disk (it shows up as an unassigned disk as it should). I can change the pool size from 3 to 4 and assign the 4th ssd. The existing 3 ssds stay green dots, with the new fourth ssd with a blue dot. It says nothing about formatting or losing data. I try to start the array and I immediately get the "wrong pool state" error. Is there some kind of limit going to 4 disks? The example video only goes from 2 to 3 disks. Or, perhaps there is something else going on. Thanks in advance for any help.

NexusEFR, I think you may be right about getting support. Last night, there was an Odoo17 update which "broke" Odoo. Specifically, it broke the Dashboards. As near as I can tell, the dashboard is the only thing that got broken. The error message is attached below. Of course, I have no idea how to fix this. Any ideas with respect to getting support for these types of problems?