Jump to content
jbuszkie

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

2840 posts in this topic Last Reply

Recommended Posts

I just received a WD RED 3TB drive that I will use to replace my 1TB parity drive.

I ran a preclear on it twice and got the same result. But I don't know what is the issue (if it is one). Any help would be greatly appreciated.

Thanks

 

================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdb
=               cycle 1 of 1, partition start on sector 1
=
= 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
=
Elapsed Time:  5:39:04
========================================================================1.15
==
== SORRY: Disk /dev/sdb MBR could NOT be precleared
==
== out4= 00000
== out5= 00000
============================================================================
0000000

I got that when I needed to update the firmware of my SAS Expander.  But I think it could be almost anything.  Maybe someone else has more ideas.  Attaching a Syslog (v5 unRAID) or Diagnostics (v6 unRAID) would help someone else as well.

 

I attached the Diagnostics to this post.

r2d2-diagnostics-20160407-2044.zip

Share this post


Link to post

To add to this issue, I checked the System Logs and found the following for my drive. Wondering more and more if my drive is DOA...

 

Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280139, lost async page write
Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280140, lost async page write
Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280141, lost async page write
Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280142, lost async page write
Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280143, lost async page write
Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280144, lost async page write
Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280145, lost async page write
Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280146, lost async page write
Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280147, lost async page write
Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280148, lost async page write

Share this post


Link to post

I just received a WD RED 3TB drive that I will use to replace my 1TB parity drive.

I ran a preclear on it twice and got the same result. But I don't know what is the issue (if it is one). Any help would be greatly appreciated.

 

red ata7 sd6 sdb  no smart

p    ata4 sd3 sda  197=33

d2  ata8 sd7 sdd  ok

 

Almost 5.5 hours after boot (so probably during the zeroing of the Red), write requests timed out.  It retried and retried, then repeatedly tried resetting it, but when no response, the kernel disabled the drive, dropping it from the system.  There are no other clues I can see as to why, so you cannot conclude there's anything wrong with the drive.  In fact, typically this is almost never the fault of the drive, could be a port failed, a SATA or power cable fell off, loose backframe connection, bad power, controller failure, and very remotely a total drive failure.  There are no SMART reports for the Red, so can't conclude *anything* about it.

 

After the drive was disabled, you can ignore ALL errors that pertain to it, including those of your last post.  Once you check all connections and reboot, please obtain a SMART report for the Red, and attach it for us to see.

 

Your Parity drive has 33 bad sectors.  I recommend unassigning it, and Preclear it at least twice, and look for a clean report after each.  If clean, you can reassign it and use it.  Both Seagates have some wear and tear, but are probably still usable, certainly not perfect though, should be monitored now and then.

Share this post


Link to post

Thanks RobJ

 

I'm currently running a preclear using a new sata cable and using a different sata port on the motherboard. Will see how it goes.

I'll try the SMART report right after.

 

As for the parity drive, the 3TB RED will replace it. I made this build with parts I had laying around. The 3TB RED is the only brand new part. But more new parts will come around to improve it.

Share this post


Link to post

Thanks RobJ

 

I'm currently running a preclear using a new sata cable and using a different sata port on the motherboard. Will see how it goes.

I'll try the SMART report right after.

 

As for the parity drive, the 3TB RED will replace it. I made this build with parts I had laying around. The 3TB RED is the only brand new part. But more new parts will come around to improve it.

 

After changing cable and port, running Preclear worked this time. Took long but it seems ok. Thx for the help everyone.

 

================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdb
=               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: 36C, Elapsed Time:  32:38:55
========================================================================1.15
== WDCWD30EFRX-68EUZN0   WD-WCC4N5YF2774
== Disk /dev/sdb has been successfully precleared
== with a starting sector of 1
============================================================================
** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   114     123            0        ok          36
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.

Share this post


Link to post

Beh...

 

== WDCWD2003FYYS-02W0B1  WD-WMAY04480522

== Disk /dev/sde has NOT been precleared successfully

== skip=1131600 count=200 bs=1000448 returned 00049 instead of 00000 skip=1131800 count=200 bs=1000448 returned 00003 instead of 00000 skip=

1363800 count=200 bs=1000448 returned 00101 instead of 00000 skip=1829600 count=200 bs=1000448 returned 16489 instead of 00000

 

So, like, this disk will never be added in the array and I can use it only in Windows?

 

Don't remember seeing that error before, you can try the new beta plugin:

 

http://lime-technology.com/forum/index.php?topic=39985.msg453938#msg453938

 

I tried the PreClear Beta plugin, but as I could not follow the procedure mentioned (http://lime-technology.com/forum/index.php?topic=39985.msg453938#msg453938 - I could not format the drives in 6.1.7 as first they need to be added in the Array) I run the plugin to try to PreClear the disks. I got some fails again so I stopped bothering.

 

I was "sitting" on it for quite some time and a a few minutes ago I thought I give it another go. I stopped the Array and then I noticed that the two HDDs in question were now available to join the Array (unRaid - Adding Disks 1.JPG).

 

After adding them I also got the option to format them (unRaid - Adding Disks 2.JPG).

 

Format completed successfully and the two "new" disks are now added in the array (unRaid - Adding Disks 3.JPG)

 

So... what happened? PreClear erased the disks, but failed in testing them, but as the disks are now erased they can be added and formatted in the Array?

 

Will the disks work as should or will the errors shown by PreClear eventually start to appear when saving data to disks?

 

For the time being all shares are ignoring the two new disks until I am sure they can be used. Do you think they are ok or should I now use the steps mentioned in the PreClear Beta post:

 

1) Pick a formatted disk or format it with Unassigned Devices and copy some files to it;

2) Go to Settings/PreclearBeta and start a Clear operation;

3) Once it's over, please run a Verify All the Disk operation;

4) If successful, please run both Test and Run the post-read verify operations from the older plugin;

5) If possible, assign the precleared disk to the array and start a Check Parity operation.

 

Should I run all of the above steps? I 'm kind of confused with the 5th step. As I have somehow managed to add both disks to the Array, should I just do a Check Parity?

unRaid_-_Adding_Disks_1.JPG.bd4d81340b54093a06c6e8a10149f70c.JPG

unRaid_-_Adding_Disks_2.JPG.a780ede07ea83460c49ec2ed32809f9b.JPG

unRaid_-_Adding_Disks_3.JPG.e3c2bdd691c07fd674bbbb924613d014.JPG

Share this post


Link to post

Since the disks are already part of the array I would look at the SMART reports, if all looks fine and assuming by the models that they were previously used with no issues then do a parity check, if there are doubts do an extended SMART test before the parity check.

Share this post


Link to post

I'm having a bit of an issue finding where these logs are stored. I've searched the entire flash and no luck, no log folder to be found.  Can I only see them after all the cycles are complete? It has completed 1 of 3 cycles. (Using plugin)

 

Edit: Nevermind I figured it out, for others refer to

http://lime-technology.com/wiki/index.php/Configuration_Tutorial#Preclearing_via_Web_GUI_with_unRAID_v6

Share this post


Link to post

I have a SSD cache drive.  Last night my array seemed to stop responding, but maybe I was impatient.  I ran a preclear and it reports it as OK.  However, it also claims to be moving sectors.

 

Last night I was trying to move data off of it thinking it was failing, but today I moved it off just fine.  Long story short, I want to check if it is OK of if I should be replacing it.

 

preclear_finish_CVPO050100J1160AGN_2016-04-30.txt

preclear_rpt_CVPO050100J1160AGN_2016-04-30.txt

preclear_start_CVPO050100J1160AGN_2016-04-30.txt

Share this post


Link to post

I have a SSD cache drive.  Last night my array seemed to stop responding, but maybe I was impatient.  I ran a preclear and it reports it as OK.  However, it also claims to be moving sectors.

 

Last night I was trying to move data off of it thinking it was failing, but today I moved it off just fine.  Long story short, I want to check if it is OK of if I should be replacing it.

The drive itself says it's fine, don't have any evidence to doubt it.  It does have 30000 hours on it, but the numbers imply a lot more life left.

Share this post


Link to post

So despite the sectors and old age,  I should technically be good?

 

Sent from my Nexus 6P using Tapatalk

 

 

Share this post


Link to post

So despite the sectors and old age,  I should technically be good?

According to the numbers, it's not old, it's not even middle-aged, it's young.  Media_Wearout_Indicator is the lowest at 88, down from 100, which is like saying it's 12 now and expecting to live until it's 100.  That's of course very optimistic, but it's what the numbers say.  I'd look for others with the identical drive, and see at what point it failed for them.

Share this post


Link to post

OK.  Thanks. I guess the hope is the issue I thought I had was not a real issue and instead I got impatient.  I will keep an eye on things and see what happens.

 

 

 

Share this post


Link to post

Started two brand new 4TB 5900rpm HGST drives. All default settings except for setting two runs of preclear instead of one. It's currently sitting at Post-read (1 of 2) after 46 hours. Does this seem standard?

Share this post


Link to post

Normal preclear or fast-preclear?

 

I dont have experience with the slow 5900 RPM HGST, but the 7200RPM HGST completed 3 cycles of fast-preclear in 75 hours.

Share this post


Link to post

Normal preclear or fast-preclear?

 

I dont have experience with the slow 5900 RPM HGST, but the 7200RPM HGST completed 3 cycles of fast-preclear in 75 hours.

 

Normal preclear I believe. I'm running on 62 hours of run time and it's at 50% of zeroing (2nd cycle). Seems a bit long but I'm not sure.

Share this post


Link to post

hey, guys, first time unraid and preclear user here.  quick question...

 

i'm currently preclearing 3x brand new HGST 4TB 7200 RPM drives.  is it normal to have one drive that writes almost 20% slower than the other two?  here's my current status -- http://i.imgur.com/nGIDh35.jpg.

 

thanks!

I've had that before.  This is just speculation but what I think happens: The drive could have sectors that didn't meet specs after the drive electronics were installed so some of the spare sectors were remapped and thereby slowing the drive slightly as it has to seek to the spare sectors instead of the original ones.

Share this post


Link to post

I didn't know this post existed so I started a new one - sorry about that. I can always remove that one if needed. Anyway, here's the post in it's entirety:

 

I added a new drive (4TB WD Red) to the array so I can use it to do the file system swap thing so first thing I did was try to preclear it. I used the plugin this time instead of doing it on the console and I just used it with the defaults. I'm pretty sure when I first built this in 2014 I used some parameters with the preclear script, but darned if I can remember what or why.

 

Anyway, I ran a 3 pass preclear and after 84+ hours it says it failed because it detected non-zero bytes. I have no idea what to do at this point. Should I run it again with some parameters? If so, could someone enlighten me as to what cause I can't seem to find that part anymore.

 

Attaching the output from the preclear. It doesn't seem to allow me to paste it all in here. :(

 

Also, before anyone says check RAM, I recently did a 3 hour memtest at someones suggestion for trying to determine the cause of another issue which led to me wanting to change the file system over to XFS. The memtest came back fine, BTW.

 

Just found this, if it helps:

 

= Post-Read in progress: 99% complete.

(  3,998,790,656,000  of  4,000,787,030,016  bytes read ) 66.7 MB/s

Disk Temperature: 31C, Elapsed Time:  84:58:15

================================================================== 1.15

=                unRAID server Pre-Clear disk /dev/sde

=              cycle 3 of 3, partition start on sector 1

=

= 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: 99% complete.

(  3,998,990,745,600  of  4,000,787,030,016  bytes read ) 67.0 MB/s

Disk Temperature: 31C, Elapsed Time:  84:58:21

================================================================== 1.15

=                unRAID server Pre-Clear disk /dev/sde

=              cycle 3 of 3, partition start on sector 1

=

= 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: 99% complete.

(  3,999,190,835,200  of  4,000,787,030,016  bytes read ) 66.4 MB/s

Disk Temperature: 31C, Elapsed Time:  84:58:27

================================================================== 1.15

=                unRAID server Pre-Clear disk /dev/sde

=              cycle 3 of 3, partition start on sector 1

=

= 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: 99% complete.

(  3,999,390,924,800  of  4,000,787,030,016  bytes read ) 65.7 MB/s

Disk Temperature: 31C, Elapsed Time:  84:58:32

================================================================== 1.15

=                unRAID server Pre-Clear disk /dev/sde

=              cycle 3 of 3, partition start on sector 1

=

= 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: 99% complete.

(  3,999,591,014,400  of  4,000,787,030,016  bytes read ) 66.8 MB/s

Disk Temperature: 31C, Elapsed Time:  84:58:38

================================================================== 1.15

=                unRAID server Pre-Clear disk /dev/sde

=              cycle 3 of 3, partition start on sector 1

=

= 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: 99% complete.

(  3,999,791,104,000  of  4,000,787,030,016  bytes read ) 67.3 MB/s

Disk Temperature: 31C, Elapsed Time:  84:58:44

================================================================== 1.15

=                unRAID server Pre-Clear disk /dev/sde

=              cycle 3 of 3, partition start on sector 1

=

= 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: 99% complete.

(  3,999,991,193,600  of  4,000,787,030,016  bytes read ) 65.4 MB/s

Disk Temperature: 31C, Elapsed Time:  84:58:50

================================================================== 1.15

=                unRAID server Pre-Clear disk /dev/sde

=              cycle 3 of 3, partition start on sector 1

=

= 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: 99% complete.

(  4,000,191,283,200  of  4,000,787,030,016  bytes read ) 66.7 MB/s

Disk Temperature: 31C, Elapsed Time:  84:58:55

================================================================== 1.15

=                unRAID server Pre-Clear disk /dev/sde

=              cycle 3 of 3, partition start on sector 1

=

= 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: 99% complete.

(  4,000,391,372,800  of  4,000,787,030,016  bytes read ) 66.1 MB/s

Disk Temperature: 31C, Elapsed Time:  84:59:01

================================================================== 1.15

=                unRAID server Pre-Clear disk /dev/sde

=              cycle 3 of 3, partition start on sector 1

=

= 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: 99% complete.

(  4,000,591,462,400  of  4,000,787,030,016  bytes read ) 67.5 MB/s

Disk Temperature: 31C, Elapsed Time:  84:59:07

================================================================== 1.15

=                unRAID server Pre-Clear disk /dev/sde

=              cycle 3 of 3, partition start on sector 1

=

= 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:  84:59:13

========================================================================1.15

== WDCWD40EFRX-68WT0N0  WD-WCC4E7ZUZET9

== Disk /dev/sde has NOT been precleared successfully

== skip=2273000 count=200 bs=1000448 returned 00008 instead of 00000 skip=2287200 count=200 bs=1000448 returned 00008 instead of 00000 skip=

2301600 count=200 bs=1000448 returned 00008 instead of 00000 skip=2316000 count=200 bs=1000448 returned 00008 instead of 00000 skip=2330200

count=200 bs=1000448 returned 00008 instead of 00000 skip=2344600 count=200 bs=1000448 returned 00008 instead of 00000 skip=2358800 count=20

0 bs=1000448 returned 00008 instead of 00000 skip=2373200 count=200 bs=1000448 returned 00008 instead of 00000 skip=2387400 count=200 bs=100

0448 returned 00008 instead of 00000 skip=2401800 count=200 bs=1000448 returned 00008 instead of 00000

============================================================================

** Changed attributes in files: /tmp/smart_start_sde  /tmp/smart_finish_sde

                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

      Temperature_Celsius =  121    123            0        ok          31

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 3.

0 sectors were pending re-allocation after zero of disk in cycle 1 of 3.

0 sectors were pending re-allocation after post-read in cycle 1 of 3.

0 sectors were pending re-allocation after zero of disk in cycle 2 of 3.

0 sectors were pending re-allocation after post-read in cycle 2 of 3.

0 sectors were pending re-allocation after zero of disk in cycle 3 of 3.

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.

root@Tower:/usr/local/emhttp#

preclear-052016.txt

Share this post


Link to post

I had this once. Turned out to be bad RAM.

 

Been running with it for 2 years and I just ran a memtest for 3 hours with no errors. How the heck do I determine if that's indeed the problem?

Share this post


Link to post

I had this once. Turned out to be bad RAM.

 

Wow. Ram prices sure have dropped since my build. Should I just buy new ram anyway? Honestly have nothing else to go on, but Ram was the first suggestion to my other issue as well. Figured a 3 hour passed memtest was good though.

Share this post


Link to post

When I did memtest it was immediately obvious. Then I did memtest with each stick in each slot and it was definitely a bad stick. I was able to run without it fine until I got another one.

 

Yours looks like a stuck bit somewhere since it always comes up "returned 00008 instead of 00000". The bit could be stuck elsewhere in the system I guess, controller or somewhere. In any case it sounds like a recipe for data corruption. If you had another disk I guess you could try it just to make sure it isn't really something with the disk. Could be stuck in the drive electronics I suppose.

Share this post


Link to post

When I did memtest it was immediately obvious. Then I did memtest with each stick in each slot and it was definitely a bad stick. I was able to run without it fine until I got another one.

 

Yours looks like a stuck bit somewhere since it always comes up "returned 00008 instead of 00000". The bit could be stuck elsewhere in the system I guess, controller or somewhere. In any case it sounds like a recipe for data corruption. If you had another disk I guess you could try it just to make sure it isn't really something with the disk. Could be stuck in the drive electronics I suppose.

 

Ah. Well, I ordered some new ram anyway. I haven't had any errors elsewhere, but it can't hurt.

 

I'll run a very long memtest when I get them and then run preclear again. If I still have problems it's either the drive or something else as you state. I just don't want a chance for data corruption!

Share this post


Link to post

When I did memtest it was immediately obvious. Then I did memtest with each stick in each slot and it was definitely a bad stick. I was able to run without it fine until I got another one.

 

Yours looks like a stuck bit somewhere since it always comes up "returned 00008 instead of 00000". The bit could be stuck elsewhere in the system I guess, controller or somewhere. In any case it sounds like a recipe for data corruption. If you had another disk I guess you could try it just to make sure it isn't really something with the disk. Could be stuck in the drive electronics I suppose.

 

So after I posted this I rebooted the thing and ran a single preclear. It finished successfully so the mystery deepens. I still have new memory that should arrive today and since this would be the second unexplained incident, I'll go ahead and swap it. Then test the hell out of it.

 

And I should probably run another preclear cycle once that's all done just to be extra sure, but that might be overkill.

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.