bad block/superblock on new disk?

[Karl Auer]

On Sat, 2020-05-23 at 15:43 +0200, M. Fioretti wrote:
> dmesg says:
> 
> [256797.921297] print_req_error: critical medium error, dev sdb,
> sector 0
> [256802.521195] sd 6:0:0:0: [sdb] tag#0 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_SENSE
> [256802.521241] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error
> [current]
> [256802.521250] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read
> error
> [256802.521260] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00
> 00 00 00 08 00
> [256802.521269] print_req_error: critical medium error, dev sdb,
> sector 0
> [256802.521285] Buffer I/O error on dev sdb, logical block 0, async
> page read

If I saw that on a new drive I would just return the drive for a refund
or replacement. At pennies per gigabyte these days (not to mention the
fact that some manufacturers refurbish and resell returns), life's too
short to muck about trying to figure out storage failures.

The only thing that gives me (slight) pause is the fact that it's in an
enclosure - try a different one before giving up, or if you have a
spare drive bay in a desktop, try it there. Enclosures are cheap too,
or borrow one for a few hours.

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: 2561 E9EC D868 E73C 8AF1 49CF EE50 4B1D CCA1 5170
Old fingerprint: 8D08 9CAA 649A AFEF E862 062A 2E97 42D4 A2A0 616D