Bug#954134: [d-i bullseye alpha2] installing grub fails

[Steve McIntyre <steve@einval.com>]

Hi Holger,

On Tue, Mar 17, 2020 at 11:13:27AM +0100, Holger Wansing wrote:
>
>Holger Wansing <hwansing@mailbox.org> wrote:
>> > 
>> > I will sent installation logs shortly.
>> 
>> Logs attached.
>
>The relevant part seems to be:

...

>Mar 16 09:55:43 main-menu[285]: (process:1258): corrupted size vs. prev_size
>Mar 16 09:55:43 main-menu[285]: (process:1258): Aborted

Ooh, that's not good.

>Mar 16 09:55:43 main-menu[285]: (process:1258): File descriptor 3 (pipe:[11552]) leaked on lvdisplay invocation.
>Mar 16 09:55:43 main-menu[285]: (process:1258):  Parent PID 1549: /bin/sh
>Mar 16 09:55:43 main-menu[285]: (process:1258): File descriptor 4 (/dev/pts/0) leaked on lvdisplay invocation.
>Mar 16 09:55:43 main-menu[285]: (process:1258):  Parent PID 1549: /bin/sh
>Mar 16 09:55:43 main-menu[285]: (process:1258): File descriptor 5 (/dev/pts/0) leaked on lvdisplay invocation.
>Mar 16 09:55:43 main-menu[285]: (process:1258):  Parent PID 1549: /bin/sh
>Mar 16 09:55:43 main-menu[285]: (process:1258): File descriptor 6 (/dev/pts/0) leaked on lvdisplay invocation.
>Mar 16 09:55:43 main-menu[285]: (process:1258):  Parent PID 1549: /bin/sh
>Mar 16 09:55:43 main-menu[285]: (process:1258):   
>Mar 16 09:55:43 main-menu[285]: (process:1258): Volume group "sda" not found
>Mar 16 09:55:43 main-menu[285]: (process:1258):   Cannot process volume group sda
>Mar 16 09:55:43 main-menu[285]: (process:1258): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename
>Mar 16 09:55:43 main-menu[285]: (process:1258): corrupted size vs. prev_size
>Mar 16 09:55:43 main-menu[285]: (process:1258): Aborted
>Mar 16 09:55:43 main-menu[285]: (process:1258): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename
>Mar 16 09:55:43 main-menu[285]: (process:1258): grub-probe: error: unknown filesystem.

I can see from your log that you're just using ext4 for the new
system, and you're booting in BIOS mode. Any other disks attached to
the system?

Testing at the weekend didn't show any problems for me or Andy. I'm
doing an explicit re-test now so I can check for any of the above
messages in my log.s

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
< liw> everything I know about UK hotels I learned from "Fawlty Towers"