LinuxQuestions.org - 2TB HDD and badblocks

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - 2TB HDD and badblocks (https://www.linuxquestions.org/questions/linux-newbie-8/2tb-hdd-and-badblocks-815010/)

2TB HDD and badblocks

Not sure where else to put this, but has anyone else ran the badblocks command on a 2TB drive? I've been running it as follows:

badblocks -wvs /dev/sda

This is a brand new drive and apparently the "Testing with pattern" stage went by pretty quick, however now I'm on the "Reading and comparing" stage and it's taking forever. Every so often it lists off a rather large number followed by the time elapsed.

At the same time I'm running badblocks on an older 200GB drive with bad sectors and it's already on the 2nd pass with no similar listing as the new drive. According to dmesg I'm getting these messages:

Code:

[78595.927302] ata1.00: status: { DRDY ERR }

[78595.927305] ata1.00: error: { UNC }

[78595.948629] ata1.00: configured for UDMA/100

[78595.948637] ata1: EH complete

[78599.702318] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

[78599.702322] ata1.00: BMDMA stat 0x25

[78599.702327] ata1.00: failed command: READ DMA EXT

[78599.702335] ata1.00: cmd 25/00:80:40:53:6f/00:00:14:00:00/e0 tag 0 dma 65536 in

[78599.702336]          res 51/40:00:85:53:6f/40:00:14:00:00/e0 Emask 0x9 (media error)

[78599.702340] ata1.00: status: { DRDY ERR }

[78599.702343] ata1.00: error: { UNC }

[78599.724531] ata1.00: configured for UDMA/100

[78599.724541] sd 0:0:0:0: [sda] Unhandled sense code

[78599.724544] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

[78599.724548] sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]

[78599.724553] Descriptor sense data with sense descriptors (in hex):

[78599.724555]        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 

[78599.724565]        14 6f 53 85 

[78599.724569] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed

[78599.724575] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 14 6f 53 40 00 00 80 00

[78599.724584] end_request: I/O error, dev sda, sector 342840197

[78599.724592] ata1: EH complete

The new drive is a SATA drive if that makes any difference... this is running off of the latest systemrescueCD distro...

What do you want to achieve if the bad blocks are managed by the controller and transparent to the user?

What is the question? A 2 TB is ten times larger than a 200Gig HD; you would certainly expect it to take 10X to run.

I wouldn't worry about the sense errors; usually that just means the drive has to re-read the sector. May have come about because of vibration or some external influence. It isn't an issue unless the drive fails repeatedly to read the sector.

I see... I suppose my question wasn't more along the lines of why is it taking longer, but more as to why I'm seeing a bunch of lines with increasing numbers along with the elapsed time for the new drive while the smaller, older drive does not.

Minor drive errors are normal if it gets the data without the click of death.

So in theory a second pass on this new drive should not yield much, if any, errors?

So in theory a second pass should not yield as much, if any, errors then?

^ It likely still will.

Isn't badblocks supposed to eliminate that eventually even on a bad drive?

But those are probably not bad blocks but rather controller errors.