crwdns2933423:0crwdne2933423:0
crwdns2918538:0crwdne2918538:0

crwdns2934243:0crwdne2934243:0 Nick

crwdns2934249:0crwdne2934249:0:

Correcting the drive under drive options->Drive->Autodetect read command now fixed the problem. No errors on the second run for Foreigner 4.
-It seems like the solution short of buying new externals every ~5 years (Black Friday 2015 purchase) is to run a autodetect command to bring the drive back into calibration. I don’t anticipate this working more then a few times when data accuracy is critical once it happens, but once it can no longer be recovered it’s time to start over with a new drive.
+It seems like the solution short of buying new externals every ~5 years as it happens (Black Friday 2015 purchase) is to run a autodetect command to bring the drive back into calibration. I don’t anticipate this working more then a few times when data accuracy is critical once it happens, but once it can no longer be recovered it’s time to start over with a new drive.

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Nick

crwdns2934249:0crwdne2934249:0:

Correcting the drive under drive options->Drive->Autodetect read command now fixed the problem. No errors on the second run for Foreigner 4.
-It seems like the solution short of buying new externals every ~5 years is to run a autodetect command to bring the drive back into calibration. I don’t anticipate this working more then a few times when data accuracy is critical once it happens, but once it can no longer be recovered it’s time to start over with a new drive.
+It seems like the solution short of buying new externals every ~5 years (Black Friday 2015 purchase) is to run a autodetect command to bring the drive back into calibration. I don’t anticipate this working more then a few times when data accuracy is critical once it happens, but once it can no longer be recovered it’s time to start over with a new drive.

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Nick

crwdns2934249:0crwdne2934249:0:

Correcting the drive under drive options->Drive->Autodetect read command now fixed the problem. No errors on the second run for Foreigner 4.
+
+It seems like the solution short of buying new externals every ~5 years is to run a autodetect command to bring the drive back into calibration. I don’t anticipate this working more then a few times when data accuracy is critical once it happens, but once it can no longer be recovered it’s time to start over with a new drive.

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Nick

crwdns2934249:0crwdne2934249:0:

-Correcting the drive under drive options->Drive->Autodetect read command now fixed the problem. No errors on the second run.
+Correcting the drive under drive options->Drive->Autodetect read command now fixed the problem. No errors on the second run for Foreigner 4.

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Nick

crwdns2934249:0crwdne2934249:0:

-Correcting the drive under drive options->Drive->Autodetect read command now fixed the problem :). No errors on the second run.
+Correcting the drive under drive options->Drive->Autodetect read command now fixed the problem. No errors on the second run.

crwdns2915684:0crwdne2915684:0:

open

crwdns2934241:0crwdne2934241:0 Nick

crwdns2934249:0crwdne2934249:0:

Correcting the drive under drive options->Drive->Autodetect read command now fixed the problem :). No errors on the second run.

crwdns2915684:0crwdne2915684:0:

open