Potential corrupted iso file

lawful_x86 · 2023-07-11 12:46:24

Hi , so I downloaded the arch iso file twice now but when I flash it on my usb (8 GB) using belena etcher it doesn't boot at all i also tried ventoy on a 64 GB usb and i know it's not the usb's problem because i have other (iso)s debian,manjaro Heck even windows is booting from that usb also this only happened to me in this last revision of the iso i had an old one about 600 to 700 MB in size "arch iso" which booted normally I accidentally deleted it so i tried downloading another one. Now it's 813 MB and this happened. Is it only me or is there anyone else who have this problem.
Also first time downloaded using qbittorrent and second time using brave-browser built-in Torrent downloading extension

ainz · 2023-07-11 17:29:43

Verify iso file integrity using checksums from arch's download page to see if it's corrupted or not.

Use dd or any of the methods from archwiki on how to create an Arch Linux Installer USB drive.

 dd bs=4M if=path/to/archlinux-version-x86_64.iso of=/dev/disk/by-id/usb-My_flash_drive conv=fsync oflag=direct status=progress

https://wiki.archlinux.org/title/USB_fl … ion_medium

lawful_x86 · 2023-07-11 21:11:31

Nope no progress thanks for the help anyway ainz
I guess it's something to do with my hardware i don't know im sick of it i will wait until the next revision I guess 10 hours in the trash i guess well shame

seth · 2023-07-11 21:53:56

What do you mean "no progress"?
1. is the checksum correct?
2. what does "it doesn't boot at all" mean exactly?
Is the device not bootable by your firmware or do you get to the grub bootloader but then things fail? Do you see anything at first? Can you boot when passing "nomodeset" to the kernel commandline?

lawful_x86 · 2023-07-11 23:44:09

1- yes the checksum is correct
2- when i use a usb with the flashed iso the laptop display the following "bootable image found, notebook will shutdown" not in terminal but just like how bios display errors white (screen)
When using ventoy the boot in normal mode it gives the following:

VVVVVVVV x grub_errno 17
error: syntax error.
VVVVVVVV x grub_errno 16
error: $.
VVVVVVVV x grub_errno 17
error: can't find command

The x before grub_errno is a number it's as if it's trying to check something tens of times over and over after that the laptop just shutdown

VVVVVVVV 1 grub_errno 17
.
.
.
. VVVVVVVV 100 grub_errno17

I'm writing from my phone and English is not my strength so sorry if something is note clear please tell me if anything is not and i will try my best to clarify it

Last edited by lawful_x86 (2023-07-11 23:47:48)

seth · 2023-07-12 06:17:17

I'm writing from my phone and English is not my strength so sorry if something is note clear please tell me if anything is not and i will try my best to clarify it

Make, upload and link photos of what you see.

But grub errros 16 & 17 are for filesystem inconsistency and a bogus partition type
https://wiki.gentoo.org/wiki/GRUB_Error … B_error_15 & https://wiki.gentoo.org/wiki/GRUB_Error … B_error_17

Either the iso is corrupt (unlikely if the checksum is correct) or the image writing went wrong (try dd, really) or the medium is fried (ie. you need a new usb key)

frostschutz · 2023-07-12 07:19:59

You can use cmp to verify the stick.

cmp /dev/usbstick file.iso

It should say "EOF on file.iso" then you know the stick and the iso file is identical (at least for as many bytes as the iso size provides).

If it says "differ, byte X, line X" then there is some kind of corruption or read error going on. This can happen with faulty hardware or if you dd to the stick while the stick is still mounted (a mounted filesystem writes on the stick and corrupts the iso contents that way).

Before copying the iso over, you can also run 'wipefs -a' on the USB stick to get rid of old GPT header (at end of stick) which may be causing problems. Since the ISO won't overwrite it (ISO smaller than USB stick).

The ISO file itself also has to have the correct checksum and support BIOS/UEFI mode (whichever you are using). dd does not make a stick boot correctly, it all depends on the ISO itself.

Some mainboards also have issues with some usb sticks, so if in doubt, try a different one anyway.

You could also try a different iso (from a different distro), as long as its up-to-date... it involves some extra steps, but you can bootstrap pacman from any current Linux system, it's described in the wiki.

Last edited by frostschutz (2023-07-12 07:21:12)

lawful_x86 · 2023-07-12 11:47:22

There you go

https://imgur.com/a/2yDhqOV ventoy
https://imgur.com/a/b0cK3s1 directly flashed on the usb
https://imgur.com/a/4zlfgM6 my hardware

I tried using another usb same problem
On other computers though, it works flawlessly so I think it's a problem with the hardware i guess

seth · 2023-07-12 13:54:48

What does "directly flashed on the usb" mean exactly?

lawful_x86 · 2023-07-12 13:59:13

Like how normally you would flash an iso on the usb
I said "directly on the usb" to clarify that I'm not using ventoy

seth · 2023-07-12 14:32:26

There's no "normally", which of https://wiki.archlinux.org/title/USB_fl … ion_medium ?

Trilby · 2023-07-12 14:46:28

Under that image a caption says the iso was created with Balena Etcher. That hardly seems "direct" to me. While "direct" is vague, I'd assume that either means using `cat` or `dd`.

lawful_x86, if you have not done so yet, please try using `dd` as outlined on the wiki.

Arch Linux

#1 2023-07-11 12:46:24

Potential corrupted iso file

#2 2023-07-11 17:29:43

Re: Potential corrupted iso file

#3 2023-07-11 21:11:31

Re: Potential corrupted iso file

#4 2023-07-11 21:53:56

Re: Potential corrupted iso file

#5 2023-07-11 23:44:09

Re: Potential corrupted iso file

#6 2023-07-12 06:17:17

Re: Potential corrupted iso file

#7 2023-07-12 07:19:59

Re: Potential corrupted iso file

#8 2023-07-12 11:47:22

Re: Potential corrupted iso file

#9 2023-07-12 13:54:48

Re: Potential corrupted iso file

#10 2023-07-12 13:59:13

Re: Potential corrupted iso file

#11 2023-07-12 14:32:26

Re: Potential corrupted iso file

#12 2023-07-12 14:46:28

Re: Potential corrupted iso file

Board footer