JPilla415

I was trying to play it as safe as possible, keep the array in the exact same state, so that I could always load back in my old data disk and USB config in case I had a disk failure during the re-build. Things seem fine now, as soon as I started the array in normal mode the rebuild fired off on its own. I guess if you're in Maintenance Mode, the data rebuild doesn't start automatically, as per the wiki. That paired with my missing "step 2" in the wiki, had me concerned.

Ah, well, that's a great reason to upgrade then. As soon as I can get this current array stable and safe, I'll upgrade. Thanks for the heads up.

Thanks again for the help. FYI, in case it matters. I started in Maintenance Mode. EDIT:

This version has been super stable and I just never got around to updating... I kinda figured, why mess with a good thing? No other reason beyond that. Yes, WDC WD80EFAX-68KNBN0 is the drive I was trying to rebuild to.

To clarify, I didn't unassign the original disk 3 before powering down the system. I started the system with the disk removed and the new 8TB in it's place. Assigned the new drive, and then started the array. Based on my reading of this wiki (https://wiki.unraid.net/Replacing_a_Data_Drive), I missed step 2. I also did not have to check the "Yes, I'm sure checkbox" before starting the array.

Thanks so much for weighing in and helping out. I definitely did not create a new config. I am trying to replace Disk 3. When I first powered on the system after replacing Disk 3, I saw a warning that Disk 3 was missing (4TB drive). I then assigned my new drive (8TB) as the new Disk 3. I clicked the "Start" button, which indicated that it would bring the array online and start a parity check and/or rebuild. The array came online, and I waited ~20 mins but the rebuild never started, so I stopped the array.

After searching around, it seems that I could revert to a backed up USB drive and put the OLD disk back in place and then start the whole process over. That seems like quite a bit of effort. Could I just manually start a parity check - would that rebuild the drive?

Diagnostics attached. I had an older drive that I wanted to replace with a larger drive and I am worried that I did things slightly out of order. Before starting, I backed up my usb drive. 1) I stopped the array. 2) Powered down 3) Replaced the hard drive 4) Turned on the system 5) Assigned the new drive in the slot of the old drive 6) Started the array The rebuild process never started and the disk contents were being shown as emulated. So, I stopped and powered down the array. I booted back up the array to take diagnostics, but have taken no further steps. What is the best course of action? I was running a bit on auto-pilot and followed the old instructions for v4: https://wiki.unraid.net/Replacing_a_Data_Drive tower-diagnostics-20200514-1611.zip

I don't mind at all. Again, I appreciate it.

Things are looking good on this end. I replaced the SATA card last night and things looked stable. Ran a parity check, which resulted in no errors. I used the same cables as before to test them out. I'm guess that either the card was starting to fail or it got partially unseated in the last hardware upgrade. Thanks very to johnnie.black for weighing in and the guidance! I really appreciate it.

Thanks so much. I appreciate the feedback. I had replaced and re-seated the cables back in early April and I thought that had fixed the issue. Clearly not. Given that I have a replacement SATA card on hand (https://www.amazon.com/gp/product/B07ST9CPND/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1), are there any things I should be aware of when swapping out the card? I just did a parity check (all good), I backed up my flash drive, and took a screenshot of my drive assignments. Anything else that I would need to be aware of? Will this hardware change trigger a parity check? Thanks again!

Thanks for the help. Sorry! I should have attached from the start. Last night I ran a parity check, but left "write corrections to parity" un-checked and no errors were reported. tower-diagnostics-20200427-0710.zip

Hello! I was hoping to get a little advice from the community. I've been using a Sata expansion card for years now without issue and in the last month I have started seeing warnings and errors like: Apr 26 15:36:01 Tower kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Apr 26 15:36:01 Tower kernel: ata10.00: failed command: SMART Apr 26 15:36:01 Tower kernel: ata10.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 15 pio 512 in Apr 26 15:36:01 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 26 15:36:01 Tower kernel: ata10.00: status: { DRDY } Apr 26 15:36:01 Tower kernel: ata10: hard resetting link I should note that the errors started popping up after installing a new drive, so it is possible I un-seated the card or cables. I have a new card ready to install, but here is where I need the feedback: My last parity check was 25 days ago. My gut tells me to run a parity check before doing any sort of hardware upgrade. I am just nervous that I might introduce more problems by doing a parity check with an unreliable expansion card. Anyone have thoughts on what I should do? Is my best bet to do a check, but not write corrections to parity? Skip the check altogether? Thanks in advance for the help! It's been about 8 years with no issue, so this is new for me