Badblocks test for WD60EFRX?

Status
Not open for further replies.

TooMuchData

Contributor
Joined
Jan 4, 2015
Messages
188
I'm burning-in some 6TB WD Red drives. I attempted to run badblocks and got the following error:

[jeff@freenas ~]# badblocks -wsv /dev/ada0
badblocks: Value too large to be stored in data type invalid end block (58605225
84): must be 32-bit value

The command fails for any of the 6TB drives, but runs properly for a 1TB drive. Does badblocks not support the larger disks?

Any suggestions will be appreciated.

Running FreeNAS 9.3 Stable 20150109 on ASRock C2750D4I with Crucial (2 x 8GB) CT2KIT102472BD160B, Seasonic SSR-450RM, Node 304 case. No Zpools defined yet.

Thanks for your help.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
If I'm reading that right, badblocks is limited to 2^32 sectors...? Since it defaults to 1024 byte sectors, it would seem that badblocks can only be used on disks up to 4TB. That's... very weird.

For now, I'd recommend you try jgreco's script instead.

Edit: Setting the block size to 4096 might allow you to hack around the problem.
 
Last edited:

Fraoch

Patron
Joined
Aug 14, 2014
Messages
395

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Doesn't matter. The drive uses 4k sectors internally, anyway.
 

TooMuchData

Contributor
Joined
Jan 4, 2015
Messages
188
Thanks again, Ericloewe.

I'll ask another question, please.

My new WD 6TB drives average 170 MB/s serial and parallel read rates. The individual rates range from 165 (97%) to 173 (102%). Does that variability seem reasonable? (I would think so, but don't know how consistent these devices should be). None of the drives have thrown an error in 10 days of constant testing, and none of them has any reassigned sectors.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
I don't have hard data to offer you, but +-3% is not something I'd worry about.

The only problematic ones are the obviously bad ones, where no question remains.
 
Status
Not open for further replies.
Top