Help! Preclear problem


Recommended Posts

I just bought new 3tb wd green hdd and got errors when preclearing.

 

here are the screen details

 

================================================================== 1.13
=                unRAID server Pre-Clear disk /dev/sdi
=               cycle 1 of 3, 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
=
Elapsed Time:  13:52:59
========================================================================1.13
==
== SORRY: Disk /dev/sdi MBR could NOT be precleared
==
== out4= 00000
== out5= 00000
============================================================================
0+0 records in
0+0 records out
0 bytes (0 B) copied0000000
, 4.2438e-05 s, 0.0 kB/s

 

this are some of the syslog.

Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi] Unhandled error code (Errors)
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi]   (Drive related)
Jul  8 05:12:49 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 (System)
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi] CDB:  (Drive related)
Jul  8 05:12:49 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 e8 83 ce c8 00 00 04 00 00 00
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi] Unhandled error code (Errors)
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi]   (Drive related)
Jul  8 05:12:49 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 (System)
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi] CDB:  (Drive related)
Jul  8 05:12:49 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 e8 83 d2 c8 00 00 04 00 00 00
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi] Unhandled error code (Errors)
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi]   (Drive related)
Jul  8 05:12:49 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 (System)
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi] CDB:  (Drive related)
Jul  8 05:12:49 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 e8 83 d6 c8 00 00 04 00 00 00
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi] Unhandled error code (Errors)
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi]   (Drive related)
Jul  8 05:12:49 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 (System)
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi] CDB:  (Drive related)
Jul  8 05:12:49 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 e8 83 da c8 00 00 04 00 00 00
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi] Unhandled error code (Errors)
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi]   (Drive related)
Jul  8 05:12:49 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 (System)
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi] CDB:  (Drive related)
Jul  8 05:12:49 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 e8 83 de c8 00 00 04 00 00 00
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi] Unhandled error code (Errors)
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi]   (Drive related)
Jul  8 05:12:49 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 (System)
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi] CDB:  (Drive related)
Jul  8 05:12:49 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 e8 83 e2 c8 00 00 04 00 00 00
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi] Unhandled error code (Errors)
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi]   (Drive related)
Jul  8 05:12:49 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 (System)
Jul  8 05:12:49 Tower kernel: sd 9:0:0:0: [sdi] CDB:  (Drive related)
Jul  8 05:12:49 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 e8 83 e6 c8 00 00 04 00 00 00

 

What is the problem? What should I do?

 

Thanks.

Link to comment

Quick searching around indicates that Result: hostbyte=0x04 means the drive went offline.  I would check connections, cables, etc.  If all checks out oki i would get that drive exchanged.

I agree.  Check cabling first and any power splitters, etc.
Link to comment

Quick searching around indicates that Result: hostbyte=0x04 means the drive went offline.  I would check connections, cables, etc.  If all checks out oki i would get that drive exchanged.

I agree.  Check cabling first and any power splitters, etc.

 

Thank you. The hdd slot that I use have been used before to successfully preclear another drive(later, ive decided not to use the drive, hence the slot still empty). Most likely, cable and connection might not be the problem. To make sure, I preclear on another slot. Got the same error. If you guys still think that this might be connection error, do tell.

 

I have attached syslog file. I have to delete some logs at the end to reduce file size.

 

Please take a look.

 

thanks.

syslog.crop.7z.zip

Link to comment

Quick searching around indicates that Result: hostbyte=0x04 means the drive went offline.  I would check connections, cables, etc.  If all checks out oki i would get that drive exchanged.

I agree.  Check cabling first and any power splitters, etc.

 

Thank you. The hdd slot that I use have been used before to successfully preclear another drive(later, ive decided not to use the drive, hence the slot still empty). Most likely, cable and connection might not be the problem. To make sure, I preclear on another slot. Got the same error. If you guys still think that this might be connection error, do tell.

 

I have attached syslog file. I have to delete some logs at the end to reduce file size.

 

Please take a look.

 

thanks.

If you've tried the same disk in another slot (with a different SATA and power connection) and it still fails, then yes, you probably have a defective disk.

 

Joe L.

Link to comment

Quick searching around indicates that Result: hostbyte=0x04 means the drive went offline.  I would check connections, cables, etc.  If all checks out oki i would get that drive exchanged.

I agree.  Check cabling first and any power splitters, etc.

 

Thank you. The hdd slot that I use have been used before to successfully preclear another drive(later, ive decided not to use the drive, hence the slot still empty). Most likely, cable and connection might not be the problem. To make sure, I preclear on another slot. Got the same error. If you guys still think that this might be connection error, do tell.

 

I have attached syslog file. I have to delete some logs at the end to reduce file size.

 

Please take a look.

 

thanks.

If you've tried the same disk in another slot (with a different SATA and power connection) and it still fails, then yes, you probably have a defective disk.

 

Joe L.

 

sigh.

 

What do you guys recommend me to do? Send the drive back to wd for rma? If i do this, I will get a refurbish drive wont I? How reliable is refurbish drive? What would you guys do if you were in my spot? And why?

 

Thanks.

Link to comment

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.