You are not logged in.
Pages: 1
Hi,
Apologies if this too dumb to be true or if it's been answered before. But I'm having to manage a house move with elderly parents and associated legal issues at the same time so overly stressed. Would be immensely grateful for help. I have some experience with arch and find that I can usually fix problems without asking the forums but I'm basically a beginner. I'm writing on my mobile phone so apologies for the formatting.
I mistyped my password three times on gnome 40, then did the stupid thing (stupid,stupid,stupid, I know) and used the button to force shutdown.
Then I got a message from secure boot which I promptly disabled (hadn't appreciated it was on to begin with).
Then when I boot, I get the usual boot screen (systemd-boot) and it seems to start but:
:: running early hook [udev]
Starting version 249-3-arch
:: running hook [udev]
:: Triggering uevents
Waiting ten seconds for device /dev/disk/by-uuid/f3a....(the whole number)
ERROR device 'UUID=f3a...' not found. Skipping fsck.
mount: /new_root: can't find UUID=f3a...
You are being dropped to an emergency she'll.
sh: can't access try; job control turned off
Additionally, when I boot using the install medium, I can't find the disks to chroot into. fdisk -l finds only the installation medium proper.
Anyway, I'm desperate, help would be very much a life saver
Last edited by Mifune (2021-07-19 09:43:20)
Offline
PS apologies if this is the wrong section to post in.
Offline
Then I got a message from secure boot which I promptly disabled
Additionally, when I boot using the install medium, I can't find the disks to chroot into. fdisk -l finds only the installation medium proper.
Either the drive died and that caused the initial crash or the UEFI blocks access to it because of the unspecified secure boot incident.
=> The answer is in the BIOS/UEFI
Offline
Thank you! It was indeed had to reset a setting in the BIOS/UEFI. I'll sort put the details on later and mark it solved. Thank you, thank you, thank you.
Offline
So problem was the SATA mode had changed from the correct one which is AHCI. I think I'm going to keep secure boot off.
Anyway, thanks again, during a very stressful time
Offline
Pages: 1