March 21, 201214 yr Hi, I am about to replace a bad drive (lots of read errors) and plan on doing a 4.7 upgrade at the very same time. My drives a 2TD WD Greens (EARS), and are currently using the jumpers. I'm replacing with a EARX, should I use the jumper too or will I be able to take advantage of support for AF drives even though the drive it's replacing had the jumper? thanks, del
March 21, 201214 yr Hi, I am about to replace a bad drive (lots of read errors) and plan on doing a 4.7 upgrade at the very same time. My drives a 2TD WD Greens (EARS), and are currently using the jumpers. I'm replacing with a EARX, should I use the jumper too or will I be able to take advantage of support for AF drives even though the drive it's replacing had the jumper? thanks, del EARX does not use a jumper. Pre-clear new drive with -A option for sector 64 start. (or let unRAID partition the drive, and select 4k-aligned first in its options before replacing the drive)
March 21, 201214 yr Author EARX does not use a jumper. Pre-clear new drive with -A option for sector 64 start. (or let unRAID partition the drive, and select 4k-aligned first in its options before replacing the drive) Heh. I guess I read Advanced Format on it, and saw the pins and assumed it worked the same way. Thanks for the clarification. This is odd. After restarting with 4.7, I'm not getting the read errors. Is it normal for a drive to error out and then start acting like normal all of a sudden? I'll be pre-clearing the new drive anyway and hope the old drive holds on for a few more months.
March 21, 201214 yr Author Post smart report for the drive in question. The command I executed was: smartctl -a -d ata /dev/sdi >/boot/smart.txt The results are attached. And, while I don't know anything about SMART, it does say that it failed/is about to. smart.txt
Archived
This topic is now archived and is closed to further replies.