Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Solved] Freezing issues on boot

Featured Replies

Unraid version 4.7

 

Almost every time I boot unraid, it freezes once, I reboot, and then it boots properly.

 

This morning it froze during "load bzroot." It's never done that before. It usually gets all the way to root login, the screen fills up with code (I dont have a photo) and becomes unresponsive.

 

I ran a memtest and it came out fine. I haven't changed any bios settings or anything on the flash drive in years.

syslog-2013-07-19.txt

Have you ran chkdsk on your usb drive?

If you just restart the server after it running for some time do you get the same problem or does it only happens when system cold, i.e. at 1st boot after power up? If this is the case then you may want to try to run memtest asap right at 1st boot. Some time ago I had a defective ram module that did only show errors when cold, right after it warms up a bit it would pass all tests... then I was getting similar problems with OS crashing always on 1st boot. Such temperature triggered problems may sometimes be hard to check... as last resource if you have multiple ram modules you may just try to remove one module at a time and test it.

 

Btw, you may also try a different usb drive...

  • Author

in one file, "first allocation unit is not valid"

 

go ahead and run chkdsk again with the fix option?

chkdsk.gif.6ac875e649ba2a0a728ad2daa9f3169f.gif

Yes, better to fix it but corruption on that smarthistory file is surely not the cause of the problems you are getting...

  • Author

Shut it down at night. Booted in the morning and got "CMOS checksum bad." I hit F2 to continue and it continued to boot.

 

I ran a memtest for 6 hours. zero errors. Rebooted again and got the CMOS checksum bad error again.

 

This is new. Never saw a CMOS checksum error until today. Change the battery?

cmos.jpg.2b8df982aca3caf5edd5aa982c226809.jpg

I'd change the battery.  The last system I saw this on the BIOS eventually became wholly corrupt, only spewing gibberish on the screen (it looked like a normal bios boot - text in the right places, mostly, but a lot of the characters were extended ASCII nonsense).  Once it was that corrupt it wouldn't get past the bios to boot the computer.  Hopefully it's just the battery in your case.

  • Author

Still running into issues even after replacing the battery. Going to bite the bullet and replace the motherboard :(

 

Thanks

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.