Input output error during read on dev sdb

fdisk works on disks, not partitions. On Linux, a disk is referred to as e.g. /dev/sdb, whereas the partitions on it are referred to as /dev/sdb1, /dev/sdb2 etc. Note that old-style (/dev/[hs]d?, /dev/[hs]d??) partition specifiers always end with a digit, whereas disk specifiers always end with a letter.

If you just format the disk (no bad blocks checking etc.), then a format time of a few seconds is not entirely unreasonable. All you did was write the initial file system metadata structures to disk, and while I don’t have any exact numbers to cite, those are fairly small, and USB is pretty fast for writing such relatively small amounts of data. If you didn’t get any errors, the format process probably did its thing.

The first thing you should do is run fdisk on the proper device. In your case, it sounds like that will be sudo fdisk /dev/sdb, but note that in some cases the device name can change with time. I recommend using one of the entries in /dev/disk/by-id instead, as those will not change. You can see what the disk shows up with there by running, immediately before you connect the disk:

diff <(ls /dev/disk/by-id) <(sleep 15; ls /dev/disk/by-id)

This will show the differences in directory content between the two executions of ls, which will be spaced 15 seconds apart thanks to the sleep invocation in the second input pipe. 15 seconds should give the kernel enough time to identify the disk and let udev create the appropriate device nodes. If it doesn’t show any differences (empty output), unplug the disk and try it again increasing the delay. You will see both partition devices (ending with -part followed by a number and possibly @) and disk devices (without the -part part). If the file names do end with @, disregard that character; it’s a ls output artefact.

Once you have partition(s) properly in place, you can make a file system on it/them. For example, sudo mkfs.ext4 -v /dev/disk/by-id/xxxxx-Passport-XXXXXXX-part1. The -v turns on extra output («v» for verbose) which will give you an idea of whether the file system is created successfully.

After that, the disk should be perfectly usable.

Complete error log:

SMART Error Log Version: 1
ATA Error Count: 21225 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It «wraps» after 49.710 days.

Error 21225 occurred at disk power-on lifetime: 8408 hours (350 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
40 51 00 00 00 00 40 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————— ———————
60 08 00 00 00 00 00 08 00:08:02.389 READ FPDMA QUEUED
ef 10 02 00 00 00 00 08 00:08:02.378 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 00 08 00:08:02.378 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 08 00:08:02.375 IDENTIFY DEVICE
ef 03 46 00 00 00 00 08 00:08:02.375 SET FEATURES [Set transfer mode]

Error 21224 occurred at disk power-on lifetime: 8408 hours (350 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
40 51 00 00 00 00 40 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————— ———————
60 08 00 00 00 00 00 08 00:07:59.163 READ FPDMA QUEUED
ef 10 02 00 00 00 00 08 00:07:59.163 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 00 08 00:07:59.161 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 08 00:07:59.160 IDENTIFY DEVICE
ef 03 46 00 00 00 00 08 00:07:59.160 SET FEATURES [Set transfer mode]

Error 21223 occurred at disk power-on lifetime: 8408 hours (350 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
40 51 00 00 00 00 40 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————— ———————
60 08 00 00 00 00 00 08 00:07:56.113 READ FPDMA QUEUED
ef 10 02 00 00 00 00 08 00:07:56.113 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 00 08 00:07:56.113 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 08 00:07:56.110 IDENTIFY DEVICE
ef 03 46 00 00 00 00 08 00:07:56.110 SET FEATURES [Set transfer mode]

Error 21222 occurred at disk power-on lifetime: 8408 hours (350 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
40 51 00 00 00 00 40 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————— ———————
60 08 00 00 00 00 00 08 00:07:53.064 READ FPDMA QUEUED
ef 10 02 00 00 00 00 08 00:07:53.064 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 00 08 00:07:53.064 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 08 00:07:53.061 IDENTIFY DEVICE
ef 03 46 00 00 00 00 08 00:07:53.061 SET FEATURES [Set transfer mode]

Error 21221 occurred at

Hi all.

This is my first post in the forum. Since English is not my mother language, if I did not describe something clearly just let me know and I will try my best again. Much thanks.

I am trying to rescue a portable hard drive but right now I cannot figure out what happened to it. Previously I know this disk has some connection problems but it was not so serious, and I can still mount the disk after serveral times pluging. and unpluging.

But right now it seems it is totally down. When connected via USB port it sounds like it only spins less than 1 sec. Then I heard a snap and it stops. This repeats 3 times then it is totally silent. I guess it may be caused by not sufficient power so I’ve tried another port and it behaves like spin, snap, spin, snap without an end.

When tried with lsblk, it shows a raw disk without partitions. I dissected the wrapper and saw the hard drive is marked 500GB, but it is recognized as 2TB in lsblk. I cannot remember how large it should be when it still worked sorry.

What I have tested so far are:
hdparm:

 delta67@Pollux  ~  sudo hdparm -I /dev/sdb

/dev/sdb:

ATA device, with non-removable media
Standards:
	Likely used: 5
Configuration:
	Logical		max	current
	cylinders	0	0
	heads		0	0
	sectors/track	0	0
	--
	Logical/Physical Sector size:           512 bytes
	device size with M = 1024*1024:           0 MBytes
	device size with M = 1000*1000:           0 MBytes 
	cache/buffer size  = unknown
Capabilities:
	IORDY(may be)(cannot be disabled)
	Standby timer values: spec'd by Vendor
	R/W multiple sector transfer: Max = 0	Current = ?
	DMA: not supported
	PIO: pio0 
Logical Unit WWN Device Identifier: 50014ee6abe7ac97
	NAA		: 5
	IEEE OUI	: 0014ee
	Unique ID	: 6abe7ac97
Checksum: correct

parted:

(parted) mkpart primary btrfs 0 10
Error: /dev/sdb: unrecognised disk label
(parted) mklabel gpt                                                      
Error: Input/output error during read on /dev/sdb
Retry/Ignore/Cancel? ^C                                                   
Error: Input/output error during write on /dev/sdb
Retry/Ignore/Cancel? ^C

PS: when I chose cancel or ignore, parted did not respond any more.

fdisk:

 delta67@Pollux  ~  sudo fdisk -l /dev/sdc
fdisk: cannot open /dev/sdc: Input/output error

dmesg:

[189049.345604] sd 20:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[189049.345608] sd 20:0:0:0: [sdb] tag#0 Sense Key : 0x5 [current] 
[189049.345610] sd 20:0:0:0: [sdb] tag#0 ASC=0x20 ASCQ=0x0 
[189049.345613] sd 20:0:0:0: [sdb] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[189049.345615] blk_update_request: critical target error, dev sdb, sector 0
[189049.345617] Buffer I/O error on dev sdb, logical block 0, async page read

I’ve also tried testdisk and did a quick search but had no luck. The deep search gives IO error for every bit it reads.

I am not so sure if it is still the connection problem. And if the disk is partly broken, is there any way that I may rescue at least some of the data inside?

Thanks again for everyone.

Last edited by delta67 (2016-04-14 10:17:18)

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1]   Вверх