Bug#909643: installation-reports: doing a dist-upgrade from debian7 to debian8 ended with a non bootable system
Hello, Thanks for your concern. On 27 September 2018 at 10:32, Ben Hutchings wrote: > > What is the kernel command line? (Run "cat /proc/cmdline" to show it.) > With the bootable kernel 3.2 # uname -a Linux ahs-clone 3.2.0-6-686-pae #1 SMP Debian 3.2.102-1 i686 GNU/Linux # cat /etc/debian_version 8.11 # cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.2.0-6-686-pae root=/dev/mapper/vg00-root ro In a non-bootable state in initramfs prompt with kernel 3.16 BOOT_IMAGE=/vmlinuz-3.16.0-6-686-pae root=/dev/mapper/vg00-root ro > > Please also send a copy of the /etc/initramfs-tools/initramfs.conf > file. > Here is the file in attachment. Thank you. -- - Tranchemer Stephane System dept. Asahinet, inc. Kabukiza tower 21st Fl. 4-12-15 Ginza Chuo-ku, Tokyo 104-0061 Japan initramfs.conf Description: Binary data
Bug#909643: installation-reports: doing a dist-upgrade from debian7 to debian8 ended with a non bootable system
Control: reassign -1 src:initramfs-tools 0.120+deb8u3 Control: tag -1 moreinfo On Wed, 2018-09-26 at 17:13 +0900, stranche wrote: > Package: installation-reports > Severity: normal > > Dear Maintainer, > >* What led up to the situation? > doing a dist-upgrade from debian7 to debian8 > >* What exactly did you do (or not do) that was effective (or ineffective)? > # apt-get upgrade > editing /etc/apt/sources.list changing instances of "wheezy" to "jessie" > # apt-get update > # apt-get upgrade > # apt-get dist-upgrade > # apt-get autoremove > reboot > >* What was the outcome of this action? > system boots a newly installed 3.16.0-6-686-pae kernel but gets stuck > on a BusyBox initramfs prompt > > kernel 3.2.0-6-686-pae from previous distribution works fine > > kernel/initrd files copied form a working debian8 that was installed > from scratch with CD on an identical machine boots fine too > > if update-initramfs -u is ran to update the initrd, the resulting > initrd file makes the system in the same unbootable state > > when at initramfs prompt, it is possible to > -activate LVM with vgchange -ay > -mount and access the root partition > However, ussing the "exit" command ends up in a kernel panic, root > filesystem being mounted on /root or not [...] What is the kernel command line? (Run "cat /proc/cmdline" to show it.) Please also send a copy of the /etc/initramfs-tools/initramfs.conf file. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part
Bug#909643: installation-reports: doing a dist-upgrade from debian7 to debian8 ended with a non bootable system
Package: installation-reports Severity: normal Dear Maintainer, * What led up to the situation? doing a dist-upgrade from debian7 to debian8 * What exactly did you do (or not do) that was effective (or ineffective)? # apt-get upgrade editing /etc/apt/sources.list changing instances of "wheezy" to "jessie" # apt-get update # apt-get upgrade # apt-get dist-upgrade # apt-get autoremove reboot * What was the outcome of this action? system boots a newly installed 3.16.0-6-686-pae kernel but gets stuck on a BusyBox initramfs prompt kernel 3.2.0-6-686-pae from previous distribution works fine kernel/initrd files copied form a working debian8 that was installed from scratch with CD on an identical machine boots fine too if update-initramfs -u is ran to update the initrd, the resulting initrd file makes the system in the same unbootable state when at initramfs prompt, it is possible to -activate LVM with vgchange -ay -mount and access the root partition However, ussing the "exit" command ends up in a kernel panic, root filesystem being mounted on /root or not the last lines in the console: done. Target filesystem doesn't have requested /sbin/init. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... mount: Mounting /dev on /root/dev failed : No such file or directory doe. No Init found. Try passing init= bootarg. [several messages about ACPI and USB related stuff like usbcore initialization [ [ [ [ [ [ [ [ [ [ BusyBox v1.00-pre10 (Debian 20040623-1) Built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned off (initramfs) * What outcome did you expect instead? system run with newly installed distribution and its kernel/initrd flawlessly
