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.

[6.7.0] unRAID will not boot in default mode after update

Featured Replies

I upgraded my backup server from 6.6.7 to 6.7.0 today resulting in a boot loop after restarting. The server boots to the OS selection screen then reboots after loading bzimage and bzroot. If I select unRAID OS GUI Mode the system boots and everything appears to be running correctly.

 

My first thought was an issue with the update so I recreated the USB key using the unRAID utility and copied the original config folder back onto the drive. I have verified that I am running the latest BIOS and have reset the BIOS settings to optimized defaults.

 

I found two similar posts about this issue with previous versions of unRAID but they seem to end with the user just accepting the workaround of booting into GUI mode by default. My primary server runs nearly identical hardware so i would like to resolve the issue before I move forward with the update.

 

Server Hardware

MOBO: Asus P10S-M WS

CPU: Intel Xeon E3-1245 V6 

RAM: 16GB DDR4 ECC

HBA: LSI 9211-8i P20 IT Mode

 

Thanks in advance for any help you can provide.

  • Community Expert

There have been numerous posts where only gui or non-gui mode would work on a particular hardware/release combination, but I do not think the exact reason why has ever been identified.

Or to rephrase the above, why worry about it?  Zero downside to booting in GUI mode by default (and depending upon how you look at it, there's many upsides)

Edited by Squid

I think the reason one boot mode works and another doesn't is because of corruption in the non-working bz file.

The gui-mode boot requires about 270MB more RAM, hence if RAM is tight and you don't need GUI, then use non-GUI boot mode.

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.