cannot open /dev/sdb: Input/output error on installing new hard drive

So recently I was salvaging parts of my old DishTV receiver after switching to streaming services and found a "Seagate Video 3.5 HDD, 1000GB Model so of course, I installed it into my personal PC. I have it mounted, both SATA and power are plugged in, and my pc recognizes it but I can't mount, access the data, or reformat it in any way with any method. The error I get on most commands is cannot open /dev/sdb: Input/output error

I don't know if I've installed the drive itself wrong or if it’s software/OS related, but I’d be grateful for any help.

here is some output of various commands used in other solutions online (none of which worked for me):

[wyattn@wyatt-pc ~]$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0    7:0    0  44.9M  1 loop /var/lib/snapd/snap/gtk-common-themes/1440
loop1    7:1    0 163.7M  1 loop /var/lib/snapd/snap/spotify/41
loop2    7:2    0 160.2M  1 loop /var/lib/snapd/snap/gnome-3-28-1804/116
loop3    7:3    0  58.9M  1 loop /var/lib/snapd/snap/discord/108
loop4    7:4    0  54.7M  1 loop /var/lib/snapd/snap/core18/1668
loop5    7:5    0 415.9M  1 loop /var/lib/snapd/snap/libreoffice/173
loop6    7:6    0  24.7M  1 loop /var/lib/snapd/snap/snapd/6434
sda      8:0    0 698.7G  0 disk 
├─sda1   8:1    0 165.7G  0 part /run/media/wyattn/HP
├─sda2   8:2    0  11.3G  0 part /run/media/wyattn/FACTORY_IMAGE
└─sda3   8:3    0 521.6G  0 part /
sdb      8:16   0   3.9G  0 disk 
[wyattn@wyatt-pc ~]$ sudo fdisk /dev/sdb

Welcome to fdisk (util-linux 2.35.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open /dev/sdb: Input/output error
[wyattn@wyatt-pc ~]$ sudo fdisk -l
Disk /dev/loop0: 44.9 MiB, 47063040 bytes, 91920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 163.68 MiB, 171618304 bytes, 335192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 160.16 MiB, 167931904 bytes, 327992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 58.87 MiB, 61710336 bytes, 120528 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 54.66 MiB, 57294848 bytes, 111904 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 415.89 MiB, 436072448 bytes, 851704 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 24.73 MiB, 25915392 bytes, 50616 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[wyattn@wyatt-pc ~]$ sudo sfdisk -l
Disk /dev/loop0: 44.9 MiB, 47063040 bytes, 91920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 163.68 MiB, 171618304 bytes, 335192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 160.16 MiB, 167931904 bytes, 327992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 58.87 MiB, 61710336 bytes, 120528 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 54.66 MiB, 57294848 bytes, 111904 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 415.89 MiB, 436072448 bytes, 851704 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 24.73 MiB, 25915392 bytes, 50616 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[wyattn@wyatt-pc ~]$ sudo fsck /dev/sdb
fsck from util-linux 2.35.1
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext2: Input/output error while trying to open /dev/sdb

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>

[wyattn@wyatt-pc ~]$ sudo file -s /dev/sdb
/dev/sdb: ERROR: cannot read `/dev/sdb' (Input/output error)
[wyattn@wyatt-pc ~]$ sudo fdisk -l /dev/sdb
fdisk: cannot open /dev/sdb: Input/output error
[wyattn@wyatt-pc ~]$ sudo ntfsinfo -m /dev/sdb
Error reading bootsector: Input/output error
Failed to mount '/dev/sdb': Input/output error
NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!
The usage of the /f parameter is very IMPORTANT! No modification was
made to NTFS by this software.
Failed to open '/dev/sdb'.

Also the output of inxi -Fxxxz

[wyattn@wyatt-pc ~]$ inxi -Fxxxz
System:
  Host: wyatt-pc Kernel: 5.5.8-1-MANJARO x86_64 bits: 64 compiler: gcc 
  v: 9.2.1 Desktop: Xfce 4.14.2 tk: Gtk 3.24.13 info: xfce4-panel wm: xfwm4 
  dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:
  Type: Desktop System: HP-Pavilion product: KQ497AA-ABA m9340f v: N/A 
  serial: <filter> Chassis: Hewlett-Packard type: 3 serial: <filter> 
  Mobo: PEGATRON model: Benicia v: 1.01 serial: <filter> 
  BIOS: American Megatrends v: 5.23 date: 04/21/2008 
Battery:
  Device-1: hidpp_battery_0 
  model: Logitech M720 Triathlon Multi-Device Mouse serial: <filter> 
  charge: 100% (should be ignored) rechargeable: yes status: Discharging 
CPU:
  Topology: Quad Core model: Intel Core2 Quad Q6700 bits: 64 type: MCP 
  arch: Core Merom rev: B L2 cache: 4096 KiB 
  flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 21341 
  Speed: 1617 MHz min/max: 1600/2667 MHz Core speeds (MHz): 1: 1675 2: 2359 
  3: 1600 4: 1600 
Graphics:
  Device-1: NVIDIA G96 [GeForce 9500 GS] vendor: Micro-Star MSI 
  driver: nouveau v: kernel bus ID: 05:00.0 chip ID: 10de:0644 
  Display: x11 server: X.Org 1.20.7 driver: nouveau unloaded: modesetting 
  alternate: fbdev,nv,vesa resolution: 1680x1050~60Hz 
  OpenGL: renderer: NV96 v: 3.3 Mesa 19.3.5 direct render: Yes 
Audio:
  Device-1: Intel 82801I HD Audio vendor: Hewlett-Packard Asus IPIBL-LB 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:293e 
  Device-2: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video 
  Decoder with 3D Comb 
  vendor: Hauppauge works driver: cx23885 v: 0.0.4 bus ID: 03:00.0 
  chip ID: 14f1:8880 
  Sound Server: ALSA v: k5.5.8-1-MANJARO 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Hewlett-Packard Asus IPIBL-LB driver: r8169 v: kernel port: e800 
  bus ID: 02:00.0 chip ID: 10ec:8168 
  IF: enp2s0 state: down mac: <filter> 
  Device-2: Ralink RT2790 Wireless 802.11n 1T/2R PCIe vendor: Lite-On 
  driver: rt2800pci v: 2.3.0 port: e800 bus ID: 04:00.0 chip ID: 1814:0781 
  IF: wlp4s0 state: up mac: <filter> 
Drives:
  Local Storage: total: 702.50 GiB used: 217.26 GiB (30.9%) 
  ID-1: /dev/sda vendor: Hitachi model: HDS721075KLA330 size: 698.64 GiB 
  speed: 3.0 Gb/s serial: <filter> rev: A87A scheme: MBR 
  ID-2: /dev/sdb vendor: Seagate model: ST1000VM002 size: 3.86 GiB 
  speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> rev: SC12 
RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 
  port: b080 bus ID: 00:1f.2 chip ID: 8086.2822 rev: 02 
Partition:
  ID-1: / size: 512.44 GiB used: 56.82 GiB (11.1%) fs: ext4 dev: /dev/sda3 
Sensors:
  System Temperatures: cpu: 40.0 C mobo: N/A gpu: nouveau temp: 43 C 
  Fan Speeds (RPM): N/A gpu: nouveau fan: 0 
Info:
  Processes: 225 Uptime: 2h 30m Memory: 5.81 GiB used: 1.97 GiB (34.0%) 
  Init: systemd v: 244 Compilers: gcc: 9.2.1 Shell: bash v: 5.0.16 
  running in: xfce4-terminal inxi: 3.0.37 

$ sudo ntfsinfo -m /dev/sdb
Error reading bootsector: Input/output error
Failed to mount '/dev/sdb': Input/output error
NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!
The usage of the /f parameter is very IMPORTANT! No modification was
made to NTFS by this software.
Failed to open '/dev/sdb'.

If the disk is NTFS formatted, did you try this?

Unfortunately the only windows device I have is a laptop and I can’t plug that drive into it to try that

If it is actually NTFS, that would be the best option. However, from a Linux system you could use ntfsfix but:

ntfsfix is a utility that fixes some common NTFS problems. ntfsfix is NOT a Linux version of chkdsk. It only repairs some fundamental NTFS inconsistencies, resets the NTFS
journal file and schedules an NTFS consistency check for the first boot into Windows.

see man ntfsfix

Try anyway:

sudo ntfsfix -bd /dev/sdb

the output:

Mounting volume... Error reading bootsector: Input/output error
Failed to sync device /dev/sdb: Input/output error
FAILED
Attempting to correct errors... Error reading bootsector: Input/output error
Failed to sync device /dev/sdb: Input/output error
FAILED
Failed to startup volume: Input/output error
Error reading bootsector: Input/output error
Volume is corrupt. You should run chkdsk.

Volume is corrupt. You should run chkdsk.

I am short of ideas here as to what course of action to suggest. Everything so far points to fixing the issue in a Windows system.

Perhaps I could make a windows partition on my pc and try there

That is also a tricky business if you are going to install Windows after your Linux installation. Many times it tends to overwrite your boot record and cause other calamties. Is your system installed in UEFI or Legacy mode? Could you post the output of sudo parted -l ?

the output of sudo parted -l:

[wyattn@wyatt-pc ~]$ sudo parted -l
Model: ATA Hitachi HDS72107 (scsi)
Disk /dev/sda: 750GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size    Type     File system  Flags
 1      32.3kB  178GB  178GB   primary  ntfs         boot
 3      178GB   738GB  560GB   primary  ext4
 2      738GB   750GB  12.2GB  primary  ntfs


Error: /dev/sdb: unrecognised disk label
Warning: Error fsyncing/closing /dev/sdb: Input/output error
Retry/Ignore? Retry                                                       
Warning: Error fsyncing/closing /dev/sdb: Input/output error
Retry/Ignore? Ignore                                                      
Model: ATA ST1000VM002 (scsi)
Disk /dev/sdb: 4142MB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags: 

If you would have the possibility to take the drive to a local computer repair shop (or some friend with Windows) that would be an alternative to installing Windows.

You could of courrse make some space in your disk for installing Windows. You have a disk with msdos partition table, so we are dealing with an installation in legacy/mbr mode. You need to make sure to boot your installation media in legacy mode. I am not sure what you got in the partiton #1 but it is an NTFS file system with boot flag indicating a Windows install or the remnant of one.

At any rate, you should make sure to have a Manjaro live usb. Installing Windows will surely overwrite Manjaro's bootloader. You could use the live usb later to restore it.

That partition is a very old (circa 2008) partition containing a very broken windows vista. I only have it because there are a ton of pictures from years ago that I have yet to move over to my Linux (that and there’s some games and nostalgia hooked to it as it was my first ever computer and OS) would chkdsk work in that old of a system

Looks like it can! I had to look it up;


and

Good luck!

  1. Can you try to use Gparted ?
  2. Maybe the SATA or power cable is defective.

So I am having the same exact issue, but with Western Digital drives. I have run chkdsk /r on the disk(s) and Windows finds no errors, yet the problem persists in Manjaro (input/output error). What's interesting, if I insert a cloned seagate drive, the issues dissappear (Grub Update hangs for hours in dual boot Manjaro/XP).
from dmesg:

blk_update_request: I/O error, dev sdb, sector 976773160 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Buffer I/O error on dev sdb, logical block 122096645, async page read

But just prior to this I ran chkdsk /f on the same drive in Windows without one error. Rebooted twice afterwards. Drive was accessible in Windows and read/write functions worked as expected.

Another interesting twist: If I pull the same drive that was giving me errors while connected via SATA to the mobo, and connect it via usb to the same pc, then run smartctl -a /dev/sdf which previously would report Input/Output errors, I get the following:

sudo smartctl -a /dev/sdf
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.39-1-MANJARO] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green
Device Model:     WDC WD5000AADS-00M2B0
Serial Number:    WD-WCAV5U434434
LU WWN Device Id: 5 0014ee 205f975e1
Firmware Version: 01.00A01
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Wed May 13 21:25:09 2020 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(10380) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 122) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x3037)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   204   183   021    Pre-fail  Always       -       5791
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       201
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       885
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       167
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       48
193 Load_Cycle_Count        0x0032   197   197   000    Old_age   Always       -       9423
194 Temperature_Celsius     0x0022   120   106   000    Old_age   Always       -       27
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       1
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Hello. I am having similar problems. HDD was running fine and passes all tests under Windows and Linux (in fact it's a "new" Seagate 6-Tb HDD). But its partitions are not found at boot time. Then later I get this error, over and over:

[   10.925153] ata1.00: irq_stat 0x40000000
[   10.929102] ata1.00: failed command: READ DMA
[   10.933485] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 16 dma 4096 in
[   10.933485]          res 53/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[   10.948630] ata1.00: status: { DRDY SENSE ERR }
[   10.953179] ata1.00: error: { ABRT }
[   10.957031] ata1.00: configured for UDMA/133 (device error ignored)
[   10.963359] ata1: EH complete
[   10.978687] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   10.985155] ata1.00: irq_stat 0x40000000

When I run smarctctl -a /dev/sdb I get:

**Read SMART Data failed: scsi error badly formed scsi parameters**

When I run sudo ntfsfix -n /dev/sdb I get:

Mounting volume... Error reading bootsector: Input/output error
FAILED
Attempting to correct errors... Error reading bootsector: Input/output error
FAILED
Failed to startup volume: Input/output error
Error reading bootsector: Input/output error
Volume is corrupt. You should run chkdsk.
No change made

I'll post further info later but I want to keep this thread open.

Forum kindly sponsored by