• Posts

  • Joined

  • Last visited


  • Member Title
    This is fun!


  • Gender
  • URL
  • Location
    Chicago USA and Berlin Germany
  • Personal Text
    Video Calibration Engineer

Recent Profile Visitors

4722 profile views

craigr's Achievements


Enthusiast (6/14)




Community Answers

  1. If you have a second GPU like Nvidia or AMD the BIOS will likely choose it as primary. However, even without another GPU, AUTO often does not work and iGPU or internal graphics must be set manually. This should get you the /dev/dri directory after the step you've already taken.
  2. Do you have your integrated graphics set as primary in your BIOS? It usually cannot be set to auto and should not be set to anything other than the integrated graphics.
  3. Have you seen this thread: Also, many things have changed since this thread here was first started.
  4. Did you power down or do a restart? Just wondering if your system crashed or if you even tempted fate?
  5. Strange and interesting. Thanks for the data point. In my case, this never happened until 6.12.x though.
  6. It's impossible to get log data now, because it won't crash again (based on prior experience). It only happens on the first boot after the upgrade.
  7. Thank you for these ideas. I like them all, though I think 2 & 3 have the most likelihood of providing some help. After no crash upgrading to 6.12.3 I didn't worry, but next time I will be sure to write the log to flash as well and hopefully glean some information from that. Thanks for your help and again kind regards, craigr
  8. Upgraded from 6.12.3 to 6.12.4 and it went mostly smoothly as everything is running fine and well now. However, I followed the instructions and did shutdown the array before upgrading. Upon reboot, unRAID briefly came online (web GUI and all) and then completely crashed. This has happened upgrading to 6.12.0, 6.12.1, 6.12.2, 6.12.4; but NOT 6.12.3. My IPMI records show this for each of the upgrades. This is the ONLY time my machine has EVER crashed; only after the FIRST reboot after the four upgrades I have mentioned. I have had this configuration since 2019 with very few changes. Supermicro IPMI: unRAID IPMI plugin: Above are my IPMI errors, one for each upgrade 😬. When it crashes there is no cursor blinking at the terminal on the monitor connected to the machine, no ssh, no web GUI, but the IPMI fan control seems to be running as the fans are not at full speed. I have to do a hard shutdown with the power button, and then of course a parity check starts on the next reboot which I always cancel because there will be no errors. Also, after this update, for some reason my Deluge docker would not start. I forced an update and it started fine after that. I really don't like these crashes after moving to 6.12.x on my system. Thanks for the update and kind regards, craigr
  9. Did you follow the instructions in the first post to this thread before rebooting?
  10. I seem to have upgraded from 6.12.2 to 6.12.3 without incident. I had been out of town and did not want to apply the update remotely as both previous version (6.12.1 and 6.12) crashed my machine on the first reboot after update, and had to be hard reset. This update is so far painless and rebooted without problems.
  11. And again on 6/21. I should pay more attention to my emails! error: Compressing program wrote following message to stderr when compressing log /var/log/nginx/error.log.1: gzip: stdout: No space left on device error: failed to compress log /var/log/nginx/error.log.1
  12. Actually, I bet that was generated when my log was at 100% capacity?
  13. Hey so I found this email for June 6th, does this give any further clues? Don't know how I missed it. Everything seems fine now but still... error: Compressing program wrote following message to stderr when compressing log /var/log/nginx/error.log.1: gzip: stdout: No space left on device error: failed to compress log /var/log/nginx/error.log.1