DiscoStu

Sorry I probably wasn't super clear, 2 separate confusions....I do understand all discs read on turbo mode, I was just trying to figure out what they were reading, as I wasn't transferring, no dockers running, etc etc. It did eventually relax and spin down, so no worries. As for disk4 I didn't consider the physical platter sizes, so certainly part of it. I was watching it closely later and did notice times where it was at 70% or so of the other discs which made sense. But some of the time it was at like 0.5% of the other drives speeds so I do think that drive might be hurting. Thanks again for talking me through. Plan to do parity check, backup to the offline drives again this week, and if everything is stable move to the new case this weekend.

Thanks as always, I figure I will leave it on while doing these big moves, then put it back to auto or normal. Quick question, I am allllmost done with all the moves and organization, and suddenly speeds have again dropped off a ton. I noticed 2 things likely related... Disk4 is either not reading at all, or reading at kb/s speeds. While im on turbo this seems strange, but all smart tests say 4 is just fine. This is also my oldest drive and wouldn't be surprised if it is dying from all these transfers. Also noticed that even when I paused/finished all the transfers that I was running (and neither mover/parity check running at the time) that my disks were all still reading or writing at decent speeds. Couldn't find what they were doing, even had all my dockers closed at the time. discoraid-diagnostics-20260202-2318.zip

haha bummer, just feel bad for future guy in the same boat. I've just learned about turbo or reconstruct write, and now its around 100MB. Is this safe to use during this move, and keep on after as well?

Thanks again for your help and the info dump. I have a lot to do when I'm back stable. Update, I now have disk1 back to stable, mounted the old disk1 and files are copying now. I tested move vs copy and doesn't seem to have any speed difference, so stuck with copy just in case something goes wrong. I've never done transfers from a mounted disc outside of the array like this, is it supposed to be quite slow? seems pretty consistent around 25-35 MB/s.(update: found out about turbo/reconstruct write and now its closer to 100-125MB/s so not terrible) Also I do feel like I should have some sort of conclusion to this thread for people looking in the future... I suppose we are blaming the usb error, or I somehow messed up the filesystem check then fix? I'm unclear how I would even recreate what happened the first time (erasing just disc1s info)

i feel like youve looked into my soul sir so all the a........ not existing are failed appdata backups? it created them at first somehow, not it works correctly, but I never knew how or if i could safely delete them. the e..... not using cache is long term backup disk3 is part of, rarely does anything once I filled it, I probaly just never set it to use cache, but I should. How does one set cache for the whole system? i only know how to set it by share. Also if it did hit the overflow point, does it pause until enough room, or just skip the cache and move straight in that instance?

Yep that was my thought, i shall wait. I do move/download to the cache pool first, but its only 2tb and in this case if I move its going to be around 10tb so certainly just wait. Thanks for the diagnostic info, Ive basically just been looking at syslog so good to know. Checking out the rest now, gives me stuff to research i understand 60% of this. Let me know if you found any other no nos while sorting through my junk haha. I really sad thing is I was ready to move to a new case for better cooling this weekend, but that will wait for a bit now. May I ask why you don't use hot swap cases / racks on either of your servers? I tried one years and years ago first doing large data stuff and never looked back

rebuilding, probably will 24 hours or so Is it safe to attempt mount the old drive during this, or transfer files to the array during the rebuild? I like being efficient, but I don't want to stress the drives. Thanks again, lurking hard on your signature links, much to poke at when i get this back up!

Should i format it first while not selected as disc1? (or stop array first and attempt to format there) then stop array, restart with it in that slot?

Thanks great. I ran a smart test and checked the folders seems all good. Dumb question, is there a write up on how to read the diagnostics? I want to learn what you are reading and didn't find exactly that in your signature links.

sorry forgot it was in maintenance (embarrassed face) discoraid-diagnostics-20260130-1917.zip

finished, and says fixed. I can't post all the results way too long but here is the end... Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Note - stripe unit (0) and width (0) were copied from a backup superblock. Please reset with mount -o sunit=,swidth= if necessary done discoraid-diagnostics-20260130-1908.zip

Thanks again gents Fix is in progress, noticed that under main it at least says xfs next to disk3 where it once said unmountable, so hopeful this does the trick. Even if it nukes the data, as long as it is stable I'll move onto disk1. For that... stop array, format disk1, then put it back into array, start in regular mode, let data rebuild? unsure if I need to do this part in maintenance mode as well

K, very scared but I'll do it when I get home. I hope it doesn't make me run the check again to do the fix, it took a whiiiiile

Sorry that for formatting was so bad, there were about 100 lines of ......, too big to paste

Finished by the time I woke up... Going to stop the array until I get home from work Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! 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. Now there is the option to "Fix, file system corrupted". Is the next step to try the fix? Is it really dumb I'm debating trying to make a backup of what is on disk3 (that is currently emulated), just in case it nukes again? Again this data not the end of the world if I lose though.