update grub-common grub-pc broke apt
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| debconf (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: debconf
I had grub installed on a RAID-5 Array.
`apt-get update` broke "grub". The last 30 lines repeat again and again...
The following packages will be upgraded:
grub-common grub-pc
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 2156kB of archives.
After this operation, 0B of additional disk space will be used.
Get:1 http://
Get:2 http://
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 2156kB in 0s (4860kB/s)
(Reading database ... 94533 files and directories currently installed.)
Preparing to replace grub-pc 1.98-1ubuntu6 (using .../grub-
Unpacking replacement grub-pc ...
Preparing to replace grub-common 1.98-1ubuntu6 (using .../grub-
Unpacking replacement grub-common ...
Processing triggers for man-db ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
Processing triggers for install-info ...
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Setting up grub-common (1.98-1ubuntu7) ...
Setting up grub-pc (1.98-1ubuntu7) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
Configuring grub-pc
-------------------
The GRUB boot loader was previously installed to a disk that is no longer
present, or whose normally unique identifier has changed for some reason. It is
important to make sure that the installed GRUB stays in sync with other
components such as grub.cfg or with newer Linux images it will have to load, and
so you should check again to make sure that GRUB is installed to the appropriate
boot devices.
If you're unsure which drive is designated as boot drive by your BIOS, it is
often a good idea to install GRUB to all of them.
Note: It is possible to install GRUB to partition boot records as well, and some
appropriate partitions are offered here. However, this forces GRUB to use the
blocklist mechanism, which makes it less reliable, and therefore is not
recommended.
1. /dev/sda (1997149 MB, Morphed_JBOD_00)
2. /dev/sdb (1997149 MB, Morphed_JBOD_01)
3. /dev/sdc (1997149 MB, Morphed_JBOD_02)
4. /dev/sdd (1997149 MB, Morphed_JBOD_03)
5. /dev/sde (1997149 MB, Morphed_JBOD_04)
6. /dev/sdf (1997149 MB, Morphed_JBOD_05)
7. /dev/sdg (1997149 MB, Morphed_JBOD_06)
8. /dev/sdh (1997149 MB, Morphed_JBOD_07)
9. /dev/sdi (1997149 MB, Morphed_JBOD_08)
10. /dev/sdj (1997149 MB, Morphed_JBOD_09)
11. /dev/sdk (1997149 MB, Morphed_JBOD_10)
12. /dev/sdl (1997149 MB, Morphed_JBOD_11)
(Enter the items you want to select, separated by spaces.)
GRUB install devices: Use of uninitialized value $ret in chomp at /usr/share/
Use of uninitialized value $_[1] in join or string at /usr/share/
You chose not to install GRUB to any devices. If you continue, the boot loader
may not be properly configured, and when your computer next starts up it will
use whatever was previously in the boot sector. If there is an earlier version
of GRUB 2 in the boot sector, it may be unable to load modules or handle the
current configuration file.
If you are already running a different boot loader and want to carry on doing
so, or if this is a special environment where you do not need a boot loader,
then you should continue anyway. Otherwise, you should install GRUB somewhere.
Continue without installing GRUB? Use of uninitialized value $ret in chomp at /usr/share/
Use of uninitialized value $_[1] in join or string at /usr/share/
The GRUB boot loader was previously installed to a disk that is no longer
present, or whose normally unique identifier has changed for some reason. It is
important to make sure that the installed GRUB stays in sync with other
components such as grub.cfg or with newer Linux images it will have to load, and
so you should check again to make sure that GRUB is installed to the appropriate
boot devices.
If you're unsure which drive is designated as boot drive by your BIOS, it is
often a good idea to install GRUB to all of them.
-------
`dpkg --configure -a`:
Setting up grub-pc (1.98-1ubuntu7) ...
debconf: DbDriver "config": /var/cache/
dpkg: error processing grub-pc (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
grub-pc
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in debconf (Ubuntu): | |
| status: | New → Confirmed |
Status changed to 'Confirmed' because the bug affects multiple users.