Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix new_root UUID not found error #94

Closed
LukeShortCloud opened this issue Jul 18, 2021 · 2 comments
Closed

Fix new_root UUID not found error #94

LukeShortCloud opened this issue Jul 18, 2021 · 2 comments
Assignees
Labels
add_upgrade Eligible for adding to the upgrade script bug Something isn't working
Milestone

Comments

@LukeShortCloud
Copy link
Owner

Copied from the release notes for 2.1.0:


KNOWN ISSUES

On some storage devices, users have reported seeing an error on boot similar to this:

ERROR: device 'UUID=<UUID>' not found. Skipping fsck.
mount: /new_root: can't find UUID=<UUID>.
You are now being dropped into an emergency shell.

As a workaround, once you get to the GNU GRUB version 2.06~1~manjaro menu go to Advanced options for Manjaro Linux and then select Manjaro Linux (Kernel: 5.10.41-1-MANJARO x64 - fallback initramfs). This has more device storage drivers enabled by default.

@LukeShortCloud LukeShortCloud added bug Something isn't working add_upgrade Eligible for adding to the upgrade script labels Jul 18, 2021
@LukeShortCloud LukeShortCloud added this to the 2.2.0 milestone Jul 18, 2021
@LukeShortCloud LukeShortCloud self-assigned this Jul 18, 2021
@LukeShortCloud
Copy link
Owner Author

I have tested and confirmed the long-term fix:

"Before creating the initial RAM disk, in /etc/mkinitcpio.conf move the block and keyboard hooks before the autodetect hook." - https://wiki.archlinux.org/title/Install_Arch_Linux_on_a_removable_medium

Two other things to note:

  1. Depending on how many people this affects, we may want to release 2.1.1 with the fix or at least provide an easy way to run the upgrade script to fix it.
  2. We may no longer need to pin the Linux 5.10 kernel to an older release. It may have been by pure chance that booting happened to only work with an older kernel. Related: MacBook Pro 16" 2019 bug does not boot #79

@LukeShortCloud
Copy link
Owner Author

File: /etc/mkinitcpio.conf

Before (original, default install of Manjaro):

HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)

After:

HOOKS=(base udev block keyboard autodetect modconf filesystems fsck)

LukeShortCloud added a commit that referenced this issue Sep 5, 2021
This resolves an issue documented here:

#94
LukeShortCloud added a commit that referenced this issue Sep 5, 2021
This reverts commit ea9a870.

Resolved-By: #94
LukeShortCloud added a commit that referenced this issue Sep 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
add_upgrade Eligible for adding to the upgrade script bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant