Phorte

Is there a way where I can add a comment/description for each unassigned drive? I have a few old 1-2TB drives lying around that I use for unimportant data that doesn't need to be on unRAID. These drives are mounted when needed using a USB dock and then unmounted and undocked after I've used it. At the moment, I differentiate them only by their serial number. I'm hoping that Unassigned Devices can have a field where for each historical unassigned device, where I can put in a comment/description for that drive. E.g. "2023 Archives" or "Need to preclear later" or "2020 Pr0n".

Is someone able to sift through my diagnostics please and confirm if unRAID did indeed shutdown cleanly? I'm assuming my issue is not OS related.

No share/remote share mounted. I've just done a normal/manual shutdown and once again, unRAID appears to have shutdown properly (unpingable), but physically, unRAID is still running with case lights and fans all on/spinning. I then force shutdown (holding physical power button), power it back on and unRAID thinks it's had a clean shutdown and there are no notifications. New diagnostics attached tower-diagnostics-20250215-0920.zip

Thanks for the reply. However, this is set to "No".. I'm not sure how this would effect the unRAID server from powering off completely. I don't need the UPS to power off.

Hi all, Tonight I had an event where a fuse got tripped, power went out, then my UPS kicked in for unRAID. I have my UPS setting for "Time on battery before shutdown" = 60. However, after a minute, I could see/hear that unRAID was still on and running off the UPS (lights on, case fans spinning and UPS beeping). After the fuse was reset and power was restored, I attempted to login into unRAID but found it was completely unpingable/unreachable. I then had to hold down the physical power button to power off unRAID before powering it back on again. This led me to believe that the UPS correctly sent the shutdown request (after running on battery for 60s) but something hung within unRAID causing it to be unpingable/unreachable. However, once back up, there was no notifications of an unclean shutdown, nor did a parity check commence. I immediately grabbed diagnostics and in syslog-previous.txt, the final entry actually showed "apcupsd shutdown succeeded". Ultimately, this is great because as far as unRAID is concerned, it shutdown cleanly. However, something stopped the server from powering off completely and had I not been home at the time, unRAID would have continued to run off the UPS until the battery was drained. Can someone please assist with troubleshooting why the server did not shutdown completely? Thanks in advance. Linh tower-diagnostics-20250214-0314.zip

Reviving an older thread (less than a year old isn't too bad, right) and just wanted to say to OP that my history and issue is almost exactly the same as yours. Same long time user, same LSI 9300-16i, same firmware versions and even similar number of drives. However, in my case, although it also says in BIOS that the HBA is in IT-mode and running the old 7.0.1.0, when I start it up, I got some really weird issues with my drives. A few dropped off, a few had unsupported XFS system issues... The only thing that changed was adding the new SAS HBA and reconnecting everything to the new breakout cables. I'll be upgrading the firmware on the LSI shortly to that version that everyone references on the FreeNAS/TrueNAS forums (16.00.12.00) and will see how I go. Also, I'm waiting for a Noctua fan to arrive tomorrow and will be attaching a 3D printed fan shroud to the HBA to help cool down the heatsink. Have read elsewhere that these run extremely hot and can cause weird issues (Link to fan shroud for anyone else with a LSI 9300-16i - https://www.printables.com/model/1046107-lsi-9300-16i-hba-cooling-fan-shroud).

Just wanted to say that I used unBALANCE in the last week to move all data off one disk at a time to (finally) upgrade my array from ResiserFS to XFS and it worked without a hitch. Thank you so much for an amazing plugin.