visionmaster

OK thanks for the guidance. So far I've changed the power supply from the 750w to a 1000w that I had. I checked all connections and reseated everything. I changed out disk 16 to a spare and started rebuild. It mounted fine and the data was emulated. About a minute in, disk 15 started racking up read errors and then no data was visible on that disk or 16. I stopped and shut down and moved those 2 drives onto a different controller and booted up again. Everything appears good with no errors. Rebuild restarted and the data is emulated again and visible on both drives. I guess I'll let it finish, and hopefully with no errors. I'm going to research a whole new build to get this 13 year old hardware updated. I'd like a big case like a rack mount 36 bay Supermicro hot swap. Thanks again for the assistance. -R

Thanks for the replies so far. Is there a way to reenable disk 16 which got disabled (if it were related to a loose connection) and trust the parity. And recheck everything from there? Thanks, -R tower-diagnostics-20230214-0728.zip

Hi, Before I mess anything up, just looking for advice how to proceed. I have 24 drives and 1 parity (I know I need to add another one, but my case is full.) System has been stable for 12+ years. Last parity check a couple of months ago with no issues (0 errors). I was going to upgrade a drive or 2 to get rid of old drives and increase the size of the 2tb to 8tb. I started a parity check to make sure it was good to go before the upgrade, and about 41% in, I got 1 drive disabled and 4 others with errors. (all read errors) My gut tells me its a loose connection issue. My webGUI has has paused the operation. Should I powerdown and re-seat all connections and do another parity check? What about the current disk that is disabled? Thanks, -R syslog.1.txt syslog.2.txt syslog.txt

Here is that report.tower-diagnostics-20210927-0651.zip

I've posted in the past regarding my issue with the Seagate 8TB ST8000VN0022 drives. ( https://forums.unraid.net/topic/105350-unraid-os-version-692-available/page/5/?tab=comments#comment-981758 ) and after reviewing this thread ( https://forums.unraid.net/topic/103938-69x-lsi-controllers-ironwolf-disks-disabling-summary-fix/ ) ultimately my fix was just to keep these 2 drives of mine set to never spin down as the errors occurred when the drives spin up from a spun down state. Last week I noticed that drive 12 temp wasn't reading out on the dashboard and then disk disabled. I had tried running SMART tests but it wouldn't allow it. I then removed that drive and replaced it with another same model ST8000VN0022 (as I had 2 more of these as spares which had been precleared and ready to go) and parity rebuilt drive 12 normally and completed with 0 errors. Stupidly, I set that drive to spin down at default which is 1 hour, and when it spun up again the read errors started and the disk went into a disabled state. I have not written anything to any disk since before the rebuild. I attempted to find the trust my array procedure to reenable the disk and use the parity as it had just rebuilt with zero errors. But I ended up reassigning the disks in the original configuration and when starting the array, it would only allow it with a parity sync. I left the check box for correct sync errors and was expecting it to run and complete with 0 errors as it had just rebuilt drive 12 with no errors and nothing has been written to any drive. Well, it is 7 hours in and there are 581 sync errors corrected so far. The data on drive 12 is mostly just movies and the few movies I've tested seem to play fine. What would be the best thing to do at this point? I still have the original drive 12 which I plugged into my other test server and is reading normally and appears to have no SMART errors. Should I let it finish rebuilding parity with all these new errors or just replace the original disk 12 back into the array and rebuild the parity again? Maybe a cable wasn't seated properly? Looks like I don't have any data loss at this point... I'd like to keep it that way and get an error free protected array back online ASAP. Thanks for any help, as I'm still a noob with this, eventhough I've been running unRaid successfully for over 10 years... syslog.txt

I tried updating to 6.9.1, 2 weeks ago from 6.8.3 which has been stable for years. I had the Seagate drive issue after the drives spin down and then spin back up, I start getting read errors on 2 versions of my Seagate drives (ST8000VN004 and ST8000VN0022). Once reverting, no issues and stable again. I just tried to upgrade to 6.9.2 and immediately back to same 2 drives and spin up read errors, so I back to stable on 6.8.3. Hopefully fixed on next update. Those are the only type of Seagate drives affected on my system. My 4TB Seagates work fine. My drive controllers are Supermicro (MV88SX6081 8-port SATA II PCI-X Controller and MV64460/64461/64462 System Controller, Revision B).

I was searching around and this seems to do what I want. (The previous work around was telnet into server and type lsof). I'm a total noob with linux. http://lime-technology.com/forum/index.php?topic=42881.0

Hi. I just upgraded to Pro 6.1.9 from 5.0.6. I have the same question as stourwalk. I had a script on unMenu that Joe had written that would show the active stream including the disk number. I was not planning on reinstalling unMenu. Is there a way to have the active stream include the disk number? Thanks!

As always, thanks for the quick input. Much appreciated. I love this forum!

Hi, I was looking through the last couple of pages and it seems like this new drive I just did a 1 round preclear on, is pretty similar to axeman's, but the seek error rate and raw read error rate seem really, really high. I know the important reallocated markers are 0. Should I just consider this a healthy drive and use it as normal? It is a Seagate removed from an enclosure. I also did a preclear on a 2TB refurb WD drive that has way better looking numbers. Thanks for your input! preclear_results-3tb6-4-13.txt Fatboy_2TB_WD-WMC300165370_preclear_results.txt