Hi,

Roger Price wrote:
>   Device hd0: Filesystem type ISO9660 - Label 'Debian 12.7.0 amd64 n'
> [...]
> So it looks as if hd0 is the installation USB stick.

Indeed (unless you have a hard disk with an ISO 9660 filesystem around
the disk's partitions).


> I don't understand why the USB stick no longer boots, since it did in the
> past, on this same workstation.

Does the USB stick yield the proper checksum when inspected on a running
GNU/Linux system ?
Assuming that the USB stick is /dev/sdc and that you got file SHA512SUMS
from where the ISO image was offered for download:

  $ sudo /sbin/isosize -x /dev/sdc
  sector count: 323072, sector size: 2048
  $ sudo dd if=/dev/sdc count=323072 bs=2048 | sha512sum | awk '{print $1}'
  
e0bd9ba03084a6fd42413b425a2d20e3731678a31fe5fb2cc84f79332129afca2ad4ec897b4224d6a833afaf28a5d938b0fe5d680983182944162c6825b135ce
  $ fgrep debian-12.7.0-amd64-netinst.iso SHA512SUMS
  
e0bd9ba03084a6fd42413b425a2d20e3731678a31fe5fb2cc84f79332129afca2ad4ec897b4224d6a833afaf28a5d938b0fe5d680983182944162c6825b135ce
  debian-12.7.0-amd64-netinst.iso
  $ test 
e0bd9ba03084a6fd42413b425a2d20e3731678a31fe5fb2cc84f79332129afca2ad4ec897b4224d6a833afaf28a5d938b0fe5d680983182944162c6825b135ce
 = 
e0bd9ba03084a6fd42413b425a2d20e3731678a31fe5fb2cc84f79332129afca2ad4ec897b4224d6a833afaf28a5d938b0fe5d680983182944162c6825b135ce
 && echo IT MATCHES
  IT MATCHES
  $

If the checksums look different or if the final test command does not
yield "IT MATCHES", then some change has happened to the ISO on the USB
stick. (You may check file debian-12.7.0-amd64-netinst.iso the same way
as /dev/sdc to check whether already the ISO image was altered.)


>  grub> cat (hd0,msdos2)/efi/debian/grub.cfg
>   search --file --set=root /.disk/id/e8185...
>   set prefix-($root)/boot/grub

I see "=" instead of "-" in this file when the partition is mounted:

  set prefix=($root)/boot/grub

Better check whether you see the same when inspecting the file by GRUB.


>   source $prefix/${grub_cpu}-efi/grub.cfg

Does GRUB find the files:

  (hd0)/boot/grub/x86_64-efi/grub.cfg
  (hd0)/boot/grub/grub.cfg

I assume /${grub_cpu} is "x86_64". A 32-bit EFI might want the other
file (hd0)/boot/grub/i386-efi/grub.cfg. Both are supposed to just contain
the instruction

  source /boot/grub/grub.cfg

The file (hd0)/boot/grub/grub.cfg is supposed to contain a typical GRUB
configuration with 162 lines:

  if [ x$feature_default_font_path = xy ] ; then
  ...
  menuentry --hotkey=g 'Graphical install' {
      set background_color=black
      linux    /install.amd/vmlinuz vga=788 --- quiet
      initrd   /install.amd/gtk/initrd.gz
  }
  ...
  menuentry --hotkey=s 'Install with speech synthesis' {
      set background_color=black
      linux    /install.amd/vmlinuz vga=788 speakup.synth=soft --- quiet
      initrd   /install.amd/gtk/initrd.gz
  }

GRUB is supposed to show a graphical menu after having read this file.

If it does not find the file, then you might get progress by executing
the commands of your favorite menu item in the shell. E.g with
"Graphical install":

  grub> set background_color=black
  grub> linux    /install.amd/vmlinuz vga=788 --- quiet
  grub> initrd   /install.amd/gtk/initrd.gz

and to start the action:

  grub> boot

But there might be more obstacles, given that the menu does not show up.


Have a nice day :)

Thomas

Reply via email to