Installed distro won't boot, stuck in emergency mode on both machines
by Vertruc from LinuxQuestions.org on (#4VHZD)
Hello everyone,
I decided 2 or 3 weeks ago to ditch Windows for Linux on my computer (yay me).
The past weeks i have been juggling my files so that i won't loose anything switching from one OS to the other. As my HDDs were quite full, i decided i'd transfer everything into my laptop (running Linux Mint) using USB sticks, then transfer everything back into my computer once everything was set up.
I don't know what i messed up... but i messed up. Not only is my computer stuck in emergency mode, but so is my laptop ! I'm currently writing from a live Ubuntu on USB.
I think it may have something to do with the continuous use of USB sticks between my two machines though.
For once, at first the sticks were not formatted for Linux so they weren't readable. I tried reformatting them to exFAT so i could use them both in Windows and Linux environments. Something went wrong there because sometimes they would work and sometimes they would'nt.
Or maybe it's something in the very files i transfered, something corrupt that would have broken the same thing in both machines ? At one point when i transfered files, i was noticed one file's path name was too long to be taken care of. Could it be that it somehow passed this warning and broke stuff where it shouldn't have ?
Doing some research, i also noticed i forgot to make a swap partition on my computer, and that the laptop didn't have one to begin with. It seems some cases of people stuck in emergency mode were linked to this...
Also, i would very much like to give you the full result of journalctl -xb here but i couldn't find a way to save the result into a file, i tried somecommand > textfile.txt but it didn't seem to work... i feel helpless and stupid :(
I figured i should focus on the laptop first, and decided i would copy by hand some of the lines that popped up on there for lack of a better solution. :doh:
The situation for this machine is that it should be running Linux Mint. But it doesn't want to. As you guessed from the title, it's stuck in emergency mode. Here is a selection of lines from journalctl i found could be of interest (the ones in bold were in red):
Code:Kernel is locked down from EFI secure boot; see man kernel_lockdown.7
random: get_random_bytes called from start_kernel+0x99/0x4fd with crng_init=0
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=cde903d0-011b-41cb-b4fa-64ad327a8df5 ro quiet stplash
do-IRQ: 1.55 No irq handler for vector
audit: type=200 audit(1574350269.204:1): state=initialized audit_enabled=0 res=1
ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
SCSI subsystem initialized
VFS: Disk quotas dquot_6.6.0
Initialise system trusted keyrings
Key type blacklist registered
Key type asymmetric registered
Assymetric key parser 'x509' registered
(NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info()
Key type dns_resolver registered
Loading compiled-in X.509 certificates
Loaded X.509 cert 'Build time autogenerated kernel key: 1859b0531897959199376c446a0bd70df75fd1fc'
Loaded UEFI:db cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53' linked to secondary sys keyring
Loaded UEFI:db cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4' linked to a secondary sys keyring
Loaded UEFI:db cert 'Toshiba Corporation Utility CA 2012: cc37e82804de6d8242718850b1af8d5f' linked to secondary syskeyring
Couldn't get size: 0x800000000000000e
Key type big_key registered
Key type trusted registered
Key type encrypted registered
Lockdown: Hybernation is restricted; see man kernel_lockdown.7There is also a case of failed dependency regarding sdb1:
Code:unit ufw.service has finished startup
dev-sdb1.device/start timed out.
Timed out waiting for device dev-sdb1.devicebut as strange as it looked to me, it seems not to be related to my problem, since sdb1 is not where the EFI system partition is hosted.
One thing i tried already is verify if /etc/fstab had the right partition set for the ESP, but it was the right one...
I tried updating grub as well... didn't work.
I'm really lost on this. I don't know what to do and what to not do, why it happened and how.
Thank you very much in advance, i'm in dire need of help ! :(
I decided 2 or 3 weeks ago to ditch Windows for Linux on my computer (yay me).
The past weeks i have been juggling my files so that i won't loose anything switching from one OS to the other. As my HDDs were quite full, i decided i'd transfer everything into my laptop (running Linux Mint) using USB sticks, then transfer everything back into my computer once everything was set up.
I don't know what i messed up... but i messed up. Not only is my computer stuck in emergency mode, but so is my laptop ! I'm currently writing from a live Ubuntu on USB.
I think it may have something to do with the continuous use of USB sticks between my two machines though.
For once, at first the sticks were not formatted for Linux so they weren't readable. I tried reformatting them to exFAT so i could use them both in Windows and Linux environments. Something went wrong there because sometimes they would work and sometimes they would'nt.
Or maybe it's something in the very files i transfered, something corrupt that would have broken the same thing in both machines ? At one point when i transfered files, i was noticed one file's path name was too long to be taken care of. Could it be that it somehow passed this warning and broke stuff where it shouldn't have ?
Doing some research, i also noticed i forgot to make a swap partition on my computer, and that the laptop didn't have one to begin with. It seems some cases of people stuck in emergency mode were linked to this...
Also, i would very much like to give you the full result of journalctl -xb here but i couldn't find a way to save the result into a file, i tried somecommand > textfile.txt but it didn't seem to work... i feel helpless and stupid :(
I figured i should focus on the laptop first, and decided i would copy by hand some of the lines that popped up on there for lack of a better solution. :doh:
The situation for this machine is that it should be running Linux Mint. But it doesn't want to. As you guessed from the title, it's stuck in emergency mode. Here is a selection of lines from journalctl i found could be of interest (the ones in bold were in red):
Code:Kernel is locked down from EFI secure boot; see man kernel_lockdown.7
random: get_random_bytes called from start_kernel+0x99/0x4fd with crng_init=0
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=cde903d0-011b-41cb-b4fa-64ad327a8df5 ro quiet stplash
do-IRQ: 1.55 No irq handler for vector
audit: type=200 audit(1574350269.204:1): state=initialized audit_enabled=0 res=1
ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
SCSI subsystem initialized
VFS: Disk quotas dquot_6.6.0
Initialise system trusted keyrings
Key type blacklist registered
Key type asymmetric registered
Assymetric key parser 'x509' registered
(NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info()
Key type dns_resolver registered
Loading compiled-in X.509 certificates
Loaded X.509 cert 'Build time autogenerated kernel key: 1859b0531897959199376c446a0bd70df75fd1fc'
Loaded UEFI:db cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53' linked to secondary sys keyring
Loaded UEFI:db cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4' linked to a secondary sys keyring
Loaded UEFI:db cert 'Toshiba Corporation Utility CA 2012: cc37e82804de6d8242718850b1af8d5f' linked to secondary syskeyring
Couldn't get size: 0x800000000000000e
Key type big_key registered
Key type trusted registered
Key type encrypted registered
Lockdown: Hybernation is restricted; see man kernel_lockdown.7There is also a case of failed dependency regarding sdb1:
Code:unit ufw.service has finished startup
dev-sdb1.device/start timed out.
Timed out waiting for device dev-sdb1.devicebut as strange as it looked to me, it seems not to be related to my problem, since sdb1 is not where the EFI system partition is hosted.
One thing i tried already is verify if /etc/fstab had the right partition set for the ESP, but it was the right one...
I tried updating grub as well... didn't work.
I'm really lost on this. I don't know what to do and what to not do, why it happened and how.
Thank you very much in advance, i'm in dire need of help ! :(