[SOLVED] ERROR: device 'UUID=XX-XX-XX' not found. Skipping sfck.

user_231578 · 2020-03-28 13:44:10

It's three days that I'm trying to install ArchLinux in dual boot with OS X, and failing. OS X is booting fine, but when I try to boot Arch Linux this happens:

:: running early hook [udev]
Warning: /lib/modules/5.5.13-arch1-1/modules.devname not found - ignoring
Starting version 245.3-1-arch
:: running hook [udev]
:: Triggering uevents...
Waiting 10 seconds for device /dev/disk/by-partuuid/ea3b7a4d-aab0-40d4-b419-07ca71c8604d ...
ERROR: device 'PARTUUID=ea3b7a4d-aab0-40d4-b419-07ca71c8604d' not found. Skipping fsck.
:: mounting 'PARTUUID=ea3b7a4d-aab0-40d4-b419-07ca71c8604d' on real root
mount: /new_root: can't find PARTUUID=ea3b7a4d-aab0-40d4-b419-07ca71c8604d.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]# _

This shell is not even working, I can't type anything
Some background: 1 week ago succeeded to install ArchLinux in dual boot with OS X (using grub). Then, few days ago I wanted to upgrade my MacBook4.1 with an SSD. I reinstalled OS X on the SSD, partitioned the disk and installed Arch Linux following the same identical step I used before, but this time the error I showed you appeared. The shell at that time was working though.. I was able to mount the root partition manually from the shell typing "mount /dev/sdaX /new_root". and ArchLinux then was fully functional (except I had to manually mount root every time at startup). As I wasn't able to permanently fix the problem I thought that maybe the SSD itself was the problem, I put back the old HDD (sadly I wiped it so I had to reinstall everything again), followed the same usual step, the problem occurred again. I tried to fix the problem in many ways, nothing worked. Now, I'm trying to use systemd-boot instead of grub. The problem is the same but the shell doesn't work.
I reinstalled Arch Linux both using grub and systems-boot several times, trying everything I have found on the internet about this problem but nothing worked for me.

I'm definitely not an expert, I have some questions I can't answer myself and that may be helpful to solve my problem:
1) Can the problem be related to this warning? I am not able fix it. Looking on the internet I fount that who has this warning also happens to have the same problem I have.

Warning: /lib/modules/5.5.13-arch1-1/modules.devname not found - ignoring

2) Since I was able to properly install Arch Linux the first time, why I'm I not able to install it now following the same identical steps from scratch? How is that even possible?

If anyone can help me it would be really appreciated! I'll post here some command output for you to help me debug my problem:

# fdisk -l

Disk /dev/sda: 149.5 GiB, 160041885696 bytes, 312581808 sectors
Disk model: FUJITSU MHY2160B
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: gpt
Disk identifier: D0FC89C2-822B-4EF3-BE02-51F982168EEC

Device         Start       End   Sectors   Size Type
/dev/sda1         40    409639    409600   200M EFI System
/dev/sda2     409640 250409639 250000000 119.2G Apple HFS/HFS+
/dev/sda3  250409640 251679183   1269544 619.9M Apple boot
/dev/sda4  251941328 312581774  60640447  28.9G Linux filesystem


Disk /dev/loop0: 534.78 MiB, 560738304 bytes, 1095192 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

# blkid

/dev/sda1: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="70D6-1701" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="4d0eac79-f89f-4619-9fe1-dab233c61430"
/dev/sda2: UUID="ec39a965-f551-30c7-851d-0ef31ccd898f" BLOCK_SIZE="4096" LABEL="Macintosh HD" TYPE="hfsplus" PARTLABEL="Macintosh HD" PARTUUID="68a9d117-cdbc-4d88-b1a7-54f465e2cff9"
/dev/sda3: UUID="d5c110dc-c968-3f2e-8f62-19d74483bf25" BLOCK_SIZE="4096" LABEL="Recovery HD" TYPE="hfsplus" PARTLABEL="Recovery HD" PARTUUID="efd8311e-9ce5-4581-9d6b-0fd695026d30"
/dev/sda4: UUID="62133f46-61b8-49f9-8502-e4b39e7c04c8" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Root" PARTUUID="ea3b7a4d-aab0-40d4-b419-07ca71c8604d"
/dev/sr0: BLOCK_SIZE="2048" UUID="2020-03-01-09-32-57-00" LABEL="ARCH_202003" TYPE="iso9660" PTUUID="3372b9d9" PTTYPE="dos"
/dev/loop0: TYPE="squashfs"
/dev/sdb1: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="67E3-17ED" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="21a6a161-9443-4de1-a115-e91509d1a20a"
/dev/sdb2: LABEL="Untitled" UUID="5E7B-524E" BLOCK_SIZE="512" TYPE="exfat" PARTUUID="a5064eb4-1c93-473a-aa74-01c9a567d60c"

# cat /etc/fstab

# /dev/sda4
UUID=62133f46-61b8-49f9-8502-e4b39e7c04c8    /             ext4          rw,relatime    0 1

# /dev/sda1 LABEL=EFI
UUID=70D6-1701          /boot         vfat          rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro    0 2

# mkinitcpio -p linux

==> 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.5.13-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-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.5.13-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

# bootctl status

System:
     Firmware: UEFI 1.10 (Apple 1.10)
  Secure Boot: disabled
   Setup Mode: user

Current Boot Loader:
      Product: systemd-boot 244.3-1-arch
     Features: ✓ Boot counting
               ✓ Menu timeout control
               ✓ One-shot menu timeout control
               ✓ Default entry control
               ✓ One-shot entry control
               ✓ Support for XBOOTLDR partition
               ✓ Support for passing random seed to OS
               ✗ Boot loader sets ESP partition information
          ESP: n/a
         File: └─/EFI/BOOT/loader.efi

Random Seed:
 Passed to OS: no
 System Token: set
       Exists: yes

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/4d0eac79-f89f-4619-9fe1-dab233c61430)
         File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 245.3-1-arch)
         File: └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 245.3-1-arch)

Boot Loaders Listed in EFI Variables:
        Title: Linux Boot Manager
           ID: 0x0002
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/4d0eac79-f89f-4619-9fe1-dab233c61430
         File: └─/EFI/systemd/systemd-bootx64.efi

        Title: Linux Boot Manager
           ID: 0x0001
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/fb577f03-2b46-46a2-8463-0194ce373ebc
         File: └─/EFI/systemd/systemd-bootx64.efi

        Title: Linux Boot Manager
           ID: 0x0000
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/1e4f2b9d-06d0-4a35-ba21-031550f9f13a
         File: └─/EFI/systemd/systemd-bootx64.efi

        Title: Mac OS X
           ID: 0x0081
       Status: active
    Partition: /dev/disk/by-partuuid/000013ba-56fb-0000-204c-0000b5320000
         File: └─/EFI/APPLE/FIRMWARE/SmcFlasher.efi

Boot Loader Entries:
        $BOOT: /boot (/dev/disk/by-partuuid/4d0eac79-f89f-4619-9fe1-dab233c61430)

Default Boot Loader Entry:
        title: Arch Linux
           id: arch.conf
       source: /boot/loader/entries/arch.conf
        linux: /vmlinuz-linux
       initrd: /intel-ucode.img
               /initramfs-linux-lts.img
      options: root=PARTUUID=ea3b7a4d-aab0-40d4-b419-07ca71c8604d rw

# cat /boot/loader/loader.conf

#timeout 3
#console-mode keep
#default 8bdd93e1ff4b43aa837997d9f4479520-*
default arch
timeout 4
console-mode max
editor no

# tree /boot

/boot
├── ad2090dff2694a2ba4a6d12a2bcfc991
├── EFI
│   ├── APPLE
│   │   └── EXTENSIONS
│   │       └── Firmware.scap
│   ├── BOOT
│   │   └── BOOTX64.EFI
│   ├── Linux
│   └── systemd
│       └── systemd-bootx64.efi
├── initramfs-linux-fallback.img
├── initramfs-linux.img
├── initramfs-linux-lts-fallback.img
├── initramfs-linux-lts.img
├── intel-ucode.img
├── loader
│   ├── entries
│   │   └── arch.conf
│   ├── loader.conf
│   └── random-seed
├── vmlinuz-linux
└── vmlinuz-linux-lts

9 directories, 13 files

Last edited by user_231578 (2020-03-28 14:31:25)

Scimmia · 2020-03-28 13:51:47

That warning means that you're loading the wrong initramfs. You only posted part of the bootloader config, and not the most important part.

schard · 2020-03-28 13:54:54

Is this a typo from posting here or in the bootloader config?

ERROR: device 'PAERUUID=ea3b7a4d-aab0-40d4-b419-07ca71c8604d' not found. Skipping fsck.

user_231578 · 2020-03-28 13:58:49

schard wrote:

Is this a typo from posting here or in the bootloader config?
ERROR: device 'PAERUUID=ea3b7a4d-aab0-40d4-b419-07ca71c8604d' not found. Skipping fsck.

Sorry the typo comes from me. I copied it manually! I will correct it now.

Last edited by user_231578 (2020-03-28 13:58:59)

user_231578 · 2020-03-28 14:00:48

Scimmia wrote:

That warning means that you're loading the wrong initramfs. You only posted part of the bootloader config, and not the most important part.

What is the most important part? Thanks for your help

Scimmia · 2020-03-28 14:02:34

https://wiki.archlinux.org/index.php/Sy … ng_loaders

user_231578 · 2020-03-28 14:05:39

Scimmia wrote:

https://wiki.archlinux.org/index.php/Sy … ng_loaders

I imagine you are referring to this file: /boot/loader/entries/arch.conf

title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux-lts.img
options root=PARTUUID=ea3b7a4d-aab0-40d4-b419-07ca71c8604d rw

Last edited by user_231578 (2020-03-28 14:12:33)

Scimmia · 2020-03-28 14:06:39

So you're loading the "linux" kernel with the "linux-lts" initramfs. Why?

user_231578 · 2020-03-28 14:08:51

Scimmia wrote:

So you're loading the "linux" kernel with the "linux-lts" initramfs. Why?

Because of long term support. I thought it would be more stable.. Is it wrong?

Scimmia · 2020-03-28 14:09:31

The kernel and the initramfs MUST match

user_231578 · 2020-03-28 14:11:23

Scimmia wrote:

The kernel and the initramfs MUST match

So, if I edit the arch.conf to be like:

title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options root=PARTUUID=ea3b7a4d-aab0-40d4-b419-07ca71c8604d rw

may solve the issue?

Edit: IT DID SOLVE THE ISSUE. Thank you! As you can see I'm definitely not an expert.. Thanks again!

Last edited by user_231578 (2020-03-28 14:18:11)

Arch Linux

#1 2020-03-28 13:44:10

[SOLVED] ERROR: device 'UUID=XX-XX-XX' not found. Skipping sfck.

#2 2020-03-28 13:51:47

Re: [SOLVED] ERROR: device 'UUID=XX-XX-XX' not found. Skipping sfck.

#3 2020-03-28 13:54:54

Re: [SOLVED] ERROR: device 'UUID=XX-XX-XX' not found. Skipping sfck.

#4 2020-03-28 13:58:49

Re: [SOLVED] ERROR: device 'UUID=XX-XX-XX' not found. Skipping sfck.

#5 2020-03-28 14:00:48

Re: [SOLVED] ERROR: device 'UUID=XX-XX-XX' not found. Skipping sfck.

#6 2020-03-28 14:02:34

Re: [SOLVED] ERROR: device 'UUID=XX-XX-XX' not found. Skipping sfck.

#7 2020-03-28 14:05:39

Re: [SOLVED] ERROR: device 'UUID=XX-XX-XX' not found. Skipping sfck.

#8 2020-03-28 14:06:39

Re: [SOLVED] ERROR: device 'UUID=XX-XX-XX' not found. Skipping sfck.

#9 2020-03-28 14:08:51

Re: [SOLVED] ERROR: device 'UUID=XX-XX-XX' not found. Skipping sfck.

#10 2020-03-28 14:09:31

Re: [SOLVED] ERROR: device 'UUID=XX-XX-XX' not found. Skipping sfck.

#11 2020-03-28 14:11:23

Re: [SOLVED] ERROR: device 'UUID=XX-XX-XX' not found. Skipping sfck.

Board footer