Getting checksum error while installing Rocky Linux 8 from generated ISO from original ISO

Rocky Linux Help & Support
1

Hi All,

getting checksum error while installing Rocky Linux 8 from generated ISO from original ISO.

Error

No checksum information is available unable to verify media.

dracut-initqueue job for checkisomd5@dev-sr0 : service failed because control process exited with error code

dracut : FATAL : CD check failed

dracut : refusing to continue

system halted.

but when i checked the generated iso checksum it is fine

md5sum rocky8.iso

94571d07eaa9b530fb95fd088795e5ab rocky8.iso

image
image1072×141 2.42 KB

appreciate help on this. Thanks in advance.

2

What were the exact steps you took to make this iso? That information is important to help determine what the issue is.

3

Hi,

i used genisoimage command to generate iso.

genisoimage -U -r -v -T -J -joliet-long -V “Rocky-8-10-x86_64-dvd” -volset “Rocky-8-10-x86_64-dvd” -A “Rocky-8-10-x86_64-dvd” -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot -e images/efiboot.img -no-emul-boot -o rocky8.iso test/

test is the directory where i extracted all the contents of original ISO file copied from rocky site.(Index of /pub/rocky/8/isos/x86_64/)

Thanks.

4

What specific changes are you making, if any? Why are you needing to make a custom ISO? Are you adding a kickstart? Are you updating packages?

If you are adding a kickstart, consider using mkksiso instead. If you are adding/updating packages or data on the image, consider using xorriso, which doesn’t require the amount of switches that genisoimage needs. See here for when I talked about it before.

5

Thanks for the update.

i tried with xorriso but vm not able to boot from generated iso instead it is going to boot manager setup. i used below command to generate iso through xorriso.

xorriso -as mkisofs -o output.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table test

if possible could you please provide the exact command syntax for both mkksiso and xorriso.

Thank you.

6

The link I provided above shows what we use when making our ISO’s for general use.

xorriso \
  -indev Rocky-9.5-x86_64-boot.iso \  # Input ISO
  -outdev test.iso \  # Output ISO
  -boot_image any replay \   # Maintains all boot information
  -joliet on \  # Generates joliet tree with ISO 9660 and rock ridge
  -system_id LINUX \  # sets system ID has LINUX - without this, some systems will not boot
  -compliance joliet_long_names \  # Allows long file names up to 103 characters
  -volid Rocky-9-5-x86_64-dvd # volume ID

We don’t use -as mkisofs or any of the related switches. We simply “replay” the boot part of the ISO and make the changes we want to make. If you’re adding files, use -map. If you’re updating an already existing file, use -update.

-update /mnt/compose/9/latest-Rocky-9/work/lorax/x86_64/dvd/EFI/BOOT/grub.cfg EFI/BOOT/grub.cfg

-map /mnt/compose/9/latest-Rocky-9/work/lorax/x86_64/dvd/.treeinfo .treeinfo

If you’re only adding a kickstart, use mkksiso.

% mkksiso /path/to/kickstart.ks /path/to/dvd.iso
# or...
% mkksido --ks /path/to/kickstart.ks /path/to/dvd.iso
7

Hi,

Thank you for the update let me go ahead and try this.

Thanks.