You are not logged in.

#1 2022-05-30 15:37:14

curlywei
Member
Registered: 2022-05-30
Posts: 9

[SOLVED] After update, ERROR: device not found. Skipping fsck.

1. Error message when boot
::running early hook [udev]
Starting version 251.1-1-arch
::running hook [udev]
Waiting 10 seconds for device /dev/disk/by-uuid/2c6ef7eb-b946-46ad-978f-8ddd3db6a850...
ERROR: device `2c6ef7eb-b946-46ad-978f-8ddd3db6a850` not found. Skipping fsck.
:: mounting `2c6ef7eb-b946-46ad-978f-8ddd3db6a850` on real root
mount: /new_root: can't find UUID=2c6ef7eb-b946-46ad-978f-8ddd3db6a850. 
You are being dropped to a recovery shell
    Type 'exit' to try and continue booting
sh: can't access tty; job control turned off
[rootfs /]# _

After I update I got this error message.
My computer also configure nvme-raid1

2. Tried, but still can't boot, still the same error message
  1. Insert arch-live USB and boot with it

  2.  # mount /dev/md127p1/mnt &&mount /dev/sda1 /boot 
  3.  # mdadm --detail --scan >> /mnt/etc/mdadm.conf
  4. Check and modify mdadm.con, result as 3.Maybe useful information

  5.   # genfstab -U -p> /mnt/etc/fstab
  6.  # arch-chroot /mnt 
  7.  # mkinitcpio -p
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
      -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    ==> Starting build: 5.18.0-arch1-1
      -> Running build hook: [base]
      -> Running build hook: [udev]
      -> Running build hook: [autodetect]
      -> Running build hook: [modconf]
      -> Running build hook: [block]
    ==> WARNING: Possibly missing firmware for module: xhci_pci
      -> Running build hook: [mdadm_udev]
    Custom /etc/mdadm.conf file will be used in initramfs for assembling arrays.
      -> Running build hook: [filesystems]
      -> Running build hook: [keyboard]
      -> Running build hook: [fsck]
    ==> Generating module dependencies
    ==> Creating zstd-compressed initcpio image: /boot/initramfs-linux.img
    ==> Image generation successful
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
      -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    ==> Starting build: 5.18.0-arch1-1
      -> Running build hook: [base]
      -> Running build hook: [udev]
      -> Running build hook: [modconf]
      -> Running build hook: [block]
    ==> WARNING: Possibly missing firmware for module: qed
    ==> WARNING: Possibly missing firmware for module: qla1280
    ==> WARNING: Possibly missing firmware for module: wd719x
    ==> WARNING: Possibly missing firmware for module: aic94xx
    ==> WARNING: Possibly missing firmware for module: qla2xxx
    ==> WARNING: Possibly missing firmware for module: bfa
    ==> WARNING: Possibly missing firmware for module: xhci_pci
      -> Running build hook: [mdadm_udev]
    Custom /etc/mdadm.conf file will be used in initramfs for assembling arrays.
      -> Running build hook: [filesystems]
      -> Running build hook: [keyboard]
      -> Running build hook: [fsck]
    ==> Generating module dependencies
    ==> Creating zstd-compressed initcpio
  8. exit and reboot, still can't boot

3. Maybe useful information (in arch-chroot)

This is the information that comes to my mind right now.
If any information I forgot,
please let me know, thanks!!


[root@archiso /]# lsblk
NAME          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
loop0           7:0    0 669.2M  1 loop
sda             8:0    0 238.5G  0 disk
└─sda1          8:1    0     1G  0 part  /boot
sdb             8:16   1  14.5G  0 disk
└─sdb1          8:17   1  14.5G  0 part
nvme1n1       259:0    0 953.9G  0 disk
└─nvme1n1p1   259:1    0 953.9G  0 part
  └─md127       9:127  0 953.7G  0 raid1
    └─md127p1 259:4    0 953.7G  0 part  /
nvme0n1       259:2    0 953.9G  0 disk
└─nvme0n1p1   259:3    0 953.9G  0 part
  └─md127       9:127  0 953.7G  0 raid1
    └─md127p1 259:4    0 953.7G  0 part  /
[root@archiso /]#blkid
/dev/nvme0n1p1: UUID="ec190935-18a0-9ea4-17a3-5d0ea7d17106" UUID_SUB="66419acb-3caa-40ad-e2b6-96823b7c2e86" LABEL="archiso:RAID1_DEV" TYPE="linux_raid_member" PARTLABEL="RAID1_0" PARTUUID="6f01dc2f-8e3b-4b4e-be23-b058be4cda11"
/dev/md127p1: LABEL="SYS_FS" UUID="2c6ef7eb-b946-46ad-978f-8ddd3db6a850" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="MD_PART" PARTUUID="bf0d8110-59d1-474f-872e-b0012c0e741b"
/dev/sdb1: LABEL="ARCH_202205" UUID="74AE-A2F5" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="Main Data Partition" PARTUUID="99b59577-fa77-4689-9edd-a34d8e4f93fc"
/dev/loop0: TYPE="squashfs"
/dev/nvme1n1p1: UUID="ec190935-18a0-9ea4-17a3-5d0ea7d17106" UUID_SUB="7e33712b-49b1-9e35-9c89-f15e43dcf8a1" LABEL="archiso:RAID1_DEV" TYPE="linux_raid_member" PARTLABEL="RAID1_1" PARTUUID="b4905d9f-48b3-46d4-a9d4-bf1833964b94"
/dev/sda1: LABEL_FATBOOT="EFI_FS" LABEL="EFI_FS" UUID="A117-6BA2" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI_PART" PARTUUID="6bc9babe-9925-4467-b091-6d5162320cb4"
[root@archiso /]#  cat /etc/fstab
# UUID=2c6ef7eb-b946-46ad-978f-8ddd3db6a850 LABEL=SYS_FS
/dev/md127p1            /               ext4            rw,relatime     0 1

# UUID=A117-6BA2 LABEL=EFI_FS
/dev/sda1               /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro   0 2
[root@archiso /]# cat /proc/mdstat
Personalities : [raid1]
md127 : active raid1 nvme1n1p1[1] nvme0n1p1[0]
      1000071488 blocks super 1.2 [2/2] [UU]
      bitmap: 0/8 pages [0KB], 65536KB chunk

unused devices: <none>
[root@archiso /]# cat /boot/loader/entries/arch.conf
title archlinux
initrd /amd-ucode.img
initrd /initramfs-linux.img
linux /vmlinuz-linux
options root=UUID=2c6ef7eb-b946-46ad-978f-8ddd3db6a850 rw
[root@archiso /]# cat /boot/loader/entries/arch.conf
title archlinux
initrd /amd-ucode.img
initrd /initramfs-linux.img
linux /vmlinuz-linux
options root=UUID=2c6ef7eb-b946-46ad-978f-8ddd3db6a850 rw
[root@archiso /]# cat /etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=(amdgpu)

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=(mdmon)

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS=(base udev autodetect modconf block mdadm_udev filesystems keyboard fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
#COMPRESSION="zstd"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
[root@archiso /]# cat /etc/mdadm.conf
# mdadm configuration file
#
# mdadm will function properly without the use of a configuration file,
# but this file is useful for keeping track of arrays and member disks.
# In general, a mdadm.conf file is created, and updated, after arrays
# are created. This is the opposite behavior of /etc/raidtab which is
# created prior to array construction.
#
#
# the config file takes two types of lines:
#
#       DEVICE lines specify a list of devices of where to look for
#         potential member disks
#
#       ARRAY lines specify information about how to identify arrays so
#         so that they can be activated
#


# You can have more than one device line and use wild cards. The first
# example includes SCSI the first partition of SCSI disks /dev/sdb,
# /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second
# line looks for array slices on IDE disks.
#
#DEVICE /dev/sd[bcdjkl]1
#DEVICE /dev/hda1 /dev/hdb1
#
# The designation "partitions" will scan all partitions found in
# /proc/partitions
DEVICE partitions


# ARRAY lines specify an array to assemble and a method of identification.
# Arrays can currently be identified by using a UUID, superblock minor number,
# or a listing of devices.
#
#       super-minor is usually the minor number of the metadevice
#       UUID is the Universally Unique Identifier for the array
# Each can be obtained using
#
#       mdadm -D <md>
#
# To capture the UUIDs for all your RAID arrays to this file, run these:
#    to get a list of running arrays:
#    # mdadm -D --scan >>/etc/mdadm.conf
#    to get a list from superblocks:
#    # mdadm -E --scan >>/etc/mdadm.conf
#
#ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
#ARRAY /dev/md1 super-minor=1
#ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1
#
# ARRAY lines can also specify a "spare-group" for each array.  mdadm --monitor
# will then move a spare between arrays in a spare-group if one array has a
# failed drive but no spare
#ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df spare-group=group1
#ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 spare-group=group1
#


# When used in --follow (aka --monitor) mode, mdadm needs a
# mail address and/or a program.  To start mdadm's monitor mode, enable
# mdadm.service in systemd.
#
# If the lines are not found, mdadm will exit quietly
MAILADDR my-email@aaa.bbb
#PROGRAM /usr/sbin/handle-mdadm-events
ARRAY /dev/md/RAID1_DEV metadata=1.2 name=archiso:RAID1_DEV UUID=ec190935:18a09ea4:17a35d0e:a7d17106

Last edited by curlywei (2022-05-31 03:02:12)

Offline

#2 2022-05-30 15:39:46

loqs
Member
Registered: 2014-03-06
Posts: 17,192

Re: [SOLVED] After update, ERROR: device not found. Skipping fsck.

Offline

#3 2022-05-30 15:50:00

curlywei
Member
Registered: 2022-05-30
Posts: 9

Re: [SOLVED] After update, ERROR: device not found. Skipping fsck.

Many thanks your info.
I supply this information about it:

# mdadm --assemble --scan --verbose
mdadm: looking for devices for further assembly
mdadm: no recogniseable superblock on /dev/md/RAID1_DEV1
mdadm: Cannot assemble mbr metadata on /dev/md/RAID1_DEV
mdadm: no recogniseable superblock on /dev/loop0
mdadm: Cannot assemble mbr metadata on /dev/sdb1
mdadm: Cannot assemble mbr metadata on /dev/sdb
mdadm: /dev/nvme0n1p1 is busy - skipping
mdadm: Cannot assemble mbr metadata on /dev/nvme0n1
mdadm: /dev/nvme1n1p1 is busy - skipping
mdadm: Cannot assemble mbr metadata on /dev/nvme1n1
mdadm: Cannot assemble mbr metadata on /dev/sda1
mdadm: Cannot assemble mbr metadata on /dev/sda
mdadm: No arrays found in config file or automatically

As far as you see, it seems to be the same problem

Last edited by curlywei (2022-05-30 15:51:23)

Offline

#4 2022-05-31 03:00:58

curlywei
Member
Registered: 2022-05-30
Posts: 9

Re: [SOLVED] After update, ERROR: device not found. Skipping fsck.

Hi:
Today, I update kernel(Use live-CD/ [acrh-chroot]) to version 5.18.1-arch1-1 as well as [mkinitcpio].
No problem for me now.

Last edited by curlywei (2022-05-31 03:04:05)

Offline

Board footer

Powered by FluxBB