New drive help


swells

Recommended Posts

Ok, I need some help.

 

I picked up a new 8TB Seagate drive to serve two purposes. I have a few 2TB WD20EARS drives still in play and one of them has 1 sector pending relocation. I also am getting low on space and need to expand soon. The 8TB drive will become my new parity drive to replace a 3TB drive in use currently and the 3TB parity drive will replace this 2TB WD drive so I can retire it (it has been in use for ~5 years in this server). So that is the background.

 

The drive was finishing up a single pass of preclear on the post read phase and was about 70% complete last night. I was about to go to bed and figured I would kick off a parity check and make sure all was well before the preclear finished and I could continue on. I woke up to the preclear complete, but the 8TB disk was spun down and would not spin up. It was basically not available any longer. I checked the logs and it was full of errors. Looks like two drives had some issues, ATA12 is the 2TB WDEARS drive I would like to replace, it reconnected to the controller and is fine now from what I can tell. And ATA15 (sdn) is the 8TB Seagate and it did not and is offline. I have no idea what I should be looking at. Is there a huge problem here? Did i over stress something by running a parity check while running the preclear? If someone could please take a look at the logs you will see everything of relevance I believe. I have removed a bunch of crap that was spamming the logs, which I have also never seen before, but it was basically thousands of lines of this:

 

Feb 24 23:47:49 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

Errors.txt

Link to comment

Instead of an uncompressed and incomplete syslog, for V6 you should always go to Tools - Diagnostics and post the complete diagnostics zip file.

 

My guess is that you have an unreliable SATA or power connection on one or more drives caused when you were poking around inside. Stop, shutdown, check all connections, reboot, then post diagnostics.

Link to comment

I just ran an extended. It still passes. Has a current pending sector count of 1 and offline uncorrectable count of 1. Otherwise no errors.

 

 

 

Device Model:     WDC WD20EARS-00MVWB0
Serial Number:    WD-WMAZA4049015

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%     39715         291445898

 

SMART test failed, you have to replace this disk first.

 

8TB Seagate looks fine, maybe bad connection.

Link to comment

Ok, thanks! I guess I was just looking at the part that said passed up top. Any way for me to do this according to my original plans without purchasing another drive?

Make sure any files you don't want to lose are backed up before you mess with it more. There is a not insignificant risk of data loss if something doesn't go just right.
Link to comment

Nothing I can't afford to lose on this server. Entirely media. I would however rather be safe than sorry, so will probably try to replace that disk before I do anything else. I do however wish to continue with my move to bigger 8TB drives. Any problems with the below plan? With the last couple steps, is there a way to expand the file system once the larger parity drive is in place or do I need to remove it and put it back in like a new disk to utilize the space?

 

My current plan is something like:

1) Ensure 8TB disk is fine

2) Rebuild bad 2TB disk onto precleared 8TB disk.

3) Order another 8TB disk and preclear it.

4) Replace current 3TB disk with new 8TB disk.

5) Replace 8TB data disk previously used to replace failed 2TB disk with 3TB former parity disk.

6) Utilize full 8TB of original 8TB disk in array.

 

 

Link to comment

 

My current plan is something like:

1) Ensure 8TB disk is fine

2) Rebuild bad 2TB disk onto precleared 8TB disk.

3) Order another 8TB disk and preclear it.

4) Replace current 3TB disk with new 8TB disk.

5) Replace 8TB data disk previously used to replace failed 2TB disk with 3TB former parity disk.

6) Utilize full 8TB of original 8TB disk in array.

 

You can't do this, parity has to be same or larger size than any data disk, you can do the parity swap procedure I linked above, it will first copy your parity data to the 8tb disk, then rebuild the bad 2tb on the old parity.

Link to comment

Nothing I can't afford to lose on this server. Entirely media. I would however rather be safe than sorry, so will probably try to replace that disk before I do anything else. I do however wish to continue with my move to bigger 8TB drives. Any problems with the below plan? With the last couple steps, is there a way to expand the file system once the larger parity drive is in place or do I need to remove it and put it back in like a new disk to utilize the space?

 

My current plan is something like:

1) Ensure 8TB disk is fine

2) Rebuild bad 2TB disk onto precleared 8TB disk.

3) Order another 8TB disk and preclear it.

4) Replace current 3TB disk with new 8TB disk.

5) Replace 8TB data disk previously used to replace failed 2TB disk with 3TB former parity disk.

6) Utilize full 8TB of original 8TB disk in array.

Unraid will not allow you to use a disk that appears larger than the current parity drive as a data drive. In order for this plan to work, you would need to use a HPA to block off all but 3TB of the 8TB drive so it will appear the same size as your current parity.

 

This procedure is riskier to implement than the parity swap that johnnie.black linked IMHO.

Link to comment

Alright, i'll run with that then. Should I do a full preclear again or just a post read? Thats where it was when it disconnected from the controller last night. As far as I can tell, everything was ok with the preclear up to that point. With the plug in it looks like I can just do the post read and save a couple days, but I have no problem doing it all again if need be. Just not sure about leaving that bad disk there a while longer.

Link to comment

You can't do that and just not utilize the extra disk space? hmm, well crap.

 

No, it’s not possible, and I don’t see I you would want to do that, you can just:

 

-do the parity swap

-buy another 8tb disk and add it to the array

 

Unless I’m missing something you’ll be with the same setup as above with less steps

 

Link to comment

Alright, i'll run with that then. Should I do a full preclear again or just a post read? Thats where it was when it disconnected from the controller last night. As far as I can tell, everything was ok with the preclear up to that point. With the plug in it looks like I can just do the post read and save a couple days, but I have no problem doing it all again if need be. Just not sure about leaving that bad disk there a while longer.

 

Full precleasr would be better, but it will also leave you more time with a bad disk, that leaves you vulnerable in case of another disk failure, so in my view it’s a toss up.

Link to comment

Ok. So I ran the post read portion of the preclear and it was fine. So I trusted the new 8TB disk and wanted to replace that failed 2TB disk asap. I did the swap and everything went fine. After the swap I started a nocorrect parity check and so far, at 27% complete (2.2TB or so), there are 4201 sync errors. My first thought is to let this run and then do it again and see if it is the same. If it is, do I correct it? How should I proceed at this point?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.