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.

madwyn

Members
  • Joined

  • Last visited

  1. I'm giving up the idea of using a Mac Pro 4.1 as a NAS, the reason is power consumption. The standby for a Mac Pro 4.1 with an Intel L5640 is 100 watts, this is less than ideal.
  2. Thanks. I'm thinking long term support, even a temporary hack make it working on Mac Pro, I'd have to modify the installation every time when there is a new release which I don't prefer. Today I made some progress, it seems the best way for now is to run unraid in a virtualised environment, such as Proxmox EV.
  3. I have also tried other Linux distros, including Fedora and FreeNAS, they all worked without problems. However, I only want to use unraid on this machine.
  4. There are other users experiencing the same kernel panic issue when booting unraid on Mac Pro 4.1/5.1 or Mac Mini 2009. I'm hoping unraid team can help to identify and solve this problem. In order to boot unraid on a Mac Pro, you must use the UEFI Boot with unraid. To isolate the issue, I have removed all the hard drives from the machine in later tests. I used a capture card to get a clear output of the kernel panic screenshot attached. I've tried 6.8, 6.8-rc8, 6.8-rc9, they all showed the same kernel panic. Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) -6 My Mac Pro was able to boot 6.8-rc6/7, as it has a different kernel (5.7) and it gave a slightly different kernel panic output generally removed the register section. I've also tried different USB drives and different USB ports (Mac Pro only has USB 2.0), none of them worked. Then I tried to append root=/dev/sda1. A little progress lead to a new kernel panic, now it has two error pieces: devtmpfs: error mounting -2 Kernel panic - not syncing: No working init found. Try passing init= option to kernel. Then I booted unraid in VirtualBox and verified that only /sbin/init exists, so I added init=/sbin/init to the kernel parameters. Then it showed a new kernel panic: Kernel panic - not syncing: Requested init /sbin/init failed (error-2) I don't feel confident with this error message, so I booted the USB drive in VirtualBox again and it started without a problem. This is where I'm stuck, could anyone please point where I should go?
  5. I tried 6.8 and 6.8 RC7 and RC9. 6.8 RC7 gave a slightly different kernel panic output screen without the CPU #0 section. I’m having slightly hope to try the 6.9 RC with new kernels.
  6. I've updated the BootRom to 144, yet no luck to boot unraid. The same error.
  7. You are not the only one. I’m having the same error with my Mac Pro 4.1. Would you please confirm your BootRom version? It can be found from the crash screen.
  8. Did you manage to boot unraid from the Mac Pro 5.1? I tried mine many times with different versions but got stuck at a kernel panic just like this one:

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.