0
My hard drive has a few bad blocks, so I'm trying to get a list of them all in order to bypass them when creating a new ext4 filesystem, like this:
badblocks -wsv -o badblocks_sdf.txt /dev/sdf
As soon as it actually hits a bad block, every other block after that fails.
My syslog is filled with these messages:
[91197.287574] blk_update_request: I/O error, dev sdf, sector 4563147104
[91202.286344] scsi_io_completion: 126841 callbacks suppressed
[91202.286352] sd 3:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[91202.286360] sd 3:0:0:0: [sdf] tag#0 CDB: Read(16) 88 00 00 00 00 01 0f ff f8 50 00 00 00 08 00 00
[91202.286362] blk_update_request: 126841 callbacks suppressed
[91202.286364] blk_update_request: I/O error, dev sdf, sector 4563400784
[91202.286956] sd 3:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[91202.286962] sd 3:0:0:0: [sdf] tag#0 CDB: Read(16) 88 00 00 00 00 01 0f ff f8 50 00 00 00 08 00 00
Is that expected behaviour, can something be done about it?
It seems logical you should be reading each sector to determine the bad sectors instead of wrtitting – Ramhound – 2016-09-14T23:22:50.747