dthedj

I managed to start Plex server by removing the setting "--device=/dev/dvb/" in extra parameter. I'll troubleshoot the tuner card issue another day. Again, many thanks for your support.

Yes, I have a tuner card that I removed during troubleshooting but It's now back in the PCI slot. I think that the tuner appears in the system PCI devices list: ... [109e:036e] 09:00.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 02) [109e:0878] 09:00.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 02) ... How can I reset Plex settings so it finds the tuner? PCI devices log.txt

I have completed restoring data from backups. Thank you all for your support, especially trurl and itimp! There is only one remaining thing to fix: my Plex server can no longer start. I tried rebooting my unRAID server but always get "Execution error - Server error" Any idea what I should do to fix this? Server Log - Plex error.txt

The parity sync is completed and array seams to work normally. See latest Diagnostics file attached. Now I need to restore my data from the backups. I guest the easiest would be to copy the backups from my PC to the unRAID Shares over the network. unraid-diagnostics-20260410-0915.zip

OK, then no worry about the warning "All existing data on this device will be OVERWRITTEN when array is Started" => This will only erase the parity drive, right?

Sorry but with what I just experienced, I'm nervous about losing the data of the other disks, for which I don't have backups. Is there a possibility that the New Config process make the data of my other disks unavailable? Should I backup data before to proceed? Thanks

Could you please let me know how to proceed with New Config disk 9? Thanks

So for each of my drives, I need to add "1, 200" in SMART Attribute Notifications and click APPLY? Yes, three disks are showing errors. What should I do about this?

Which method is less "stressful" on the disks? Which one you recommend? Thanks

I restarted the array with disk 9 but it went back to same issue with both disk 6 and 9 showing empty and disk 9 emulated. unraid-diagnostics-20260407-1449.zip

Here's the latest diagnostics unraid-diagnostics-20260407-1114.zip

To confirm the recovery process: if I restore from a backup, do I simply reassign Disk 9 and restart the array? Will both disks then appear as empty, implying that without a backup, this data would be permanently lost? This experience is concerning, especially for a system designed for data redundancy. What are the potential root causes for this—could it be hardware-related? What should I do to ensure this doesn't happen again?" Thanks

yes

Done the Zeroing and got the message "File system corruption fixed!". See attached log. Now I can mount the disk 9 in UD and can browse the data which seam to be all available! What should I do next? log file zeroing log disk 9 UD.txt

I clicked on the button and got the attached log. Next I guess I click on "FORCE LOG ZEROING" ? (sorry for being such a nooby) log file system check disk 9 UD.txt

I ran check file system check from UD by clicking on the checkmark icon. See attached results. Next, I click on the "RUN WITH CORRECT FLAG" button in pop-up window? file system check disk 9 UD.txt

Since I already have a data backup of disk 9, I could skip the cloning and try to run again file system check, right? For this, I suppose I need to reallocate disk 9 to array, start in maintenance mode and re-run the file system check?

I stopped the array and selected "no device" for disk 9. I did not restart the array without disk 9. I tried to mount disk 9 using "Unassigned Disk Devices" but it did not work (see system log attached). System Log - mounting disk 9.txt

No, I did not format the disks. Just did the procedure as described in my previous message. Here a copy of the file check logs if it helps. xfs_repair status Check Disk 6.txt xfs_repair status Check Disk 9.txt

Here's the new diagnostics. Thanks unraid-diagnostics-20260406-1028.zip

Thanks trurl. I ran the file system check on both disks using the GUI. Both were showing a long list of errors, so I clicked the FIX button. For disk 9 only, the ZERO LOG button appeared and I used it. At the end of the process, I got the message "File system corruption fixed" for both disks. I stopped the array and restart in normal mode. Now the disk 6 and 9 are showing almost empty, and disk 9 is being emulated (red "X" in the GUI). I have no access to files on either of these disks through the Unraid shares. What should I do next?

Thank you for the quick assistance! Please see the attached logs of the dry-run checks for both drives. Let me know if I can proceed without the -n flag. Thanks! Log disk 6 (xfs_repair -n).txt Log disk 9 (xfs_repair -n).txt

Description of Issue: I recently completed a rebuild of Disk 6 from Parity. Following the subsequent reboot, both the newly rebuilt drive (Disk 6) and an existing drive (Disk 9) are showing as "Unmountable: Unsupported or no file system. Current Array Status: The array is started, but: Disk 9 is being emulated (red "X" in the GUI). Both Disk 6 and the emulated Disk 9 are listed as unmountable. I currently have no access to files on either of these disks through the Unraid shares. Console Corruption Errors: The physical console displays critical XFS metadata corruption errors for Disk 9 (md9p1): XFS (md9p1): Metadata corruption detected at xfs_buf_ioend... XFS (md9p1): Unmount and run xfs_repair XFS (md9p1): metadata I/O error in "xlog_recover_items_pass2..." Hardware Configuration: The two affected disks are on separate controllers: Disk 6: Connected via an LSI SAS HBA card. Disk 9: Connected via the onboard SATA port on the motherboard. Boot Flash: Samsung Flash Drive FIT (Logs show normal initialization as sda, despite intermittent -71 enumeration errors during boot). Troubleshooting Steps Taken: External Verification: I pulled the physical Disk 9 and connected it to a Windows machine via SATA dock. DiskInternals Linux Reader confirmed the data is intact and readable, but Unraid cannot mount the emulated version. Services: Plex Media Server is down as a result. OS Version: 7.2.3 Questions for the Community: What is the safest way to proceed? Thanks in advance for your help! unraid-diagnostics-20260404-1632.zip

Hit the "ZERO LOG" button and it successfully fixed the log. See attached. Restarted in normal mode and got rid of the Unmountable error. Now it seems that all files are available from emulated drive #2 🙂 Next: hopefully rebuilding from parity will work. Check Filesystem Status 3.txt