danimal86

is it this part thats telling you there is an error: or the entire line is what tells you that drive SDL has an error. just trying to figure out what to look for in the future.

Ok, i'm kinda stuck until the parity check completes. Once its done i'll start messing with the cables and double check SDL/SDM/SDH drives. What part of that error shows you that there's drive errors (just for future reference so i can look) Last night, i went ahead and turned off every docker except for plex and turned off a script and any dockers that would do work overnight and the server didn't lock up over night. Maybe i'll actually be able to finish this parity check.

Could this be a hba issue? I'm using a hba and a SAS expander. Any way of telling what disks are erroring? I have a few disks I did get UDMA CRC error counts errors on one of the unclean shutdowns but the value hasn't gone up past 1 for both drives. I got no other errors on the dashboard. I went ahead and ordered replacement HBA and Sas Expander cards. I have a spare psu as well. It would be a pain to redo every cable to the drives. Any way to tell which ones are erroring?

I'm kinda grasping at straws, but could this be a hba card issue? Looking through the log's final entry last night: Reading through some other threads it was said that it was an issue with hba during spindown. A parity check was going because of an un-clean shutdown, so it shouldn't have spundown any drives. My cache is dual m.2's on the mobo.

Well, it happened again...3rd time in 3 days. Seems like everything is fine when i go to sleep and then something bad happens overnight. Attached is the syslog. ping'ing @itimpi also syslog-192.168.1.99.log

i might just do both. Is it an insane amount of writes to the flash? look about right?

Do i need to do anything other than these settings? In the event of another crash, what information should i provide?

Thats what i was worried of. I enabled the syslog server, hopefully i dont have to use it anytime soon.

Last night, i noticed that i couldn't get onto plex. Tried logging into the server via a windows machine and coudn't bring up the dashboard. Its happened in the past but hasn't in a long time. I went ahead and did a hard reset of the server and everything was fine last night. I woke up this morning and Plex was unresponsive again. I tried logging into the server and same thing. Non responsive. I didn't really know what to do, so just gave the server a hard restart again....parity check was still running from the first time, not sure if that's going to mess anything up. Server fired right up, everything seemeds normal except that both my parity drives have a UDMA CRC error count of 1 now. I believe this is just usually a connection error, i'll keep an eye on it to see if it increases. Any ideas? Any red flags in the diagnostics? Diagnostic 083024.zip

Thats what I was worried about.

seagate SMART.zip

I've finally gotten a replacement disk precleared (and a backup) and i'm getting ready to RMA the disk that had the issues. It hasn't had the same issue as it did the last 3 times, but i dont trust it. I was wondering if you would be able to help me by letting me know what information i could provide to seagate regarding the error. I did a quick scan of the drive and it came back fine. I'm just trying to cover my bases before i submit the rma.

Dang, well too late.....started the rebuild. Unbalance still the best tool for the job?

I still need to do the rebuild first correct? Is unbalance plugin still the best way to move data off the drive? The extended test came back without error.

any reason why I cant/shouldnt do the rebuild then shrink the array and remove that disk and rma it? I've got plenty of room

yeah, its the same drive that keeps failing. I didn't try new cables, just used power/sata cables that weren't previously used. I'll try reaching out to seagate and seeing what options i have. As far as the array goes, the failing drive (16tb) is the one that was currently being filled up, i hav two 14tb drives that have only had 97.6gb (file system?) written to them. Can i just do a rebuild onto one of the 14tb drives while i figure out whats going on with that 16tb drive?

Well, it happened for a 3rd time. At this point im at a loss. This will be the 3rd rebuild i've done. Last time i made sure to use different sata and power cable. I wonder if its something wrong with the hba or the sas expander card. I believe that the drive is still under warranty, but the health checks still come back without any errors, so i'm not sure if its an actual drive issue or what. Not sure if its worth spending another day running a extended health test, or if i should just start the rebuild process. tower-diagnostics-20240730-0655.zip

Extended smart test completed without any errors. Attached is the smart report. I'm going to go ahead and swap cables and start the rebuild process. tower-smart-20240719-0653.zip

Yeah thats a good call. I'll run the full test. It just takes forever for a 16tb drive and if its like last time (2 weeks ago) it will come back with no errors.

Thanks for looking into it.....multiple disk errors you say? Something to be concerned about? I'll try using a different power and sata cable and see if it changes anything......now for another rebuild.

We'll i just checked on the server and saw that disk 9 is in an error state AGAIN. I ran a short self test and it Completed without error. Attached is an updated diagnostic. I need to go back and look, but i think that this drive might still be under warranty....not sure if this is a connection issue, or the drive is failing. here's the smart info if that helps tower-diagnostics-20240718-0650.zip

Extended Smart report is attached. It completed without error. I shutdown, reseated cables, and ran another dignostic (attached). I'm going to start the rebuild process as i posted above with the same disk. tower-smart-20240704-1715.zip tower-diagnostics-20240704-1726.zip

Thanks! All my drives are on hba 9207-8i and connected through an intel RES2SV240 sas expander. I'll try reseating that plug on the sas -> sata breakout cable when i shut it down to reboot and re-run diagnostic.....once the extended test is complete.

Last night i received two emails saying that my array has errors and that Disk 9 is in an error state. The main tab shows 807 errors. I ran a quick smart test on drive 9 and it came back healthy. The extended test is currently running (16tb drive) for the last 10 hours now, probably has a few hours to go. Once its done i'll attach the test results. Will the extended test give me a result like the quick test did, or will i need to comb through all the smart attributes? In the meantime, i've attached diagnostics. From reading around if the smart test comes back fine, i'll reboot once the server post another diagnostic and then start the rebuild process by: Stop array Unassign disk to be rebuilt Start array with disk unassigned Stop array Reassign disk to be rebuilt Start array to begin rebuild During this rebuild time, will my server be functional (plex)? I've got dual parity if that matters. If the smart test comes back bad (or something bad in the diagnostics), can i rebuild from a hot spare (14tb) thats part of the array but hasn't had anything written to it yet except 97.6gb which i'm assuming is the file system? Much appreciated. tower-diagnostics-20240704-1001.zip

So if you were to manually delete an item from the txt file then the mover wouldn't ignore it and it would get moved off the cache? Just so i know how it works. Once the cache hits the MAX_SIZE then it starts deleting items off the list starting at the bottom and then the mover does not ignore those anymore and moves them off the cache to the array?