scrathe

I did a poor job of explaining what steps I took previously. I did xfs_repair -n, no -n (repaired), and another -n which reported no errors. Despite no errors, it still reported "Unmountable: not mounted". Thank you trurl 🙏 for taking the time on this thread. I was able to save my data. Posting the *cough solution below?... may some other poor soul who's thinking they lost data find help here. TLDR; Run xfs_repair (without -n) before you run Data-Rebuild. Data-Rebuild didn't work the first time. Removed/readded the disk to the array and re-ran Data-Rebuild. Disk and array are back to normal. Scenario: Older/established server experienced a mini-SAS to 4-drive cable failure. (SFF-8643 to SFF-8482) Two drives were knocked offline. Parity2 and Disk1. unRAID array status reported: Disk1 was emulated. However the data, and total array space was missing. Disk1 was "Unmountable: not mounted". Powered down. Replaced cable. Removed Parity2. Left healthy Parity1 in place. Powered up. Started array, started Data-Rebuild. unRAID array status reported: Disk1 was emulated. Data and space still missing. Disk1 was "Unmountable: not mounted". Data-Rebuild completed: Disk1 is marked "green, in operation". Data and space still missing. Disk1 was "Unmountable: not mounted". Stopped array. Solution? It worked... not entirely sure if all steps are needed. Started array (maintenance). Disk1: xfs_repair -n (100s and 100s of errors) Disk1: xfs_repair (repair without -n) Disk1: xfs_repair -n (no errors) Stopped array. Started array (normal). unRAID array status reported: Disk1 is marked "green, in operation". Data and space still missing. Disk1 was "Unmountable: not mounted". Stopped array. Removed Disk1 from array. Started array (maintenance). Stopped array. Added Disk1 to array. Started array (normal). unRAID array status reported: Disk1 was emulated. Data APPEARED, and total array space was BACK. Disk1 was "Unmountable: not mounted". Started Data-Rebuild. Data-Rebuild completed: Disk1 back to NORMAL.

While array was in maintenance mode. Ran xfs_repair with options set to blank (see Spoiler) Stopped / Started array still in maintenance mode. Ran xfs_repair -n (see Spoiler) Disk1 still says "Unmountable: not mounted"

Hi Community! Looking for some guidance on how best to proceed with my issue. Thank you in advance for your review and any suggestions shared! Diagnostic logs hoth-diagnostics-20221006-0923.zip Scenario: Older/established server experienced a mini-SAS to 4-drive cable failure. (SFF-8643 to SFF-8482) Two drives were knocked offline. Parity2 and Disk1. Powered down. Replaced cable. Removed Parity2. Left healthy Parity1 in place. Powered up. Started array, Data-Rebuild started automatically if I recall correctly. Note: During the rebuild, the disk was labeled as "Unmountable: not mounted". I didn't know if this was to be expected. Left it be during the rebuild. Rebuild completed. Disk1 is marked "green, in operation", but still shows "Unmountable: not mounted". Did some research on the community forums and https://wiki.unraid.net/index.php/Replacing_a_Data_Drive. Checked Disk1 xfs filesystem. Stopped array, mounted in maintenance, performed an xfs_repair -n. (see Spoiler below). Note I only performed "-n" and have not taken any further actions. Ideas: New Config, Keep Parity, and let Data Rebuild again? Let xfs_repair try and repair? There were 100s and 100s of errors. Data loss more likely?

Fixed the problem with this addition to my script: export LD_LIBRARY_PATH="/usr/lib/x86_64-linux-gnu"

Hi All, hoping someone can point me in the right direction. I customize the Linuxserver.io Plex docker to add ffmpeg/mediainfo/etc for a custom DVR post-processing script. It's been working great, but somewhere about September 14th, I'm now getting this error... ffmpeg: /usr/lib/plexmediaserver/libz.so.1: version `ZLIB_1.2.9' not found (required by /usr/lib/x86_64-linux-gnu/libpng16.so.16) What's super weird, is that error only occurs when Plex executes the script. If I console into the docker and run it manually, I have no problems.