Arch: root partition not found at boot
Clash Royale CLAN TAG#URR8PPP
For an unknown reason, my system stopped booting.
Now, it fails to find my root partition after 10 sec and drops me in an emergency shell where my keyboard is not detected
What I did so far was to boot from a live CD and ran the following commands.
With sdc7 my root partitionsudo su
mkdir /mnt
mount /dev/sdc7 /mnt
With sdc2 my EFI partitionmkdir /mnt/boot
mount /dev/sdc2 /mnt/boot
modprobe efivars
mount -t proc proc /mnt/proc
mount -t sysfs sys /mnt/sys
mount -o bind /dev /mnt/dev
mount -t devpts pts /mnt/dev/pts/
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
chroot /mnt
pacman -Syu
mkinitcpio -P
grub-mkconfig -o /boot/grub/grub.cfg "$@"
No success
NB: I think the acpi errors on the photo are not new
Thanks
boot partition
asked Jan 12 at 20:38
zakrapoviczakrapovic
1371212
add a comment |
For an unknown reason, my system stopped booting.
Now, it fails to find my root partition after 10 sec and drops me in an emergency shell where my keyboard is not detected
What I did so far was to boot from a live CD and ran the following commands.
With sdc7 my root partitionsudo su
mkdir /mnt
mount /dev/sdc7 /mnt
With sdc2 my EFI partitionmkdir /mnt/boot
mount /dev/sdc2 /mnt/boot
modprobe efivars
mount -t proc proc /mnt/proc
mount -t sysfs sys /mnt/sys
mount -o bind /dev /mnt/dev
mount -t devpts pts /mnt/dev/pts/
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
chroot /mnt
pacman -Syu
mkinitcpio -P
grub-mkconfig -o /boot/grub/grub.cfg "$@"
No success
NB: I think the acpi errors on the photo are not new
Thanks
boot partition
asked Jan 12 at 20:38
zakrapoviczakrapovic
1371212
1
Have you checked /etc/fstab?
– novice
Jan 12 at 20:45
add a comment |
For an unknown reason, my system stopped booting.
Now, it fails to find my root partition after 10 sec and drops me in an emergency shell where my keyboard is not detected
What I did so far was to boot from a live CD and ran the following commands.
With sdc7 my root partitionsudo su
mkdir /mnt
mount /dev/sdc7 /mnt
With sdc2 my EFI partitionmkdir /mnt/boot
mount /dev/sdc2 /mnt/boot
modprobe efivars
mount -t proc proc /mnt/proc
mount -t sysfs sys /mnt/sys
mount -o bind /dev /mnt/dev
mount -t devpts pts /mnt/dev/pts/
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
chroot /mnt
pacman -Syu
mkinitcpio -P
grub-mkconfig -o /boot/grub/grub.cfg "$@"
No success
NB: I think the acpi errors on the photo are not new
Thanks
boot partition
asked Jan 12 at 20:38
zakrapoviczakrapovic
1371212
For an unknown reason, my system stopped booting.
Now, it fails to find my root partition after 10 sec and drops me in an emergency shell where my keyboard is not detected
What I did so far was to boot from a live CD and ran the following commands.
With sdc7 my root partitionsudo su
mkdir /mnt
mount /dev/sdc7 /mnt
With sdc2 my EFI partitionmkdir /mnt/boot
mount /dev/sdc2 /mnt/boot
modprobe efivars
mount -t proc proc /mnt/proc
mount -t sysfs sys /mnt/sys
mount -o bind /dev /mnt/dev
mount -t devpts pts /mnt/dev/pts/
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
chroot /mnt
pacman -Syu
mkinitcpio -P
grub-mkconfig -o /boot/grub/grub.cfg "$@"
No success
NB: I think the acpi errors on the photo are not new
Thanks
boot partition
boot partition
asked Jan 12 at 20:38
zakrapoviczakrapovic
1371212
asked Jan 12 at 20:38
zakrapoviczakrapovic
1371212
asked Jan 12 at 20:38
zakrapoviczakrapovic
1371212
asked Jan 12 at 20:38
zakrapoviczakrapovic
1371212
asked Jan 12 at 20:38
zakrapoviczakrapovic
1371212
1371212
1
Have you checked /etc/fstab?
– novice
Jan 12 at 20:45
add a comment |
1
Have you checked /etc/fstab?
– novice
Jan 12 at 20:45
1
1
Have you checked /etc/fstab?
– novice
Jan 12 at 20:45
Have you checked /etc/fstab?
– novice
Jan 12 at 20:45
add a comment |
1 Answer
1
active
oldest
votes
This is a bug in systemd's udev (more precisely communication between udevadm and udevd) affecting distributions shipping udev 240 but not systemd 240 in initramfs.
For Archlinux: FS#61328 - udev 240 not recognising keyboard
My answer for Debian there.
The effect is that enumeration in /dev is missing or incomplete. This prevent the /dev/disk/ tree to be filled, including UUID symlinks. It will also prevent keyboard detection etc.
The usual fix is to revert to udev 239 (so after your chroot) and rebuild the initramfs. It's possible that having systemd (not busybox) handling boot during initramfs can fix this problem too (because some settings get a bigger buffer used for communication between udevadm and udevd then), if that's possible on Archlinux.
Upstream bug report, fix proposition and fix commit there. It boils down to allow a bigger buffer for communication (and is probably not the best fix):
udev fails to trigger loading of modules #11314
Set systemd-udevd monitor buffer size to 128MB #11389
sd-device-monitor: fix ordering of setting buffer size
answered Jan 12 at 23:07
A.BA.B
4,5321725
2
Last update of systemd (240.34-2) fixed it
– zakrapovic
Jan 13 at 9:40
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494156%2farch-root-partition-not-found-at-boot%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is a bug in systemd's udev (more precisely communication between udevadm and udevd) affecting distributions shipping udev 240 but not systemd 240 in initramfs.
For Archlinux: FS#61328 - udev 240 not recognising keyboard
My answer for Debian there.
The effect is that enumeration in /dev is missing or incomplete. This prevent the /dev/disk/ tree to be filled, including UUID symlinks. It will also prevent keyboard detection etc.
The usual fix is to revert to udev 239 (so after your chroot) and rebuild the initramfs. It's possible that having systemd (not busybox) handling boot during initramfs can fix this problem too (because some settings get a bigger buffer used for communication between udevadm and udevd then), if that's possible on Archlinux.
Upstream bug report, fix proposition and fix commit there. It boils down to allow a bigger buffer for communication (and is probably not the best fix):
udev fails to trigger loading of modules #11314
Set systemd-udevd monitor buffer size to 128MB #11389
sd-device-monitor: fix ordering of setting buffer size
answered Jan 12 at 23:07
A.BA.B
4,5321725
2
Last update of systemd (240.34-2) fixed it
– zakrapovic
Jan 13 at 9:40
add a comment |
This is a bug in systemd's udev (more precisely communication between udevadm and udevd) affecting distributions shipping udev 240 but not systemd 240 in initramfs.
For Archlinux: FS#61328 - udev 240 not recognising keyboard
My answer for Debian there.
The effect is that enumeration in /dev is missing or incomplete. This prevent the /dev/disk/ tree to be filled, including UUID symlinks. It will also prevent keyboard detection etc.
The usual fix is to revert to udev 239 (so after your chroot) and rebuild the initramfs. It's possible that having systemd (not busybox) handling boot during initramfs can fix this problem too (because some settings get a bigger buffer used for communication between udevadm and udevd then), if that's possible on Archlinux.
Upstream bug report, fix proposition and fix commit there. It boils down to allow a bigger buffer for communication (and is probably not the best fix):
udev fails to trigger loading of modules #11314
Set systemd-udevd monitor buffer size to 128MB #11389
sd-device-monitor: fix ordering of setting buffer size
answered Jan 12 at 23:07
A.BA.B
4,5321725
2
Last update of systemd (240.34-2) fixed it
– zakrapovic
Jan 13 at 9:40
add a comment |
This is a bug in systemd's udev (more precisely communication between udevadm and udevd) affecting distributions shipping udev 240 but not systemd 240 in initramfs.
For Archlinux: FS#61328 - udev 240 not recognising keyboard
My answer for Debian there.
The effect is that enumeration in /dev is missing or incomplete. This prevent the /dev/disk/ tree to be filled, including UUID symlinks. It will also prevent keyboard detection etc.
The usual fix is to revert to udev 239 (so after your chroot) and rebuild the initramfs. It's possible that having systemd (not busybox) handling boot during initramfs can fix this problem too (because some settings get a bigger buffer used for communication between udevadm and udevd then), if that's possible on Archlinux.
Upstream bug report, fix proposition and fix commit there. It boils down to allow a bigger buffer for communication (and is probably not the best fix):
udev fails to trigger loading of modules #11314
Set systemd-udevd monitor buffer size to 128MB #11389
sd-device-monitor: fix ordering of setting buffer size
answered Jan 12 at 23:07
A.BA.B
4,5321725
This is a bug in systemd's udev (more precisely communication between udevadm and udevd) affecting distributions shipping udev 240 but not systemd 240 in initramfs.
For Archlinux: FS#61328 - udev 240 not recognising keyboard
My answer for Debian there.
The effect is that enumeration in /dev is missing or incomplete. This prevent the /dev/disk/ tree to be filled, including UUID symlinks. It will also prevent keyboard detection etc.
The usual fix is to revert to udev 239 (so after your chroot) and rebuild the initramfs. It's possible that having systemd (not busybox) handling boot during initramfs can fix this problem too (because some settings get a bigger buffer used for communication between udevadm and udevd then), if that's possible on Archlinux.
Upstream bug report, fix proposition and fix commit there. It boils down to allow a bigger buffer for communication (and is probably not the best fix):
udev fails to trigger loading of modules #11314
Set systemd-udevd monitor buffer size to 128MB #11389
sd-device-monitor: fix ordering of setting buffer size
answered Jan 12 at 23:07
A.BA.B
4,5321725
answered Jan 12 at 23:07
A.BA.B
4,5321725
answered Jan 12 at 23:07
A.BA.B
4,5321725
answered Jan 12 at 23:07
A.BA.B
4,5321725
4,5321725
2
Last update of systemd (240.34-2) fixed it
– zakrapovic
Jan 13 at 9:40
add a comment |
2
Last update of systemd (240.34-2) fixed it
– zakrapovic
Jan 13 at 9:40
2
2
Last update of systemd (240.34-2) fixed it
– zakrapovic
Jan 13 at 9:40
Last update of systemd (240.34-2) fixed it
– zakrapovic
Jan 13 at 9:40
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494156%2farch-root-partition-not-found-at-boot%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Have you checked /etc/fstab?
– novice
Jan 12 at 20:45