Bug#775560: upgrade-reports: Wheezy -> Jessie: machine becomes unbootable due to missing Grub
Hi,
I can confirm I have experienced this problem as well. First I ran an
automated install of Wheezy from a Squeeze (Debian 6) recovery image.
Then I upgraded a few packages from wheezy to wheezy-backports but had
apt-get dependencies I could not solve. So I upgraded to Jessie.
After the upgrade to Jessie I got a warning that grub could not be found
etc. I thought "this is crazyness, of course my server has grub, I've
seen it and it boots."
I rebooted, and discovered that in fact, grub that was installed by
Squeeze, was incapable of booting Jessie. (I might be wrong, I'm not a
Debian guru or anything)
My disk layout is as follows
I believe grub was installed on sda and sdb (I didn't do it myself, it
was done by some script of my hosting provider's rescue disk)
sda1 and sdb1 formed md0, which was about 500MB, ext2 filesystem mounted
as /boot.
sda2 and sdb2 form another mdX with LVM.
One of the logical volumes is root, and that was /
This is what I saw when attempting to boot the non-booting system (I
typed this out manually and roughly)
---------------------------------------------
checking root filesystem ... fsck from util linux blah dev mapper
vg0-root clean x/y files blocks etc.
3.2 ext4-fs dm-0 mounted filesytem with ordered data role opts done.
begin running /scripts/local-bottom ... done
begin running /scripts/init-bottom ... done
3.7 systemd failed to mount tmpfs at /sys/fs/cgroup: no such file or
directory.
--------------------------------
Thanks
Reply to: