kjclark23

Well I'm not sure what's going on then. I'm getting notifications that my array returned to normal and then about two minutes after that it will say Disk 1 has read errors. They started yesterday (1/3/24) and did it about three times, each about 20 minutes apart. Then right after the last one, Disk 2 had the current pending sector count. I'm guessing both drives just need replaced, they are old.

I got a message yesterday that my Array has 0 disks with read errors, but right afterwards it gave a message that Disk 1 has 64 errors. Thought that was odd. Also, I got a message that Disk 2 has a Smart error with the current pending sector is 1. I ran the extended test on this HDD and it completed without error. I'm wondering if there's something going on causing multiple issues now. I did order a new HDD for Disk 1, but now I'm wondering if I should use it for Disk 2 instead. New to wait to order another one. gamingnas-diagnostics-20250104-1042.zip

During my scheduled parity check, I got a warning message that Disk 1 has errors. The parity check finished with 0 errors. I ran an extended test on Disk 1 which Completed Without Error. Not sure what to do from here, but pretty sure I need to power off and maybe check cables. Want to be sure before moving forward, so posting diagnostics. Many thanks! gamingnas-diagnostics-20250102-1121.zip

After the rebuild, everything is working correctly. No data loss. I want to thank you a lot for your hand holding through this. I'm not sure what the exact fix was, whether it was the PSU or if the MINI SAS to Sata cables were not good or if it was the HBA card was getting too hot. But I fixed all at the same time and that is not the proper way to troubleshoot it but it was a way for me to get it back in order quicker. I also did the data rebuild in maintenance mode to be on the safe side. How do I but you a beer?

Ok, I installed my new PSU and new Mini SAS to Sata cables. I also mounted a fan to my HBA card to help keep it cool. I just started it, and immediately had to power off because a different disk was missing. Luckily I have a table that tells me which HDD is where in my server case, wasn't hard to notice the sata power was pulled out some. Whoops. But it just booted and I ran the diags. Parity 2 and Disk 9 are still disabled and not sure what to do here. Many thanks! gamingnas-diagnostics-20240803-1848.zip

I will do this once I get my new PSU and Sata cables all hooked up. It's all suppose to get here by tomorrow so it'll be a couple days until I'll get the diags. Unless it's ok to do this now, I just don't want to run into more problems if it's my PSU and/or Sata cables.

Disk 1 as well as Parity 2 had their extended tests return as "Completed without error". What's next? Also, should I disable auto start?

Ok, so I did order a new PSU, because I just want to replace the one I have as it could've been under powered... I guess. Kinda hard to tell what exactly is giving me issues. So I'm going to wait until I get that, power everything down and put in the new PSU. This will also have me mess with connections. I'm also replacing my mini SAS to Sata cables, because I suspect those as they seem cheap. I also got a fan to get the temp down on my HBA card. So hopefully issues won't come up again. Worried if I do a rebuild or something and I still have power issues, than I'm probably going to get into a worse situation. After HDDs extended tests are done, I'm not really sure what to do next. I don't think I have done a new config before, and I just read some of it and now I'm scared because one of my drives disabled is a parity drive, and another is a data drive. While I also have a drive that has a pending sector counts, but it is still enabled. I'm now wondering what data loss I will have. Should I turn off auto start in disk settings? I'm also afraid to boot it down, to turn it back on and the array starts back up. Many thanks for the help.

Disk 9 Extended self test completed without error, so I started the other two this morning. I'm not sure what steps I should take now. Boot it down and check connectors? I just did this last week when adding another HDD. Disk 9 and the Parity 2 are both disabled, so I'm not sure how to get them back. I'll reply once the two drives self test finishes.

My parity check started last night and ran till about half way through the parity check to see that it has stalled and three disks have read errors, and one of these three also has a current sector pending of 1. I have read several forums and I suspect my PSU (CX850M), but after checking some things, I'm thinking it could also be my HBA card (LSI SAS 9300-16i), which I got a temp of 140 on the heat sink. I'm running an extended self test on one of the drives, didn't know if it's a good idea to run all three HDDs. I did stop my array before the self test. Really appreciate some hand holding on this one. I'm afraid to do things. gamingnas-diagnostics-20240731-1650.zip

Thank you everyone for helping me through this. I feel very dumb now, but I was too afraid to do anything without someone else also saying to do that. Mighty thanks!

Thank you very much. This was a lot simpler than I took it. wow. Is there anything I should do now? gamingnas-diagnostics-20240308-1912.zip

Finished. This is the output. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 5 - agno = 3 - agno = 4 - agno = 1 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... Maximum metadata LSN (1:569424) is ahead of log (1:2). Format log to cycle 4. done Sorry if it's obvious, but what do I do next? I really don't want to mess this up.

Did the check without -n (leaving it blank). Got this response: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. I assume I should go ahead and do the Check with -L option but would like to hear from you first.

Yep, that's important. gamingnas-diagnostics-20240307-2144.zip

I noticed that some of my movies were having playback errors to find they all came to one disc. So I restarted the server just to see if that would do anything, and it made my Disc 1 to be unmountable: no file system. I tried to follow some forums on here that had this but I believe I missed something. The drive is now getting the data rebuild, while still being unmountable: no file system. I have no clue what to do here, but I'm freaking out that I just lost 6TB of data. Any help? I tried doing the xfs_repair -vL /dev/md1, it didn't do anything, couldn't find anything. I did this after taking the drive out to emulate it. I then added the drive back and started the array, which is where it is at now. Says the drive now needs formatted too.