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.

BrickPotato

Members
  • Joined

  • Last visited

  1. Still crashing - Can't figure it out. Guess I'm forced into downgrading to 6.12.14.
  2. I'll give this a shot and report back.
  3. I've updated from 7.0 -> 7.1 -> 7.1.2. I didnt see anything in the .4 changelog about this issue, but maybe I missed it?
  4. Hi Friends -- Having an issue since upgrading to Unraid 7.x.x. The Unraid Web UI becomes inaccessible/unresponsive after a few days. Attempting to load the dashboard in a browser results in a blank page or a failed load, regardless of device, browser, or incognito/private mode. However, all Docker containers and VMs are fully operational, and the server is reachable via SSH. This suggests that core system functionality is intact, but the Web UI backend (possibly emhttp or PHP rendering) is failing silently. No clear errors appear in syslog, and standard recovery steps (such as restarting emhttp or disabling plugins) have not resolved the issue. It's also worth noting that I've struggled with clean restarts. I am forced into an unclean shutdown if I ever want to restart the server. I think these issues are related, but not sure how to confirm. Troubleshooting steps: Checked emhttp process Command: ps aux | grep emhttp Result: emhttp was not running. Only background PHP pollers (nchan) were present. Manually started emhttp Command: /usr/local/sbin/emhttp & Result: Process launched in background with no error. Verified web server listening on ports Command: netstat -tuln | grep ':80' Result: Confirmed emhttp was listening on both 127.0.0.1:80 and 192.168.xx.xx:80. Tested HTTP and HTTPS curl access Command: curl -I http://192.168.xx.xx Result: 302 redirect to HTTPS. Command: curl -kI https://192.168.xx.xx Result: 302 redirect to /Dashboard. Command: curl -kL https://192.168.xx.xx/Dashboard Result: No response. Blank output. Tested browsers and devices Result: Tried Chrome, Firefox, Edge, and Incognito modes on multiple devices. GUI still not accessible. Temporarily disabled all plugins. Command: mkdir /boot/config/plugins-disabled mv /boot/config/plugins/* /boot/config/plugins-disabled/ killall emhttp /usr/local/sbin/emhttp &Result: No change. GUI still unresponsive. Plugins restored afterward. Reviewed system logs Command: tail -n 100 /var/log/syslog Result: No emhttp or PHP errors. Only repeated usbhid-ups USB input/output errors. Also checked plugin logs in /var/log/plugins — found only install notes, no crash output. Attempted reboot Command: reboot Result: Hung and failed to reboot. Will attempt force reboot or Safe Mode next. Current theory:Something in the GUI backend is failing silently (or at least silent enough that its not obvious to me what the issue is, albeit I'm fairly new to Unraid). Reading online, my guess is this is some issue with the PHP render of the pages, but I can't locate an error in logs. What I need help with: Ideas for deeper PHP or GUI diagnostics (while the issue is happening) Where else to check for errors beyond syslog Troubleshooting the inability to do a clean restart Thanks in advance. Let me know if you'd like any command outputs. I'm also happy to go deep into live troubleshooting if anyone has interest in this topic and some extra time, I will gladly compensate an expert for their time and support, and maybe I'll learn a thing or two. Thank you for reading :) potato-server-diagnostics-20250619-0944.zip
  5. Turns out the issue wasn’t Unraid or the HBAs directly... it was CSM being disabled in my motherboard BIOS. (Doh!) After enabling CSM, Unraid recognized all my drives connected to the LSI 9207-8i cards. The “problem getting id” errors disappeared, and the array started up with no issues. I've attached the diagnostics file I was looking over while the issue was still occurring. Strange that this is a change in behavior between Unraid 6 < - > Unraid 7, but happy to have it figured out. My motherboard doesn't let me use iGPU wish CSM enabled, so that's something else I'll have to figure out. diagnostics-20250420-1333.zip
  6. Found this post with almost my exact same config (motherboard, HBAs, etc): Going to troubleshoot based on their findings. Will report back.
  7. I ran dmesg | grep -i sas and it looks like both of my LSI 9207-8i HBAs are being detected. The kernel loads the mpt3sas driver successfully and both controllers initialize with port enable: SUCCESS. It logs all 6 attached drives under SCSI with valid SAS addresses, and I see this for each: scsi 3:0:X:0: SATA: handle(...), sas_addr(...), phy(X), device_name(0x0000000000000000) Despite this, Unraid is still spamming the log every second with: emhttpd: device /dev/sdX problem getting id for all 6 drives. These same drives show up correctly in Unraid 6.12.4 with no issues, so this (to me) looks like a Unraid 7 issue with how it identifies drives from the HBA. Let me know if there's anything else I can try. Happy to pull more logs or test patches.
  8. Also seeing this error spam the logs every second. These are the devices connected to the HBA: Apr 20 13:22:08 Potato-Server emhttpd: device /dev/sdh problem getting id Apr 20 13:22:08 Potato-Server emhttpd: device /dev/sdg problem getting id Apr 20 13:22:08 Potato-Server emhttpd: device /dev/sdd problem getting id Apr 20 13:22:08 Potato-Server emhttpd: device /dev/sde problem getting id Apr 20 13:22:08 Potato-Server emhttpd: device /dev/sdf problem getting id Apr 20 13:22:08 Potato-Server emhttpd: device /dev/sdc problem getting id Apr 20 13:22:09 Potato-Server emhttpd: device /dev/sdh problem getting id Apr 20 13:22:09 Potato-Server emhttpd: device /dev/sdg problem getting id Apr 20 13:22:09 Potato-Server emhttpd: device /dev/sdd problem getting id Apr 20 13:22:09 Potato-Server emhttpd: device /dev/sde problem getting id Apr 20 13:22:09 Potato-Server emhttpd: device /dev/sdf problem getting id Apr 20 13:22:09 Potato-Server emhttpd: device /dev/sdc problem getting id Here is my config prior to the upgrade:
  9. Here is what the array looks like after boot:
  10. BrickPotato changed their profile photo
  11. BrickPotato joined the community
  12. Im having a strange issue. When i upgrade to Unraid 7 from Unraid 6, none of my array drives connected to my LSI HBA are detected (both nvme cache drives are working). Array is stopped on boot and start array says there are missing disks. All drives parity+data show unassigned with no drives available in the drop-down. My Setup is: Motherboard: Asus Pro W680 + IPMI CPU: Intel i9-14900k Array connected via two LSI LSI 9207-8i cards in in IT Mode Parity: 24TB Seagate Data drives: 3x 8TB WD data drives 2x 24TB Seagate This is the second time Ive attempted this upgrade. Last time I had the same issue and just rolled back and everything worked again. I'm sure is something with Unraid 7. My HBA cards are both visible in the ASUS bios on Legacy BIOS config. Another issue, perhaps related, is my server wont power down. It sends the commands and terminal says SHUTDOWN, but it just stalls. I can figure this out later after I get my server in a better state, but wanted to share here in case its tickles someones brain and is related. Anyone have any ideas? Ive searched around and came up blank. Ive also read the upgrade forum and none of those known issues sould like what i'm expiriencing.

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.