Jump to content
jbuszkie

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

2840 posts in this topic Last Reply

Recommended Posts

Well Joe, I need your advice.  Attached is the syslog after I precleared a brand new 2 TB WD EARS w/ jumper.  It took 64 hours to complete!  I figure something must be wrong for it to take that long.

 

First off, I know I have HPA on some of my drives.  I no longer use a gigabyte mobo and I haven't bothered to get rid of them.

 

Some things I've noticed:

Jul 28 18:36:38 Tower emhttp: pci-0000:00:11.0-scsi-0:0:0:0 host1 (sda) WDC_WD10EADS-00L5B1_WD-WCAU45951367

Jul 28 18:36:38 Tower emhttp: pci-0000:00:11.0-scsi-1:0:0:0 host2 (sdb) WDC_WD10EADS-00L5B1_WD-WCAU49026373

Jul 28 18:36:38 Tower emhttp: pci-0000:00:11.0-scsi-2:0:0:0 host3 (sdc) WDC_WD10EARS-00Y5B1_WD-WMAV50673569

Jul 28 18:36:38 Tower emhttp: pci-0000:00:11.0-scsi-3:0:0:0 host4 (sdd) SAMSUNG_HD103UJ_S13PJ1LS631384

Jul 28 18:36:38 Tower emhttp: pci-0000:00:14.1-ide-0:0 ide0 (hda) WDC_WD15EARS-00Z5B1_WD-WMAVU2570536

Jul 28 18:36:38 Tower emhttp: pci-0000:00:14.1-ide-0:1 ide0 (hdb) WDC_WD20EARS-00MVWB0_WD-WMAZA0132941

Jul 28 18:36:38 Tower emhttp: pci-0000:03:05.0-scsi-0:0:0:0 host5 (sde) ST3320620AS_6QF0WRZW

Jul 28 18:36:38 Tower emhttp: pci-0000:03:05.0-scsi-1:0:0:0 host6 (sdf) WDC_WD5000AAJS-22TKA0_WD-WCAPW5380433

 

Two of my drives (one of which is this new 2 TB WD EARS) are in IDE emulation mode even though I have AHCI turned on in the BIOS.  Any idea why?  I'm using a Promise TX4 card, do I need to do some special configuration for that?

 

Jul 30 10:22:15 Tower kernel:  hdb: hdb1
Jul 30 10:22:25 Tower kernel: udev: starting version 141
Jul 30 10:46:06 Tower kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jul 30 10:46:06 Tower kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=98144375, sector=98144112
Jul 30 10:46:06 Tower kernel: hdb: possibly failed opcode: 0x25
Jul 30 10:46:06 Tower kernel: end_request: I/O error, dev hdb, sector 98144112
Jul 30 10:46:06 Tower kernel: Buffer I/O error on device hdb, logical block 12268014
Jul 30 10:46:06 Tower kernel: Buffer I/O error on device hdb, logical block 12268015
Jul 30 10:46:06 Tower kernel: Buffer I/O error on device hdb, logical block 12268016
Jul 30 10:46:06 Tower kernel: Buffer I/O error on device hdb, logical block 12268017
Jul 30 10:46:06 Tower kernel: Buffer I/O error on device hdb, logical block 12268018
Jul 30 10:46:06 Tower kernel: Buffer I/O error on device hdb, logical block 12268019
Jul 30 10:46:06 Tower kernel: Buffer I/O error on device hdb, logical block 12268020
Jul 30 10:46:06 Tower kernel: Buffer I/O error on device hdb, logical block 12268021
Jul 30 10:46:06 Tower kernel: Buffer I/O error on device hdb, logical block 12268022
Jul 30 10:46:06 Tower kernel: Buffer I/O error on device hdb, logical block 12268023
Jul 30 10:46:34 Tower kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jul 30 10:46:34 Tower kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=98144375, sector=98144112
Jul 30 10:46:34 Tower kernel: hdb: possibly failed opcode: 0x25
Jul 30 10:46:34 Tower kernel: end_request: I/O error, dev hdb, sector 98144112
Jul 30 10:46:34 Tower kernel: __ratelimit: 54 callbacks suppressed
Jul 30 10:46:34 Tower kernel: Buffer I/O error on device hdb, logical block 12268014
Jul 30 10:46:34 Tower kernel: Buffer I/O error on device hdb, logical block 12268015
Jul 30 10:46:34 Tower kernel: Buffer I/O error on device hdb, logical block 12268016
Jul 30 10:46:34 Tower kernel: Buffer I/O error on device hdb, logical block 12268017
Jul 30 10:46:34 Tower kernel: Buffer I/O error on device hdb, logical block 12268018
Jul 30 10:46:34 Tower kernel: Buffer I/O error on device hdb, logical block 12268019
Jul 30 10:46:34 Tower kernel: Buffer I/O error on device hdb, logical block 12268020
Jul 30 10:46:34 Tower kernel: Buffer I/O error on device hdb, logical block 12268021
Jul 30 10:46:34 Tower kernel: Buffer I/O error on device hdb, logical block 12268022
Jul 30 10:46:34 Tower kernel: Buffer I/O error on device hdb, logical block 12268023
Jul 30 20:03:59 Tower kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jul 30 20:03:59 Tower kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=1907719879, sector=1907719496
Jul 30 20:03:59 Tower kernel: hdb: possibly failed opcode: 0x25
Jul 30 20:03:59 Tower kernel: end_request: I/O error, dev hdb, sector 1907719496
Jul 30 20:03:59 Tower kernel: __ratelimit: 54 callbacks suppressed
Jul 30 20:03:59 Tower kernel: Buffer I/O error on device hdb, logical block 238464937
Jul 30 20:03:59 Tower kernel: Buffer I/O error on device hdb, logical block 238464938
Jul 30 20:03:59 Tower kernel: Buffer I/O error on device hdb, logical block 238464939
Jul 30 20:03:59 Tower kernel: Buffer I/O error on device hdb, logical block 238464940
Jul 30 20:03:59 Tower kernel: Buffer I/O error on device hdb, logical block 238464941
Jul 30 20:03:59 Tower kernel: Buffer I/O error on device hdb, logical block 238464942
Jul 30 20:03:59 Tower kernel: Buffer I/O error on device hdb, logical block 238464943
Jul 30 20:03:59 Tower kernel: Buffer I/O error on device hdb, logical block 238464944
Jul 30 20:03:59 Tower kernel: Buffer I/O error on device hdb, logical block 238464945
Jul 30 20:03:59 Tower kernel: Buffer I/O error on device hdb, logical block 238464946

 

...a bunch of these Buffer I/O errors on hdb...

 

Jul 31 10:43:07 Tower preclear_disk-diff[12912]: S.M.A.R.T. error count differences detected after pre-clear

Jul 31 10:43:07 Tower preclear_disk-diff[12912]: note, some 'raw' values may change, but not be an indication of a problem

Jul 31 10:43:07 Tower preclear_disk-diff[12912]: 54c54

Jul 31 10:43:07 Tower preclear_disk-diff[12912]: <  1 Raw_Read_Error_Rate    0x002f  100  253  051    Pre-fail  Always      -      0

Jul 31 10:43:07 Tower preclear_disk-diff[12912]: ---

Jul 31 10:43:07 Tower preclear_disk-diff[12912]: >  1 Raw_Read_Error_Rate    0x002f  200  200  051    Pre-fail  Always      -      2

Jul 31 10:43:07 Tower preclear_disk-diff[12912]: 65c65

Jul 31 10:43:07 Tower preclear_disk-diff[12912]: < 197 Current_Pending_Sector  0x0032  200  200  000    Old_age  Always      -      0

Jul 31 10:43:07 Tower preclear_disk-diff[12912]: ---

Jul 31 10:43:07 Tower preclear_disk-diff[12912]: > 197 Current_Pending_Sector  0x0032  200  200  000    Old_age  Always      -      2

Jul 31 10:43:07 Tower preclear_disk-diff[12912]: 67c67

Jul 31 10:43:07 Tower preclear_disk-diff[12912]: < 199 UDMA_CRC_Error_Count    0x0032  200  253  000    Old_age  Always      -      0

Jul 31 10:43:07 Tower preclear_disk-diff[12912]: ---

Jul 31 10:43:07 Tower preclear_disk-diff[12912]: > 199 UDMA_CRC_Error_Count    0x0032  200  200  000    Old_age  Always      -      0

 

...and then two read errors and two pending sectors.

 

Looks like I may need to RMA this drive?

Syslog-7-31-2010-2TBEARSpreclear..txt

Share this post


Link to post

I doubt that 2 re-allocated sectors would qualify you for an RMA.  They'd laugh at you since modern drives of that size have several thousand spare sectors, and your SMART report "normalized" value of 200 is nowhere near the failure threshold of "0"

 

In the same way, the read error rate of "200" is nowhere near its failure threshold.  All drives have read errors, some report it, some do not, most will re-try several times before determining a sector is un-readable.

 

As far as IDE vs SATA there is a second setting in your BIOS you need to set to get the drive out of the "legacy" mode.  It is probably the root cause of the difference in performance.

 

Joe L.

Share this post


Link to post

Great, thanks for the good news Joe.

 

Edit: I determined that it is the Promixe TX4 card that has both of it's drives in IDE mode.  The card has no BIOS screen of its own, and I can't figure out how to control it via the motherboard's BIOS settings (all of which are correct, by the way).  I plan on migrating my server to my 4220 + AOC-SASLP-MV8 setup soon, so I guess I won't worry about it.

Share this post


Link to post

Hi!

I tried to run two sessions of telnet via wireless and ran preclear on two different harddrives. One hdd (WD 1 Gb) reportet finished within 15 minutes. I know something is wrong because it took over 12 hours on other drives.

I tried to re-run preclear, but it couldn't read any driveinfo.

I am a linux newb, so will someone please tell me what went wrong?

 

Kind regards

Henrik

04-08-2010.txt

Share this post


Link to post

Hi!

I tried to run two sessions of telnet via wireless and ran preclear on two different harddrives. One hdd (WD 1 Gb) reportet finished within 15 minutes. I know something is wrong because it took over 12 hours on other drives.

I tried to re-run preclear, but it couldn't read any driveinfo.

I am a linux newb, so will someone please tell me what went wrong?

 

Kind regards

Henrik

looks like communications with the drive is failing.

 

Might try a different SATA cable, or re-seat the existing cable to the drive. You have lots of BadCRC  errors.

 

Aug  4 12:57:08 Tower kernel: ata1.00: exception Emask 0x50 SAct 0x3 SErr 0x280900 action 0x6 frozen

Aug  4 12:57:08 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error

Aug  4 12:57:08 Tower kernel: ata1: SError: { UnrecovData HostInt 10B8B BadCRC }

Aug  4 12:57:08 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED

Aug  4 12:57:08 Tower kernel: ata1.00: cmd 60/00:00:b8:24:1d/01:00:09:00:00/40 tag 0 ncq 131072 in

Aug  4 12:57:08 Tower kernel:          res 40/00:0c:b8:23:1d/00:00:09:00:00/40 Emask 0x50 (ATA bus error)

Aug  4 12:57:08 Tower kernel: ata1.00: status: { DRDY }

Aug  4 12:57:08 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED

Aug  4 12:57:08 Tower kernel: ata1.00: cmd 60/00:08:b8:23:1d/01:00:09:00:00/40 tag 1 ncq 131072 in

Aug  4 12:57:08 Tower kernel:          res 40/00:0c:b8:23:1d/00:00:09:00:00/40 Emask 0x50 (ATA bus error)

Aug  4 12:57:08 Tower kernel: ata1.00: status: { DRDY }

Aug  4 12:57:08 Tower kernel: ata1: hard resetting link

Aug  4 12:57:08 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Aug  4 12:57:08 Tower kernel: ata1.00: configured for UDMA/133

Aug  4 12:57:08 Tower kernel: ata1: EH complete

Aug  4 12:57:09 Tower kernel: ata1.00: exception Emask 0x50 SAct 0x3 SErr 0x280900 action 0x6 frozen

Aug  4 12:57:09 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error

Aug  4 12:57:09 Tower kernel: ata1: SError: { UnrecovData HostInt 10B8B BadCRC }

Aug  4 12:57:09 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED

Aug  4 12:57:09 Tower kernel: ata1.00: cmd 60/00:00:b8:4d:20/01:00:09:00:00/40 tag 0 ncq 131072 in

Aug  4 12:57:09 Tower kernel:          res 40/00:0c:b8:4c:20/00:00:09:00:00/40 Emask 0x50 (ATA bus error)

Aug  4 12:57:09 Tower kernel: ata1.00: status: { DRDY }

Aug  4 12:57:09 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED

Aug  4 12:57:09 Tower kernel: ata1.00: cmd 60/00:08:b8:4c:20/01:00:09:00:00/40 tag 1 ncq 131072 in

Aug  4 12:57:09 Tower kernel:          res 40/00:0c:b8:4c:20/00:00:09:00:00/40 Emask 0x50 (ATA bus error)

Aug  4 12:57:09 Tower kernel: ata1.00: status: { DRDY }

Aug  4 12:57:09 Tower kernel: ata1: hard resetting link

Aug  4 12:57:10 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Aug  4 12:57:10 Tower kernel: ata1.00: configured for UDMA/133

Aug  4 12:57:10 Tower kernel: ata1: EH complete

Aug  4 12:57:10 Tower kernel: ata1.00: exception Emask 0x50 SAct 0x3 SErr 0x280900 action 0x6 frozen

Aug  4 12:57:10 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error

Aug  4 12:57:10 Tower kernel: ata1: SError: { UnrecovData HostInt 10B8B BadCRC }

Aug  4 12:57:10 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED

Aug  4 12:57:10 Tower kernel: ata1.00: cmd 60/00:00:b8:a2:20/01:00:09:00:00/40 tag 0 ncq 131072 in

Aug  4 12:57:10 Tower kernel:          res 40/00:04:b8:a2:20/00:00:09:00:00/40 Emask 0x50 (ATA bus error)

Aug  4 12:57:10 Tower kernel: ata1.00: status: { DRDY }

Aug  4 12:57:10 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED

Aug  4 12:57:10 Tower kernel: ata1.00: cmd 60/00:08:b8:a3:20/01:00:09:00:00/40 tag 1 ncq 131072 in

Aug  4 12:57:10 Tower kernel:          res 40/00:04:b8:a2:20/00:00:09:00:00/40 Emask 0x50 (ATA bus error)

Aug  4 12:57:10 Tower kernel: ata1.00: status: { DRDY }

Aug  4 12:57:10 Tower kernel: ata1: hard resetting link

Aug  4 12:57:11 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Aug  4 12:57:11 Tower kernel: ata1.00: configured for UDMA/133

Aug  4 12:57:11 Tower kernel: ata1: EH complete

Aug  4 12:57:11 Tower kernel: ata1: limiting SATA link speed to 1.5 Gbps

Aug  4 12:57:11 Tower kernel: ata1.00: exception Emask 0x50 SAct 0x3 SErr 0x280900 action 0x6 frozen

Aug  4 12:57:11 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error

Aug  4 12:57:11 Tower kernel: ata1: SError: { UnrecovData HostInt 10B8B BadCRC }

Aug  4 12:57:11 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED

Aug  4 12:57:11 Tower kernel: ata1.00: cmd 60/00:00:b8:db:20/01:00:09:00:00/40 tag 0 ncq 131072 in

Aug  4 12:57:11 Tower kernel:          res 40/00:0c:b8:dc:20/00:00:09:00:00/40 Emask 0x50 (ATA bus error)

Aug  4 12:57:11 Tower kernel: ata1.00: status: { DRDY }

Aug  4 12:57:11 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED

Aug  4 12:57:11 Tower kernel: ata1.00: cmd 60/00:08:b8:dc:20/01:00:09:00:00/40 tag 1 ncq 131072 in

Aug  4 12:57:11 Tower kernel:          res 40/00:0c:b8:dc:20/00:00:09:00:00/40 Emask 0x50 (ATA bus error)

Aug  4 12:57:11 Tower kernel: ata1.00: status: { DRDY }

Aug  4 12:57:11 Tower kernel: ata1: hard resetting link

Aug  4 12:57:11 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Aug  4 12:57:11 Tower kernel: ata1.00: configured for UDMA/133

Aug  4 12:57:11 Tower kernel: ata1: EH complete

Aug  4 12:57:11 Tower kernel: ata1.00: exception Emask 0x50 SAct 0x3 SErr 0x280900 action 0x6 frozen

Aug  4 12:57:11 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error

Aug  4 12:57:11 Tower kernel: ata1: SError: { UnrecovData HostInt 10B8B BadCRC }

Aug  4 12:57:11 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED

Aug  4 12:57:11 Tower kernel: ata1.00: cmd 60/00:00:b8:dc:20/01:00:09:00:00/40 tag 0 ncq 131072 in

Aug  4 12:57:11 Tower kernel:          res 40/00:0c:b8:db:20/00:00:09:00:00/40 Emask 0x50 (ATA bus error)

Aug  4 12:57:11 Tower kernel: ata1.00: status: { DRDY }

Aug  4 12:57:11 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED

Aug  4 12:57:11 Tower kernel: ata1.00: cmd 60/00:08:b8:db:20/01:00:09:00:00/40 tag 1 ncq 131072 in

Aug  4 12:57:11 Tower kernel:          res 40/00:0c:b8:db:20/00:00:09:00:00/40 Emask 0x50 (ATA bus error)

Aug  4 12:57:11 Tower kernel: ata1.00: status: { DRDY }

Aug  4 12:57:11 Tower kernel: ata1: hard resetting link

Aug  4 12:57:12 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Aug  4 12:57:12 Tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x100)

Aug  4 12:57:12 Tower kernel: ata1.00: revalidation failed (errno=-5)

Aug  4 12:57:17 Tower kernel: ata1: hard resetting link

Aug  4 12:57:17 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Aug  4 12:57:17 Tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x100)

Aug  4 12:57:17 Tower kernel: ata1.00: revalidation failed (errno=-5)

Aug  4 12:57:22 Tower kernel: ata1: hard resetting link

Aug  4 12:57:23 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Aug  4 12:57:23 Tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x100)

Aug  4 12:57:23 Tower kernel: ata1.00: revalidation failed (errno=-5)

Aug  4 12:57:23 Tower kernel: ata1.00: disabled

Aug  4 12:57:23 Tower kernel: ata1: exception Emask 0x52 SAct 0x0 SErr 0x280d00 action 0x6 frozen t4

Aug  4 12:57:23 Tower kernel: ata1: irq_stat 0x08000000, interface fatal error

Aug  4 12:57:23 Tower kernel: ata1: SError: { UnrecovData Proto HostInt 10B8B BadCRC }

Aug  4 12:57:23 Tower kernel: ata1: hard resetting link

Aug  4 12:57:23 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Aug  4 12:57:23 Tower kernel: ata1: EH complete

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Unhandled error code

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 09 20 db b8 00 01 00 00

Aug  4 12:57:23 Tower kernel: end_request: I/O error, dev sda, sector 153148344

Aug  4 12:57:23 Tower kernel: Buffer I/O error on device sda, logical block 19143543

Aug  4 12:57:23 Tower kernel: Buffer I/O error on device sda, logical block 19143544

Aug  4 12:57:23 Tower kernel: Buffer I/O error on device sda, logical block 19143545

Aug  4 12:57:23 Tower kernel: Buffer I/O error on device sda, logical block 19143546

Aug  4 12:57:23 Tower kernel: Buffer I/O error on device sda, logical block 19143547

Aug  4 12:57:23 Tower kernel: Buffer I/O error on device sda, logical block 19143548

Aug  4 12:57:23 Tower kernel: Buffer I/O error on device sda, logical block 19143549

Aug  4 12:57:23 Tower kernel: Buffer I/O error on device sda, logical block 19143550

Aug  4 12:57:23 Tower kernel: Buffer I/O error on device sda, logical block 19143551

Aug  4 12:57:23 Tower kernel: Buffer I/O error on device sda, logical block 19143552

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Unhandled error code

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 09 20 dc b8 00 01 00 00

Aug  4 12:57:23 Tower kernel: end_request: I/O error, dev sda, sector 153148600

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Unhandled error code

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 09 20 db b8 00 00 08 00

Aug  4 12:57:23 Tower kernel: end_request: I/O error, dev sda, sector 153148344

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Unhandled error code

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 09 20 db b8 00 00 08 00

Aug  4 12:57:23 Tower kernel: end_request: I/O error, dev sda, sector 153148344

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Unhandled error code

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 09 21 17 b8 00 00 20 00

Aug  4 12:57:23 Tower kernel: end_request: I/O error, dev sda, sector 153163704

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] READ CAPACITY(16) failed

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Sense not available.

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] READ CAPACITY failed

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Sense not available.

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Write Protect is on

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Mode Sense: 80 80 52 f4

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Got wrong page

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through

Aug  4 12:57:23 Tower kernel: sda: detected capacity change from 1000204886016 to 0

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] READ CAPACITY(16) failed

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Sense not available.

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] READ CAPACITY failed

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Sense not available.

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Write Protect is off

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Mode Sense: 00 00 00 00

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Asking for cache data failed

Aug  4 12:57:23 Tower kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through

Share this post


Link to post

So it's most likely due to a bad cable/connection?

I tried rebooting, and its running on 1h15m without problem. But when it's done i will change the cable/see if anything looks loose.

 

Thank you wery much for the reply!!

Share this post


Link to post

I have a newbie question.  I ran preclear on a new 2 TB western digital (ears with 7+8 jumpered) from the console on the unraid box itself. there are SMART differences listed, but most of the report is off the top of the screen.  are the results written anywhere that I can look at them.  I usually run it from a terminal window on my linux  desktop where I can scroll up, copy/paste, etc.  i don't want to have to run this again.

 

thanks,

c+h

 

Share this post


Link to post

I have a newbie question.  I ran preclear on a new 2 TB western digital (ears with 7+8 jumpered) from the console on the unraid box itself. there are SMART differences listed, but most of the report is off the top of the screen.  are the results written anywhere that I can look at them.  I usually run it from a terminal window on my linux  desktop where I can scroll up, copy/paste, etc.  i don't want to have to run this again.

 

thanks,

c+h

 

The two SMART reports were logged to your syslog.

 

You can scroll up on the system console...  (Shift-PageUp and Shift-PageDown)

 

Joe L.

Share this post


Link to post
The two SMART reports were logged to your syslog.

 

Dec 31 17:27:56 lionfish preclear_disk-start[7080]: SMART Attributes Data Structure revision number: 16
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: Vendor Specific SMART Attributes with Thresholds:
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 3 Spin_Up_Time 0x0027 171 171 021 Pre-fail Always - 6441
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 12
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 0
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 10
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 10
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
Dec 31 17:27:56 lionfish preclear_disk-start[7080]:
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: SMART Error Log Version: 1
Dec 31 17:27:56 lionfish preclear_disk-start[7080]: No Errors Logged

 

After....

 

Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: SMART Attributes Data Structure revision number: 16
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: Vendor Specific SMART Attributes with Thresholds:
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 3 Spin_Up_Time 0x0027 171 171 021 Pre-fail Always - 6441
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 12
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 20
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 10
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 14
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]:
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: SMART Error Log Version: 1
Aug 2 11:38:45 lionfish preclear_disk-finish[29294]: No Errors Logged

 

No, the preclear did not take 7 months....my clock got reset when putting in the new drive, and in the meantime, the clock got updated.

 

Looks good to me unless somone tells me otherwise.

Share this post


Link to post

Just precleared a new drive that I'm going to use as a boot drive in another machine and got some stuff that looks weird to me. Any thoughts?

 

== Disk /dev/sdc has been successfully precleared

==

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

S.M.A.R.T. error count differences detected after pre-clear

note, some 'raw' values may change, but not be an indication of a problem

55c55

<  1 Raw_Read_Error_Rate    0x002f  100  253  051    Pre-fail  Always      -      0

---

>  1 Raw_Read_Error_Rate    0x002f  200  200  051    Pre-fail  Always      -      0

68c68

< 199 UDMA_CRC_Error_Count    0x0032  200  253  000    Old_age  Always      -      0

---

> 199 UDMA_CRC_Error_Count    0x0032  200  200  000    Old_age  Always      -      0

70,72c70,72

< 240 Head_Flying_Hours      0x0032  100  100  000    Old_age  Always      -      2

< 241 Unknown_Attribute      0x0032  200  200  000    Old_age  Always      -      2353

< 242 Unknown_Attribute      0x0032  200  200  000    Old_age  Always      -      9631

---

> 240 Head_Flying_Hours      0x0032  100  100  000    Old_age  Always      -      6

> 241 Unknown_Attribute      0x0032  200  200  000    Old_age  Always      -      625144849

> 242 Unknown_Attribute      0x0032  200  200  000    Old_age  Always      -      1903926051

 

Thanks in advance.

Share this post


Link to post

Just precleared a new drive that I'm going to use as a boot drive in another machine and got some stuff that looks weird to me. Any thoughts?

 

== Disk /dev/sdc has been successfully precleared

==

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

S.M.A.R.T. error count differences detected after pre-clear

note, some 'raw' values may change, but not be an indication of a problem

55c55

<   1 Raw_Read_Error_Rate     0x002f   100   253   051    Pre-fail  Always       -       0

---

>   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0

68c68

< 199 UDMA_CRC_Error_Count    0x0032   200   253   000    Old_age   Always       -       0

---

> 199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0

70,72c70,72

< 240 Head_Flying_Hours       0x0032   100   100   000    Old_age   Always       -       2

< 241 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       2353

< 242 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       9631

---

> 240 Head_Flying_Hours       0x0032   100   100   000    Old_age   Always       -       6

> 241 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       625144849

> 242 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       1903926051

 

Thanks in advance.

Nothing looks weird to me.

 

What looks weird to you?

Share this post


Link to post

OK...pre-clearing 3 disks.

1 completed and I would think is good.

 

Other 2 were at 98% and 96% of post-read phase when had a storm power outage.

 

This is not on UPS (but I see the value in getting one now) so naturally the starting SMART logs no longer exist.

 

Attached is the output from smartctl -a /dev/sd[a,b]

 

As much as I know, they look good.

So what should really be paid attention to??  reallocate, error_rate, what else?

 

So would you figure they are good or recommend going thru the pre-clear process again for them?

 

smart-sda.txt

smart-sdb.txt

Share this post


Link to post

Here are the smartctl for the disk that completed.  diff is:

 

19,20c19,20

< Offline data collection status:  (0x80) Offline data collection activity

< was never started.

---

> Offline data collection status:  (0x84) Offline data collection activity

> was suspended by an interrupting command from host.

 

 

smart_start1387.txt

smart_finish1387.txt

Share this post


Link to post

About all we care about is re-allocated sectors and sectors pending re-allocation.

Of course, if any given parameter's "normalized" value is getting near its affiliated failure threshold that would be a cause for concern.

Share this post


Link to post

Just precleared a new drive that I'm going to use as a boot drive in another machine and got some stuff that looks weird to me. Any thoughts?

 

== Disk /dev/sdc has been successfully precleared

==

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

S.M.A.R.T. error count differences detected after pre-clear

note, some 'raw' values may change, but not be an indication of a problem

55c55

<   1 Raw_Read_Error_Rate     0x002f   100   253   051    Pre-fail  Always       -       0

---

>   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0

68c68

< 199 UDMA_CRC_Error_Count    0x0032   200   253   000    Old_age   Always       -       0

---

> 199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0

70,72c70,72

< 240 Head_Flying_Hours       0x0032   100   100   000    Old_age   Always       -       2

< 241 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       2353

< 242 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       9631

---

> 240 Head_Flying_Hours       0x0032   100   100   000    Old_age   Always       -       6

> 241 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       625144849

> 242 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       1903926051

 

Thanks in advance.

Nothing looks weird to me.

 

What looks weird to you?

 

I thought that

 

> 241 Unknown_Attribute      0x0032  200  200  000    Old_age  Always      -      625144849

> 242 Unknown_Attribute      0x0032  200  200  000    Old_age  Always      -      1903926051

 

was weird, but if there is nothing to worry about I'm cool. Thanks.

Share this post


Link to post

Just precleared a new drive that I'm going to use as a boot drive in another machine and got some stuff that looks weird to me. Any thoughts?

 

== Disk /dev/sdc has been successfully precleared

==

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

S.M.A.R.T. error count differences detected after pre-clear

note, some 'raw' values may change, but not be an indication of a problem

55c55

<   1 Raw_Read_Error_Rate     0x002f   100   253   051    Pre-fail  Always       -       0

---

>   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0

68c68

< 199 UDMA_CRC_Error_Count    0x0032   200   253   000    Old_age   Always       -       0

---

> 199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0

70,72c70,72

< 240 Head_Flying_Hours       0x0032   100   100   000    Old_age   Always       -       2

< 241 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       2353

< 242 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       9631

---

> 240 Head_Flying_Hours       0x0032   100   100   000    Old_age   Always       -       6

> 241 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       625144849

> 242 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       1903926051

 

Thanks in advance.

Nothing looks weird to me.

 

What looks weird to you?

 

I thought that

 

> 241 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       625144849

> 242 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       1903926051

 

was weird, but if there is nothing to worry about I'm cool. Thanks.

It indicates the manufacturer has not told anybody about what those two parameters represent, but that their "normalized" value of  200 is nowhere near their failure threshold of "000"

 

Joe L.

Share this post


Link to post

Hi!

 

I'm currently preclearing a new Samsung 2TB drive and it really takes forever. The post-read is still in progress and over 29 hours have elapsed since I've started preclear. Is it normal that it takes that long to preclear a drive? And is it also normal that the read speed drops from around 105 MB/s to 50 MB/s?

Share this post


Link to post

Hi!

 

I'm currently preclearing a new Samsung 2TB drive and it really takes forever. The post-read is still in progress and over 29 hours have elapsed since I've started preclear. Is it normal that it takes that long to preclear a drive? And is it also normal that the read speed drops from around 105 MB/s to 50 MB/s?

 

Similiar to my just preclearing 2 WD 2TB drives.  From other readings, the speed difference is normal due to where on the platter you are reading.  Joe could give a better explanation than I.

 

Since you are in the post-read, you could calculate the estimated time remaining by taking the full size in bytes minus already read, divide that by 1048576 to get MB, then divide that by 50MB/s (or whatever your current speed is) which will give you seconds, divide that by 60 to get approx minutes left.

Share this post


Link to post

Hi!

 

I'm currently preclearing a new Samsung 2TB drive and it really takes forever. The post-read is still in progress and over 29 hours have elapsed since I've started preclear. Is it normal that it takes that long to preclear a drive?

Yes.  Quite normal.  A 2TB drive usually takes between 33 and 36 hours depending on what else is going on on the server.  If you are doing a lot of other disk IO, it could take a bit longer.

And is it also normal that the read speed drops from around 105 MB/s to 50 MB/s?

Yes, also normal.  The inner cylinders on the disk do not hold as much data as the outer ones because their tracks are not as long, since the rotational speed is constant, the potential "read rate" of inner cylinders is always slower.

 

Let's assume an average "read" speed of 75 MB/s.  That means you'll read 1000 MB (1 GB) in 13.333 seconds.

We need to read 2000 GB (2TB) so, we would get at best 13.333 * 2000 seconds = 26,666.666 seconds

26,666 seconds = 444.44 minutes

444.44 minutes = 7.4 hours.

 

So, 7.4 hours roughly just to read the entire disk, and you cannot speed that up no matter what you do, and that does not count the time verifying the zeros were written properly in the post read phase.

 

Joe L.

Share this post


Link to post

Thanks for the replys. I knew that the speed varies depending where on the platter the disk is reading but I am surprised by the huge difference. It's down to 47 MB/s right now that's less than half the initial value.

 

But if that is normal  I'm reassured. Thanks again  :)

Share this post


Link to post

Thanks for the replys. I knew that the speed varies depending where on the platter the disk is reading but I am surprised by the huge difference. It's down to 47 MB/s right now that's less than half the initial value.

 

But if that is normal  I'm reassured. Thanks again  :)

The circumference of those inner cylinders is a lot smaller than the outer.  The disk manufacturers like to boast about the peak speeds on the outer cylinders, they seldom talk about the slower sustained speeds on the inner cylinders.  :'(

Share this post


Link to post

Another question :) The disk has been successfully precleared. It took 30 hours and 23 minutes.

 

But there are some SMART values which I'm not sure if they might indicate an issue.

 

< 1 Raw_Read_Error_Rate  0x002f  100  100  051  Pre-fail  Always - 2

> 1 Raw_Read_Error_Rate  0x002f  100  100  051  Pre-fail  Always - 4

 

Is this anything I have to worry about?

 

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.