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.

Array not starting up - upgraded from 5a-10a

Featured Replies

  • Community Expert

I had a working ubuntu domU prior to upgrading to 10a. It would start automatically on boot. Now the array no longer starts on bootup and boots to "Stopped" status.

 

I renamed /boot/packages to /boot/packages.old and added a pound to the line, in the go script to remove some things I thought was causing this.

#cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

 

I do see the following in the log:

 

Oct 22 17:01:59 Tower001 emhttp: too many devices

 

I simply copied bzimage/bzroot/xen.

 

Please help

log.txt

  • Community Expert

It sounds as if the license file is not being found.  Where have you got the .key file?    It needs to be in the config folder to be recognized.

  • Author
  • Community Expert

The .key file is in /boot as it was prior to upgrading - which worked before. I copied in /boot/config. Still doesn't start.

  • Community Expert

The .key file is in /boot as it was prior to upgrading - which worked before. I copied in /boot/config. Still doesn't start.

key file being in /boot used to work (although the official location was always /boot/config).  Somewhere around one of the recent betas this location got tightened up and/boot stopped working (it is mentioned in the Release Notes when this happened).

 

If putting the key file in the correct location has not resolved the issue, then I suggest that providing a new syslog might help with diagnosis of your issue.

  • Author
  • Community Expert

Thanks, for some reason it now it appears to work in /boot/config now.

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.