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.

Maz

Members
  • Joined

Everything posted by Maz

  1. Thanks... Thanks. I was able to get as far as 6.12.11 without issue. When I go to 6.12.13 is when this issue starts. Might I ask, How do I get the attention of the Dev team to look at my diagnostics and determine the root cause? can this post be at least noted? I have standard hardware and controllers used in my build. To be honest there is nothing unique about my hardware that should cause this... if so, I would like to think it would be beneficial to all to understand where the issue lies. If I move up to the 7.0 betas, is there the chance they will work? Can I downgrade back to 6.12.11 after upgrading to 7.0 B3 if there are still issues? Thanks again..
  2. So I just downgraded back to 6.12.10 and the server now reboots again without error. So its a bug or something that changes in 6.12.13 causing the issue for me. I would suspect something in 6.12.13 is causing this issue??>>> SYSLOG indicating "crashing the kernel on kernel split_locks and warning on user-space split_locks" I see there is middle update being skipped which is 6.12.11 ... should I update to that first instead of going directly to 6.12.13? Any help or feedback is appreciated... I cannot be stuck downgraded indefinitely. Thank you!!!
  3. I just downgraded and it reboots without issue ... so something is wrong with 6.12.13
  4. Thanks for the feedback. Can I just downgrade back instead? its quicker to do that rather than obtaining another drive... will do so if its the only option. thanks
  5. Unraid hangs on boot after updating from 6.10 to 6.13 stable Diagnostics attached... I can get get the server to boot only if I enter the bios, then exit... it will boot up just that once. Any reboot or power down and restart causes it to hang again on boot.... Unless I enter the bios on startup and then exit it seems to only boot under this condition. I receive the below error in the system log: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks Please help I cannot afford to lose my server. Any feedback on what to do is appreciated. unraid2-diagnostics-20241018-0948.zip
  6. My concern is because ZFS does not have the same flexibility as XFS for Mixed drive size and pool expansion. Yes of course ZFS much more robust, but I think I possibly speak for many core users who purchased Unraid for the same reason which is that We just want XFS or a file system that allows easy expansion of drive pools and the ability to mix and match with dual parity and nothing more. I 'm hoping the original focus that made Unraid a better option for many, wont be forgotten while jumping on the bandwagon in supporting ZFS. Again this is just my humble feedback for what its worth.... And, What happens if the Linux Kernel does in fact drop support for XFS??? are the core users of Unraid left out because XFS becomes depreciated in Linux? I only bring this to the attention of the Unraid team in hope it can plan ahead with a clear path to support this functionality at its core, for those users who care about the conveniences of XFS, and nothing more. Thats what I enjoy most about using Unraid vs. the others. As a home user, I've been using it for years with XFS and have been content for what it is.
  7. Im a home-user and enjoy the flexibility of using XFS with mixed drives and expanded drive pools which was the main attraction to Unraid in the first place. I simply have no interest in switching over to ZFS. If XFS is removed future builds, i will no longer have interest. A question For the Unraid dev team, What are the future intentions here regarding future your roadmap in supporting XFS???
  8. Thanks- .. so, I changed the Ethernet rx/tx buffer sizes from 512 back to 256 (using the tips and tweaks plugin) which is default, and enabled flow control. Not sure exactly why, but so far it’s seems to have resolved the dropped connection issue. I will continue to monitor. My amd system ram speed is set to 2400mhz with memory profile turned to off- which is the slowest speed allowed. not seeing any relation to the connection drops due to ram speed or improper motherboard settings. Still a little bit confused as to why, but it seems stable after above Eth buffer size changes w/ flow control enabled.
  9. Please advise. My Unraid server has been constantly dropping connection at random for months and is getting worse. each time requires hard shutdown of the array. reboot lasts a while then sudden disconnects. Syslog & Diagnostics attached. syslog.txt unraid1-diagnostics-20230330-1453.zip
  10. Same problem with the latest my servers plugin 2022.09.06.2108 - Failed to sync flash backup.

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.