Package: grub2
Version: 2.02~beta2-14
Followup-For: Bug #765540
Dear Maintainer,
my system became unbootable after upgraind from grub 2.00-22 to 2.02~beta2-14
with the error message
symbol 'grub_term_highlight_color' not found
I had to boot a rescue system and downgrade grub again to fix this.
And now I have to learn that this problem is actually known
and the packages was still allowed to migrate, which leaves me completely
puzzled.
I can attach a picture of the rror if that helps, but it seems you are
more interested in the output of some commands, so here you go:
$ sudo debconf-show grub-pc
grub-pc/partition_description:
grub-pc/install_devices_disks_changed:
grub2/device_map_regenerated:
grub-pc/disk_description:
* grub-pc/install_devices:
/dev/disk/by-id/ata-Hitachi_HTS547575A9E384_J2540059C322KE
grub-pc/install_devices_empty: false
grub2/kfreebsd_cmdline:
grub-pc/mixed_legacy_and_grub2: true
* grub2/linux_cmdline_default: quiet
grub2/kfreebsd_cmdline_default: quiet
grub-pc/kopt_extracted: false
grub-pc/chainload_from_menu.lst: true
grub-pc/hidden_timeout: false
grub-pc/install_devices_failed: false
* grub2/linux_cmdline:
grub-pc/install_devices_failed_upgrade: true
grub-pc/timeout: 3
grub-pc/postrm_purge_boot_grub: false
$ sudo cat /proc/mounts
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=10240k,nr_inodes=1010331,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,relatime,size=1620492k,mode=755 0 0
/dev/mapper/cryptvg-rootlv / ext4
rw,relatime,discard,errors=remount-ro,data=ordered 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup
rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd
0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup
rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup
rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/perf_event cgroup
rw,nosuid,nodev,noexec,relatime,perf_event 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs
rw,relatime,fd=21,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0
tmpfs /tmp tmpfs rw 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
/dev/mapper/cryptvg-homelv /home ext4
rw,relatime,discard,errors=remount-ro,data=ordered 0 0
/dev/sdb2 /boot ext4 rw,relatime,discard,errors=remount-ro,data=ordered 0 0
/dev/mapper/store /mnt/store ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
tmpfs /run/user/110 tmpfs
rw,nosuid,nodev,relatime,size=810248k,mode=700,uid=110,gid=117 0 0
tmpfs /run/user/1000 tmpfs
rw,nosuid,nodev,relatime,size=810248k,mode=700,uid=1000,gid=1000 0 0
$ sudo ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 9 Oct 16 22:59
ata-Hitachi_HTS547575A9E384_J2540059C322KE -> ../../sda
lrwxrwxrwx 1 root root 10 Oct 16 22:59
ata-Hitachi_HTS547575A9E384_J2540059C322KE-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Oct 16 22:59
ata-Hitachi_HTS547575A9E384_J2540059C322KE-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Oct 16 22:59
ata-Hitachi_HTS547575A9E384_J2540059C322KE-part4 -> ../../sda4
lrwxrwxrwx 1 root root 9 Oct 16 22:59
ata-Samsung_SSD_840_PRO_Series_S1ATNSAD717874B -> ../../sdb
lrwxrwxrwx 1 root root 10 Oct 16 22:59
ata-Samsung_SSD_840_PRO_Series_S1ATNSAD717874B-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Oct 16 22:59
ata-Samsung_SSD_840_PRO_Series_S1ATNSAD717874B-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-name-cryptpv -> ../../dm-0
lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-name-cryptvg-homelv -> ../../dm-2
lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-name-cryptvg-rootlv -> ../../dm-1
lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-name-cryptvg-swaplv -> ../../dm-3
lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-name-store -> ../../dm-4
lrwxrwxrwx 1 root root 10 Oct 16 22:59
dm-uuid-CRYPT-LUKS1-406e399ce7b142b48a2ff35346797b8f-cryptpv -> ../../dm-0
lrwxrwxrwx 1 root root 10 Oct 16 22:59
dm-uuid-CRYPT-LUKS1-931f27b22a6841f58108104d494cd284-store -> ../../dm-4
lrwxrwxrwx 1 root root 10 Oct 16 22:59
dm-uuid-LVM-sApY335FtcFuHL2m19uYEfus1ztFVjpNKF1Y0gALnWEBRKiPAkcEYexuCXOFW40j ->
../../dm-1
lrwxrwxrwx 1 root root 10 Oct 16 22:59
dm-uuid-LVM-sApY335FtcFuHL2m19uYEfus1ztFVjpNmTjHP0oJbPs8IQQZdXoyJHWy9XelP7kG ->
../../dm-2
lrwxrwxrwx 1 root root 10 Oct 16 22:59
dm-uuid-LVM-sApY335FtcFuHL2m19uYEfus1ztFVjpNOEiDlPiIwuIw9sD30JQ2Tn5K3fZNscH2 ->
../../dm-3
lrwxrwxrwx 1 root root 10 Oct 16 22:59
lvm-pv-uuid-pSnle7-vu3S-t2pM-Mt7p-dRlq-YiTP-VxucVI -> ../../dm-0
lrwxrwxrwx 1 root root 9 Oct 16 22:59 wwn-0x5000cca6dfc164ee -> ../../sda
lrwxrwxrwx 1 root root 10 Oct 16 22:59 wwn-0x5000cca6dfc164ee-part1 ->
../../sda1
lrwxrwxrwx 1 root root 10 Oct 16 22:59 wwn-0x5000cca6dfc164ee-part2 ->
../../sda2
lrwxrwxrwx 1 root root 10 Oct 16 22:59 wwn-0x5000cca6dfc164ee-part4 ->
../../sda4
lrwxrwxrwx 1 root root 9 Oct 16 22:59 wwn-0x50025385a00884b2 -> ../../sdb
lrwxrwxrwx 1 root root 10 Oct 16 22:59 wwn-0x50025385a00884b2-part2 ->
../../sdb2
lrwxrwxrwx 1 root root 10 Oct 16 22:59 wwn-0x50025385a00884b2-part3 ->
../../sdb3
Regarding my setup, I have two disks in my laptop. /dev/sda in the HDD that was
shipped
with the machine, which I originally installed Debian on. Later, I added an SSD
/dev/sdb
and moved Debian to it. However, as far as I remember, the machine is still
booting
from the HDD (and the debconf output seems to support that). This always worked
fine,
until today.
I will check my BIOS configuration for the main boot device.
Kind regards
Ralf
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.17.0-rc7+ (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
