Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
David wrote: ... >Device to use as root file system /dev/mapper/sda4_crypt >Mount separate /boot parititionYes >Mount separate /boot/efi parititionYes >Rescue operations Force GRUB installation to the >EFI removable media path > -> Yes >Rescue operations Reboot the system > >Power down at POST. Remove debian-10.2.0-amd64-xfce-CD-1 USB >stick. > >Power up. Press F2 to enter Setup. Boot sequence starts with >"debian". Exit. > >Boots into Debian GNU/Linux. >Thanks! :-) \o/ -- Steve McIntyre, Cambridge, UK.st...@einval.com Armed with "Valor": "Centurion" represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud.
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
On 2020-02-08 12:46, Steve McIntyre wrote: select the "Rescue mode" option from the d-i boot menu (which is just an easier way to do that!). It will start d-i as normal, then ask you to identify and mount the root device of the system you're trying to fix Use Dell PowerEdge T30. Insert debian-10.2.0-amd64-xfce-CD-1 USB stick into front top USB 3.0 port. Insert buster USB stick into front bottom USB 3.0 port. Configure Setup for UEFI Secure Boot. Adjust boot order so that UEFI: SanDisk is first. Apply -> Save as Custom User Settings -> Exit Debian GNU/Linux 10.2.0 Debian GNU/Linux UEFI Installer menuAdvanced options -> Rescue Mode LanguageC Continent or region North America Country, territory or area United States Keymap to use American English Hostnamebuster Domain name tracy.holgerdanske.com Full name for the new user debian Select your time zone Pacific Passphrase for /dev/sda4 Device to use as root file system /dev/mapper/sda4_crypt Mount separate /boot paritition Yes Mount separate /boot/efi paritition Yes Rescue operations Force GRUB installation to the EFI removable media path -> Yes Rescue operations Reboot the system Power down at POST. Remove debian-10.2.0-amd64-xfce-CD-1 USB stick. Power up. Press F2 to enter Setup. Boot sequence starts with "debian". Exit. Boots into Debian GNU/Linux. Thanks! :-) David
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
David wrote: >On 2020-02-07 16:47, Steve McIntyre wrote: > >> If you *do* want to install to the removable media path too, then we >> also support that but you have to ask for it. See >> >> >> https://wiki.debian.org/UEFI#Force_grub-efi_installation_to_the_removable_media_path >> >> for details on how to do that. This will probably fix your problem. > >I would like to try this work-around: > > "There is a d-i Rescue Mode option to force this - if you've just >installed Debian on your UEFI system but it won't boot Debian >afterwards, this may fix the problem for you." > >How do I accomplish it? E.g. what choices do I make when booting d-i? >Or, do I use the d-i rescue shell to issue some command? What command? You can add "rescue/enable=true" to the d-i command line to enable resscue mode, or simply select the "Rescue mode" option from the d-i boot menu (which is just an easier way to do that!). It will start d-i as normal, then ask you to identify and mount the root device of the system you're trying to fix. -- Steve McIntyre, Cambridge, UK.st...@einval.com Armed with "Valor": "Centurion" represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud.
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
On 2020-02-07 16:47, Steve McIntyre wrote: Apologies for the slow response - I've had 3 back-to-back conferences and I'm just catching up on mail... :-/ Thanks for the reply. :-) If you *do* want to install to the removable media path too, then we also support that but you have to ask for it. See https://wiki.debian.org/UEFI#Force_grub-efi_installation_to_the_removable_media_path for details on how to do that. This will probably fix your problem. I would like to try this work-around: "There is a d-i Rescue Mode option to force this - if you've just installed Debian on your UEFI system but it won't boot Debian afterwards, this may fix the problem for you." How do I accomplish it? E.g. what choices do I make when booting d-i? Or, do I use the d-i rescue shell to issue some command? What command? David
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
Apologies for the slow response - I've had 3 back-to-back conferences and I'm just catching up on mail... :-/ David wrote: >On 2020-01-30 16:47, Steve McIntyre wrote: >> OK. How exactly have you partitioned the target USB drive? What >> files are on the EFI System Partition there? Did you tell the >> installer to also install grub to the removable media path? That >> would be my first guess for what's missing. > >On 2020-01-30 16:47, Steve McIntyre wrote: >> You don't need to tell grub-install to use x86_64-efi-signed as a >> target - it should work things out automatically and install shim >> etc. as needed. There is*not* a modinfo.sh for the signed grub >> packaging as the signed binaries we build for grub are monolithic >> (i.e. no loadable modules allowed). ... >I zeroed another USB stick and used a Dell PowerEdge T30 in UEFI Secure >Boot mode to install Debian onto the blank USB stick: > > Insert debian-10.2.0-amd64-xfce-CD-1 USB flash drive into > front top USB 3.0 port. > > Insert wiped SanDisk Ultra Fit USB 3.0 16 GB flash drive into > front bottom USB 3.0 port. > > Boot. > > Debian GNU/Linux 10.2.0 > > Debian GNU/Linux UEFI Installer menu Install > Language C > Continent or region North America > Country, territory or areaUnited States > Keymap to use American English > Primary network interface eth0 > Hostname buster > Domain name tracy.holgerdanske.com > Root password > Full name for the new userdebian > Username for your account debian > Choose a password for the new user > Select your time zone Pacific > Partitioning method manual > > Press Alt+F2 and open second virtual terminal. Installation media > is /dev/sdb and blank media is /dev/sda. > > Select sda and create empty partition table. > > Encrypted volume (sda3_crypt) - 1.0 GB Linux device-mapper (crypt) > #1 1.0 GBf swap swap > Encrypted volume (sda4_crypt) - 13.0 GB Linux device-mapper (crypt) > #1 13.0 GBf btrfs / > SCSI5 (0,0,0) (sda) - 15.6 GB SanDisk Ultra Fit >1.0 MB FREE SPACE >#1499.1 MBF ESP buster_esp >#2 1.0 GBF btrfs buster_boot /boot >#3 1.0 GBK crypto buster_swap (sda3_crypt) >#4 12.0 GBK crypto buster_root (sda4_crypt) > 51.4 MB FREESPACE > SCSI6 (0,0,0) (sdb) - 15.6 GB SanDisk Ultra Fit > > Finish partitioning and write changes to disk > Use a network mirror No > Participate in the package usage survey No > Choose software to install > Debian desktop environment > Xfce > standard system utilities > Installation complete Continue > > Power down at POST. > > Remove installation media. > > >Note that I was never prompted to install GRUB. No, for EFI we just do it by default. Due to the ESP, we already know where to install so by default we don't have to prompt like we do in BIOS mode. ... >2020-01-30 21:40:36 root@tinkywinky ~ ># mount -o ro /dev/sdb1 /mnt/sdb1 > >2020-01-30 21:41:05 root@tinkywinky ~ ># mount | grep sdb1 >/dev/sdb1 on /mnt/sdb1 type vfat >(ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro) > >2020-01-30 21:41:37 root@tinkywinky ~ ># ls -AlR /mnt/sdb1 >/mnt/sdb1: >total 4 >drwxr-xr-x 3 root root 4096 Jan 30 19:42 EFI > >/mnt/sdb1/EFI: >total 4 >drwxr-xr-x 2 root root 4096 Jan 30 19:43 debian > >/mnt/sdb1/EFI/debian: >total 5208 >-rwxr-xr-x 1 root root 108 Jan 30 19:43 BOOTX64.CSV >-rwxr-xr-x 1 root root 1206824 Jan 30 19:43 fbx64.efi >-rwxr-xr-x 1 root root 121 Jan 30 19:43 grub.cfg >-rwxr-xr-x 1 root root 1529200 Jan 30 19:43 grubx64.efi >-rwxr-xr-x 1 root root 1261192 Jan 30 19:43 mmx64.efi >-rwxr-xr-x 1 root root 1322936 Jan 30 19:43 shimx64.efi OK, that's all looking like expected for a normal installation. >Inserting the installed stick into the Dell PowerEdge T30 front top USB >3.0 port, powering up, and pressing F2 to enter Setup: > >General -> Boot Sequence -> debian -> View > > Boot Option Name > debian > > File System List > VenHw(99E275E7-75A0-4B37-A2E6-C5385E6C00CB) > > File Name > \EFI\BOOT\BOOTX64.EFI > > >I find it strange that there is no EFI\BOOT\BOOTX64.EFI in the ESP >partition/ filesystem listing, above. That's the removable media path that I mentioned in earlier mail. Operating system installers are *not* meant to
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
On 2020-02-01 04:51, didier.gau...@gmail.com wrote: Hello David, - probably, you were not asked about grub during installation because you did not chose the expert installation mode - possibly, your problems originate, at least in part, from the fact that albeit creating a new ESP (EFI) partition on your USB key, the installer try to use also the ESP partition(s) of the disk(s) on the computer used for the installation. I would suggest to verify that none of the partitions on the disks in the computer (ESP, swap, /boot, etc...) are used during partitionning. Thanks for the reply. :-) When I installed from a USB stick onto a USB stick, the only other drive in the machine was an optical drive with no disc loaded. David
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
Hello David, - probably, you were not asked about grub during installation because you did not chose the expert installation mode - possibly, your problems originate, at least in part, from the fact that albeit creating a new ESP (EFI) partition on your USB key, the installer try to use also the ESP partition(s) of the disk(s) on the computer used for the installation. I would suggest to verify that none of the partitions on the disks in the computer (ESP, swap, /boot, etc...) are used during partitionning.
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
On 2020-01-29 23:07, Keith Bainbridge wrote: Good afternoon I take it that you have booted the .iso and run the installer - on to a separate usb stick. Where did you install grub?If by chance it installed on to sda, then allowing the PC to just boot should run grub and offer the choice of booting debian or win10. What happens if boot from the .iso and plug the other usb in. It should open thunar and list the contents. Running gparted from the .iso and looking at the other usb stick may show something of interest - like did it set to bootable. Are there boot and efi partitions as well as a system partition - showing about 5G used? I'm working on instinct, so feel free to ignore me. On 2020-01-29 23:22, Alexander V. Makartsev wrote: Here is info about one of my disks, GPT partition table with EFI partition, boots fine into UEFI mode without Secure Boot. It's a dual-boot setup (Debian 10 + Windows 10) with GRUB bootloader. Information about partitions from "gdisk" utility: Disk /dev/sdb: 500118192 sectors, 238.5 GiB Model: KINGSTON Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 20DF70EC-1097-4EE4-9BBE-569BE071281B Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 500118158 Partitions will be aligned on 2048-sector boundaries Total free space is 2669 sectors (1.3 MiB) Number Start (sector)End (sector) Size Code Name 1 2048 923647 450.0 MiB 2700 Basic data partition 2 923648 1128447 100.0 MiB EF00 EFI system partition 3 1128448 1161215 16.0 MiB0C01 Microsoft reserved ... 4 1161216 163842047 77.6 GiB0700 Basic data partition 5 163842048 500117503 160.3 GiB 8300 Debian-system On 2020-01-30 00:40, didier.gau...@gmail.com wrote: In your case (USB removable device), perhaps (not sure) you will succeed with the --removable or --force-extra-removable options of grub-install. There is a similar option in the expert mode of installation of Debian at the grub installation step. I have already run Debian in UEFI (non Legacy mode), GPT and Secure Boot with no problem (Secure Boot mode: briefly, I am using Insecure Mode). On 2020-01-30 01:04, Phil Wyett wrote: Hi, I am running buster with two disk setup in laptop (PC Specialist - Lafite 3) - GPT, (U)EFI and Secure Boot enabled. First disk (NVME) is> '/' and second (SSD) is '/home'. Disk /dev/nvme0n1: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk model: WDS500G3X0C-00SJG0 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 245E1C83-E8A6-4F79-90E6-BB2020B3E161 Device Start End Sectors Size Type /dev/nvme0n1p1 2048 1953791 1951744 953M EFI System /dev/nvme0n1p2 914272256 976771071 62498816 29.8G Linux swap /dev/nvme0n1p3 1953792 914272255 912318464 435G Linux filesystem Partition table entries are not in disk order. Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk model: Seagate BarraCud Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 841BBA13-490B-4A02-BB6A-80C088CF51B0 Device Start End Sectors Size Type /dev/sda1 2048 976771071 976769024 465.8G Linux filesystem Regards Phil On 2020-01-30 16:38, Steve McIntyre wrote: Unetbootin has caused many difficult support problems over the years, wasting lots of time for me and other Debian developers. We've worked very hard to make the installer boot and run on diverse computers, then unetbootin has broken things for users. We explicitly disrecommend it for that exact reason. This is even more important with new features like UEFI and Secure Boot. Rufus is a different matter - it has a "DD mode" which*is* useful for writing an image to a USB stick unmolested. On 2020-01-30 16:47, Steve McIntyre wrote: OK. How exactly have you partitioned the target USB drive? What files are on the EFI System Partition there? Did you tell the installer to also install grub to the removable media path? That would be my first guess for what's missing. On 2020-01-30 16:47, Steve McIntyre wrote: You don't need to tell grub-install to use x86_64-efi-signed as a target - it should work things out automatically and install shim etc. as needed. There is*not* a modinfo.sh for the signed grub packaging as the signed binaries we build for grub are monolithic (i.e. no loadable modules allowed). Thank you, everyone, for the replies. :-) Given that the 'grub-install ...' idea did not fix the problem, and also made changes to the "buster" stick, I decided it would be best to wipe the target USB stick and start over. Here is the d-i image I started with: 2020-01-30
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
hans.ullr...@loop.de wrote: >Am Mittwoch, 29. Januar 2020, 19:51:28 CET schrieb David Christensen: >Hi David, > >although it is not recommended as the documentation is telling, but just try >out RUFUS or UNETBOOTIN to create a bootable USB-Stick. > >Maybe this works better than using dd. NO NO NO. Do not listen to this. Unetbootin has caused many difficult support problems over the years, wasting lots of time for me and other Debian developers. We've worked very hard to make the installer boot and run on diverse computers, then unetbootin has broken things for users. We explicitly disrecommend it for that exact reason. This is even more important with new features like UEFI and Secure Boot. Rufus is a different matter - it has a "DD mode" which *is* useful for writing an image to a USB stick unmolested. -- Steve McIntyre, Cambridge, UK.st...@einval.com Armed with "Valor": "Centurion" represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud.
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
David wrote: >debian-users: > >I would like to create a USB flash drive with Debian that I can boot in >new Windows 10 machines with UEFI Secure Boot, so that I can examine >things, run tools, take images of the Windows system drive, etc., before >booting Windows for the first time. > > >I have downloaded, verified the checksum, and burned the following to a >USB flash drive: > > https://cdimage.debian.org/debian-cd/current/amd64/jigdo-cd/ > >debian-10.2.0-amd64-xfce-CD-1.iso > > >Using a Dell PowerEdge T30 with CMOS Setup configured for UEFI and >Secure Boot, I booted d-i and installed onto a wiped USB flash drive -- >hostname "buster". > > >When I attempt to boot buster, the T30 firmware does not see the it: > > No bootable devices found > Press F1 key to retry boot. > Press F2 to reboot into setup. > Press F5 key to run onboard diagnostics. OK. How exactly have you partitioned the target USB drive? What files are on the EFI System Partition there? Did you tell the installer to also install grub to the removable media path? That would be my first guess for what's missing. ... >Using the T30 in Secure Boot again, I booted d-i into a rescue shell, >mounted buster root, boot, efi, dev, proc, and sys, and started Bash: > > root@d-i:/# ls -1 /usr/lib/grub > grub-mkconfig_lib > x86_64-efi > x86_64-efi-signed > > root@d-i:/# grub-install --target x86_64-efi-signed > grub-install: error: /usr/lib/grub/x86_64-efi-signed/modinfo.sh >doesn't exist. Please specify --target or --directory. > > root@d-i:/# find /usr/lib/grub -name modinfo.sh > /usr/lib/grub/x86_64-efi/modinfo.sh > > >It seems /usr/lib/grub/x86_64-efi/modinfo.sh is missing. You don't need to tell grub-install to use x86_64-efi-signed as a target - it should work things out automatically and install shim etc. as needed. There is *not* a modinfo.sh for the signed grub packaging as the signed binaries we build for grub are monolithic (i.e. no loadable modules allowed). -- Steve McIntyre, Cambridge, UK.st...@einval.com Armed with "Valor": "Centurion" represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud.
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
On Wed, 2020-01-29 at 21:27 -0800, David Christensen wrote: > On 2020-01-29 10:51, David Christensen wrote: > > root@d-i:/# grub-install --target x86_64-efi-signed > > grub-install: error: /usr/lib/grub/x86_64-efi- > > signed/modinfo.sh > > doesn't exist. Please specify --target or --directory. > > I was able to install grub for x86_64-efi: > > root@d-i:/# grub-install --target x86_64-efi > Installing for x86_64-efi platform. > Installation finished. No error reported. > > > But, the drive still will not boot in the PowerEdge T30, UEFI, with > or > without Secure Boot, or in the DQ67SW, UEFI without Secure Boot. > > > Is anybody booting and running Buster from a GPT disk using > UEFI? With > or without Secure Boot? > > > David > Hi, I am running buster with two disk setup in laptop (PC Specialist - Lafite 3) - GPT, (U)EFI and Secure Boot enabled. First disk (NVME) is '/' and second (SSD) is '/home'. Disk /dev/nvme0n1: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk model: WDS500G3X0C-00SJG0 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 245E1C83-E8A6-4F79-90E6-BB2020B3E161 Device Start End Sectors Size Type /dev/nvme0n1p1 2048 1953791 1951744 953M EFI System /dev/nvme0n1p2 914272256 976771071 62498816 29.8G Linux swap /dev/nvme0n1p3 1953792 914272255 912318464 435G Linux filesystem Partition table entries are not in disk order. Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk model: Seagate BarraCud Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 841BBA13-490B-4A02-BB6A-80C088CF51B0 Device Start End Sectors Size Type /dev/sda1 2048 976771071 976769024 465.8G Linux filesystem Regards Phil -- *** Playing the game for the games sake. *** WWW: https://kathenas.org Twitter: @kathenasorg IRC: kathenas GPG: 724AA9B52F024C8B signature.asc Description: This is a digitally signed message part
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
Le jeudi 30 janvier 2020 06:30:04 UTC+1, David Christensen a écrit : > On 2020-01-29 10:51, David Christensen wrote: > > root@d-i:/# grub-install --target x86_64-efi-signed > > grub-install: error: /usr/lib/grub/x86_64-efi-signed/modinfo.sh > > doesn't exist. Please specify --target or --directory. > > I was able to install grub for x86_64-efi: > > root@d-i:/# grub-install --target x86_64-efi > Installing for x86_64-efi platform. > Installation finished. No error reported. > > > But, the drive still will not boot in the PowerEdge T30, UEFI, with or > without Secure Boot, or in the DQ67SW, UEFI without Secure Boot. > > > Is anybody booting and running Buster from a GPT disk using UEFI? With > or without Secure Boot? > > > David In your case (USB removable device), perhaps (not sure) you will succeed with the --removable or --force-extra-removable options of grub-install. There is a similar option in the expert mode of installation of Debian at the grub installation step. I have already run Debian in UEFI (non Legacy mode), GPT and Secure Boot with no problem (Secure Boot mode: briefly, I am using Insecure Mode).
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
Good afternoon I take it that you have booted the .iso and run the installer - on to a separate usb stick. Where did you install grub?If by chance it installed on to sda, then allowing the PC to just boot should run grub and offer the choice of booting debian or win10. What happens if boot from the .iso and plug the other usb in. It should open thunar and list the contents. Running gparted from the .iso and looking at the other usb stick may show something of interest - like did it set to bootable. Are there boot and efi partitions as well as a system partition - showing about 5G used? I'm working on instinct, so feel free to ignore me. Keith Bainbridge keith.bainbridge.3...@gmail.com 0447 667 468 On 30/1/20 5:51 am, David Christensen wrote: Using a Dell PowerEdge T30 with CMOS Setup configured for UEFI and Secure Boot, I booted d-i and installed onto a wiped USB flash drive -- hostname "buster".
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
On 30.01.2020 10:27, David Christensen wrote: > On 2020-01-29 10:51, David Christensen wrote: >> root@d-i:/# grub-install --target x86_64-efi-signed >> grub-install: error: /usr/lib/grub/x86_64-efi-signed/modinfo.sh >> doesn't exist. Please specify --target or --directory. > > I was able to install grub for x86_64-efi: > > root@d-i:/# grub-install --target x86_64-efi > Installing for x86_64-efi platform. > Installation finished. No error reported. > > > But, the drive still will not boot in the PowerEdge T30, UEFI, with or > without Secure Boot, or in the DQ67SW, UEFI without Secure Boot. > > > Is anybody booting and running Buster from a GPT disk using UEFI? > With or without Secure Boot? > > > David > Here is info about one of my disks, GPT partition table with EFI partition, boots fine into UEFI mode without Secure Boot. It's a dual-boot setup (Debian 10 + Windows 10) with GRUB bootloader. Information about partitions from "gdisk" utility: Disk /dev/sdb: 500118192 sectors, 238.5 GiB Model: KINGSTON Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 20DF70EC-1097-4EE4-9BBE-569BE071281B Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 500118158 Partitions will be aligned on 2048-sector boundaries Total free space is 2669 sectors (1.3 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 923647 450.0 MiB 2700 Basic data partition 2 923648 1128447 100.0 MiB EF00 EFI system partition 3 1128448 1161215 16.0 MiB 0C01 Microsoft reserved ... 4 1161216 163842047 77.6 GiB 0700 Basic data partition 5 163842048 500117503 160.3 GiB 8300 Debian-system -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
On 2020-01-29 10:51, David Christensen wrote: root@d-i:/# grub-install --target x86_64-efi-signed grub-install: error: /usr/lib/grub/x86_64-efi-signed/modinfo.sh doesn't exist. Please specify --target or --directory. I was able to install grub for x86_64-efi: root@d-i:/# grub-install --target x86_64-efi Installing for x86_64-efi platform. Installation finished. No error reported. But, the drive still will not boot in the PowerEdge T30, UEFI, with or without Secure Boot, or in the DQ67SW, UEFI without Secure Boot. Is anybody booting and running Buster from a GPT disk using UEFI? With or without Secure Boot? David
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
On 2020-01-29 11:28, Peter Ehlert wrote: maybe this will help http://cosmolinux.no-ip.org/raconetlinux2/persistence.html Thanks for the reply. :-) I prefer a working Debian install on a USB flash drive, so I can install whatever tools I choose (including home-grown) in a familiar environment. David
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
On 2020-01-29 11:09, Hans wrote: Am Mittwoch, 29. Januar 2020, 19:51:28 CET schrieb David Christensen: Hi David, although it is not recommended as the documentation is telling, but just try out RUFUS or UNETBOOTIN to create a bootable USB-Stick. Maybe this works better than using dd. Just a suggestion. Best regards Hans Thanks for the reply. :-) dd(1) and cmp(1) are excellent tools for creating and verifying Debian Installer USB flash drives. David
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
maybe this will help http://cosmolinux.no-ip.org/raconetlinux2/persistence.html On 1/29/20 10:51 AM, David Christensen wrote: debian-users: I would like to create a USB flash drive with Debian that I can boot in new Windows 10 machines with UEFI Secure Boot, so that I can examine things, run tools, take images of the Windows system drive, etc., before booting Windows for the first time. I have downloaded, verified the checksum, and burned the following to a USB flash drive: https://cdimage.debian.org/debian-cd/current/amd64/jigdo-cd/ debian-10.2.0-amd64-xfce-CD-1.iso Using a Dell PowerEdge T30 with CMOS Setup configured for UEFI and Secure Boot, I booted d-i and installed onto a wiped USB flash drive -- hostname "buster". When I attempt to boot buster, the T30 firmware does not see the it: No bootable devices found Press F1 key to retry boot. Press F2 to reboot into setup. Press F5 key to run onboard diagnostics. I have tried all of the USB ports -- nope. I disabled Secure Boot and tried all of the USB ports -- nope. So, I wiped the USB flash drive and installed again, without selecting a Debian mirror (in case there are bugs since the 10.2.0 d-i was released) -- nope. I tried all of the USB ports on an Intel DQ67SW desktop motherboard with CMOS Setup configured for UEFI boot (no Secure Boot support): Intel(R) Boot Agent GE v1.3.95 Copyright (C) 1997-2012, Intel Corporation CLIENT MAC ADDR: GUID: PXE-E53: No boot filename received PXE-M0F: Exitng Intel Boot Agent. Reboot and Select proper Boot device or Insert Boo Media in select Boot device and press a key (I recall successfully booting Debian 9 with UEFI in the past.) STFW people have succeeded by running grub-install: https://lists.debian.org/debian-user/2020/01/msg5.html Using the T30 in Secure Boot again, I booted d-i into a rescue shell, mounted buster root, boot, efi, dev, proc, and sys, and started Bash: root@d-i:/# ls -1 /usr/lib/grub grub-mkconfig_lib x86_64-efi x86_64-efi-signed root@d-i:/# grub-install --target x86_64-efi-signed grub-install: error: /usr/lib/grub/x86_64-efi-signed/modinfo.sh doesn't exist. Please specify --target or --directory. root@d-i:/# find /usr/lib/grub -name modinfo.sh /usr/lib/grub/x86_64-efi/modinfo.sh It seems /usr/lib/grub/x86_64-efi/modinfo.sh is missing. Suggestions? David
Re: Fresh install UEFI debian-10.2.0-amd64-xfce-CD-1 will not boot
Am Mittwoch, 29. Januar 2020, 19:51:28 CET schrieb David Christensen: Hi David, although it is not recommended as the documentation is telling, but just try out RUFUS or UNETBOOTIN to create a bootable USB-Stick. Maybe this works better than using dd. Just a suggestion. Best regards Hans > debian-users: > > I would like to create a USB flash drive with Debian that I can boot in > new Windows 10 machines with UEFI Secure Boot, so that I can examine > things, run tools, take images of the Windows system drive, etc., before > booting Windows for the first time. > > > I have downloaded, verified the checksum, and burned the following to a > USB flash drive: > > https://cdimage.debian.org/debian-cd/current/amd64/jigdo-cd/ > > debian-10.2.0-amd64-xfce-CD-1.iso > > > Using a Dell PowerEdge T30 with CMOS Setup configured for UEFI and > Secure Boot, I booted d-i and installed onto a wiped USB flash drive -- > hostname "buster". > > > When I attempt to boot buster, the T30 firmware does not see the it: > > No bootable devices found > Press F1 key to retry boot. > Press F2 to reboot into setup. > Press F5 key to run onboard diagnostics. > > > I have tried all of the USB ports -- nope. > > > I disabled Secure Boot and tried all of the USB ports -- nope. > > > So, I wiped the USB flash drive and installed again, without selecting a > Debian mirror (in case there are bugs since the 10.2.0 d-i was released) > -- nope. > > > I tried all of the USB ports on an Intel DQ67SW desktop motherboard with > CMOS Setup configured for UEFI boot (no Secure Boot support): > > Intel(R) Boot Agent GE v1.3.95 > Copyright (C) 1997-2012, Intel Corporation > > CLIENT MAC ADDR: GUID: > PXE-E53: No boot filename received > > PXE-M0F: Exitng Intel Boot Agent. > > Reboot and Select proper Boot device > or Insert Boo Media in select Boot device and press a key > > > (I recall successfully booting Debian 9 with UEFI in the past.) > > > STFW people have succeeded by running grub-install: > > https://lists.debian.org/debian-user/2020/01/msg5.html > > > Using the T30 in Secure Boot again, I booted d-i into a rescue shell, > mounted buster root, boot, efi, dev, proc, and sys, and started Bash: > > root@d-i:/# ls -1 /usr/lib/grub > grub-mkconfig_lib > x86_64-efi > x86_64-efi-signed > > root@d-i:/# grub-install --target x86_64-efi-signed > grub-install: error: /usr/lib/grub/x86_64-efi-signed/modinfo.sh > doesn't exist. Please specify --target or --directory. > > root@d-i:/# find /usr/lib/grub -name modinfo.sh > /usr/lib/grub/x86_64-efi/modinfo.sh > > > It seems /usr/lib/grub/x86_64-efi/modinfo.sh is missing. > > > Suggestions? > > > David signature.asc Description: This is a digitally signed message part.
