Dear Linuxmint Community, huge and green newbie reporting in.
When i just installed my LM 18.2, in the Update Manager for some very personal reasons i've chosen not the 1st quickest local mirrors, but 2nd and 3rd instead. Everything was nice until few days later my Update Manager started showing ominous red icon in the tray: it suggested i would rather choose the quickest local mirrors. Being possessed with naturally daring behavior, i've tried to choose some very different mirrors, refreshed list of updates and tried to install them. After some errors i've switched to 1st quickest local mirrors, refresh cache, refresh list of updates, tried to install them, but then Update Manager again responds with error message. 'Okay, things will sort themselves out', - i thought and turned the machine off.
Next day, when i tried to boot the system, instead of LM 18.2 Cinnamon x64 i saw something that which i intuitively figured out as BusyBox with initramfs going on.
It stated about line 24 not being found in some script.
Somehow, i feel that this line or this script should be fixed, but i had little success trying initramfs. Gave up when tried to 'pwd' (print working directory) and system said i'm working within '/', which is root, probably. I have little wish to mess up root.
Here's my machine info from last attempt to do recovery:
https://gist.github.com/anonymous/038ac ... c950da5e65
Would appreciate any kind of help. I promise not to do any daring behavior until i finished my 9000 hours of GNU/Linux education.
Failed to update and now cannot boot, showing initramfs
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Failed to update and now cannot boot, showing initramfs
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Failed to update and now cannot boot, showing initramfs
Can you boot a live usb session to try to fix the initrd ?
Re: Failed to update and now cannot boot, showing initramfs
Well, Sounds like a real bummer. If this is a fresh install with no real personal data in your home directory then I would take the easy route and just reinstall. If thats not the case then...
I would boot from your bootable iso device and open up a term window. Then find the hard drive. It could be /dev/sda or /dev/sdb ect.. so do a
sudo fdisk -l (thats a lower case L) and take note of the device your hard drive is. Lets say its /dev/sda for arguments. Then lets check the file system and attempt a repair.
Then reboot and see if it fixed things.
Going further, If you run into an error about a UEFI partition (depends on how things were installed) then try it on the second partition:
Answer yes to the prompts.
Keep in mind that you first have to figure out what device your hard drive is. Do not take my example (/dev/sdaX) as gospel. Make sure.
Report back after rebooting after the filesystem check
I would boot from your bootable iso device and open up a term window. Then find the hard drive. It could be /dev/sda or /dev/sdb ect.. so do a
sudo fdisk -l (thats a lower case L) and take note of the device your hard drive is. Lets say its /dev/sda for arguments. Then lets check the file system and attempt a repair.
Code: Select all
sudo e2fsck /dev/sda1
Going further, If you run into an error about a UEFI partition (depends on how things were installed) then try it on the second partition:
Code: Select all
sudo e2fsck /dev/sda2
Keep in mind that you first have to figure out what device your hard drive is. Do not take my example (/dev/sdaX) as gospel. Make sure.
Report back after rebooting after the filesystem check
Ryzen x1800 Asus Prime x370-Pro 32 gigs Ram RX480 graphics
Dell PE T610, Dell PE T710 - List your hardware Profile: inxi -Fxpmrz
MeshCentral * Virtualbox * Debian * InvoiceNinja * NextCloud * Linux since kernel 2.0.36
Dell PE T610, Dell PE T710 - List your hardware Profile: inxi -Fxpmrz
MeshCentral * Virtualbox * Debian * InvoiceNinja * NextCloud * Linux since kernel 2.0.36
Re: Failed to update and now cannot boot, showing initramfs
Thanks for attention, everyone!
it fails with /dev/sda1 as well as with /dev/sda2.
Maybe, if it's worth to note, i noticed one thing: when i've tried to do recovery from bootable usb device, in 'Advanced boot' options there were versions 4.8 and 4.10 - is it different kernel updates?
Also, reinstall is an opinion too (because i always do back-ups to anything important), but i would like to know how to manage 'bad updates' in further. It seems to be an issue.
In my case it was totally /dev/sda1, just as you mentioned. But 'sudo fdisk -l' also told something red about 'Partition 2 does not start on physical sector boundary' - is it somehow related to usb stick i booted system from? And when i trycoffee412 wrote:I would boot from your bootable iso device and open up a term window. Then find the hard drive. It could be /dev/sda or /dev/sdb ect.. so do a
sudo fdisk -l (thats a lower case L) and take note of the device your hard drive is. Lets say its /dev/sda for arguments. Then lets check the file system and attempt a repair.
Then reboot and see if it fixed things.
Code: Select all
e2fsck
Also, reinstall is an opinion too (because i always do back-ups to anything important), but i would like to know how to manage 'bad updates' in further. It seems to be an issue.
Re: Failed to update and now cannot boot, showing initramfs
mono chrome wrote:Thanks for attention, everyone!
In my case it was totally /dev/sda1, just as you mentioned. But 'sudo fdisk -l' also told something red about 'Partition 2 does not start on physical sector boundary' - is it somehow related to usb stick i booted system from?coffee412 wrote:I would boot from your bootable iso device and open up a term window. Then find the hard drive. It could be /dev/sda or /dev/sdb ect.. so do a
sudo fdisk -l (thats a lower case L) and take note of the device your hard drive is. Lets say its /dev/sda for arguments. Then lets check the file system and attempt a repair.
Then reboot and see if it fixed things.
sudo fdisk -l.png
And when i tryit fails with /dev/sda1 as well as with /dev/sda2.Code: Select all
e2fsck
sudo e2fsck dev sda2.png
Maybe, if it's worth to note, i noticed one thing: when i've tried to do recovery from bootable usb device, in 'Advanced boot' options there were versions 4.8 and 4.10 - is it different kernel updates?
Also, reinstall is an opinion too (because i always do back-ups to anything important), but i would like to know how to manage 'bad updates' in further. It seems to be an issue.
One must remember to be root to perform such things. Also be sure your filesystems (/dev/sdaX) are not mounted. If you fsck a mounted file system your asking for a major scrambling.
sudoe2fsck is not a command.
sudo e2fsck is what you need.
sudo means run the following as root. You will need to enter your user password to run the command.
Could you just copy and paste the output in your terminal instead of posting a pic. Too hard to see and not worth the effort. Just copy paste your output text and then highlight it all again and click the code button at the top of this editor
Ryzen x1800 Asus Prime x370-Pro 32 gigs Ram RX480 graphics
Dell PE T610, Dell PE T710 - List your hardware Profile: inxi -Fxpmrz
MeshCentral * Virtualbox * Debian * InvoiceNinja * NextCloud * Linux since kernel 2.0.36
Dell PE T610, Dell PE T710 - List your hardware Profile: inxi -Fxpmrz
MeshCentral * Virtualbox * Debian * InvoiceNinja * NextCloud * Linux since kernel 2.0.36
Re: Failed to update and now cannot boot, showing initramfs
If you run via lveDVD or USB, the commands aremono chrome wrote:it fails with /dev/sda1 as well as with /dev/sda2.Code: Select all
e2fsck
Code: Select all
sudo umount /dev/sda1 ## if it is mounted
sudo fsck -fyc /dev/sda1
/dev/sda2
is an extented partition, so do not do anything with it.