[SOLVED] how to fix : Buffer I/O error on dev sdc, logical block 122096624, async page read

BW-userx · 08-18-2018, 08:04 PM

WD 500 GB blue HDD find. I'm trying to get it to work as it is a 98% chance it took a beating. I found it still attached to a destroyed laptop in the trash bin at a bus stop.

they ripped it in half and such.

I've got it to finally see it beyond just dmesg then wiped it, screwed it up and now am trying to fix it.

I used fdisk to give it a new partition table, then at this posting I've used cfdisk and gave it the entire HDD for a partition not formatting it after I ran fsck on it.

as the last time I ran formatting on it it was sitting for over an hour saying writing to the HDD whatever I do not remember, I've never really use the cli for formatting, I use gparted, but gparted is hanging, prob due to the bad block thing, so I went CLI on it.

anyways this is where it is sitting at the time of this posting.

Quote:

[ 66.389438] usb-storage 4-2:1.0: USB Mass Storage device detected
[ 66.389743] scsi host6: usb-storage 4-2:1.0
[ 67.411006] scsi 6:0:0:0: Direct-Access WDC WD50 00LPCX-24VHAT0 0003 PQ: 0 ANSI: 6
[ 67.411862] sd 6:0:0:0: [sdc] 976773120 512-byte logical blocks: (500 GB/466 GiB)
[ 67.412311] sd 6:0:0:0: [sdc] Write Protect is off
[ 67.412316] sd 6:0:0:0: [sdc] Mode Sense: 27 00 00 00
[ 67.412791] sd 6:0:0:0: [sdc] No Caching mode page found
[ 67.412800] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 67.480894] sdc:
[ 67.482795] sd 6:0:0:0: [sdc] Attached SCSI disk
[ 72.259254] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 72.259263] sd 6:0:0:0: [sdc] tag#0 Sense Key : Aborted Command [current]
[ 72.259269] sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
[ 72.259276] sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 3a 38 5f 80 00 00 08 00
[ 72.259282] print_req_error: I/O error, dev sdc, sector 976772992
[ 74.326801] radeon_dp_aux_transfer_native: 368 callbacks suppressed
[ 78.907565] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 78.907569] sd 6:0:0:0: [sdc] tag#0 Sense Key : Aborted Command [current]
[ 78.907571] sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
[ 78.907574] sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 3a 38 5f 80 00 00 08 00
[ 78.907576] print_req_error: I/O error, dev sdc, sector 976772992
[ 78.907581] Buffer I/O error on dev sdc, logical block 122096624, async page read

-------------
fsck on a raw non formatted hdd , couldn't remember if I format it or not, I've been messing with this HDD for a few hours now.

Quote:

$ sudo fsck.ext4 /dev/sdc
e2fsck 1.44.3 (10-July-2018)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdc

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>

/dev/sdc contains `DOS/MBR boot sector' data

Keruskerfuerst · 08-18-2018, 11:29 PM

You should buy a new HDD/SSD.

BW-userx · 08-19-2018, 09:15 AM

It was a freebie I found it still attached to a ripped in half laptop in the trash. I was just hoping I could salvage it. Thanks.