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.

TacticalTuna

Members
  • Joined

  • Last visited

  1. Posting here for anyone else who may be using ASUS Pro WS W680-ACE motherboard and are getting an F6 error code on boot. Turning off fast boot in the bios fixed the issue for me. Thanks @1adam12 and @Daniel15 who suggested this, I was on the verge of returning the motherboard as defective.
  2. I just did a new build using this particular motherboard. The boot sequence hangs with code F6 on the motherboard LED. I upgraded the bios to the latest version, and I ran a successful memtest in additional to removing all devices. The odd thing is is that if I boot into the bios setup before the machine posts and then exit the system will continue and boot normally into unraid. however if I just do a reboot, the system will hang with the F6 code.
  3. Hey @Forusim I came across your post in a frantic Google search after my machine had the same symptoms as yours. Turns out it was a bad PSU in my case as well. Wanted to say thanks you saved me a lot of time and headaches.
  4. Posting this here for anyone who might be searching for a solution to the same issue I was having. I was steaming some content from my Unraid machine and suddenly the connection dropped. I noticed that the system had powered off. After powering the machine back on it would immediately crash and power off again. In some cases I could boot up and it would stay on for a minute before crashing again. After booting into safe mode I was able to run a SMART check on all disks and xfs repair with no problems. As soon as I would try to spin up the array or run a parity check the system would power off immediately. Oddly I was able to start the array In maintenance mode sometimes. After a few hours of searching I found this post which tipped me off. Turns out I had a bad power supply unit (PSU). After swapping it out for a new one everything runs just fine and the machine has been running with zero issues. My theory is that since the PSU was going bad the machine would boot and run fine in safe mode no problem but the additional power draw from spinning up the disks to mount the array or run parity check would be enough to trip up the bad PSU.

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.