[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#909643: marked as done (installation-reports: doing a dist-upgrade from debian7 to debian8 ended with a non bootable system)

Your message dated Sun, 03 Feb 2019 22:10:14 +0100
with message-id <efb604c0acf8948b19d4678a3564fabc292532c4.camel@decadent.org.uk>
and subject line Re: doing a dist-upgrade from debian7 to debian8 ended with a non bootable system
has caused the Debian Bug report #909643,
regarding installation-reports: doing a dist-upgrade from debian7 to debian8 ended with a non bootable system
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
909643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909643
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
On Thu, 24 Jan 2019 16:56:41 +0900 Stephane Tranchemer <
stephane.tranchemer@asahinet.com> wrote:
> I did test once again with a different machine, same result.
> 
> It seems really that initramfs is the culprit here, the old 3.2 kernel from
> debian7 boots fine.
> 
> when thrown back in busybox with the (initramfs) prompt you can do vgchange
> -ay and access partitions.
> So there's no valid reason to get an error about /etc/fstab being not
> accessible nor readable.

The screenshot shows:

"busybox 20040623-1"

You have an ancient version of busybox installed and you must upgrade
it.

Ben.

-- 
Ben Hutchings
Horngren's Observation:
              Among economists, the real world is often a special case.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: