MetricTonto

Thank you: I've started the thread here: https://forums.unraid.net/topic/199814-loss-of-pool-devices-device-assignments-after-update-to-732-if-possibly-unrelated/

After updating from Unraid 7.3.1 to 7.3.2 and rebooting, my Pool Devices' device assignments vanished: the pools were there but empty, all devices showing up as Unassigned. The Array was unaffected. Everything else seems normal. The pools were: A dual BTRFS SSD cache pool. A four HDD RaidZ. A single laptop-grade HDD. Reverting to 7.3.1 didn't help (in a bit of a panic there, as I'm a novice). Checking things while guided by ChatGPT 😑 revealed that the /boot/config/pools/ config files had apparently been reset in some manner: no drive assignment info in them. Luckily everything else seemed intact and just assigning the devices back sufficed. The boot USB drive's current files reflect this (its pool config files show the drives now). I enclose both the diagnostic files generated inmediately after noticing the issue, and the pool config files from a backup previous to updating. nas-diagnostics-20260709_2227.zip Pool config files before incident.zip

The upgrade seemingly ate my Pool Devices' device assignments (a dual BTRFS SSD cache pool, a four HDD RaidZ, and a HDD for music streaming). Reverting to 7.3.1 didn't help. Luckily everything was intact and just assigning them back sufficed. Most scary for a non-poweruser (I had to recourse to ChatGPT, which is something I hate if I don't know enough to catch any glaringly bad advice). I keep backups of the boot USB drive and appdata. I'll try to see what could have happened: I don't have anything out of the ordinary, apps and plugins-wise, but maybe there was some weird interaction there.

You are right. I was grasping at straws. (Possibly unrelated, but who knows: the WebGUI, both locally and remotely, started to show enormous lag. I've rebooted and things seem normal now)

I see. Thanks for taking the time to investigate and highlight that. I guess I could produce some tests (get some TV episode file, duplicate it to a quantity enough to pass for a multi-season collection, try again, and monitor the process). (Previous balancing adventures used the Unbalanced tool. I'll limit myself to it fornow)

Thank you for your assistance. The destination folder was created before the move operation (the origin one no longer exists, so, I've recreated it). The ones in the destination hardly hold one or two files instead of the complete seasons they ought to. (I don't use the cache pool for staging, so, typically file transfers go directly to the Array) nas-diagnostics-20260627-2243.zip

To manually balance my array's drives, I used Dynamix File Explorer's move tool to group some TV series folders, in a share that straddles two disks, into the least filled one. The UI let me choose the destination folder (a newly created one), and once launched I could see the progress in the File Explorer and the drives' activity in the main window, its speed being as expected. But when checking the result I saw that it had hardly created some subdirectories and moved a few files. 95% of the material is just gone. The only thing I can think that could be an issue is that I had Krusader open in another webbrowser tab (I tipically have it so). Could that be a factor? I'm on Unraid 7.3.1. (Is there any procedure to have Unraid check the Array's drives and shares for inconsistencies that might let me try to rescue that material? It's not that crucial and could have it around in some old HDDs, but…)

This motherboard's BIOS at the very least allows for setting it to require a four seconds button press for it to act.

OK, so, it was the no-name PC keyboard's power down button 😑 (I never use such, and I used to have a Mac keyboard there instead). I wonder if I can disable that in the BIOS or somewhere else.

That's worrisome 🤨. The PC case is set in such a way that the button is difficult to reach. The cradle has one of those buttons meant to trigger a Windows HDD cloner app, though. I wonder if I pressed that one without meaning to and it produced a similar reaction. I'll have to test that. In any case, thank you for giving it a look 🙂.

I was checking the contents of a SSDs via my USB3 cradle (it never was trouble), working directly with the server's display and keyboard. Once appearing as an Unassigned drive, I attempted to mount it. Instantly, the GUI was replaced by the console and a flurry of lines, and the system shut down in maybe ten seconds. Fearing the worst, I booted and logged in, but I saw no warnings about any need to rebuild the parity data anywhere. Not restarting the Array just yet, I tried mounting the SSD's volume again, and this time it worked normally. After perusing its contents, I unmounted it and switched the cradle off. Then I started the Array. Again, no warnings of anything wrong with the parity data. The only notification was one of the SSD having showed an inordinate amount of CRC errors (although I seem to remember those not being real but some kind of artifact). I'm checking syslog-previous. As I'm a complete novice, I don't understand it, but I can see the references to the "SuperSpeed USB device" (the SSD), and what feels like an orderly shutdown process. I would be grateful if somebody could give it a look and opine on it. syslog-previous.txt

In the end I went that route: ZFS Master set to manual refresh, and having Dynamix Auto Fan Control to exclude all the concerned drives from reading their temperatures, while setting the minimum PWM values to ones that can keep them decent while they are active (max rpm, these days 🫠). I need to do that because this old mainboard's BIOS is too limited and won't let me set a constant value: it varies it in real time based on a mix of CPU and chipset temperature reads.

Thanks! Safe mode worked 🙂. I'll have to uninstall the most suspect plugins and reinstall and try them one by one. My guess is the fan control one is the culprit, as it has to interrogate the drives for their temperatures. If the Dashboard can't show them already while spun down, that suggests getting the info will reactivate them. The problem is that I can't rely on the BIOS's fan curves (too old a board, "what's a fan curve?" 😒) to keep the HDDs decent. We'll see.

I've tried setting it so that refreshing its data requires manual action, to no avail. I'll try uninstalling it. It might not be the culprit, though: there are also the Dynamix System Temperature and Dynamix Auto Fan Control plugins: I'm happening to need them, as my motherboard's BIOS doesn't give me any means to regulate fan speeds based on HDD temperatures, and we are in the middle of a heatwave. They might be the ones waking up the drives, every time they check their temps. I guess I could manipulate their settings so that they exclude all the concerned drives while having a floor value high enough to keep them cool while spun up.

As I'm having the same problems many do with trying to keep ZFS-formatted drives spun down (a RAIDZ in my case), I was wondering if a base Unraid installation with no additions (plugins, dockers, etc.) has been verified to be able to achieve that, at all. And, if it has, what are the required settings. (If the Dashboard, alone, is prone to waking up the drives to do its reporting, it would need some kind of adjustment to limit that)