Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Sandro Tosi]

i do agree this is a regression from jessie, but it is also something
that happens only on some machines, so it may be something related to
how kernel, bios, and various hardware interacts with each other.

if you are already using a customized preseed file for the
installation, we found that this will workaround the issue, giving us
a bootable system:

d-i preseed/late_command string update-dev; in-target update-grub ;


Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Leonardo Lopes]

Hi guys.

I can confirm that this bug in fact occurs. I am using the official  
netinst media (debian-9.2.0-amd64-netinst.iso, MD5:  
fdf1905e3fa321e0b930e47bcbc4d1e2) to install a Dell R730 server --  
which will be used as a Xen virtualization host -- all the VMs in the  
virtualization structure.


I *all* cases -- physic and virtual machines -- the installation  
finishes without any reference to UUIDs in /boot/grub/grub.cfg. If I  
only run 'update-grub' the 'root=' clauses are updated to use UUIDs.


Additionally, the /etc/fstab appears to be correctly configured with  
the UUIDs, as one would expect.


===

# grep root= /boot/grub/grub.cfg

set root='hd1,msdos2'
set root='hd1,msdos2'
linux   /boot/vmlinuz-4.9.0-4-amd64 root=/dev/sdb2 ro  quiet
set root='hd1,msdos2'
linux   /boot/vmlinuz-4.9.0-4-amd64 root=/dev/sdb2 ro  quiet
set root='hd1,msdos2'
linux   /boot/vmlinuz-4.9.0-4-amd64 root=/dev/sdb2 ro single
# update-grub

Generating grub configuration file ...
Imagem Linux encontrada: /boot/vmlinuz-4.9.0-4-amd64
Imagem initrd encontrada: /boot/initrd.img-4.9.0-4-amd64
concluído

# grep root= /boot/grub/grub.cfg

set root='hd1,msdos2'
set root='hd1,msdos2'
	linux	/boot/vmlinuz-4.9.0-4-amd64  
root=UUID=fec2345a-1188-4f2d-ad47-b9a808fe280a ro  quiet

set root='hd1,msdos2'
		linux	/boot/vmlinuz-4.9.0-4-amd64  
root=UUID=fec2345a-1188-4f2d-ad47-b9a808fe280a ro  quiet

set root='hd1,msdos2'
		linux	/boot/vmlinuz-4.9.0-4-amd64  
root=UUID=fec2345a-1188-4f2d-ad47-b9a808fe280a ro single


# cat /etc/fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sdb2 during installation
UUID=fec2345a-1188-4f2d-ad47-b9a808fe280a /   ext4 
errors=remount-ro 0   1

# /boot/efi was on /dev/sdb1 during installation
UUID=67A3-323A  /boot/efi   vfatumask=0077  0   1
# /var/log was on /dev/sdb3 during installation
UUID=5e3c4cab4-278d-435e-a5b9-d56a7baf225a /var/logext4 
defaults0   2

# swap was on /dev/sdb4 during installation
UUID=27416194-409c2-4eb9-91a7-a73e050aef91 noneswapsw   
0   0

/dev/sr1/media/cdrom0   udf,iso9660 user,noauto 0   0
/dev/sr0/media/cdrom1   udf,iso9660 user,noauto 0   0

===

Hope you find what is happening.



Atenciosamente,
Leonardo Lopes
DITIC/CEFET-MG


--
Esta mensagem foi verificada pelo sistema de antivírus e
acredita-se estar livre de perigo.

Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Raphael Hertzog]

On Mon, 09 Oct 2017, Michael Stone wrote:
> > I'd still expect the installer to DTRT with UUIDs in that case, though.
> > I'm more thinking of a non-standard bootup / custom kernel or similar...
> 
> Maybe I'm missing something here? Fire up a current debian netinst 9.2 iso
> in a kvm session (no special image or unusual hardware), go through an
> install. On reboot, look at the defult boot entry in grub, note that on the
> kernel command line root=/dev/sda1 (or somesuch) not UUID=X. This is very
> reproducible. In practice this results in an unbootable system for a
> non-expert user if they install from a USB stick that comes up as sda (so
> the grub entry is sdb) and they pull the USB stick out to boot into debian.
> If the kernel command line is manually fixed up, running update-grub after
> boot will create the expected root=UUID=X kernel command line.
> 
> This is a regression from jessie, for which the exact same sequence of
> commands would result in a grub kernel command line with root=UUID=X

This smells similar to the problem I have seen here when update-grub
is run in a chroot:
https://bugs.debian.org/872999

Unfortunately, the root cause is not clear. It looks like a behaviour
change at the kernel level...

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Michael Stone]

I'd still expect the installer to DTRT with UUIDs in that case, 
though. I'm more thinking of a non-standard bootup / custom kernel or 
similar...


Maybe I'm missing something here? Fire up a current debian netinst 9.2 
iso in a kvm session (no special image or unusual hardware), go through 
an install. On reboot, look at the defult boot entry in grub, note that 
on the kernel command line root=/dev/sda1 (or somesuch) not UUID=X. This 
is very reproducible. In practice this results in an unbootable system 
for a non-expert user if they install from a USB stick that comes up as 
sda (so the grub entry is sdb) and they pull the USB stick out to boot 
into debian. If the kernel command line is manually fixed up, running 
update-grub after boot will create the expected root=UUID=X kernel 
command line.


This is a regression from jessie, for which the exact same sequence of 
commands would result in a grub kernel command line with root=UUID=X 


Mike Stone

Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Richard Owlett]

On 01/23/2017 10:03 AM, Steve McIntyre wrote:

On Mon, Jan 23, 2017 at 06:43:27PM +0300, Andrey Jr. Melnikov wrote:

Package: debian-installer
Severity: important
Tags: d-i


Installation procedure of grub2 dont't transform root= entry from /dev/sd?? to 
UUID notation.
This lead to unbootable system after install.


Hmmm. It normally does this reliably in my experience. What version of
d-i did you use, and did you follow through the menus as normal? Is
there anything special about your setup?



I suspect I have a symptom of the same, or very similar, bug.

My environment is unusual:
  1. I'm interested in extremely minimal installs.
  2. I have minimal internet connectivity thus I purchase DVD sets.

While waiting for the latest DVD set to arrive, I decided to download 
debian-9.1.0-i386-netinst.iso and write it to a USB flash drive. I then 
used it to install a very minimal system to another USB flash drive 
plugged into the *SAME USB expander*. I specified that Grub be installed 
to the MBR of the destination flash drive.


My hardware, on power on, will repeatably recognize multiple devices 
attached to the expander in a specific order {based on the physical 
location}. The install went normally and it would boot as expected *as 
long as* the source drive was present -- independent of the bios seeing 
the primary hard drive or the flash drive as the boot device. [1]


If only the destination device was present at boot time there were 
multiple scenarios.


If the bios saw the flash device as the boot device *and only if* its 
grub.cfg had had all references to /dev/sdd changed to /dev/sdb, it 
would boot successfully. [2]


The situation is more complicated if the active grub is in the MBR of 
the permanently installed HDD (/dev/sda). I had noticed that running 
update-grub did not always yield a workable menu entry. It's a 
pathological corner case and I did not record the circumstances.


I see the need to perform multiple installs to document exactly what 
factors trigger a failure. Before I run them I need to know what log 
files I should preserve for each case.


I also suspect that Bug#876866 is related.


[1]  What happens is dependent on whether or not my WiFi hub is attached 
to the USB3 port having priority over the USB2 port into which the port 
expander was attached.


[2]  My WiFi was plugged into the USB3 port during install.

Re: Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Richard Owlett]

On 10/06/2017 08:11 AM, Richard Owlett sent to the wrong list.

Re: Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Richard Owlett]

On 01/23/2017 10:03 AM, Steve McIntyre wrote:

On Mon, Jan 23, 2017 at 06:43:27PM +0300, Andrey Jr. Melnikov wrote:

Package: debian-installer
Severity: important
Tags: d-i


Installation procedure of grub2 dont't transform root= entry from /dev/sd?? to 
UUID notation.
This lead to unbootable system after install.


Hmmm. It normally does this reliably in my experience. What version of
d-i did you use, and did you follow through the menus as normal? Is
there anything special about your setup?




I suspect I have a symptom of the same, or very similar, bug.

My environment is unusual:
  1. I'm interested in extremely minimal installs.
  2. I have minimal internet connectivity thus I purchase DVD sets.

While waiting for the latest DVD set to arrive, I decided to download 
debian-9.1.0-i386-netinst.iso and write it to a USB flash drive. I then 
used it to install a very minimal system to another USB flash drive 
plugged into the *SAME USB expander*. I specified that Grub be installed 
to the MBR of the destination flash drive.


My hardware, on power on, will repeatably recognize multiple devices 
attached to the expander in a specific order {based on the physical 
location}. The install went normally and it would boot as expected *as 
long as* the source drive was present -- independent of the bios seeing 
the primary hard drive or the flash drive as the boot device. [1]


If only the destination device was present at boot time there were 
multiple scenarios.


If the bios saw the flash device as the boot device *and only if* its 
grub.cfg had had all references to /dev/sdd changed to /dev/sdb, it 
would boot successfully. [2]


The situation is more complicated if the active grub is in the MBR of 
the permanently installed HDD (/dev/sda). I had noticed that running 
update-grub did not always yield a workable menu entry. It's a 
pathological corner case and I did not record the circumstances.


I see the need to perform multiple installs to document exactly what 
factors trigger a failure. Before I run them I need to know what log 
files I should preserve for each case.


I also suspect that Bug#876866 is related.


[1]  What happens is dependent on whether or not my WiFi hub is attached 
to the USB3 port having priority over the USB2 port into which the port 
expander was attached.


[2]  My WiFi was plugged into the USB3 port during install.

Re: Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Richard Owlett]

On 01/23/2017 10:03 AM, Steve McIntyre wrote:

On Mon, Jan 23, 2017 at 06:43:27PM +0300, Andrey Jr. Melnikov wrote:

Package: debian-installer
Severity: important
Tags: d-i


Installation procedure of grub2 dont't transform root= entry from /dev/sd?? to 
UUID notation.
This lead to unbootable system after install.


Hmmm. It normally does this reliably in my experience. What version of
d-i did you use, and did you follow through the menus as normal? Is
there anything special about your setup?




I suspect I have a symptom of the same, or very similar, bug.

My environment is unusual:
  1. I'm interested in extremely minimal installs.
  2. I have minimal internet connectivity thus I purchase DVD sets.

While waiting for the latest DVD set to arrive, I decided to download 
debian-9.1.0-i386-netinst.iso and write it to a USB flash drive. I then 
used it to install a very minimal system to another USB flash drive 
plugged into the *SAME USB expander*. I specified that Grub be installed 
to the MBR of the destination flash drive.


My hardware, on power on, will repeatably recognize multiple devices 
attached to the expander in a specific order {based on the physical 
location}. The install went normally and it would boot as expected *as 
long as* the source drive was present -- independent of the bios seeing 
the primary hard drive or the flash drive as the boot device. [1]


If only the destination device was present at boot time there were 
multiple scenarios.


If the bios saw the flash device as the boot device *and only if* its 
grub.cfg had had all references to /dev/sdd changed to /dev/sdb, it 
would boot successfully. [2]


The situation is more complicated if the active grub is in the MBR of 
the permanently installed HDD (/dev/sda). I had noticed that running 
update-grub did not always yield a workable menu entry. It's a 
pathological corner case and I did not record the circumstances.


I see the need to perform multiple installs to document exactly what 
factors trigger a failure. Before I run them I need to know what log 
files I should preserve for each case.


I also suspect that Bug#876866 is related.


[1]  What happens is dependent on whether or not my WiFi hub is attached 
to the USB3 port having priority over the USB2 port into which the port 
expander was attached.


[2]  My WiFi was plugged into the USB3 port during install.

Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Andrey Melnikov]

additional data (chroot'ed from installer console)

root@server:/# ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Jan 24 14:41
e5635a37-b72e-40e7-85b5-4a40867a2f71 -> ../../sdb1
root@server:/# blkid
/dev/sda1: TYPE="vfat"
/dev/sdb2: UUID="dbe73c33-f6ad-43b1-8976-c8b6cee7a673" TYPE="swap"
PARTUUID="40d1b763-199c-446d-9fd5-008086740fb2"
/dev/sdb3: UUID="01385666-8e64-46de-9edf-5c86bf5a7b5e" TYPE="ext4"
PARTUUID="f89d01ef-1b38-42b2-a04e-2f8303a87eb7"
/dev/sdb4: UUID="0daa25cb-257d-4e52-a20b-4fa2a1b95486" TYPE="ext4"
PARTUUID="2352072f-e7a5-4ad5-a6c7-910a5bf9bb3c"
/dev/sdb1: PARTUUID="43c414a3-63a2-4949-b337-fc381fa48ec5"
root@server:/#

running /bin/update-dev in installer env by hands - change situation a bit:
root@server:/# ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Jan 24 16:24
01385666-8e64-46de-9edf-5c86bf5a7b5e -> ../../sdb3
lrwxrwxrwx 1 root root 10 Jan 24 16:24
0daa25cb-257d-4e52-a20b-4fa2a1b95486 -> ../../sdb4
lrwxrwxrwx 1 root root 10 Jan 24 16:24
dbe73c33-f6ad-43b1-8976-c8b6cee7a673 -> ../../sdb2

after this - reinstall grub from installer window - and it write
correct line in grub.cfg "linux   /boot/vmlinuz-4.8.0-2-amd64
root=UUID=01385666-8e64-46de-9edf-5c86bf5a7b5e ro  quiet"

Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Andrey Melnikov]

2017-01-23 19:03 GMT+03:00 Steve McIntyre :
> On Mon, Jan 23, 2017 at 06:43:27PM +0300, Andrey Jr. Melnikov wrote:
>>Package: debian-installer
>>Severity: important
>>Tags: d-i
>>
>>
>>Installation procedure of grub2 dont't transform root= entry from /dev/sd?? 
>>to UUID notation.
>>This lead to unbootable system after install.
>
> Hmmm. It normally does this reliably in my experience. What version of
> d-i did you use, and did you follow through the menus as normal? Is
Netboot image (This is a Debian 9 (stretch) installation netboot
image. It was built on 20170112.) with integrated preseed.cfg and
adjusted syslinux timeouts.

> there anything special about your setup?
Nothing. Supermicro server, one disk 4Tb - hardware raid 1 (apadtec
ASR-8805). iso booted from usb-flash (there is no CD-ROM).

Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Lennart Sorensen]

On Mon, Jan 23, 2017 at 04:03:06PM +, Steve McIntyre wrote:
> On Mon, Jan 23, 2017 at 06:43:27PM +0300, Andrey Jr. Melnikov wrote:
> >Package: debian-installer
> >Severity: important
> >Tags: d-i
> >
> >
> >Installation procedure of grub2 dont't transform root= entry from /dev/sd?? 
> >to UUID notation. 
> >This lead to unbootable system after install.
> 
> Hmmm. It normally does this reliably in my experience. What version of
> d-i did you use, and did you follow through the menus as normal? Is
> there anything special about your setup?

Well the log indicates the use of a GPT partition table with BIOS boot
and not creating the GPT bios boot partition.  So at least that qualifies
as not normal.

Perhaps that is an indication that the system is supposed to be EFI
booted but somehow the installer was booted in the wrong mode.

-- 
Len Sorensen

Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Steve McIntyre]

On Mon, Jan 23, 2017 at 11:19:02AM -0500, Lennart Sorensen wrote:
>On Mon, Jan 23, 2017 at 04:03:06PM +, Steve McIntyre wrote:
>> On Mon, Jan 23, 2017 at 06:43:27PM +0300, Andrey Jr. Melnikov wrote:
>> >Package: debian-installer
>> >Severity: important
>> >Tags: d-i
>> >
>> >
>> >Installation procedure of grub2 dont't transform root= entry from /dev/sd?? 
>> >to UUID notation. 
>> >This lead to unbootable system after install.
>> 
>> Hmmm. It normally does this reliably in my experience. What version of
>> d-i did you use, and did you follow through the menus as normal? Is
>> there anything special about your setup?
>
>Well the log indicates the use of a GPT partition table with BIOS boot
>and not creating the GPT bios boot partition.  So at least that qualifies
>as not normal.
>
>Perhaps that is an indication that the system is supposed to be EFI
>booted but somehow the installer was booted in the wrong mode.

I'd still expect the installer to DTRT with UUIDs in that case,
though. I'm more thinking of a non-standard bootup / custom kernel or
similar...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"I used to be the first kid on the block wanting a cranial implant,
 now I want to be the first with a cranial firewall. " -- Charlie Stross

Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Steve McIntyre]

On Mon, Jan 23, 2017 at 06:43:27PM +0300, Andrey Jr. Melnikov wrote:
>Package: debian-installer
>Severity: important
>Tags: d-i
>
>
>Installation procedure of grub2 dont't transform root= entry from /dev/sd?? to 
>UUID notation. 
>This lead to unbootable system after install.

Hmmm. It normally does this reliably in my experience. What version of
d-i did you use, and did you follow through the menus as normal? Is
there anything special about your setup?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Managing a volunteer open source project is a lot like herding
 kittens, except the kittens randomly appear and disappear because they
 have day jobs." -- Matt Mackall

Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Andrey Jr. Melnikov]

Package: debian-installer
Severity: important
Tags: d-i


Installation procedure of grub2 dont't transform root= entry from /dev/sd?? to 
UUID notation. 
This lead to unbootable system after install.

-- cut --
Jan 19 12:39:50 pkgsel: finishing up
Jan 19 12:39:50 main-menu[6301]: INFO: Falling back to the package description 
for brltty-udeb
Jan 19 12:41:20 main-menu[6301]: INFO: Falling back to the package description 
for brltty-udeb
Jan 19 12:41:20 main-menu[6301]: INFO: Menu item 'grub-installer' selected
Jan 19 12:41:20 grub-installer: info: architecture: amd64/generic
Jan 19 12:41:20 in-target: Reading package lists...
Jan 19 12:41:20 in-target: 
Jan 19 12:41:20 in-target: Building dependency tree...
Jan 19 12:41:20 in-target: 
Jan 19 12:41:20 in-target: Reading state information...
Jan 19 12:41:20 in-target: 
Jan 19 12:41:20 in-target: The following additional packages will be installed:
Jan 19 12:41:20 in-target:   gettext-base libfreetype6 libfuse2 libpng16-16
Jan 19 12:41:20 in-target: Suggested packages:
Jan 19 12:41:20 in-target:   multiboot-doc grub-emu xorriso desktop-base fuse
Jan 19 12:41:20 in-target: Recommended packages:
Jan 19 12:41:20 in-target:   os-prober
Jan 19 12:41:20 in-target: The following NEW packages will be installed:
Jan 19 12:41:20 in-target:   gettext-base grub-common libfreetype6 libfuse2 
libpng16-16
Jan 19 12:41:22 in-target: 0 upgraded, 5 newly installed, 0 to remove and 0 not 
upgraded.
Jan 19 12:41:22 in-target: Need to get 3,135 kB of archives.
Jan 19 12:41:22 in-target: After this operation, 17.5 MB of additional disk 
space will be used.
Jan 19 12:41:22 in-target: Get:2 http://debian.noc.ntua.gr/debian stretch/main 
amd64 libpng16-16 amd64 1.6.26-6 [280 kB]
Jan 19 12:41:22 in-target: Get:1 http://ftp.debian.chuvsu.ru/debian 
stretch/main amd64 gettext-base amd64 0.19.8.1-1 [121 kB]
Jan 19 12:41:22 in-target: Get:5 http://ftp.bme.hu/debian stretch/main amd64 
grub-common amd64 2.02~beta3-3 [2,173 kB]
Jan 19 12:41:23 in-target: Get:3 http://debian.noc.ntua.gr/debian stretch/main 
amd64 libfreetype6 amd64 2.6.3-3+b1 [437 kB]
Jan 19 12:41:24 in-target: Get:4 http://debian.noc.ntua.gr/debian stretch/main 
amd64 libfuse2 amd64 2.9.7-1 [125 kB]
Jan 19 12:41:28 in-target: Fetched 3,135 kB in 7s (422 kB/s)
...
Jan 19 12:41:28 in-target: Preparing to unpack 
.../grub-common_2.02~beta3-3_amd64.deb ...^M
Jan 19 12:41:28 in-target: Unpacking grub-common (2.02~beta3-3) ...^M
Jan 19 12:41:29 in-target: Setting up libpng16-16:amd64 (1.6.26-6) ...^M
Jan 19 12:41:29 in-target: Setting up libfuse2:amd64 (2.9.7-1) ...^M
Jan 19 12:41:29 in-target: Setting up gettext-base (0.19.8.1-1) ...^M
Jan 19 12:41:29 in-target: Setting up libfreetype6:amd64 (2.6.3-3+b1) ...^M
Jan 19 12:41:29 in-target: Processing triggers for libc-bin (2.24-8) ...^M
Jan 19 12:41:29 in-target: Setting up grub-common (2.02~beta3-3) ...^M
Jan 19 12:41:29 in-target: Reading package lists...
Jan 19 12:41:29 in-target: 
Jan 19 12:41:29 in-target: Building dependency tree...
Jan 19 12:41:30 in-target: 
Jan 19 12:41:30 in-target: Reading state information...
Jan 19 12:41:30 in-target: 
Jan 19 12:41:30 in-target: grub-common is already the newest version 
(2.02~beta3-3).
Jan 19 12:41:30 in-target: 0 upgraded, 0 newly installed, 0 to remove and 0 not 
upgraded.
Jan 19 12:41:30 grub-installer: info: Identified partition label for /dev/sdb1: 
gpt
Jan 19 12:41:30 grub-installer: dpkg: warning: ignoring request to remove grub 
which isn't installed
Jan 19 12:41:30 grub-installer: dpkg: warning: ignoring request to remove 
grub-legacy which isn't installed
Jan 19 12:41:30 grub-installer: dpkg: warning: ignoring request to remove 
grub-efi which isn't installed
Jan 19 12:41:30 grub-installer: dpkg: warning: ignoring request to remove 
grub-efi-amd64-bin which isn't installed
Jan 19 12:41:30 grub-installer: dpkg: warning: ignoring request to remove 
grub-efi-amd64 which isn't installed
Jan 19 12:41:30 grub-installer: dpkg: warning: ignoring request to remove 
grub-efi-ia32-bin which isn't installed
Jan 19 12:41:30 grub-installer: dpkg: warning: ignoring request to remove 
grub-efi-ia32 which isn't installed
Jan 19 12:41:30 in-target: Reading package lists...
Jan 19 12:41:31 in-target: 
Jan 19 12:41:31 in-target: Building dependency tree...
Jan 19 12:41:31 in-target: 
Jan 19 12:41:31 in-target: Reading state information...
Jan 19 12:41:31 in-target: 
Jan 19 12:41:31 in-target: The following additional packages will be installed:
Jan 19 12:41:31 in-target:   grub-pc-bin grub2-common
Jan 19 12:41:31 in-target: Suggested packages:
Jan 19 12:41:31 in-target:   desktop-base
Jan 19 12:41:31 in-target: The following NEW packages will be installed:
Jan 19 12:41:31 in-target:   grub-pc grub-pc-bin grub2-common
Jan 19 12:41:32 in-target: 0 upgraded, 3 newly installed, 0 to remove and 0 not 
upgraded.
Jan 19 12:41:32 in-target: Need to get 1,619 kB of archives.
Jan 19 12:41:32 in-target: After this operation, 4,709 kB of additional disk