Jump to content
jbuszkie

Preclear.sh results - Questions about your results? Post them here.

2840 posts in this topic Last Reply

Recommended Posts

The full SMART report would show more; but there's enough info in what you posted to say that the drive is clearly bad and should be tossed.

 

The very large # of pending sectors indicates that there are a lot of "uncertain" sectors that aren't reliably writable.  The fact this number changed so much indicates that when zeroes were written to them, the writes were successful; but then 9 of these had read issues in the post-read so you had 9 pendings at the end of the pre-clear.

 

You've only got one re-allocated sector; but with the large number of "flaky" sectors that are being marked as pending, and then cleared on the next write; and then sometimes being re-marked, etc. the drive clearly is NOT reliable.

 

In addition, it's got a "Failing Now" parameter => if you have ANY SMART parameters marked with this you should trash the drive.

 

In other words ... Toss it  :)

Share this post


Link to post

As or more concerning, the multizone error rate has an extremely low normalized value of 1. Anything below 51 is considered failed. While you might use this drive as a "better than nothing" backup drive, I would not use it to store primary data.

 

This drive is also quite old. The power on hours normalized value is 10. It has clearly provided you with valuable service for a long time. But it is time to let it retire to Florida!  :)

Share this post


Link to post

Thank you, I picked this old drive that I had remove because I suspected it was flaky so I could see what negative result look like.

 

Planning on replacing all my drives with some new HGST 3tb NAS drives soon.

 

thanks!

 

 

Share this post


Link to post

Older WD 2TB popped a single pending sector. Replaced the drive, precleared it three times and ran a long self test, still have 1 pending sector.

 

Thoughts?

smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.7-unRAID] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green (AF)
Device Model:     WDC WD20EARS-00J2GB0
Serial Number:    WD-WCAYY0240773
LU WWN Device Id: 5 0014ee 25a299d4d
Firmware Version: 80.00A80
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Sun Nov  1 22:27:25 2015 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82)	Offline data collection activity
				was completed without error.
				Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
				without error or no self-test has ever 
				been run.
Total time to complete Offline 
data collection: 		(40260) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
				Auto Offline data collection on/off support.
				Suspend Offline collection upon new
				command.
				Offline surface scan supported.
				Self-test supported.
				Conveyance Self-test supported.
				Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
				power-saving mode.
				Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
				General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 459) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x3031)	SCT Status supported.
				SCT Feature Control supported.
				SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   167   162   021    Pre-fail  Always       -       8641
  4 Start_Stop_Count        0x0032   093   093   000    Old_age   Always       -       7534
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   039   039   000    Old_age   Always       -       45254
10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       129
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       60
193 Load_Cycle_Count        0x0032   055   055   000    Old_age   Always       -       437832
194 Temperature_Celsius     0x0022   120   110   000    Old_age   Always       -       32
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     45254         -
# 2  Extended offline    Completed without error       00%     45253         -
# 3  Extended offline    Aborted by host               80%     45176         -

SMART Selective self-test log data structure revision number 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Share this post


Link to post

Drive seems to be stuck on same reading whilst running pre clear.  I am currently Pre Clearing 8 4tb Reds.

 

The 8th drive seems to have been showing this for about the last 4 hours without moving.

 

"================================================================== 1.15b

=                unRAID server Pre-Clear disk /dev/sdp

=              cycle 1 of 1, partition start on sector 1

= Disk Pre-Clear-Read completed                                DONE

= Step 1 of 10 - Copying zeros to first 2048k bytes            DONE

= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE

= Step 3 of 10 - Disk is now cleared from MBR onward.          DONE

= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4      DONE

= Step 5 of 10 - Clearing MBR code area                        DONE

= Step 6 of 10 - Setting MBR signature bytes                    DONE

= Step 7 of 10 - Setting partition 1 to precleared state        DONE

= Step 8 of 10 - Notifying kernel we changed the partitioning  DONE

= Step 9 of 10 - Creating the /dev/disk/by* entries            DONE

= Step 10 of 10 - Verifying if the MBR is cleared.              DONE

= Post-Read in progress: 0% complete.

(  30,613,708,800  of  4,000,787,030,016  bytes read ) 126 MB/s

Disk Temperature: 29C, Elapsed Time:  22:21:31"

 

It has been stuck on 30,613,708,800 for hours with an occasional flickering drive light - where as the others are flashing away non stop.

 

Anyone else had this?  Should I just leave the others finish then try it again?

 

 

Or has the preclear done its job and killed an iffy drive before I used it :-)

 

Cheers

 

Stuart

Share this post


Link to post

Interesting it has started again but way behind the others - wonder what we shall see at the end!

 

================================================================== 1.15b

=                unRAID server Pre-Clear disk /dev/sdp

=              cycle 1 of 1, partition start on sector 1

= Disk Pre-Clear-Read completed                                DONE

= Step 1 of 10 - Copying zeros to first 2048k bytes            DONE

= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE

= Step 3 of 10 - Disk is now cleared from MBR onward.          DONE

= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4      DONE

= Step 5 of 10 - Clearing MBR code area                        DONE

= Step 6 of 10 - Setting MBR signature bytes                    DONE

= Step 7 of 10 - Setting partition 1 to precleared state        DONE

= Step 8 of 10 - Notifying kernel we changed the partitioning  DONE

= Step 9 of 10 - Creating the /dev/disk/by* entries            DONE

= Step 10 of 10 - Verifying if the MBR is cleared.              DONE

= Post-Read in progress: 3% complete.

(  140,462,899,200  of  4,000,787,030,016  bytes read ) 127 MB/s

Disk Temperature: 31C, Elapsed Time:  24:45:09

Share this post


Link to post

How can I tell - seems to be working ok?

Mostly about RAM. You seem to have plenty according to your sig, but I don't think I have heard of anyone else doing that many at once. Maybe it was stuck waiting for memory.

Share this post


Link to post

Thanks :-)

 

Memory usage seems to be hovering around 10% on the dashboard page and in the Dynamix Stats section this ...

Untitled-2.jpg.14168f781c46b463c82264c1be344e3a.jpg

Share this post


Link to post

Thanks :-)

 

Memory usage seems to be hovering around 10% on the dashboard page and in the Dynamix Stats section this ...

I think it is maybe the cache space that's in play, buffering I/O. Not entirely sure. I know back when I was running with less RAM on 32bit unRAID it would run out of RAM preclearing large drives unless I set some options to make it do smaller chunks. See here.

 

Not sure this can even be an issue on 64bit unRAID, especially with 32GB RAM.

Share this post


Link to post

I'm assuming these pre-clear results are bad, but I figured I'd check here anyway. As soon as I finished pre-clearing this drive, I tried to add it to the array, and it wouldn't let me. The drive failed, and now it's showing as a completely different model & serial number.

 

This was a replacement drive I got when I RMA'd a broken Seagate Baracuda Green 2TB. I thought I had previously pre-cleared this drive back when I received the replacement, but maybe I hadn't. Either way, I wanted to add it to the array, but it looks like that's not going to happen. It's now out of warranty, so I guess maybe it's just trash.

 

Before I did the pre-clear, it showed as model #: ST2000DL003-9VT166 & serial #: 5YD5WFVG. Now it shows up as a 4GB drive with model #: ST_M13FQBL & serial #: QNR_BFW. The weird thing is, I pulled the drive out of my Unraid case, plugged it into my Windows 7 machine, and Windows recognized it as the correct model & serial #. I ran SeaTools, and it passed the short test, but failed the long test. I then ran a "Fix All Fast", and it passed. So now I'm waiting for the results of a "Long Generic" test with SeaTools.

 

Any info regarding the preclear results would be greatly appreciated. Maybe SeaTools can fix it? I'm not very confident though.

preclear_finish_5YD5WFVG_2015-10-19.txt

Share this post


Link to post

I'm assuming these pre-clear results are bad, but I figured I'd check here anyway. As soon as I finished pre-clearing this drive, I tried to add it to the array, and it wouldn't let me. The drive failed, and now it's showing as a completely different model & serial number.

 

This was a replacement drive I got when I RMA'd a broken Seagate Baracuda Green 2TB. I thought I had previously pre-cleared this drive back when I received the replacement, but maybe I hadn't. Either way, I wanted to add it to the array, but it looks like that's not going to happen. It's now out of warranty, so I guess maybe it's just trash.

 

Before I did the pre-clear, it showed as model #: ST2000DL003-9VT166 & serial #: 5YD5WFVG. Now it shows up as a 4GB drive with model #: ST_M13FQBL & serial #: QNR_BFW. The weird thing is, I pulled the drive out of my Unraid case, plugged it into my Windows 7 machine, and Windows recognized it as the correct model & serial #. I ran SeaTools, and it passed the short test, but failed the long test. I then ran a "Fix All Fast", and it passed. So now I'm waiting for the results of a "Long Generic" test with SeaTools.

 

Any info regarding the preclear results would be greatly appreciated. Maybe SeaTools can fix it? I'm not very confident though.

 

The drive claims to be usable, but I wouldn't trust it, with over 35000 remapped sectors and other indications of a serious malfunction in the past.  A significant part of the drive has failed, but it's trying to work around it.  The only thing I would use it for is as a third or fourth backup, or for unimportant things you don't care about losing, but not part of an unRAID array.

 

It's not possible (outside of the factory) for a drive to change model and serial.  I suspect you used the same drive symbol (sde), but that can change between boots.  Either you have a 4TB drive elsewhere in your server, or the smartctl command returned garbage.

Share this post


Link to post

The drive claims to be usable, but I wouldn't trust it, with over 35000 remapped sectors and other indications of a serious malfunction in the past.  A significant part of the drive has failed, but it's trying to work around it.  The only thing I would use it for is as a third or fourth backup, or for unimportant things you don't care about losing, but not part of an unRAID array.

 

It's not possible (outside of the factory) for a drive to change model and serial.  I suspect you used the same drive symbol (sde), but that can change between boots.  Either you have a 4TB drive elsewhere in your server, or the smartctl command returned garbage.

 

Thanks for the response Rob. The changing of model & serial number is not too uncommon for failing Seagate drives. "ST_M13FQBL" comes up on a web search with similar symptoms as the drive in question. It's a 2TB drive that is now showing as 4GB in Unraid. The weird thing is, it passed the SeaTools long test when plugged into my Windows PC, and actually showed as a 2TB drive with the correct model & serial number. Then a few hours later, it isn't recognized by SeaTools at all, and now shows up in Windows Disk Management as 3.86GB unallocated with the ST_M13FQBL again.

 

Oh well, like you said, I don't trust the drive. It's not cool how Seagate will send out a replacement drive that is no good, and the warranty expires because it's not renewed when they send out the new drive.

 

Thanks again for confirming my suspicion about the bad preclear results.

Share this post


Link to post

Thanks for the response Rob. The changing of model & serial number is not too uncommon for failing Seagate drives. "ST_M13FQBL" comes up on a web search with similar symptoms as the drive in question. It's a 2TB drive that is now showing as 4GB in Unraid. The weird thing is, it passed the SeaTools long test when plugged into my Windows PC, and actually showed as a 2TB drive with the correct model & serial number. Then a few hours later, it isn't recognized by SeaTools at all, and now shows up in Windows Disk Management as 3.86GB unallocated with the ST_M13FQBL again.

 

Thank you for that info, it's the first I had heard of it.

Share this post


Link to post

I've just pre-cleared my 4TB WD red and this was the results:

 

================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdc
=               cycle 1 of 1, partition start on sector 1
= Disk Pre-Clear-Read completed                                 DONE
= Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
= Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
= Step 5 of 10 - Clearing MBR code area                         DONE
= Step 6 of 10 - Setting MBR signature bytes                    DONE
= Step 7 of 10 - Setting partition 1 to precleared state        DONE
= Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
= Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
= Step 10 of 10 - Verifying if the MBR is cleared.              DONE
= Disk Post-Clear-Read completed                                DONE
Disk Temperature: 34C, Elapsed Time:  60:57:54
========================================================================1.15
== WDCWD40EFRX-68WT0N0   WD-WCC4E2YR7DEH
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 1
============================================================================
** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   118     116            0        ok          34
No SMART attributes are FAILING_NOW

1 sector was pending re-allocation before the start of the preclear.
1 sector was pending re-allocation after pre-read in cycle 1 of 1.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
0 sectors are pending re-allocation at the end of the preclear, a change of -1 in the number of sectors pending re-allocation.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change.

 

I'm a complete noob so any input would be greatly appreciated.

Share this post


Link to post

I've just pre-cleared my 4TB WD red and this was the results:

 

================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdc
=               cycle 1 of 1, partition start on sector 1
= Disk Pre-Clear-Read completed                                 DONE
= Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
= Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
= Step 5 of 10 - Clearing MBR code area                         DONE
= Step 6 of 10 - Setting MBR signature bytes                    DONE
= Step 7 of 10 - Setting partition 1 to precleared state        DONE
= Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
= Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
= Step 10 of 10 - Verifying if the MBR is cleared.              DONE
= Disk Post-Clear-Read completed                                DONE
Disk Temperature: 34C, Elapsed Time:  60:57:54
========================================================================1.15
== WDCWD40EFRX-68WT0N0   WD-WCC4E2YR7DEH
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 1
============================================================================
** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   118     116            0        ok          34
No SMART attributes are FAILING_NOW

1 sector was pending re-allocation before the start of the preclear.
1 sector was pending re-allocation after pre-read in cycle 1 of 1.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
0 sectors are pending re-allocation at the end of the preclear, a change of -1 in the number of sectors pending re-allocation.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change.

 

I'm a complete noob so any input would be greatly appreciated.

Looks OK but I would probably do another preclear cycle. I like to see all zeros on mine.

Share this post


Link to post

Just did a faster preclear on 2 new seagate nas drives, and am a bit concerned about the results

 

dashboard has the command timeout on both flagged orange

 

also that raw read error rate?

 

1	Raw read error rate	0x000f	111	099	006	Pre-fail	Always	-	30706296
3	Spin up time	0x0003	100	100	000	Pre-fail	Always	-	0
4	Start stop count	0x0032	100	100	020	Old age	Always	-	1
5	Reallocated sector count	0x0033	100	100	010	Pre-fail	Always	-	0
7	Seek error rate	0x000f	100	253	030	Pre-fail	Always	-	428525
9	Power on hours	0x0032	100	100	000	Old age	Always	-	23 (23h)
10	Spin retry count	0x0013	100	100	097	Pre-fail	Always	-	0
12	Power cycle count	0x0032	100	100	020	Old age	Always	-	1
184	End-to-end error	0x0032	100	100	099	Old age	Always	-	0
187	Reported uncorrect	0x0032	100	100	000	Old age	Always	-	0
188	Command timeout	0x0032	100	097	000	Old age	Always	-	19
189	High fly writes	0x003a	093	093	000	Old age	Always	-	7
190	Airflow temperature cel	0x0022	064	060	045	Old age	Always	-	36 (min/max 28/40)
191	G-sense error rate	0x0032	100	100	000	Old age	Always	-	0
192	Power-off retract count	0x0032	100	100	000	Old age	Always	-	1
193	Load cycle count	0x0032	100	100	000	Old age	Always	-	1
194	Temperature celsius	0x0022	036	040	000	Old age	Always	-	36 (0 28 0 0 0)
197	Current pending sector	0x0012	100	100	000	Old age	Always	-	0
198	Offline uncorrectable	0x0010	100	100	000	Old age	Offline	-	0
199	UDMA CRC error count	0x003e	200	200	000	Old age	Always	-	0

 

1	Raw read error rate	0x000f	110	099	006	Pre-fail	Always	-	25325128
3	Spin up time	0x0003	100	100	000	Pre-fail	Always	-	0
4	Start stop count	0x0032	100	100	020	Old age	Always	-	1
5	Reallocated sector count	0x0033	100	100	010	Pre-fail	Always	-	0
7	Seek error rate	0x000f	100	253	030	Pre-fail	Always	-	431118
9	Power on hours	0x0032	100	100	000	Old age	Always	-	23 (23h)
10	Spin retry count	0x0013	100	100	097	Pre-fail	Always	-	0
12	Power cycle count	0x0032	100	100	020	Old age	Always	-	1
184	End-to-end error	0x0032	100	100	099	Old age	Always	-	0
187	Reported uncorrect	0x0032	100	100	000	Old age	Always	-	0
188	Command timeout	0x0032	100	095	000	Old age	Always	-	37
189	High fly writes	0x003a	096	096	000	Old age	Always	-	4
190	Airflow temperature cel	0x0022	064	060	045	Old age	Always	-	36 (min/max 28/40)
191	G-sense error rate	0x0032	100	100	000	Old age	Always	-	0
192	Power-off retract count	0x0032	100	100	000	Old age	Always	-	0
193	Load cycle count	0x0032	100	100	000	Old age	Always	-	1
194	Temperature celsius	0x0022	036	040	000	Old age	Always	-	36 (0 28 0 0 0)
197	Current pending sector	0x0012	100	100	000	Old age	Always	-	0
198	Offline uncorrectable	0x0010	100	100	000	Old age	Offline	-	0
199	UDMA CRC error count	0x003e	200	200	000	Old age	Always	-	0

ST3000VN000-1HJ166_W6A0HLZN-20151127-2142.txt

ST3000VN000-1HJ166_W6A0J0NX-20151127-2142.txt

Share this post


Link to post

I started 3 preclear in screen last night on 3 new 4TB Seagate NAS drive.

Two of them just stopped and spin down without errors after 8 hours.

 

preclear.jpg

 

Is there a way to spin up the drives so it can continue?

Share this post


Link to post

I started 3 preclear in screen last night on 3 new 4TB Seagate NAS drive.

Two of them just stopped and spin down without errors after 8 hours.

 

preclear.jpg

 

Is there a way to spin up the drives so it can continue?

Since you say you are using screen and not the preclear plugin, what does it look like in your screen sessions?

Share this post


Link to post

I started 3 preclear in screen last night on 3 new 4TB Seagate NAS drive.

Two of them just stopped and spin down without errors after 8 hours.

 

Is there a way to spin up the drives so it can continue?

Since you say you are using screen and not the preclear plugin, what does it look like in your screen sessions?

 

It's just frozen.

 

2015_11_27_08_02_45_192_168_1_112_Pu_TTY.png

 

I looked more into it and it may be related to hardware. It is a new build and those two disk are the first I plug into my AOC-SAS2LP-MV8 card. The other disk are plugged directly on the motherboard (Supermicro X10SL7-FO). I also have 4 Norco SS-500 5-bay and those are the only disk in the 3rd SS-500. It may be a problem with the SAS card or the SS-500. I will do more test.

Share this post


Link to post

Just did a faster preclear on 2 new seagate nas drives, and am a bit concerned about the results

 

dashboard has the command timeout on both flagged orange

 

also that raw read error rate?

Both drives look great, ignore the Command Timeouts, the Raw read error rates are better than good, 111 and 110 (initial perfect value is 100).

Share this post


Link to post

 

Both drives look great, ignore the Command Timeouts, the Raw read error rates are better than good, 111 and 110 (initial perfect value is 100).

 

Ok then thanks, after googling saw it was about bad sata or power cables, so i actually moved the drive to another cage so on different cables/card, ran another test, and it went up more, to 32 and 67.

Guess I'll just try to ignore the orange warning in dashboard :). really didn't want to get the seagates, wanted more reds, but they were $25 cheaper each. so yea, but won't be getting more in the future though

Share this post


Link to post

I've just pre-cleared my 4TB WD red and this was the results:

 

================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdc
=               cycle 1 of 1, partition start on sector 1
= Disk Pre-Clear-Read completed                                 DONE
= Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
= Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
= Step 5 of 10 - Clearing MBR code area                         DONE
= Step 6 of 10 - Setting MBR signature bytes                    DONE
= Step 7 of 10 - Setting partition 1 to precleared state        DONE
= Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
= Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
= Step 10 of 10 - Verifying if the MBR is cleared.              DONE
= Disk Post-Clear-Read completed                                DONE
Disk Temperature: 34C, Elapsed Time:  60:57:54
========================================================================1.15
== WDCWD40EFRX-68WT0N0   WD-WCC4E2YR7DEH
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 1
============================================================================
** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   118     116            0        ok          34
No SMART attributes are FAILING_NOW

1 sector was pending re-allocation before the start of the preclear.
1 sector was pending re-allocation after pre-read in cycle 1 of 1.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
0 sectors are pending re-allocation at the end of the preclear, a change of -1 in the number of sectors pending re-allocation.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change.

 

I'm a complete noob so any input would be greatly appreciated.

Looks OK but I would probably do another preclear cycle. I like to see all zeros on mine.

 

I just finished pre-clearing for the second time. Here are the results, all zeroes :):

 

================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdc
=               cycle 1 of 1, partition start on sector 1
= Disk Pre-Clear-Read completed                                 DONE
= Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
= Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
= Step 5 of 10 - Clearing MBR code area                         DONE
= Step 6 of 10 - Setting MBR signature bytes                    DONE
= Step 7 of 10 - Setting partition 1 to precleared state        DONE
= Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
= Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
= Step 10 of 10 - Verifying if the MBR is cleared.              DONE
= Disk Post-Clear-Read completed                                DONE
Disk Temperature: 40C, Elapsed Time:  61:53:15
========================================================================1.15
== WDCWD40EFRX-68WT0N0   WD-WCC4E2YR7DEH
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 1
============================================================================
** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
             Spin_Up_Time =   226     184           21        ok          5700
           Power_On_Hours =    97      98            0        ok          2209
      Temperature_Celsius =   112     119            0        ok          40
No SMART attributes are FAILING_NOW
0 sectors were pending re-allocation before the start of the preclear.
0 sectors were pending re-allocation after pre-read in cycle 1 of 1.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
0 sectors are pending re-allocation at the end of the preclear,
    the number of sectors pending re-allocation did not change.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.

 

Thanks for your help!

Share this post


Link to post

I am about to pre-clear my new 4TB HGST for my parity. All of my  2TB drives have been pre-cleared with 4k-aligned.  Should I do 4k-aligned with my new 4TB drive?  :) Thank you.

Share this post


Link to post

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.