rockytt

When I checked today, disk 13 was red balled - shut it down, swapped in new cable, powered up and unassigned the disk, started in maintenance mode, stopped array again and reassigned the disk to the same slot. Data is rebuilding on disk 13 at 155mbs - so looks like that cable was (very) bad - thank you for the help!

thank you - will do so and report back!

Doh! (Long day at work - apologies!) tower-diagnostics-20240404-0629.zip

Thank you - very curious to see what the diagnostics show - attached! tower-diagnostics-20240403-1013.zip

Hi all - running my monthly parity check and it is sooooooo slow all of sudden. I don't see anything obvious in the syslog - but I'm not an expert here and could use another set of eyes. This current setup is a couple years old at least - with a few disks being swapped out of course Nothing looks amiss after running DiskSpeed Running 6.12.9 tower-syslog-20240402-2344.zip

Thank you both for your assistance - was able to successfully clone disk13 using ddrescue and then rebuild disk9 from parity - good stuff!

Thank you both for you help - First order of business is saving as much data as possible (Windows), which will likely take me into tomorrow. Afterwards, I'll take a crack at cloning the (supposedly) bad drive13 - pretty sure XFS file system will create a few challenges - and will update here - thanks!

Wish I still had original disk9 I did pull disk13 and have it connected to a windows PC with an XFS file explorer. I don't want to jinx anything, but I've managed to grab over 100gb of files so far and the process is still running. I figure that if I can save the files from that disk at least, it will only be 50% as painful! Begs the question - wonder if there is a way to: Put a new disk13 into the array and copy the files to it (w/o affecting parity), then put in a new disk9 and rebuild that one (9) from parity? (This is likely where knowledgeable people slap their palms on their foreheads and shake their heads sadly...)

Will do - thanks!

Long story short - had been getting an intermittent error with one of my discs and it would show up as disabled. Swapped out a cable and everything was fine for a couple of months, but then the issue became persistent. Today (after red dot) I swapped out the drive (9) with a new one and started the data rebuild, which was going swimmingly until it threw an error and paused the process. Now it looks as if drive 13 has failed completely - any magic tricks to try? If not, I'll just cry and move on I did try and check filesystem status on 13 - but no love as it just errored out tower-syslog-20230110-1353.zip tower-diagnostics-20230110-0552.zip

Will give it a go - thanks!

That was fun Check Filesystem Status.txt

Gui - (and dang - fast response!) (and this is an old/old system - if new mb is needed I wouldn't be surprised in the slightest)

A bunch of errors thrown and when I try an "check file system status" , get the following error: Phase 1 - find and verify superblock... bad primary superblock - bad sector size !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now. What's the best path forward? Just swap out the disk and rebuild parity? Read through several threads, but didn't see a solution for this exact issue - thanks! fastbird-syslog-20221011-1702.zip

Makes sense to me - bombs away! thanks again for your help and patience