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.

mrichards

Members
  • Joined

  • Last visited

Everything posted by mrichards

  1. Thanks for responding, itimpi. I thought I had clicked Apply during the first New Config attempt, but based on the drive icons, it may not have completed or registered properly. I repeated the process using Retain All and Apply, and the drives then showed blue icons as expected. Mark
  2. Thanks so much, trurl. new diagnostics attached. plex-diagnostics-20260625-1249.zip
  3. Hi all I need help recovering an Unraid 6.8.0 array after two disk failures. My array has always used only the Parity 2 slot. Parity 1 has always been empty, and the array previously worked normally in this configuration. Disk 7 originally used a 2 TB Western Digital drive. It became disabled, and its SMART report showed: 897 Current Pending Sectors 315 Offline Uncorrectable Sectors Disk 9 originally used a 2 TB Seagate drive. It stopped identifying at the correct capacity and appeared as approximately 3.9 GB or 137 GB instead of 2 TB. Valid SMART data could not be read from it. I used SystemRescue and GNU ddrescue to clone the failing Disk 7 to the new 8 TB drive. The final ddrescue result was approximately: 2,000 GB rescued 99.99% rescued approximately 115,712 bytes unreadable approximately 113 bad areas remaining after retries I bought a second new 8 TB drive to replace Disk 9. The current intended assignments are: Parity 1: unassigned Parity 2: original 10 TB parity drive Disk 2 through Disk 6: original drives in their original slots Disk 7: ddrescue clone Disk 8: original drive in its original slot Disk 9: new blank replacement I used Tools > New Config and selected Preserve Current Assignments: All. I then reassigned the Disk 7 clone and the new Disk 9 replacement. Unraid still reports: “Stopped. Invalid configuration.” “Too many wrong and/or missing disks!” The Start button remains greyed out. I also tried 'mdcmd set invalidslot 0 9' The command returned no output, but the Start button is still disabled. I haven't started the array, formatted the replacement drive, or rebuilt parity. My goal is to: Accept the ddrescue clone as the valid Disk 7. Preserve the existing Parity 2 drive as valid. Rebuild only Disk 9 onto the new blank 8 TB replacement drive. Add a new12TB Parity 1 drive. It's not currently assigned to the array. I don't intend to add or build the new Parity 1 drive until Disk 9 is rebuilt, unless the recommended recovery procedure specifically requires otherwise. Can someone please confirm the correct recovery procedure for an array with only Parity 2 assigned, including whether invalidslot is appropriate and what the exact syntax should be? I'll attach the latest diagnostics ZIP and screenshots of the current disk assignments and the disabled Start button. Thanks! Mark plex-diagnostics-20260624-1851.zip

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.