ChuckBuilds

This looks like a super cool feature and something I think should help me minimize spin-up time, however it seems like it is keeping my disks awake more often than not. Any advice on how tune this better for my needs?

Not the original poster but I am having the error after updating. Weird part is it is trying to download v565.77 but I am choosing v575.57.08 . Diagnotstics attached. Thanks for the fix below. Sorry I missed it the first time. theblender-diagnostics-20250602-2335.zip

Flash passed tests but still formatted and restored from a backup. Fingers crossed for smooth sailing. Thanks.

Thanks for the response. I am going to look into some way to test the disk on module. It does have a unique GUID and plugs into the USB header on my motherboard. Before I put it in Unraid, Windows saw it just like any other flash drive. Somewhere on the forums people were recommending it for reliability and durability. Flash back up on the way. Testing to come after. Thanks

Hello, I've been on 7.1.2 for a few days now and randomly had my server become unresponsive. I couldn't ping it on local network, couldn't ssh, couldn't get the display connected to it to light up, couldn't access web gui or hosted containers. So, I did a hard restart by smothering the power button (didn't respond to just a click) and then booted into safe mode. It seemed fine in safe mode so I rebooted from there into the regular mode and immediately noticed some issues. my drives were no longer assigned, brief scare but I was able to put them back. My server name was re-named / reset to "Tower" Web Gui is very slow to load Is this just a symptom of a dirty shutdown? Is there anything in my diagnostic that looks damaged? Should I just rename my server back to what it was and carry on or should I restore from an unraid connect backup? I am using a Disk on Module instead of a flash drive for more robustness and it has been rock solid for a year or more with active cooling, so I don't think it's the usual failing usb disk. I think I'm just confused right now and looking for any pointers. Thanks for any insight you can provide. tower-diagnostics-20250526-1611.zip

13 days later got a crash. I had just re-enabled disk spin-down after 12 days so I can't help but feel that it is related. At the beginning of 13 days I reseated CPU, RAM, updated BIOS, and loaded defaults on BIOS. Disabled C States, disabled XMP, disabled "Game Mode" CPU Overclock. Timer is reset, but I am running out of ideas on what is messing up! I could access the command line locally on the machine with a connected monitor and keyboard. I tried to login as root and got the Error that login timed out after 60 seconds. Just documenting at this point, if someone stumbles across this I hope I get a definitive resolution at some point.

Unfortunately it struck again today. 15 days later. Which is a lot better up-time but I was right next to the machine this time. I was able to use the Local command line on the machine and got an error when logging in that it was timing out after 60 seconds. This led me to google and a result elsewhere on these forums that it was related to their Intel C-States. I just went to BIOS and disabled Intel C-States. Hope to be marking this the solution in the near future.

I think I narrowed it down to my BIOS settings trying to Overclock the CPU automatically and maybe crashing during peak usage. It wasn't abundantly clear how to get it off but eventually got it disabled and it seems more solid. Just hit 10 days without an issue, which is more than I could say before. I hope it continues. I am a bit surprised that is the issue as I don't recall ever turning that feature on but maybe when I was swapping the case and doing fan tuning I accidentally tuned it on. That doesn't really explain it as I swear I had issues before the case swap - but either way it seems good now (for now!). Thanks for checking JorgeB, it helped convince me it was a hardware issue and not a bad Unraid setting.

Still working on this. It is seemingly random. I had a log message of a disk spinning down right before it went unresponsive so I disabled disk spindown. Not even 24 hours later it is unresponsive and the last syslog message was from 2 hours ago when I successfully logged into the WEBGUI. I've run an extended memtest with no errors. CPU and system temps are cool. I suppose my next step is safe mode but I am not looking forward to 24+ hours without my homeassistant running. Any direction is appreciated.

Hello, I've been experiencing some (seemingly) random system lockups and instability. I am sure I have something configured poorly but can't seem to find it. Symptoms: Can't access GUI or running containers. Sometimes not even SSH into the machine. What's new: I've recently swapped cases for my machine but have had these symptoms sporadically before. What I'm doing about it: I'm not entirely sure what the issue is. I have the Syslog open on my windows machine via TFTPD64 and I don't really see any errors. (Exception: when my webgui was frozen on a blank screen I tried to change the trailing "/main" to "/docker" to see if I could identify a problem container. It had an error for that). I have previously run Memtest (in the last month or so) and did not have any errors after it finished. I'm hopeful I've got a dumb setting somewhere but I can't seem to identify it. The below image shows the High IO and the subsequent lockup / unavailability. Version 6.12.11 Diagnostics attached. Thanks for your time! theblender-diagnostics-20240810-2012.zip

That would explain why Frigate has been crashing on me lately. I'll investigate further. Thank you

Hello, I have gotten an Out of Memory error that Fix Uncommon Problems is reporting. I have restarted but it comes back each day. I've attached my Diagnostics as requested. I am on version 6.12.8 and am not seeing much error log activity outside of Fix Uncommon Problems telling me about it. Any direction is appreciated, thanks for your time! unraid diagnostics 31724.zip

No, I had decent luck with the StreamMaster Discord - got it fixed up without needing gpu but then started having issues again. I'll look into it soon fruther

Hello, I am getting error : ER_FK_INCOMPATIBLE_COLUMNS when updating ghost to :latest or :5.74 , works fine on 5.59.1 . I haven't been able to find any reason why on the Ghost Forums. Thought I'd ask here if anyone else has solved this. Thanks. UPDATE: I think I solved my own issue. Instead of deleting, just going to leave a breadcrumb for future folks (or myself). https://ghost.org/docs/faq/troubleshooting-mysql-database/#error-er_cant_create_table-with-_foreign-key-constraint-is-incorrectly-formed_ Using Adminer (community Apps) Container to connect to my MYSQL, I had the wrong (old) collation. Updated from utf8mb4_general_ci to utf8mb4_0900_ai_ci using Adminer. Execute the following SQL Statement: SELECT CONCAT('ALTER TABLE ', table_name, ' CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci;') AS sql_statement FROM information_schema.tables WHERE table_schema = 'ghost'; Using the output from above, execute the following sql statement: -- Disable foreign key checks SET foreign_key_checks = 0; -- Execute the generated ALTER TABLE statements ALTER TABLE actions CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci; ALTER TABLE api_keys CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci; -- ... (paste whole output from previous step) -- Enable foreign key checks SET foreign_key_checks = 1;

No I never solved this issue. Still unsolved.