Arch Linux

yyyyyyy

Member

Registered: 2024-04-16

Posts: 2

fsck.ext4: Input/output error while trying to re-open /dev/nvme0n1p2

I updated the system last night, reboot, and it was all working fine. I left rclone running and woke up with my screen frozen on tty. I tried rebooting, but keep getting this error and being thrown in an emergency shell.

Current output on boot:

/dev/nvme0n1p2: recovering journal
fsck.ext4: Input/output error while trying to re-open /dev/nvme0n1p2
/dev/nvme0n1p2:
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>

ERROR: fsck failed on 'UUID=8bde7707-907f-4123-8153-7d6b330f9353'
mount: /new_root: no valid filesystem type specified.
ERROR: Failed to mount 'UUID=8bde7707-907f-4123-8153-7d6b330f9353' on real root
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off

What I've tried so far

In the emergency shell:

I've tried running e2fsck as the message said:

[rootfs ~]# e2fsck -b 8193 /dev/nvme0n1p2
e2fsck 1.47.0 (5-Feb-2023)
e2fsck: Input/output error while trying to open /dev/nvme0n1p2

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>

Same error for these commands:

e2fsck -b 32768 /dev/nvme0n1p2
fsck UUID=8bde7707-907f-4123-8153-7d6b330f9353

From live media shell:

lsblk

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0 788.2M  1 loop /run/archiso/airootfs
sda           8:0    1  57.8G  0 disk
├─sda1        8:1    1   940M  0 part
└─sda2        8:2    1    15M  0 part
nvme0n1     259:0    0 476.9G  0 disk
├─nvme0n1p1 259:1    0   512M  0 part
└─nvme0n1p2 259:2    0    27G  0 part
└─nvme0n1p3 259:3    0 449.4G  0 part

lsblk -f

NAME        FSTYPE   FSVER            LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0       squashfs 4.0                                                                     0   100% /run/archiso/airootfs
sda         iso9660  Joliet Extension ARCH_202404 2024-04-01-17-57-21-00
├─sda1      iso9660  Joliet Extension ARCH_202404 2024-04-01-17-57-21-00
└─sda2      vfat     FAT16            ARCHISO_EFI 580E-F324
nvme0n1
├─nvme0n1p1 vfat     FAT32                        DBA9-7F05
└─nvme0n1p2 ext4     1.0                          8bde7707-907f-4123-8153-7d6b330f9353
└─nvme0n1p3 ext4     1.0                          802b7108-baa1-464d-b51e-1c64a33b0041

fdisk -l /dev/nvme0n1

Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: SSSTC CA5-8D512-Q79
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C49994CA-7D2F-4875-8860-479963672B61

Device            Start        End    Sectors    Size Type
/dev/nvme0n1p1     2048    1050623    1048576    512M EFI System
/dev/nvme0n1p2  1050624   57673727   56623104     27G Linux root (x86-64)
/dev/nvme0n1p3 57673728 1000214527  942540800  449.4G Linux home

fsck returns a different error from this shell:

root@archiso ~ # fsck /dev/nvme0n1p2
fsck from util-linux 2.40
e2fsck 1.47.0 (5-Feb-2023)
/dev/nvme0n1p2: recovering journal
[  256.026689] nvme0n1: Read(0x2) @ LBA 57673600, 8 blocks, Host Aborted Command (sct 0x3 / sc 0x71)
[  256.028656] I/O error, dev nvme0n1, sector 57673600 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  353.098927] nvme nvme0: Device not ready; aborting shutdown, CSTS=0x5
[  353.116801] I/O error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[  353.159160] Buffer I/O error on dev nvme0n1p2, logical block 7077872, async page read
[  353.159378] Buffer I/O error on dev nvme0n1p2, logical block 0, async page read
[  353.164144] Buffer I/O error on dev nvme0n1p2, logical block 0, async page read
fsck.ext4: Input/output error while trying to re-open /dev/nvme0n1p2

/dev/nvme0n1p2: ********** WARNING: Filesystem still has errors **********

12 root@archiso ~ # [  353.184428] Buffer I/O error on dev nvme0n1p2, logical block 7077872, async page read

After running fsck, lsblk doesn't show nvme0n1p2 as ext4 anymore:
lsblk -f

NAME        FSTYPE   FSVER            LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0       squashfs 4.0                                                                     0   100% /run/archiso/airootfs
sda         iso9660  Joliet Extension ARCH_202404 2024-04-01-17-57-21-00
├─sda1      iso9660  Joliet Extension ARCH_202404 2024-04-01-17-57-21-00
└─sda2      vfat     FAT16            ARCHISO_EFI 580E-F324
nvme0n1
├─nvme0n1p1 vfat     FAT32                        DBA9-7F05
└─nvme0n1p2
└─nvme0n1p3 ext4     1.0                          802b7108-baa1-464d-b51e-1c64a33b0041

I also tried mounting the filesystem:

root@archiso ~ # mount /dev/nvme0n1p2 /mnt
[ 1942.299963] Buffer I/O error on dev nvme0n1p2, logical block 7077872, async page read
[ 1942.303441] SQUASHFS error: Failed to read block 0x0: -5
mount: /mnt: fsconfig system call failed: unable to read squashfs_super_block.
       dmesg(1) may have more information after failed mount system call.

This is dmesg after trying to mount:

[ 2251.452952] Buffer I/O error on dev nvme0n1p2, logical block 7077872, async page read
[ 2251.454685] isofs_fill_super: bread failed, dev=nvme0n1p2, iso_blknum=16, block=32
[ 2251.454730] SQUASHFS error: Failed to read block 0x0: -5

Last edited by yyyyyyy (2024-04-16 16:07:45)

frostschutz

Member

Registered: 2013-11-15

Posts: 1,421

Re: fsck.ext4: Input/output error while trying to re-open /dev/nvme0n1p2

You shouldn't try to fsck a device that produces I/O errors. it will only make things worse. If this drive is actually failing, ddrescue.

It's weird you also get SquashFS errors. Verify the live media and also run a memtest, just in case?

yyyyyyy

Member

Registered: 2024-04-16

Posts: 2

Re: fsck.ext4: Input/output error while trying to re-open /dev/nvme0n1p2

You shouldn't try to fsck a device that produces I/O errors. it will only make things worse. If this drive is actually failing, ddrescue.

Thank you for your response. I'm running ddrescue now, sending the backup to an external drive. What should I do after?

Running now:

ddrescue --force -n /dev/nvme0n1 /dev/sdb rescue.map

It's weird you also get SquashFS errors. Verify the live media and also run a memtest, just in case?

I'll do that as soon as ddrescue finishes and post here.