Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Unable to boot after aborted package upgrade

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
twk3426
Posts: 1
Joined: 2018-01-17 01:46

Unable to boot after aborted package upgrade

#1 Post by twk3426 »

Hello -

I am running Debian Jessie. Today while running the automated package upgrade, the upgrade aborted, reporting that a script had failed (I don't recall the exact error). After exiting the aborted upgrade, I attempted to reboot, but it failed and I instead received the following error message:

Code: Select all

Loading, please wait...
mdadm: No device listed in conf file were found.   

Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
  - Check rootdelay= (did the system wait long enough?)
  - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/a5af80e7-3640-4f50-b49a-99ae46cb31ed does not exist.
Dropping to a shell!
modprobe: module ehci-orion not found in modules.dep

BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs) 
I am/was running a RAID1 array (it has been a while since I configured it).

It appears that linux boot disk UUID referenced in the GRUB boot stanza is no longer recognized (see ALERT! above). I see that there is a /conf/conf.d/resume file containing the following line:
RESUME=UUID=6752c4d8-f2c6-4820-88eb-5b5799e3ea1f <-- different than the UUID reported in the ALERT! statement)

Unfortunately I am very much a neophyte on diagnosing/fixing low-level linux issues such as these. Any help would be appreciated. Thank you!

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: Unable to boot after aborted package upgrade

#2 Post by Head_on_a_Stick »

You need to boot a "live" ISO image and use that to chroot into your broken system and re-run the aborted upgrade (and let APT fix things if needed).
deadbang

Post Reply