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.

Implosive7025

Members
  • Joined

  • Last visited

Everything posted by Implosive7025

  1. Here are the requested diagnostics, thanks in advance unraid-diagnostics-20261027-1406.zip
  2. I'm looking for advice from experienced Unraid/XFS users before attempting any modifying filesystem repair or disk rebuild. My priority is preserving recoverable data from both the original physical disk and the parity-emulated filesystem, while eventually restoring my Docker services. System and current statusUnraid: 7.3.3 Array: Single parity, five assigned data disks Affected disk: Disk 4, HGST Ultrastar 10TB, approximately 6.7 TiB previously used Failure: Disk 4 disabled following reported SATA communication errors Parity: Assigned and online at last verification Other data disks: Online at last verification Disabled assigned data disks: Disk 4 only Replacement: New 10TB HDD available but not installed or assigned Current array state: Started in Maintenance Mode, filesystems unmounted Docker: 32 containers stopped during the diagnostic These are the last recorded states, not a new live check. What happenedDisk 4 experienced SATA/communication issues and became disabled. During earlier recovery work, I investigated the original physical disk. That work reportedly included recreating a missing partition entry, inspecting XFS metadata, and successfully mounting the original disk to inspect directories. The original commands and mount flags still need to be reconstructed. The original disk was still detected by Linux during the latest inventory but was disabled as an Unraid array member. I have not established whether the disk is currently spinning or whether it can still be accessed reliably. The parity-emulated Disk 4 filesystem is recognized as XFS but cannot mount successfully. An earlier mounting attempt against the emulated filesystem failed during XFS journal recovery: XFS (md4p1): Starting recovery (logdev: internal) XFS (md4p1): Corruption detected. Unmount and run xfs_repair XFS (md4p1): Failed to recover intents XFS (md4p1): log mount finish failedRead-only XFS diagnosticOn October 26, 2026, I entered Maintenance Mode and ran one non-modifying diagnostic against the parity-emulated partition: xfs_repair -n -v /dev/md4p1Exit status: 1 Duration: 4 minutes 24 seconds No modifying repair performed The diagnostic warned: Selected findings: Diagnostic finding Reported count Multiply-claimed reports 579 In-use inode/free-map conflicts 4,851 File data forks claiming free blocks 27 Btree key lookup length errors 154 AGI unlinked-bucket entries 334 Leftover CoW extents 22 The diagnostic concluded: No modify flag set, skipping phase 5 Inode allocation btrees are too corrupted, skipping phases 6 and 7 No modify flag set, skipping filesystem flush and exiting.I understand that a dirty journal and the limitations of -n can produce repeated or cascading errors. I'm not treating these counts as numbers of permanently lost files. The scan did not report an explicit block-read failure. No new surviving-disk errors were observed in the bounded post-scan checks. Parity and disk-health concernsThe last parity check was reportedly incomplete/aborted. I haven't established the last successful parity verification, the correction setting of the aborted check, or its timing relative to Disk 4's failure. Historical SMART/transport findings: Parity disk: 3 CRC/ICRC errors Disk 3: 33 ATA errors / 34 CRC events Disk 1: 2 reallocated sectors Those counters did not increase during the monitored October 26 checks. I understand that an online parity disk does not guarantee the reconstructed filesystem is correct, so I have not initiated another parity check. Existing recovery dataPrevious recovery work left several useful artifacts: Approximately 30GB of staged Photos Approximately 660,495 files / 85.97GB across 36 staged application-data trees Previous transfer and verification logs An approximately 2.99GB XFS metadata dump with a dirty log Several restored application databases and file copies The staged data has not been established as a complete backup, and the exact original source of every recovered file is unknown. The metadata dump is non-obfuscated, and its source device is not conclusively established. I have not attached it. I have not obtained a verified full sector-level image of either the original disk or the parity-emulated filesystem. I currently have no confirmed independent imaging destination with sufficient capacity. My questionsPreservation order: Should I prioritize imaging the original physical Disk 4, the parity-emulated Disk 4, or preserving the staged recovery artifacts first? Dirty XFS journal: Since normal journal replay already failed, is there a supported way to investigate the failed intent recovery without risking the live emulated filesystem? Would experimentation on an independent image or metadata-only reconstruction be useful? Repair strategy: What should be established before considering a modifying xfs_repair? I want to avoid -L unless a knowledgeable reviewer determines that there are no safer alternatives. Parity confidence: What existing logs or records should I examine to evaluate parity reliability without starting a potentially stressful parity check or rebuild? Original disk: Because the original disk was previously readable but has a history of communication errors, would you recommend a specialist assessment or controlled imaging before further reads? Service availability: All 32 Docker containers are currently offline. Is there a supported way to return the array to normal operation without triggering another write-capable journal recovery attempt on Disk 4? If not, what safeguards should I consider before accepting that risk? Eventual rebuild: Is it correct that rebuilding the replacement disk now would reproduce the existing parity-emulated filesystem corruption rather than repair it? What I have NOT doneNo filesystem formatting No xfs_repair -L No modifying XFS repair No parity check or rebuild during these recovery phases No New Config or disk assignment changes No replacement drive installation No further physical-disk inspection during the controlled diagnostic phases The array remains in Maintenance Mode while I seek advice. I've included sanitized excerpts from the non-modifying XFS diagnostic. I can provide additional reviewed evidence if needed, but I don't want to make an irreversible change or expose the complete recovery archive unnecessarily. I'd especially appreciate recommendations on the safest preservation order and whether Docker can be restored without compromising recovery. XFS_LOG_EXCERPTS.md

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.