manny

User Customizations · April 29, 2015

Thanks RobJ, yes during the second pre clear which reported these errors I did have a power outage, though the server is connected to a UPS, for a second or two I felt the power went off. Basically when the power cut happens (which is often) the generator kicks in 2-3 mins, during this time I have UPS to supply power. Also we are having thunderstorms lately ...

User Customizations · April 29, 2015

I just completed the second preclear cycle and have Current_Pending_Sector = 2 and Raw_Read_Error_Rate=8, as per the explanation from RobJ above i think this should be ok right? I am planning to replace this drive as the Parity drive. Should I run one more cycle just to be on the safe side?

The "Raw_Read_Error_Rate=8" is not a problem, because the raw value for that attribute is meaningless. What's important is the VALUE for it, 200, which is perfect.

What IS a problem is the "Current_Pending_Sector = 2". As was stated above, that HAS to be zero. If this SMART report occurred right after a Preclear then that is a bad sign. Preclear it again, and if Current_Pending_Sector stays non-zero, I would not use that drive, it can't be trusted.

Just completed the 3rd round of preclear, Current_Pending_Sector has become zero :-) Shall iI go ahead and use this drive?


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       -       8
  3 Spin_Up_Time            0x0027   100   253   021    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       1
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       100
10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       7
194 Temperature_Celsius     0x0022   119   118   000    Old_age   Always       -       31
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


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.

This was the final output from preclear

================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdf
=               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: 31C, Elapsed Time:  32:43:31
========================================================================1.15
== WDCWD30EFRX-68EUZN0   
== Disk /dev/sdf has been successfully precleared
== with a starting sector of 1
============================================================================
** Changed attributes in files: /tmp/smart_start_sdf  /tmp/smart_finish_sdf
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   119     120            0        ok          31
No SMART attributes are FAILING_NOW

2 sectors were pending re-allocation before the start of the preclear.
2 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,
    a change of -2 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.

User Customizations · April 28, 2015

Thanks, started one more cycle now.

User Customizations · April 28, 2015

I just completed the second preclear cycle and have Current_Pending_Sector = 2 and Raw_Read_Error_Rate=8, as per the explanation from RobJ above i think this should be ok right? I am planning to replace this drive as the Parity drive. Should I run one more cycle just to be on the safe side?

Disk: /dev/sdf
smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red (AF)
Device Model:     WDC WD30EFRX-68EUZN0
LU WWN Device Id: 5 0014ee 6b002b183
Firmware Version: 82.00A82
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Tue Apr 28 08:28:42 2015 IST
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:  (0x00)	Offline data collection activity
				was never started.
				Auto Offline Data Collection: Disabled.
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: 		(41760) 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: 	 ( 418) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x703d)	SCT Status supported.
				SCT Error Recovery Control 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       -       8
  3 Spin_Up_Time            0x0027   100   253   021    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       1
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       66
10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       4
194 Temperature_Celsius     0x0022   120   119   000    Old_age   Always       -       30
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       2
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


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.

User Customizations · April 27, 2015

Thanks RobJ, I have started another pass.

User Customizations · April 26, 2015

Hi All, I am trying to add a 3TB WD Red Drive to my array and the first preclear run just got completed, can someone check and let me know if this is fine? also how many preclear cycle should I run, 20 cycles might take lot of time:-) what would be the minimum safe number of runs?

I got this one line in the final summary, is this a issue? : 1 sector was pending re-allocation after pre-read in cycle 1 of 1.

I started the preclear with this command : preclear_disk.sh -A -M 4 /dev/sdf

Summary.txt

preclear_finish_2015-04-26.txt

User Customizations · February 18, 2014

This problem is resolved, for some reason Simple Feature was giving some issues. I uninstalled it and now I am able to add the disk to the array. Please check the preclear report and let me know if everything is fine. Also i upgraded to 5.0.5 and Dynamix...

User Customizations · February 18, 2014

Hi, I just added my 4th drive to the array and completed the 3rd round of preclear, can you please let me know if everything is fine with this disk? I am attaching the preclear finish report. Also having a one more issue, this disk is not showing in the device list and hence not able to add to the array....I had the trail version and recently purchased the plus revision...These are the few reference i see in syslog for the new HDD (SDD)

Feb 18 08:35:47 Manitower kernel: scsi 4:0:0:0: Direct-Access     ATA      WDC WD20EFRX-68E 80.0 PQ: 0 ANSI: 5 (Drive related)
Feb 18 08:35:47 Manitower kernel: sd 4:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) (Drive related)
Feb 18 08:35:47 Manitower kernel: sd 4:0:0:0: [sdd] 4096-byte physical blocks (Drive related)
Feb 18 08:35:47 Manitower kernel: sd 4:0:0:0: [sdd] Write Protect is off (Drive related)
Feb 18 08:35:47 Manitower kernel: sd 4:0:0:0: [sdd] Mode Sense: 00 3a 00 00 (Drive related)
Feb 18 08:35:47 Manitower kernel: sd 4:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related)
Feb 18 08:35:47 Manitower kernel:  sdd: sdd1 (Drive related)
Feb 18 08:35:47 Manitower kernel:  sdc: sdc1 (Drive related)
Feb 18 08:35:47 Manitower kernel: sd 2:0:0:0: [sdc] Attached SCSI disk (Drive related)
Feb 18 08:35:47 Manitower kernel: sd 4:0:0:0: [sdd] Attached SCSI disk (Drive related)

[EDIT] Attaching the syslog

preclear_finish_WD-WCC4M1568296_2014-02-18.txt

syslog-2014-02-18.zip

User Customizations · January 26, 2014

Thanks Joe, looks like it has some bunch of bad blocks (0.6%), should i continue to use this drive or RMA it?

User Customizations · January 26, 2014

Thanks a lot RobJ, this is very informative, thank you for taking time to write such a detailed explanation. Meanwhile I took HDD out of the array and dropped it in my windows 7 PC and ran HD tune. Not sure if this is a good idea but as you predicated it showed bunch of bad sectors at the very beginning. It has around 0.6% of damaged blocks as per HD tune. Should I go ahead and RMA the drive or run zero pass preclear?.....

User Customizations · January 26, 2014

Thanks for the reply RobJ, I am attaching the report again, can you please check and let me know if I have RMA the drive. Can you also please how you came this conculsion, I have been reading the the SMART report but still not able to understand it.

root@Manitower:~# smartctl -a /dev/sdd
smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD20EFRX-68AX9N0
Serial Number:    WD-WCC300664700
Firmware Version: 80.00A80
User Capacity:    2,000,398,934,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   9
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Sun Jan 26 12:13:44 2014 IST
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:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
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:                 (27540) 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:        ( 255) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x70bd) SCT Status supported.
                                        SCT Error Recovery Control 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   155   081   051    Pre-fail  Always       -       1164
  3 Spin_Up_Time            0x0027   100   253   021    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       5
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       4
10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       5
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       3
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       1
194 Temperature_Celsius     0x0022   119   118   000    Old_age   Always       -       28
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       81
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


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.

User Customizations · January 25, 2014

Hi All, Having problem with my preclear please help. I already have 2 data drives and 1 parity in my unRaid Server. Just got the plus licensing today was started the preclear for my 4th drive. This is WD Red Nas drive. I got the following error when ran the first time

Jan 26 00:55:29 Manitower kernel: ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Jan 26 00:55:29 Manitower kernel: ata5.00: irq_stat 0x40000008
Jan 26 00:55:29 Manitower kernel: ata5.00: failed command: READ FPDMA QUEUED
Jan 26 00:55:29 Manitower kernel: ata5.00: cmd 60/08:00:40:c1:da/00:00:03:00:00/40 tag 0 ncq 4096 in
Jan 26 00:55:29 Manitower kernel:          res 41/40:00:40:c1:da/00:00:03:00:00/40 Emask 0x409 (media error) <F>
Jan 26 00:55:29 Manitower kernel: ata5.00: status: { DRDY ERR }
Jan 26 00:55:29 Manitower kernel: ata5.00: error: { UNC }
Jan 26 00:55:29 Manitower kernel: ata5.00: configured for UDMA/133
Jan 26 00:55:29 Manitower kernel: ata5: EH complete
Jan 26 00:55:33 Manitower kernel: ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Jan 26 00:55:33 Manitower kernel: ata5.00: irq_stat 0x40000008
Jan 26 00:55:33 Manitower kernel: ata5.00: failed command: READ FPDMA QUEUED
Jan 26 00:55:33 Manitower kernel: ata5.00: cmd 60/08:00:40:c1:da/00:00:03:00:00/40 tag 0 ncq 4096 in
Jan 26 00:55:33 Manitower kernel:          res 41/40:00:40:c1:da/00:00:03:00:00/40 Emask 0x409 (media error) <F>

Then I replaced the cable and then connected to a different SATA port and ran the preclear. Again within 1% I started getting errors, the speed reduced to 15-25 Mbs

Jan 26 01:10:00 Manitower kernel: ata5.00: irq_stat 0x40000008
Jan 26 01:10:00 Manitower kernel: ata5.00: failed command: READ FPDMA QUEUED
Jan 26 01:10:00 Manitower kernel: ata5.00: cmd 60/40:00:c0:36:a4/00:00:03:00:00/40 tag 0 ncq 32768 in
Jan 26 01:10:00 Manitower kernel:          res 41/40:00:c0:36:a4/00:00:03:00:00/40 Emask 0x409 (media error) <F>
Jan 26 01:10:00 Manitower kernel: ata5.00: status: { DRDY ERR }
Jan 26 01:10:00 Manitower kernel: ata5.00: error: { UNC }
Jan 26 01:10:00 Manitower kernel: ata5.00: configured for UDMA/133
Jan 26 01:10:00 Manitower kernel: sd 4:0:0:0: [sdd] Unhandled sense code
Jan 26 01:10:00 Manitower kernel: sd 4:0:0:0: [sdd]  Result: hostbyte=0x00 driverbyte=0x08
Jan 26 01:10:00 Manitower kernel: sd 4:0:0:0: [sdd]  Sense Key : 0x3 [current] [descriptor]
Jan 26 01:10:00 Manitower kernel: Descriptor sense data with sense descriptors (in hex):
Jan 26 01:10:00 Manitower kernel:         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
Jan 26 01:10:00 Manitower kernel:         03 a4 36 c0 
Jan 26 01:10:00 Manitower kernel: sd 4:0:0:0: [sdd]  ASC=0x11 ASCQ=0x4
Jan 26 01:10:00 Manitower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 03 a4 36 c0 00 00 40 00
Jan 26 01:10:00 Manitower kernel: end_request: I/O error, dev sdd, sector 61093568
Jan 26 01:10:00 Manitower kernel: Buffer I/O error on device sdd, logical block 7636696
Jan 26 01:10:00 Manitower kernel: Buffer I/O error on device sdd, logical block 7636697
Jan 26 01:10:00 Manitower kernel: Buffer I/O error on device sdd, logical block 7636698
Jan 26 01:10:00 Manitower kernel: Buffer I/O error on device sdd, logical block 7636699
Jan 26 01:10:00 Manitower kernel: Buffer I/O error on device sdd, logical block 7636700
Jan 26 01:10:00 Manitower kernel: Buffer I/O error on device sdd, logical block 7636701
Jan 26 01:10:00 Manitower kernel: Buffer I/O error on device sdd, logical block 7636702
Jan 26 01:10:00 Manitower kernel: Buffer I/O error on device sdd, logical block 7636703
Jan 26 01:10:00 Manitower kernel: ata5: EH complete

Can some please help me, I am a newbie in unRaid and really need some help. Last 3 drive's preclear went without any issues.

This is the command I used

preclear_disk.sh -A -M 4 /dev/sda

I am attaching the SMART report and syslog, please help !!!!

syslog.zip

SMART_Report.txt

User Customizations · December 30, 2012

Thanks , running another round of preclear on both the disks in parallel...

User Customizations · December 30, 2012

Hi , my next 2TB WD Red first preclear just got completed and the reports looks fine. Can someone please check and confirm....thanks a lot for the help....

preclear_rpt.txt

User Customizations · December 30, 2012

Thanks again, will do that. still 4 more hrs complete the first round...

User Customizations · December 30, 2012

Thanks a lot Joe, sure I will go ahead and run another round of preclear...Can you please let me know how can i fix the issue I mentioned in another post (just above urs)...

User Customizations · December 29, 2012

hi thanks for a quick reply, I think I made the mistake of adding both the drives to the array but not copied anything yet. Will this be an issue? Currently both disk1 and disk2 are red balled and showing "Missing"...

Let me explain what I did. Before preclearing the disks I add them to the array and started the array. So disk1 and disk 2 got assigned. Then i unassigned them which stopped the error stating "Too many missing drives". Now I have precleared one disk and waiting for the other one to be done so that I can assign them back to the array...

How do i fix my mistake? since you suggested 3 pre clear, I will wait for them to complete and then assign the drives? is that the the correct way? Please let me know and thanks a lot.

Also what is the impact on total time to preclear if I do both the disks at the same time? I have 8 GB memory and not many plugins, will i run into any memory issues?

User Customizations · December 29, 2012

Hi, I just started with my first unRaid server and so far its been great. This forum has been extremely helpful and spent a lot of time here !!!

My first preclear just got completed , its WD RED 2TB NAS drive. When i looked at the report it seems to be fine, can someone please check and let me know if its really fine? I have combined all three reports in a single file..

Also have couple of questions,

- How many preclear i should do ? 2 or 3?

- Is it ok to run preclear again on the precleared disk? I mean i didn't use "c" function so by default preclear was done only once

Thanks again for all your help....I really don't think i would have done anything without this forum...thanks to all...

preclear_rpt.txt

manny

Posts

Joined

Last visited

Content Type

Profiles

Forums

Downloads

Store

Gallery

Bug Reports

Documentation

Landing

Posts posted by manny

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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