spall

@JorgeB @trurl My server rack was powered down longer than I anticipated. Anyway, dual rebuild to two new drives worked like a charm. Thanks for the help! Marking as solved.

The second one just finished the extended test. All good on that drive, as well. I have to wrap the rack in about 30 hours. I have a feeling that would be cutting it real close if I started rebuild now, unfortunately.

@trurl Everything is thumps up on the dashboard including the two disabled disks. One of the disabled, disk5/sdi, has finished the extended test and is all good except for 1 UDMA CRC error which I believe was a previous error. Disk13/sdg is 90% done with the test. Unfortunately, moving is not an option for me. I have a spinal injury and cannot muscle the 4U upstairs even if I remove all the disks. I'm going to have to wrap and tarp the whole rack. Ok. Sounds like I'll probably rebuild to my spares, but I'll shut everything down when this test finishes and wait until the work is done in the basement. I'm not sure how long it will take to rebuild 2x14TB drives. Thank you.

@trurl @JorgeB Great. I appreciate the help. A few questions since I'm still waiting for the long S.M.A.R.T. to finish: 1) Do I unassign/reassign both drives at the same time? Or is this a rebuild one and then the other? 2) Since I keep two spares, would it make more sense to swap in the spares for the rebuilds? I'm assuming I could mount the existing drives via Unassigned Devices or in another server and still get to the data. They could become my spares after rebuild. 3) I am in the unfortunate spot of having drain tile work in my basement starting Friday morning. I don't know that I can pull of a 14TB rebuild in that amount of time. Am I better shutting the server down until the work finishes? Or can I stop/resume a rebuild? Thanks again, guys.

@trurl I didn't think it relevant as the cause is known because the drives were severed from their SATA connections. I'll attach both diagnostics. One prior to taking the server down to reinsert the drives, and the other as it is now. I'm trying to figure out the proper procedure to get the array back online. The long S.M.A.R.T. tests are about 40% through at this point. As I said, I expect the drives will come back fine. Thanks! spock-diagnostics-20260421-0146.zip spock-diagnostics-20260421-2248.zip

Hey all, So far it hasn't happened again which makes sense since I asked for helped. Gremlins. However, I did encounter a new problem unrelated to this over at: https://forums.unraid.net/topic/198385-two-disks-disabled-need-clarification-on-proper-procedure-to-get-them-back-online/ if anyone has any helpful advice, it is much appreciate. Once I correct that issue, I'll be monitor this one to see if it pops up again. Thanks.

Hi all, So, briefly, I had people doing work in by basement and someone slid a table over which hit the latches on two Supermicro sleds causing the drives to slide forward enough to break their connection. Unraid 7.2.4, Supermicro 846, BPN-SAS2-846EL1, dual parity- Last night I noticed two drives with grey balls and would not spin up. Log showed the following: Syslog Once I discovered the physical issue, I shut the server down and reinserted the disks. Once coming back online the disks are disabled and being emulated. I am currently running long S.M.A.R.T. test on both drives, but I expect them to be fine. There should not have been any write options during when it happened and my discovery of the physical cause this morning. I immediately disabled Mover when I noticed the situation. However, I cannot be 100% certain. What is the proper procedure here to get the drives back online into the array? Do I stop and start the array again? Or do I unassign those drives first, start/stop, and then reassign? Will a data rebuild be necessary? I've never encountered this situation before. Any help is appreciated. Thanks for reading.

@Veah Yeah. I'm still waiting on that small switch I ordered to isolate the devices from the rest of my network.

@JorgeB That was my thought, too. I was just surprised seeing a hiccup at two different end points. Even if it was a drop at the network level, Unraid would throw something in the syslog, yeah?

@JorgeB Thanks for the response. I'll try and do that next time it happens. I have looked in the system log and couldn't find anything. Are there other places I could poke around and try to diagnose?

Hey everyone! So, I was running on standby generator power the other night and (probably coincidentally) I started having videos (Kodi connected to Unraid) just stop playing and go black. Since then it has been happening at some point while watching videos almost 100% of the time with no pattern I can detect. I was assuming it was an issue with my Kodi box, and I've been mostly trying to analyze that. However, I noticed today when sitting at my Mac that a few shares I had mounted just dropped randomly and then reappeared. It then happened again when I was moving some files around. This made me think the problem could actually be my media server and not my Kodi box. I'm trying to figure out the best starting point to see if my server is the issue. I don't think it's anything between Unraid and the Kodi box as I don't have any issues when using my AppleTV for Netflix, etc. Unless it's a specific port on the switch having issues. I do have a small switch I needed anyway on order so I can isolate the network between those two when that shows up. Obviously this is super annoying when trying to watch stuff. Any help appreciated. Thanks!

+1

Thanks! Appreciate it.

Hey all, I was just putting two drives into service and noticed the vendor mistakenly sent me SED models. These are WD WUH721414ALE601. They should have been WUH721414ALE604. Does anyone know if I could run into any issues with these in the array down the line? I've never used self-encrypting drives before. I was searching and didn't come across much info. All I could find is what is in this thread: https://forums.unraid.net/topic/106487-solved-cannot-add-disks-to-array That primarily covered a problem initially adding the drives to the array. I'm preclearing and just noticed the model number discrepancy. Thanks!

Again, appreciated. I'm hoping last question: Is there a best practice for migrating data from one server to another? Preferably with some sort of verification? Should I be using rsync? Should I replicate shares on the test server and mount them via Unassigned Devices doing a share to share dump over SMB? I had originally intended to just direct connect the 2 servers via 10GbE. However, I could pull disks in batches from the main server and mount them in the test server and copy over SATA. I don't have a chassis big enough to hold all the disks at once.