WebAddict

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by WebAddict

  1. Thank you @JorgeBfor helping me navigate that. I ran an Extended SMART Disk Check on all three disks that were affected, as well as my two spare drives. 18 hours later, the one parity2 disk that started the chain of events is actually failing, but each of the other four passed smart tests. So I put the original disk9 back in storage rack, and updated disk assignments and ran the UnRaid > Tools > New Config, keeping all drive and pool assignments. It worked like a charm, I now have all 22 data disks running and zero parity drives on there. I am getting a shipment of 4 new drives today, but will need to test and zero them before installing them. Was worth making slow and deliberate decisions and I kept all of the data. I just need to remember to pull diagnostics before rebooting.
  2. Yes @JorgeB the old disk9 is still in tact. Unraid won't let me start the array with old disk9 assigned as disk9 due to "Too many wrong and/or missing disks!". I shutdown the server last night to move the spare disks off the Motherboard SATA controller to the LSI controller card by swapping with the disks that were disabled. So I'm attaching the latest diagnostics. Is my best option going forward starting a "new config" but resetting the old disk9 to a valid status? weapon-diagnostics-20231111-1028.zip
  3. 24 total disks, 22 data + 2 parity I've dealt with this multiple times, not my first rodeo... but now THREE disabled at the same time! I'm treading carefully. My question is primarily: My data disk9 was disabled after read errors, HOW DO I RE-ENABLE this DISABLED DATA DISK without WIPING it? I know this to be a good disk, and tested successfully with short smart and I believe is a cable-related issue (new cable arriving tonight). Sequence of events 16tb parity2 started having read errors (probably bad cable), I stopped array to replace with an already precleared 16tb disk. I made assignment to new disk and started the array (without rebooting). As soon as array came online, multiple additional disks (parity1 & disk9) started having read errors and were disabled. I stopped the automatic Data-Rebuild. And have been keeping the array stopped until I figure out how to proceed. I downloaded diagnostics (noting after reboot), and have attached them I'm not touching the former disk9, leaving in tact. If I can't re-enable it, I will plan on bringing online a new empty disk9 and rsync old disk9's data. Then will rebuild parity from scratch (as both parity are disabled anyways...) Thanks in advance for any of your feedback weapon-diagnostics-20231110-1412.zip
  4. I have two DISABLED data disks (with two working parity disks) - I FOUND POSSIBLE BUG & need advice! First: 14tb disk3 had hardware failure. Ordered Seagate overnight warranty replacement. After a system reboot, this disk was no longer "installed", but being emulated. (no problem, thx parity!) Array is kinda full, so also ordered, received and started pre-clearing three new 16tb disks to add to array. Once I finally received the warranty replacement 14tb disk, I hot-unplugged the failed disk, and plugged in it's replacement on same sata. Now showed up on unassigned disks, ran seagate cmd tools for SMART tests and extended tests - all passed. Now - pay attention for BUG - This is where I started a preclear for the replacement 14tb (now 4 preclears running simultaneously, with 3 for new 16tbs). It started the Pre-Read, and I was monitoring that for a few hours when I noticed the SERIAL NUMBER of the new pre-clearing 14tb disk was actually another 14tb operational disk4, not the expected serial printed on the HD. This serial number is showing up for both devices. So out of precaution, I stopped that preclear/pre-read of the 14tb, and paused the other 3 preclears so I can stop the array and reboot. Once the system came back up, all disks now showed the right serial numbers - but now the WORKING 14TB WAS MARKED DISABLED! I assume that's because in the preclear process, it labeled the wrong serial number (or other identifier) assignment, and now disk4 is out of sync. I have run some tests on that known-good disk4 14tb drive, and it passes all tests. I have been able to start a new preclear on the replacement 14tb disk, and that will be done in a day or two. Question is: For disk4 (disabled 14tb working disk), can I "Rebuild a drive onto itself" safely? Even though there is an "Not installed" disk3? I have two good parity disks perfectly emulating the data. I understand the rebuild process - but am checking here if you think I should proceed starting that disk4 rebuild while disk3 is not installed. OR should I WAIT to have two completed preclears, and do both disk3 and disk4 at the same time with full precleared disks? I have just posted my hardware profile to limetech & submitted a feedback form bug report from my dashboard. I can provide logs or anything else that might be useful.
  5. The NVENC support was what made djaydev's Handbrake docker image special... Losing that build is a huge loss.... Perhaps someone else could fork his work from djaydev/handbrake on github or dockerhub and make it available. I have used Spaceinvaderone's guide to downloading new media to a watch folder, and then sonarr/radarr moves the newly transcoded media to the array. I found a 720p quality setting for TV shows, and a 1080p setting for Movies that I felt like retained the quality, saved a ton of space, but also allows most of our devices to direct play. Many remux 45 min 1080p episodes are about 4gb, but my 720p x264 version averages about 1.2gb. I will be able to continue using djaydev's handbrake since I already had it before it went away. I feel bad for anyone else that wants to use it and can't find it.
  6. I appreciate cpshoemake's comment - that saved me a bunch of headache. I used that to enable on two of my Seagate SATA drives that were on my LSI SAS card, and wouldn't change write caching with the above hdparm or sdparm commands. This SeaChest command worked perfect for me!