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.

Jake Lowe

Members
  • Joined

  • Last visited

  1. These errors did occur after a restart each time, It never happened before with the server running for 6 months straight. Unfortunately, I don't have any room to add a new sata card, (Old motherboard)
  2. lf1-diagnostics-20260301-0804.zip Thanks for your response, Hopefully this helps. I will also run an extended smart test on all drives in the array. Is it ok to replace a single parity drive with these 5 errors present? (This should rebuild any issues?)
  3. Hi all, hoping for some guidance before I proceed with a parity drive swap. (Two parity drives, wanting to proceed with replacement one at a time) I have had the same 5 sector errors weeks apart, The first time I noticed these errors I started a correcting parity check, Then I rechecked with corrections and all errors returned to zero. Now, I am wanting to replace my parity drives, before doing this, I ran a non-correcting parity check and noticed the same errors on the same sectors. How should I proceed? Is it safe to proceed with my parity drive swap with these 5 errors present? (Probably unrelated) All drives but one are 4TB - one drive is 2TB, This drive spins down after a while during parity check. The Issue: I have 5 persistent parity errors appearing on the exact same sectors across two parity checks, two weeks apart. Feb 13 parity check errors: - Then I corrected parity errors, reran parity check, parity returned no errors. Feb 13 23:56:39 LF1 kernel: md: recovery thread: PQ incorrect, sector=3519069768 Feb 13 23:56:39 LF1 kernel: md: recovery thread: PQ incorrect, sector=3519069776 Feb 13 23:56:39 LF1 kernel: md: recovery thread: PQ incorrect, sector=3519069784 Feb 13 23:56:39 LF1 kernel: md: recovery thread: PQ incorrect, sector=3519069792 Feb 13 23:56:39 LF1 kernel: md: recovery thread: PQ incorrect, sector=3519069800 Feb 28 parity check errors (Same errors as before) - Feb 28 18:53:44 LF1 kernel: md: recovery thread: PQ incorrect, sector=3519069768 Feb 28 18:53:44 LF1 kernel: md: recovery thread: P incorrect, sector=3519069776 Feb 28 18:53:44 LF1 kernel: md: recovery thread: P incorrect, sector=3519069784 Feb 28 18:53:44 LF1 kernel: md: recovery thread: P incorrect, sector=3519069792 Feb 28 18:53:44 LF1 kernel: md: recovery thread: PQ incorrect, sector=3519069800
  4. What is the default login for mineOS

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.