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] Web interface not starting on boot

Featured Replies

Or a bios update, if available.

Really just shooting in the dark here, but if you are dead set on trying everything to make this particular motherboard work with unraid, maybe try booting off of a hard drive with your license key file on the usb stick mounted to read the license key. I don't know the procedure, but I've seen posts referencing it on here somewhere. The downside would be losing one of your sata ports, but in a small server, ports are usually at less of a premium than 3.5 slots, so maybe a small solid state hard drive mounted creatively could keep all your 3.5 slots open.

  • Author

Guys,

 

Finally some good news! Tom got involved and was able to identify the issue.

 

During boot there's a point at which it tries to mount non-root filesystems (e.g. /boot). In order to give the USB system time to initialize there's a 5 second sleep inserted before the mount is attempted. This pause apparently wasn't enough for my MB. The mount command resulted in "device does not exist", and the startup script continued on. Tom gave me a build which actually loops until it detects that USB has completed initialization. And now my system finally boots properly.

 

Thanks for all your assistance. Its nice to know there's such a helpful community behind this product.

 

Andrew

Guys,

 

Finally some good news! Tom got involved and was able to identify the issue.

 

During boot there's a point at which it tries to mount non-root filesystems (e.g. /boot). In order to give the USB system time to initialize there's a 5 second sleep inserted before the mount is attempted. This pause apparently wasn't enough for my MB. The mount command resulted in "device does not exist", and the startup script continued on. Tom gave me a build which actually loops until it detects that USB has completed initialization. And now my system finally boots properly.

 

Thanks for all your assistance. Its nice to know there's such a helpful community behind this product.

 

Andrew

 

Great to hear you got it worked out.

 

It was a weird issue and I wonder why that particular machine seems to have issues.

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.