[qubes-users] Cannot boot 4.1.0 medium

Mailing Lists qubes-users
1

Hi!

I downloaded and checked the Qubes OS 4.1.0 image and wrote it onto an USB stick.
When inserting the stick to boot (on a different computer), I'm offered UEFI boot and normal boot by BIOS.

"Nice, UEFI" I thought, but somehow that does not work (see attachment). Well, I think UEFI boot should work for Qubes OS, too as Tails has a working UEFI for quite some time now, and legacy boot is increasingly rarely supported on new hardware (IMHO).

OK, trying the other (compatibility) mode, boot also failed (see other attachment).

Now I wonder: Is my stick defective, did I have a write error, or is the image defective?

Regards,
Ulrich

IMG_20220212_181245.jpg
IMG_20220212_181245.jpg800×191 12.7 KB

IMG_20220212_181321.jpg
IMG_20220212_181321.jpg800×194 23.6 KB

2

Hi,

IMHO you should first check if the image on your USB stick is broken. See

Regards,
Tobias

3

(Sorry for top-posting, but this web-frontend cannot quote properly.)

I guess the magic number count=5199888384 is different for 4.1.0 :wink:

Despite at first sight I'd say it doesn't look corrupted:
7g4x4a:/home/windl # blkid /dev/sdf
/dev/sdf: BLOCK_SIZE="2048" UUID="2022-02-03-10-41-48-00" LABEL="QUBES-R4-1-0-X86-64" TYPE="iso9660" PTUUID="35a8509b" PTTYPE="dos"
i7g4x4a:/home/windl # blkid /dev/sdf1
/dev/sdf1: BLOCK_SIZE="2048" UUID="2022-02-03-10-41-48-00" LABEL="QUBES-R4-1-0-X86-64" TYPE="iso9660" PTUUID="35a8509b" PTTYPE="dos" PARTUUID="35a8509b-01"
# blkid /dev/sdf2
/dev/sdf2: SEC_TYPE="msdos" LABEL_FATBOOT="ANACONDA" LABEL="ANACONDA" UUID="169B-DEBF" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="35a8509b-02"
# mount -r /dev/sdf2 /mnt
# ll /mnt
insgesamt 4
drwxr-xr-x 3 root root 2048 3. Feb 10:41 EFI
drwxr-xr-x 2 root root 2048 3. Feb 10:41 System Volume Information
# ll /mnt/EFI/
insgesamt 2
drwxr-xr-x 3 root root 2048 3. Feb 10:41 BOOT
# ll /mnt/EFI/BOOT/
insgesamt 1796
-rwxr-xr-x 1 root root 1835008 3. Feb 10:41 BOOTX64.EFI
drwxr-xr-x 2 root root 2048 3. Feb 10:41 fonts
-rwxr-xr-x 1 root root 1533 3. Feb 10:41 grub.cfg
# umount /mnt
# mount -r /dev/sdf1 /mnt
# ll /mnt
insgesamt 206
-rw-r--r-- 1 root root 41 3. Feb 11:31 .discinfo
drwxr-xr-x 1 root root 2048 3. Feb 11:41 EFI
drwxr-xr-x 1 root root 2048 3. Feb 11:41 extrakernels
drwxr-xr-x 1 root root 2048 3. Feb 11:41 images
drwxr-xr-x 1 root root 4096 3. Feb 11:41 isolinux
drwxr-xr-x 1 root root 2048 3. Feb 11:41 LiveOS
drwxr-xr-x 1 root root 194560 3. Feb 11:24 Packages
drwxr-xr-x 1 root root 2048 3. Feb 11:24 repodata
-rw-r--r-- 1 root root 868 3. Feb 11:41 .treeinfo

I'll try to investigate and report back. Unfortunately I don't have the original image here right now.

Ulrich

Am 13.02.2022 um 10:04, in Nachricht <73C38467.AAF : 155 : 19119>, Tobias Killer <tokidev@posteo.de> <tokidev@posteo.de> schrieb:

Hi,

IMHO you should first check if the image on your USB stick is broken. See

Regards,
Tobias

4

I guess the magic number count=5199888384 is different for 4.1.0 :wink:

Yes. It is the size of the appropriate ISO file. For R4.1.0, it should be 5954863104.

Despite at first sight I'd say it doesn't look corrupted:

> [...]

Maybe you catched nothing bad by listing files. Maybe the files themselves are corrupted. Who knows …

I'll try to investigate and report back. Unfortunately I don't have the original image here right now.

Ulrich

Tobias