Linux fdisk input output error

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.

I have been trying to install Ubuntu 18.04, but when starting I get this error message:

Input/Output error during read on /dev/sda

I can’t make partitions. Also I tried working this out with other Linux distros, like Manjaro GNOME, which was the OS I previously had, which messed up completely so had to remove it from the disk. I need some help here as my hard disk seems to be fine. Right now I am uploading this query using Try Ubuntu before installation. I checked if my bootable flash drive has any problem, but it doesn’t. My SATA configuration is also set to AHCI. I have formatted my hard drive, and it is recognized by the OS.

On viewing my hard disk using Disk Utility:

$ sudo fdisk -l
Disk /dev/loop0: 1.9 GiB, 2029981696 bytes, 3964808 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: 89.1 MiB, 93417472 bytes, 182456 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: 54.7 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/loop3: 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/loop4: 160.2 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/loop5: 4.2 MiB, 4403200 bytes, 8600 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: 14.8 MiB, 15462400 bytes, 30200 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/loop7: 956 KiB, 978944 bytes, 1912 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/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 4ACBAC48-BCA6-43C2-B3E6-35A0B2243FD7

Device       Start        End    Sectors  Size Type
/dev/sda1     2048    1050623    1048576  512M EFI System
/dev/sda2  1050624 1953523711 1952473088  931G Linux filesystem


Disk /dev/sdb: 14.5 GiB, 15597568000 bytes, 30464000 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
Disklabel type: dos
Disk identifier: 0x14f142f8

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdb1  *     2048 30463999 30461952 14.5G  c W95 FAT32 (LBA)


Disk /dev/loop8: 3.7 MiB, 3825664 bytes, 7472 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
ubuntu@ubuntu:~$ sudo fsck -f /dev/sda2
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda2

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>

On tail -f /var/log/syslog:

Apr 22 16:51:44 ubuntu kernel: [  175.979044] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 22 16:51:44 ubuntu kernel: [  175.979050] ata1.00: cmd 61/08:00:00:08:10/00:00:20:00:00/40 tag 0 ncq dma 4096 out
Apr 22 16:51:44 ubuntu kernel: [  175.979050]          res 40/00:08:00:64:70/00:00:74:00:00/40 Emask 0x10 (ATA bus error)
Apr 22 16:51:44 ubuntu kernel: [  175.979053] ata1.00: status: { DRDY }
Apr 22 16:51:44 ubuntu kernel: [  175.979055] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 22 16:51:44 ubuntu kernel: [  175.979060] ata1.00: cmd 61/00:08:00:64:70/04:00:74:00:00/40 tag 1 ncq dma 524288 out
Apr 22 16:51:44 ubuntu kernel: [  175.979060]          res 40/00:08:00:64:70/00:00:74:00:00/40 Emask 0x10 (ATA bus error)
Apr 22 16:51:44 ubuntu kernel: [  175.979062] ata1.00: status: { DRDY }
Apr 22 16:51:44 ubuntu kernel: [  175.979065] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 22 16:51:44 ubuntu kernel: [  175.979070] ata1.00: cmd 61/00:e8:00:08:10/04:00:00:00:00/40 tag 29 ncq dma 524288 out
Apr 22 16:51:44 ubuntu kernel: [  175.979070]          res 40/00:08:00:64:70/00:00:74:00:00/40 Emask 0x10 (ATA bus error)
Apr 22 16:51:44 ubuntu kernel: [  175.979072] ata1.00: status: { DRDY }
Apr 22 16:51:44 ubuntu kernel: [  175.979075] ata1.00: failed command: READ FPDMA QUEUED
Apr 22 16:51:44 ubuntu kernel: [  175.979080] ata1.00: cmd 60/08:f0:a0:61:70/00:00:74:00:00/40 tag 30 ncq dma 4096 in
Apr 22 16:51:44 ubuntu kernel: [  175.979080]          res 40/00:08:00:64:70/00:00:74:00:00/40 Emask 0x10 (ATA bus error)
Apr 22 16:51:44 ubuntu kernel: [  175.979082] ata1.00: status: { DRDY }
Apr 22 16:51:44 ubuntu kernel: [  175.979084] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 22 16:51:44 ubuntu kernel: [  175.979088] ata1.00: cmd 61/08:f8:00:08:12/00:00:00:00:00/40 tag 31 ncq dma 4096 out
Apr 22 16:51:44 ubuntu kernel: [  175.979088]          res 40/00:08:00:64:70/00:00:74:00:00/40 Emask 0x10 (ATA bus error)
Apr 22 16:51:44 ubuntu kernel: [  175.979090] ata1.00: status: { DRDY }
Apr 22 16:51:44 ubuntu kernel: [  175.979096] ata1: hard resetting link

Apr 24 04:11:48 ubuntu kernel: [  222.190508] ata1.00: detaching (SCSI 0:0:0:0)
Apr 24 04:11:48 ubuntu kernel: [  222.190714] blk_update_request: I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
Apr 24 04:11:48 ubuntu kernel: [  222.190722] Buffer I/O error on dev sda, logical block 0, lost async page write
Apr 24 04:11:48 ubuntu kernel: [  222.190785] blk_update_request: I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Apr 24 04:11:48 ubuntu kernel: [  222.192117] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Apr 24 04:11:48 ubuntu kernel: [  222.192227] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Apr 24 04:11:48 ubuntu kernel: [  222.192235] sd 0:0:0:0: [sda] Stopping disk
Apr 24 04:11:48 ubuntu kernel: [  222.192268] sd 0:0:0:0: [sda] Start/Stop Unit failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

Apr 24 18:56:21 mayank-X510UNR kernel: [  208.822778] ata1: EH complete
Apr 24 18:56:21 mayank-X510UNR kernel: [  208.846957] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x450100 action 0x6 frozen
Apr 24 18:56:21 mayank-X510UNR kernel: [  208.846964] ata1.00: irq_stat 0x08000000, interface fatal error
Apr 24 18:56:21 mayank-X510UNR kernel: [  208.846969] ata1: SError: { UnrecovData PHYRdyChg CommWake Handshk }
Apr 24 18:56:21 mayank-X510UNR kernel: [  208.846976] ata1.00: failed command: WRITE DMA EXT
Apr 24 18:56:21 mayank-X510UNR kernel: [  208.846985] ata1.00: cmd 35/00:00:00:00:00/00:04:00:00:00/e0 tag 31 dma 524288 out
Apr 24 18:56:21 mayank-X510UNR kernel: [  208.846985]          res 50/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
Apr 24 18:56:21 mayank-X510UNR kernel: [  208.846989] ata1.00: status: { DRDY }
Apr 24 18:56:21 mayank-X510UNR kernel: [  208.846996] ata1: hard resetting link
Apr 24 18:56:21 mayank-X510UNR kernel: [  209.162445] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Apr 24 18:56:21 mayank-X510UNR kernel: [  209.174828] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Apr 24 18:56:21 mayank-X510UNR kernel: [  209.174838] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Apr 24 18:56:21 mayank-X510UNR kernel: [  209.174845] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.228657] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.228674] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.228679] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.257235] ata1.00: configured for UDMA/133
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.266501] ata1: EH complete
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.307284] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x450100 action 0x6 frozen
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.307292] ata1.00: irq_stat 0x08000000, interface fatal error
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.307297] ata1: SError: { UnrecovData PHYRdyChg CommWake Handshk }
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.307302] ata1.00: failed command: WRITE DMA EXT
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.307311] ata1.00: cmd 35/00:00:00:00:00/00:04:00:00:00/e0 tag 2 dma 524288 out
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.307311]          res 50/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.307315] ata1.00: status: { DRDY }
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.307324] ata1: hard resetting link
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.622114] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.634228] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.634236] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.634240] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.686520] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.686528] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.686532] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.714725] ata1.00: configured for UDMA/133
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.724038] ata1: EH complete
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.754765] ata1: limiting SATA link speed to 3.0 Gbps
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.754773] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x450100 action 0x6 frozen
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.754779] ata1.00: irq_stat 0x08000000, interface fatal error
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.754784] ata1: SError: { UnrecovData PHYRdyChg CommWake Handshk }
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.754790] ata1.00: failed command: WRITE DMA EXT
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.754804] ata1.00: cmd 35/00:00:00:00:00/00:04:00:00:00/e0 tag 4 dma 524288 out
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.754804]          res 50/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.754809] ata1.00: status: { DRDY }
Apr 24 18:56:22 mayank-X510UNR kernel: [  209.754820] ata1: hard resetting link
Apr 24 18:56:24 mayank-X510UNR kernel: [  211.967254] ata1: SATA link down (SStatus 1 SControl 320)
Apr 24 18:56:24 mayank-X510UNR kernel: [  211.977178] ata1: hard resetting link
Apr 24 18:56:26 mayank-X510UNR kernel: [  214.187128] ata1: SATA link down (SStatus 1 SControl 320)
Apr 24 18:56:26 mayank-X510UNR kernel: [  214.188545] ata1: hard resetting link
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395665] ata1: SATA link down (SStatus 1 SControl 320)
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395682] ata1.00: disabled
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395742] sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395749] sd 0:0:0:0: [sda] tag#4 Sense Key : Not Ready [current] 
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395754] sd 0:0:0:0: [sda] tag#4 Add. Sense: Logical unit not ready, hard reset required
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395759] sd 0:0:0:0: [sda] tag#4 CDB: Write(10) 2a 00 00 00 00 00 00 04 00 00
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395765] blk_update_request: I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 128 prio class 0
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395775] Buffer I/O error on dev sda, logical block 0, lost async page write
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395793] Buffer I/O error on dev sda, logical block 1, lost async page write
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395798] Buffer I/O error on dev sda, logical block 2, lost async page write
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395802] Buffer I/O error on dev sda, logical block 3, lost async page write
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395806] Buffer I/O error on dev sda, logical block 4, lost async page write
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395810] Buffer I/O error on dev sda, logical block 5, lost async page write
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395815] Buffer I/O error on dev sda, logical block 6, lost async page write
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395819] Buffer I/O error on dev sda, logical block 7, lost async page write
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395823] Buffer I/O error on dev sda, logical block 8, lost async page write
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.395827] Buffer I/O error on dev sda, logical block 9, lost async page write
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396026] ata1: EH complete
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396038] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396051] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396070] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396075] blk_update_request: I/O error, dev sda, sector 131072 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396185] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396200] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396207] blk_update_request: I/O error, dev sda, sector 536870912 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396242] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396250] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396257] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396261] sd 0:0:0:0: [sda] Sense not available.
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396267] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396275] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396282] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396288] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396291] sd 0:0:0:0: [sda] Sense not available.
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396297] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396305] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396314] sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396318] sd 0:0:0:0: [sda] 4096-byte physical blocks
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396324] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396332] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396340] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396347] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396353] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396362] sda: detected capacity change from 1000204886016 to 0
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396420] sd 0:0:0:0: rejecting I/O to offline device
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396435] blk_update_request: I/O error, dev sda, sector 1953523712 op 0x1:(WRITE) flags 0x100000 phys_seg 14 prio class 0
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.396983] ata1.00: detaching (SCSI 0:0:0:0)
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.398145] sd 0:0:0:0: [sda] Stopping disk
Apr 24 18:56:29 mayank-X510UNR kernel: [  216.398193] sd 0:0:0:0: [sda] Start/Stop Unit failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

Доброго времени суток, %username%!

Имеется старый HDD WD Green на 2Tb, который начал откровенно барахлить (появлялись ошибки записи при записи на диск, чтение — без проблем). Была приобретена ему замена HDD WD Red, аналогично на 2Tb. Оба винта успешно подключены к стационарной машине под управлением Win7, «примонтированы» с помощью «Ext2Fsd» и с помощью «MiniTool Partition Wizard Free» создан на нем раздел в Ext4 во всё пространство (ну лень было создавать загрузочный образ с *nix, каюсь).
В общем — все данные с помощью копипаста успешно перенесены со старой железки на новую (права доступа, разумеется — пострадали, но они не критичны). Ошибки кое-где выползали, но сугубо на чтение, и не критичные данные. После чего железка была поставлены на своё родное место под управлением CentOS 7. Раздел успешно примонтировался, но при попытке, например, под рутом сделать рекурсивный chmod — посыпались ошибки вида:

root@data:/shares# chmod -R 777 ./public/
chmod: невозможно получить доступ к «./public/Soft/AntiVirusers/nod32/Tools/NOD32view7_01/NOD32view.psw»: Ошибка ввода/вывода
chmod: невозможно получить доступ к «./public/Soft/ОСИ/Install tool/WinSetupFromUSB-1-6-beta1/files/MULTIpartitionUSBstick/USEonXPor2003_32bitsSYSTEMSonly»: Ошибка ввода/вывода
chmod: невозможно получить доступ к «./public/Soft/ОСИ/Install tool/WinSetupFromUSB-1-6-beta1/files/tools/restore»: Ошибка ввода/вывода
chmod: невозможно получить доступ к «./public/Soft/ОСИ/Install tool/WinSetupFromUSB-1-6-beta1/files/winsetup/usbdrive.tag»: Ошибка ввода/вывода

Смотрим в директорию, и видим:

root@data:/shares# ls -la ./public/Soft/AntiVirusers/nod32/Tools/NOD32view7_01/
ls: невозможно получить доступ к ./public/Soft/AntiVirusers/nod32/Tools/NOD32view7_01/NOD32view.psw: Ошибка ввода/вывода
итого 64
drwxrwxrwx 9 nobody users  4096 янв 11 17:49 .
drwxrwxrwx 3 nobody users  4096 янв 11 17:49 ..
drwxrwxrwx 2 nobody users  4096 янв 11 17:49 avz_upd
drwxrwxrwx 9 nobody users  4096 янв 11 17:49 download
drwxrwxrwx 2 nobody users  4096 янв 11 17:49 drweb_upd
drwxrwxrwx 6 nobody users  4096 янв 11 17:49 eset_upd
drwxrwxrwx 2 nobody users  4096 янв 11 17:49 kav_upd
-rwxrwxrwx 1 nobody users  2724 авг  3  2014 NOD32view.ini
-rwxrwxrwx 1 nobody users 23613 авг  3  2014 NOD32view.log
-????????? ? ?      ?         ?            ? NOD32view.psw
drwxrwxrwx 2 nobody users  4096 янв 11 17:49 Temp
drwxrwxrwx 2 nobody users  4096 янв 11 17:49 tr_upd

Проверка фс говорит что всё ок:

root@data:/# umount /shares/

root@data:/shares# fdisk -l

Disk /dev/sda: 8012 MB, 8012390400 bytes, 15649200 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 label type: dos
Disk identifier: 0x000acd0f

Устр-во Загр     Начало       Конец       Блоки   Id  Система
/dev/sda1   *        2048     1026047      512000   83  Linux
/dev/sda2         1026048    15648767     7311360   8e  Linux LVM

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x73cf5af9

Устр-во Загр     Начало       Конец       Блоки   Id  Система
/dev/sdb1            2048  3907026943  1953512448   83  Linux

Disk /dev/mapper/centos-root: 6635 MB, 6635388928 bytes, 12959744 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/mapper/centos-swap: 801 MB, 801112064 bytes, 1564672 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

root@data:/# fsck.ext4 --help
fsck.ext4: неверный ключ — «-»
Usage: fsck.ext4 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
                [-I inode_buffer_blocks] [-P process_inode_size]
                [-l|-L bad_blocks_file] [-C fd] [-j external_journal]
                [-E extended-options] device

Emergency help:
 -p                   Automatic repair (no questions)
 -n                   Make no changes to the filesystem
 -y                   Assume "yes" to all questions
 -c                   Check for bad blocks and add them to the badblock list
 -f                   Force checking even if filesystem is marked clean
 -v                   Be verbose
 -b superblock        Use alternative superblock
 -B blocksize         Force blocksize when looking for superblock
 -j external_journal  Set location of the external journal
 -l bad_blocks_file   Add to badblocks list
 -L bad_blocks_file   Set badblocks list

root@data:/# fsck.ext4 -f -y /dev/sdb1
e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
data: 54874/488407040 files (1.1% non-contiguous), 237102044/488378112 blocks

И таких ошибок довольно много, но данные совсем не критичные. Был бы рад «просто снести битые файлы». Гугл советует пройти процедуру переформатирования (очень не хочется).

Вопрос к вам, комрады — как лучше пофиксить эти ошибки?

Hi guys.
I encountered a filesystem issue after an unclean shutdown. I can’t mount my /dev/sda3.

I have booted from Live-USB and tried fsck but it gave me the following error:

fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
fsck.ext2: input/output error while trying to open /dev/sda3

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>

I then tried e2fsck -b to use alt superblocks, and all of them gave me the following in the end:

Error writing block 1 (input/output error).  Ignore error? yes

Here is the output of fdisk -l /dev/sda:

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: TOSHIBA MQ01ABD1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: A58C9090-719B-4126-B7D2-6D9980C7EE5C

Device         Start        End    Sectors  Size Type
/dev/sda1       2048    1050623    1048576  512M EFI System
/dev/sda2    1050624  126877695  125827072   60G Linux filesystem
/dev/sda3  126877696 1953523711 1826646016  871G Linux filesystem

smartctl -a /dev/sda3:

smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.9.200-antix.1-amd64-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MQ01ABD...
Device Model:     TOSHIBA MQ01ABD100
Serial Number:    66PPCA2JT
LU WWN Device Id: 5 000039 713f076c5
Firmware Version: AX0P3D
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Feb 24 16:59:15 2020 CST
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:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
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: 		(  120) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No 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: 	 ( 241) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 128
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       1747
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   066   066   000    Old_age   Always       -       13773
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1797
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       160
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       60
193 Load_Cycle_Count        0x0032   089   089   000    Old_age   Always       -       114357
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       30 (Min/Max 11/48)
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0032   074   074   000    Old_age   Always       -       10780
241 Total_LBAs_Written      0x0032   100   100   000    Old_age   Always       -       20878586044
242 Total_LBAs_Read         0x0032   100   100   000    Old_age   Always       -       26620931857
254 Free_Fall_Sensor        0x0032   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 2575 (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 2575 occurred at disk power-on lifetime: 13773 hours (573 days + 21 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 41 10 00 00 90 40  Error: UNC at LBA = 0x00900000 = 9437184

  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 10 00 00 90 40 00      06:49:14.650  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      06:49:14.650  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      06:49:14.649  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      06:49:14.649  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      06:49:14.648  SET FEATURES [Set transfer mode]

Error 2574 occurred at disk power-on lifetime: 13773 hours (573 days + 21 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 41 e0 00 00 90 40  Error: UNC at LBA = 0x00900000 = 9437184

  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 e0 00 00 90 40 00      06:49:10.863  READ FPDMA QUEUED
  60 08 d8 f0 67 70 40 00      06:49:10.863  READ FPDMA QUEUED
  60 08 70 80 67 70 40 00      06:49:10.838  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      06:49:10.829  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      06:49:10.829  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 2573 occurred at disk power-on lifetime: 13773 hours (573 days + 21 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 41 c0 00 00 90 40  Error: UNC at LBA = 0x00900000 = 9437184

  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 c0 00 00 90 40 00      06:49:07.051  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      06:49:07.050  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      06:49:07.050  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      06:49:07.049  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      06:49:07.048  SET FEATURES [Set transfer mode]

Error 2572 occurred at disk power-on lifetime: 13773 hours (573 days + 21 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 41 28 00 00 90 40  Error: UNC at LBA = 0x00900000 = 9437184

  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 28 00 00 90 40 00      06:49:03.272  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      06:49:03.271  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      06:49:03.271  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      06:49:03.270  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      06:49:03.270  SET FEATURES [Set transfer mode]

Error 2571 occurred at disk power-on lifetime: 13773 hours (573 days + 21 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 41 00 00 00 90 40  Error: UNC at LBA = 0x00900000 = 9437184

  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 20 00 00 00 90 40 00      06:48:58.991  READ FPDMA QUEUED
  ea 00 00 00 00 00 a0 00      06:48:58.990  FLUSH CACHE EXT
  ef 10 02 00 00 00 a0 00      06:27:48.070  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      06:27:48.069  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      06:27:48.069  IDENTIFY DEVICE

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     13772         -
# 2  Extended offline    Completed: read failure       00%     13771         6960152
# 3  Extended offline    Aborted by host               90%     13764         -
# 4  Short offline       Completed without error       00%     13762         -
# 5  Short offline       Aborted by host               90%       253         -
# 6  Short offline       Aborted by host               70%       253         -
# 7  Short offline       Aborted by host               90%       253         -
# 8  Short offline       Aborted by host               90%        10         -
# 9  Short offline       Aborted by host               90%        10         -
#10  Short offline       Aborted by host               90%         8         -
#11  Short offline       Aborted by host               90%         8         -
#12  Short offline       Completed without error       00%         8         -
#13  Short offline       Completed without error       00%         1         -

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.

dmesg‘s output has errors as below:

[34627.265357] blk_update_request: I/O error, dev sda, sector 126877696
[34627.265363] Buffer I/O error on dev sda3, logical block 0, async page read

It seems like a terrible failing. Can anyone help me with this? Better without any lower-level data recovery techniques. Thanks very much!

Last edited by zoron (2020-02-25 01:02:39)