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.

Thank you for your help three-eighty eight. What I did. All drives present (even failed drive). Assigned drives back to their original assignments. Selected "keep parity" Entered my original passphrase when asked for "enter new key". Array started. All data is intact. Time to attempt moving the data off the failed/failing drive. It's showing green now.

Found another thread suggesting if I enter the old passphrase, it should be ok? Apologies to everyone necro'ing a old solved post. Was thinking the OP could share what their experience was, but I think my scenario warranted a new thread.

Hi three eighty-eight, Some backstory how I got here... Existing encrypted array reported a failed drive. Shutdown Physically removed the failed drive. AND I removed a some unassigned devices that I no longer needed. Powered up Performed new-config, selected keep-existing-all (minus the missing bad drive) unRAID prompting for "enter new key" but I'm terrified that if I do, it'll reformat. Grabbed a copy of my /flash/config folder. Probably too late to help. Did some research, I seem to think since there were drives removed, the device-ids are now different? Powered down. Put bad drive back in. Powered on. Re-assigned all the drives to their corresponding array disk numbers. But I'm still seeing this "enter new key". At this point I feel pretty stupid making multiple changes during a failed drive maintenance. How screwed am I? Nothing has been formatted, or parity rebuilt. Just stuck with a stopped array and don't know how to get back w/o data loss.

I'm having the same issue as you. New Config, prompting for new passphrase. What did you do to solve? v6.5.3

@hawihoney did you ever find a suitable dual M.2 adapter? I'm looking for one myself.

Hi unRaiders, a big thank you to the community who's posts helped me get my datahoarder setup. I just wanted to share my experience, and a script that might help others with the same problem. Problem: Finally pulled the trigger on replacing my cable TV box with a HD HomeRun Prime that allows Plex to record TV. Problem is the files it generates are HUGE. e.g. a 2 hour episode is pushing 22GB. Solution: A post-processing script that transcodes video files into a smaller, more efficient format for archival. https://github.com/scrathe/plexEncode That is all. If you have problems, reach out here or better yet, report a bug on the Github.com page. Plex DVR Setup: Plex \ Settings \ Live TV & DVR \ DVR Settings \ Postprocessing Script = full path to the script