I had problems with the flash drive and recreated the previous flash drive using unRAID USB Creator. I then restored the config, custom, and extra directories and started the system. The problem now is that the pool is missing and I cannot create a pool under Pool Devices. The previous SSDs appear under Unassigned Devices.

One small detail: I can select the case model in the main menu, but it doesn't change afterwards.

I have attached the diagnosis here.

Thanks for your help.

tower-diagnostics-20250923-1210.zip

Edited September 24, 2025Sep 24 by EdgarWallace

Just now, EdgarWallace said:

and I cannot create a pool under Pool Devices.

What happens when you add a pool and try to assign the devices? Screenshot may help.

I can select the number of devices, but when I press OK, nothing happens.

Is it correct that the Flash drive has root/root permissions? Seems that I unRAID can't write anything to the Flash drive.

Edited September 23, 2025Sep 23 by EdgarWallace

Not seeing anything logged that suggests a flash drive problem, try using a different browser.

Thanks a lot @JorgeB

I was trying Vivaldi, Safari and Firefox, all latest versions on my MacBook. No luck.

I replaced the USB Flash device - still the same error.

Can you post some screenshots or a movie clip of the actual issue you see?

The problem was that there was a file named “pools” under /config but a directory named “pools” is expected.

I have now restored it from a flash backup, and VMs, etc. are working again.

There are two issues remaining:

• All dockers are away

• I still can't modify settings (e.g. display setting from "boxed" --> "unlimited"

There were two more issues similar to the issue I described above. Two more files with file size 0 were under /boot/config/plugins but directories were expected: dockerMan and dynamic.

Edited September 24, 2025Sep 24 by EdgarWallace

7 minutes ago, EdgarWallace said:

The problem was that there was a file named “pools” under /config but a directory named “pools” is expected.

This can be a symptom of file system corruption on the flash drive and the attempt to repair changing the folder entry to look like a file. If the flash drive is having issues it might explain your issues (although I could not see any direct evidence of this in the diagnostics).