I am trying to create a bootable ISO for a customised Ubuntu. The ISO I create is not bootable (it won't boot in VirtualBox). To debug I am not modifying Ubuntu, just trying to recreate a bootable ISO from the the original bootable Ubuntu ISO I downloaded from the web (it boots in VirtualBox). The steps are: 1. Mount original ISO 2. Make a read-write copy 3. Use genisoimage to create a new ISO The details are shown below. The new ISO won't boot. The file command indicates it is bootable, but does not contain a "DOS/MBR boot sector" (whereas the original ISO does). I have also shown some of the contents of the mounted disk (in case I am specifying the wrong boot catalog or image). Can anyone tell me what I am doing wrong?
---
Steps 1 and 2. Mount original ISO and make a read/write copy:

> sudo mount -t iso9660 -o loop ubuntu-24.04.iso mntpoint
> mkdir mntpoint_rw
> rsync -a mntpoint/ mntpoint_rw

Step 3. Recreate the ISO:

> sudo genisoimage \,
   -o /tmp/custom.iso \
   -R -J -b EFI/boot/grubx64.efi -c boot.catalog -no-emul-boot -boot-load-size 4 -boot-info-table \
   $(pwd)/mntpoint_rw

I have tried various combinations of -b, -c options with files boot.catalog, EFI/boot/grubx64.efi and boot/grub/grub.cfg. Info about the original ISO (downloaded from web):

> file ubuntu-24.04.iso
ubuntu-24.04.iso: ISO 9660 CD-ROM filesystem data (DOS/MBR boot sector) 'Ubuntu 24.04.2 LTS amd64' (bootable)
>  ls -lh ubuntu-24.04.iso
-rw-r--r-- 1   6.0G Aug  1 13:37 ubuntu-24.04.iso

Info about the new ISO:

> file /tmp/custom.iso
/tmp/custom.iso: ISO 9660 CD-ROM filesystem data 'Custom Ubuntu-24.04' (bootable)
> ls -lh /tmp/custom.iso
-rw-r--r-- 1 root root 6.0G Aug  1 13:56 /tmp/custom.iso

Selected content of the mounted disk:

> ls -l --block-size=K mntpoint_rw
total 84K
dr-xr-xr-x 3    4K Jan 27  2025 EFI
dr-xr-xr-x 3    4K Jan 27  2025 boot
-r--r--r-- 1    2K Feb 15 19:15 boot.catalog
dr-xr-xr-x 2   12K Feb 15 19:15 casper
dr-xr-xr-x 3    4K Feb 15 19:09 dists
dr-xr-xr-x 2    4K Feb 15 19:09 install
-r--r--r-- 1   44K Feb 15 19:15 md5sum.txt
dr-xr-xr-x 4    4K Feb 15 19:09 pool
dr-xr-xr-x 2    4K Feb 15 19:09 preseed
lrwxrwxrwx 1    1K Feb 15 19:09 ubuntu -> .

> find mntpoint_rw/EFI -type f | xargs ls -lh
-r--r--r-- 1   945K Jan 27  2025 mntpoint_rw/EFI/boot/bootx64.efi
-r--r--r-- 1   2.3M Aug  1 13:56 mntpoint_rw/EFI/boot/grubx64.efi
-r--r--r-- 1   837K Jan 27  2025 mntpoint_rw/EFI/boot/mmx64.efi

> find mntpoint_rw/boot ! \( -name '*.mod' -o -name '*.lst' \) -type f | xargs ls -lh
-r--r--r-- 1   2.4M Jan 27  2025 mntpoint_rw/boot/grub/fonts/unicode.pf2
-r--r--r-- 1    583 Feb 15 19:13 mntpoint_rw/boot/grub/grub.cfg
-r--r--r-- 1   7.5K Jan 27  2025 mntpoint_rw/boot/grub/i386-pc/efiemu32.o
-r--r--r-- 1    11K Jan 27  2025 mntpoint_rw/boot/grub/i386-pc/efiemu64.o
-r--r--r-- 1    31K Jan 27  2025 mntpoint_rw/boot/grub/i386-pc/eltorito.img
-r--r--r-- 1    318 Feb 15 19:13 mntpoint_rw/boot/grub/loopback.cfg
-r--r--r-- 1   145K Apr  9  2024 mntpoint_rw/boot/memtest86+x64.bin

I have a Linux image from which I've extracted a rootfs.img file. The file seems to contain files and information. I would like to "boot into it". File contents:

bin
dev
etc
home
lib
media
mnt
proc
run
sbin
service
sys
tmp
usr
var
lib64

How can I install a bootloader to boot it? I've tried getting a live Ubuntu image, adding a partition, and placing the contents of rootfs.img inside the partition and running "Boot Repair", which did find the other system as another bootable Linux, but I can't boot into it, it seems like I'm missing something

I need to write a windows7 iso file on my usb stick. I had been used to this task. I usually either use the dd tool, or unetbootin. Surprisingly both don't work today. With dd I did the following : dd bs=4m if='windows7.iso' of=/dev/sdb My new supposedly bootable usb stick wont boot. Ok so I used unetbootin. This time, I get the unetbootin bootloader screen, but windows7 is not listed. Only the default choice is left. In either way, I failed at creating my bootable stick. Few months ago, I could make this same USB stick boot with the very same ISO file. I also did the same tasks after formatting my stick withh this command: mkfs.vfat -F 32 -I /dev/sdb There were no difference as expected. I am probably doing something wrong here, but I can't see where my mistake is. Any idea on what is going on?

The title pretty much says it all. I have an older machine with OpenSuSE installed (12.x, IIRC) which I want to update. It does not have a UEFI BIOS. I want to create a bootable USB install, but everything I try, from the OpenSuSE imagewriter program to a straight dd copy to the thumb drive, creates an EFI directory with BOOT under it. This doesn't boot - indeed, isn't even recognized - from the target machine. I'm using the current openSUSE-Leap-15.3-NET-x86_64.iso for the install, and have tried creating the install on a couple of different machines, running 15.0 and 15.2. I installed on both of those machines using essentially the same procedure, with no more than the usual problems. Also, one of those machines is also non-UEFI, and the created USB stick works just fine with it. Both have BIOS dates from 2007. The only difference is that the one it works with is presumably an IBM BIOS (it's a ThinkPad T60p), the other has an AMI BIOS. PS: I also set the BIOS to boot only from USB, but that just causes the machine to hang on startup with a message that there's no bootable drive found. The machine also mounts & reads the stick after I boot into the installed Linux, so it's not simply that the USB hardware is broken.

Heyo, I've been working on a small distro of mine, and have stitched together a system. Now, I'd like to be able to use this to create a live install ISO. I've looked into ways, but what I found was a tool that you can install via apt. (I couldn't even use that because I'm on Portage). Thanks in advance! UPDATE: For clarification, I'm looking for a USB which someone can plug into their computer, boot to it, and run my install script. It would be nice if it was live, as well.

*I'm sorry if I mix different units in this but these are the units I see when working.* I decided to add a new partition to my bootable sd card which contained a 21GB partition of an EXT4 file system (Debian with KDE) and about 8GB of linux swapspace on another partition, using KDE partition manager on my Raspberry Pi (as opposed to the PC I usually use with my bootable drive). I made the stupid decision to try and shrink and move both partitions to allow myself a blank NTFS partition of about 11GiB for using with any Windows device. This partitioned fine but upon choosing Debian at GRUB on my PC, initramfs told me that my filesystem was probably corrupt and that I couldn't boot properly. The supposed file system size of 21 odd GB was larger than the available device (partition) size of 15GB and it couldn't continue. Trying to backpedal my decision, I took the sd card out and used my RPi to reformat it back to how it was. Everything worked fine, moving partitions about and resizing the swap space. However, KDE partition manager was unable to grow ext4 to its original size (see images 1, 2 and 3). Can anything be done to get things back to normal, or failing that, restore *some* of the data on the ext4 filesystem? I didn't have any irreplaceable documents on there really but I got a lot of settings customised to my liking and I'd like to make the restoration process as quick as possible. If you do have an answer, please tell me if there's any more information I can provide about my situation that I haven't already given. After first partitioning (1): Before attempting to grow partition (2): Error! (3): ============================ **In response to the first question about the details given under the error:** ============================

Grow partition ‘/dev/sda1’ from 14.65 GiB to 21.71 GiB 
Job: Check file system on partition ‘/dev/sda1’ 
Command: e2fsck -f -y -v /dev/sda1 
e2fsck 1.44.5 (15-Dec-2018)
The filesystem size (according to the superblock) is 5487104 blocks
The physical size of the device is 3840000 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? yes
 

Command: e2fsck -f -y -v /dev/sda1 
e2fsck 1.44.5 (15-Dec-2018)
The filesystem size (according to the superblock) is 5487104 blocks
The physical size of the device is 3840000 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? yes
 
Check file system on partition ‘/dev/sda1’: Error

Checking partition ‘/dev/sda1’ before resize/move failed. 
Grow partition ‘/dev/sda1’ from 14.65 GiB to 21.71 GiB: Error

I have an old Debian system whose hard drive failed. I connected the drive to a working system and pulled all the data off of the root partition using dd. It looks to me like all the data is fine, so I decided to just copy it onto a new drive and make it bootable. So I got a new drive, partitioned it, mounted the first partition, and copied all the data onto that partition. My system is Legacy, not EFI. I edited the /etc/fstab on that partition to change the UUIDs to those of the new drive. I ran grub-install --boot-directory=/mnt/newdriveroot/boot /dev/sdb to make it bootable, and I edited the /boot/grub/grub.cfg on that partition to change the UUID of the root partition to the new drive's first partition. When I try to boot from it, Grub loads, presenting the menu just like it would before the old drive died. When I pick the default choice, Linux begins to boot. It clears the screen and then:

Loading Linux 3.2.0-4-amd64 ...
Loading initial ramdisk ...

then clears the screen again and then:

Loading, please wait...
[    4.882479] EXT4-fs (sda1): error loading journal
mount: mounting /dev/disk/by-uuid/e14dc4cb-4b45-8418-e7a6-b2c8d6036749 on /root failed: Invalid argument
mount: mounting /dev on /root/dev failed: No such file or directory
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.

Then it drops me into the built-in shell with the (initramfs) prompt. ## Trying to fix it ## At that point I am able to mount the root partition using:

mount -o ro,noload /dev/sda1 /root

though I don't know what good that does me. (If I then exit the shell, the boot process tries to continue, but it just leads to errors about /root/sys and /root/proc not existing. To remedy that problem I followed @telcoM's advice and created /dev, /proc, and sys.) But perhaps the fact that *both* the ro and the noload are necessary in order to get it to mount is helpful information? And now is probably a good time to remember that **when it's connected to a working system, I can mount the partition without a problem** (neither ro nor noload needed). I don't know what to look for in dmesg output; the only thing that I notice is that just before the above journal error, there is a line that says:

JBD2: Unrecognised features on journal

I have run fsck and fsck -f, but **no problems were found**. As per @telcoM's suggestion, I used tunefs to disable journal features. I did:

tune2fs -O ^has_journal /dev/sdb1

After doing that and trying to boot from the drive again, I now get the following:

Loading, please wait...
Target filesystem doesn't have requested /sbin/init.
switch_root: can't execute '/bin/sh': No such file or directory
[    4.966291] Kernel panic - not syncing: Attempted to kill init!
[    4.966347] Pid: 1, comm: busybox Not tainted 3.2.0-4-amd64 #1 Debian 3.2.65-1+deb7u2

Now I no longer get dropped into the (initramfs) built-in shell. Instead, the system is just hung. ## Similar problems ## I have found no posts like the situation I am encountering. Specifically, every "error loading journal" error occurs along with errors found by fsck or an inability to mount the partition. In my situation, fsck finds nothing, and the partition can be mounted without a problem from a working system. ## System information ## What else would be helpful for me to post? Any Grub files? I don't suppose it matters, but here is the output from lsblk, when connected to my working system:

$ lsblk /dev/sdb
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sdb      8:16   0 119.2G  0 disk
├─sdb1   8:17   0    20G  0 part
├─sdb2   8:18   0     1K  0 part
├─sdb5   8:21   0    10G  0 part
├─sdb6   8:22   0     8G  0 part
├─sdb7   8:23   0     2G  0 part
└─sdb8   8:24   0  79.2G  0 part

(I partitioned sdb6 as a swap partition. 5 is intended for /var, 7 for /tmp, and 8 for /home.) Here is the /etc/fstab (UUIDs deleted for readability):

UUID=  /      ext4  errors=remount-ro  0  1
UUID=  /home  ext4  defaults           0  2
UUID=  /tmp   ext4  defaults           0  2
UUID=  /var   ext4  defaults           0  2
UUID=  none   swap  sw                 0  0

Am I missing some big step in making the drive bootable?

I have succeeded using diskutil and dd as described in this [article](). From the looks of it, the USB should be working now. However, I have plugged it into the laptop on which I want to boot Debian—have chosen the USB stick as the first disk to boot from—tried booting it as a temporary disk, and it still doesn't work. I thoroughly went through the official and up-to-date articles from Debian. I will list some resources below: - - - The ISO image file that I downloaded: Edit: In my case, the issue was that the GPT partition table was not selected. When you receive a warning that your disk could not be read by the computer and must be ejected, don't worry. Try booting the USB anyway, and it should work.

I am trying to create bootable live tails usb. I downloaded tails-amd64-6.10.img from here . I verified the download: I used balena etcher and got this error: - Since it did not work, I also downloaded from torrent but still same error. - I used different usb but still same error. I tried using ventoy. ventoy does not see the image file. I put kali linux iso file into the ventoy and ventoy recognized it when I booted.

I've been a Fedora user "since forever" (Red Hat v1.1) but, frustrated by some issues I can't ignore, I am interested in trying both Debian and Ubuntu. Step zero was to download the latest releases. I picked Debian 12.7.0 as my first to try. However, in the past I was using a Windows box to burn DVDs for no good reason but familiarity. ... And thus I'd never had to actually burn the DVD on Linux before. Following the directions from various sources here, I started with: # wodim -v dev='/dev/sg2' -eject debian-12.7.0-amd64-DVD-1.iso Whir-whir-whir went the DVD with lots of progress reported but a cup of coffee or so later I got some errors pertaining to "fixating" the disk, namely: Fixating... Errno: 5 (Input/output error), flush cache scsi sendcmd: no error CDB: 35 00 00 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 40 A0 03 21 04 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x21 Qual 0x04 (logical block address out of range) [No matching qualifier] Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 137.712s timeout 120s Trouble flushing the cache wodim: Cannot fixate disk. Fixating time: 137.712s Errno: 5 (Input/output error), prevent/allow medium removal scsi sendcmd: fatal error CDB: 1E 00 00 00 00 00 cmd finished after 0.000s timeout 40s Errno: 5 (Input/output error), start/stop unit scsi sendcmd: fatal error CDB: 1B 00 00 00 02 00 cmd finished after 0.000s timeout 40s wodim: Cannot eject media. wodim: fifo had 62911 puts and 62911 gets. wodim: fifo was 0 times empty and 7253 times full, min fill was 34%. Using man I found -fix, and tried it, but it didn't work either, as can be seen here - a VERY different kind of error: # wodim -v dev='/dev/sg2' -fix TOC Type: 1 = CD-ROM scsidev: '/dev/sg2' devname: '/dev/sg2' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.36 Wodim version: 1.1.11 SCSI buffer size: 64512 wodim: Cannot do inquiry for CD/DVD-Recorder. Errno: 5 (Input/output error), test unit ready scsi sendcmd: fatal error CDB: 00 00 00 00 00 00 cmd finished after 0.000s timeout 40s So, I figured I'd try dd since several question/answer entries here strongly implied dd can make a bootable DVD, just watch out for sync issues, so, this: # dd if=debian-12.7.0-amd64-DVD-1.iso of=/dev/sg2 bs=4M && sync But... It doesn't do anything! And from that I did research and found this entry which says dd used to be able to do this and for some unknown but likely (in my view) silly reason, the ability was removed?! However, that is disputed. Hmmm... This system usually makes the cd/dvd drive available on /dev/cdrom and to read I do something like # mount /dev/cdrom /mounts/cd0 and then I have the contents available on /mounts/cd0. But trying /dev/cdrom didn't do anything either: # dd if=debian-12.7.0-amd64-DVD-1.iso of=/dev/cdrom bs=4M && sync No Joy. I've read several other entries on stack exchange sites, such as this one or this one , among others, but didn't find a solution... MAYBE I just had a media error and need to retry the original command? I hate to waste disks but... On suggestion, I tried: # wodim -v dev=/dev/sr0 -eject -sao debian-12.7.0-amd64-DVD-1.iso TOC Type: 1 = CD-ROM scsidev: '/dev/sr0' devname: '/dev/sr0' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.11 SCSI buffer size: 64512 wodim: Cannot do inquiry for CD/DVD-Recorder. Errno: 5 (Input/output error), test unit ready scsi sendcmd: fatal error CDB: 00 00 00 00 00 00 cmd finished after 0.000s timeout 200s Hmmm... There is a /dev/sr0 entry... **I WENT TO A DIFFERENT MACHINE...** Same operating system, same brand drive, etc, and I ran the command from the answer below and it wrote a disk. **IMPORTANTLY** along the way I noted the software - wodim - said: Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. Upon reading that I instantly deduced the drives MAY be the same brand (ASUS) but not the same type, or maybe there's a motherboard difference? I don't know. Since I had copied and pasted the entire output from the original "unfixated" run, I can say it wasn't in there. However, it was in this new SUCCESSFUL run - that boots propertly! - so ... Apparently what I needed to have found was maybe this article. Aren't computers fun?

The rhel-8.10-x86_64-dvd.iso to install from which is 14GB in size. For a usb device (i.e. disk) that would show up in Linux as */dev/sdb* for example, doing a cp rhel-8.10-x86_64-dvd.iso /dev/sdb results in an **msdos** partition scheme on that usb device which is bootable and allows you to install Linux. *I suspect they use the msdos partition scheme to maintain functionality with older hardware that pre-dates EFI* The msdos partition scheme has a 2TB limit, and poses an inconvenience when I have a 4+ TB usb disk that I want to use simultaneously for being able to install Linux from (which needs [BOOT] AppStream BaseOS EFI images isolinux .discinfo .treeinfo EULA extra_files.json GPL media.repo RPM-GPG-KEY-redhat-beta RPM-GPG-KEY-redhat-release TRANS.TBL is there a way for what I have described to manually do this Linux to make a usb device bootable (using parted or fdisk or some other) ? If so how? Or is there a way with some free software under microsoft windows?

Their approach does not work (everything goes fine but usb does not become bootable). It also seems several years old and outdated. Other distros have large amounts of troubleshooting this issue, but not Debian. Any advice, how can I debug why my USB did not become Debian bootable after those procedures. My steps were: 1. Erase USB drive using disk utils and create FAT partition(i tried also exFAT and OSX Extended). 1. Downloaded the ISO and converted it to img: hdiutil convert debian-8.4.0-i386-DVD-1.iso -format UDRW -o debian-8.4.0-i386-DVD-1.img and renaming the result to remove the ".img" from name. I also tried to us UDTO instead of UDRW. 1. Finding my USB location using diskutil list, it was /dev/disk2 1. Unmounting the USB: diskutil unmountDisk /dev/disk2 1. dding the image: sudo dd if=debian-8.4.0-i386-DVD-1.img of=/dev/disk2 bs=1m What took many hours. The result was the expected message that USB could not be read. 1. Ejecting the USB with: diskutil eject /dev/disk2 The result was that the USB was not bootable (in the loading screen pressing alt button) the USB does not show.

I know there have been quite a few similar questions, but they aren't specific enough. I have a Windows 10 x64 installation ISO and I am trying to extract the files make some modifications and then make a new ISO from the extracted/modified files. It basically works just fine, but the problem is that I can't figure out how to make it UEFI bootable again (in legacy/BIOS mode it boots just fine). I have gone through countless posts following instructions on how to do this, but none of them worked for my Windows 10 ISO. Most of these posts only mention older versions of Windows and those mentioning Windows 10 don't specify if they got it to work with a current x64 version and if they were able to UEFI boot from it. (Probably not, because is surely doesn't work for me.) I ended up trying to replicate the output of isoinfo -d -i ./windows10.iso and dumpet -i ./windows10.iso as much as I could. And this is as close as I was able to get: (Edit: Updated with -eltorito-alt-boot as suggestes by telcoM) **Original ISO (isoinfo):** $ isoinfo -d -i ./original.iso CD-ROM is in ISO 9660 format System id: Volume id: CCCOMA_X64FRE_EN-US_DV9 Volume set id: CCCOMA_X64FRE_EN-US_DV9 Publisher id: MICROSOFT CORPORATION Data preparer id: MICROSOFT CORPORATION, ONE MICROSOFT WAY, REDMOND WA 98052, (425) 882-8080 Application id: CDIMAGE 2.56 (01/01/2005 TM) Copyright File id: Abstract File id: Bibliographic File id: Volume set size is: 1 Volume set sequence number is: 1 Logical block size is: 2048 Volume size is: 2411879 El Torito VD version 1 found, boot catalog is in sector 22 NO Joliet present NO Rock Ridge present Eltorito validation header: Hid 1 Arch 0 (x86) ID 'Microsoft Corporation' Key 55 AA Eltorito defaultboot header: Bootid 88 (bootable) Boot media 0 (No Emulation Boot) Load segment 0 Sys type 0 Nsect 8 Bootoff 202 514 **Modified ISO (isoinfo):** $ isoinfo -d -i ./modified.iso CD-ROM is in ISO 9660 format System id: Volume id: CCCOMA_X64FRE_EN-US_DV9 Volume set id: CCCOMA_X64FRE_EN-US_DV9 Publisher id: Microsoft Corporation Data preparer id: MICROSOFT CORPORATION, ONE MICROSOFT WAY, REDMOND WA 98052, (425) 882-8080 Application id: CDIMAGE 2.56 (01/01/2005 TM) Copyright File id: Abstract File id: Bibliographic File id: Volume set size is: 1 Volume set sequence number is: 1 Logical block size is: 2048 Volume size is: 2411275 El Torito VD version 1 found, boot catalog is in sector 1506 NO Joliet present NO Rock Ridge present Eltorito validation header: Hid 1 Arch 0 (x86) ID 'Microsoft Corporation' Key 55 AA Eltorito defaultboot header: Bootid 88 (bootable) Boot media 0 (No Emulation Boot) Load segment 0 Sys type 0 Nsect 8 Bootoff 8CD 2253 **Difference between the above isoinfo outputs:** $ diff Publisher id: Microsoft Corporation 14,15c14,15 Volume size is: 2411275 > El Torito VD version 1 found, boot catalog is in sector 1506 29c29 Bootoff 8CD 2253 **Original ISO (dumpet):** $ dumpet -i ./original.iso Validation Entry: Header Indicator: 0x01 (Validation Entry) PlatformId: 0x00 (80x86) ID: "Microsoft Corporation" Checksum: 0x494c Key bytes: 0x55aa Boot Catalog Default Entry: Entry is bootable Boot Media emulation type: no emulation Media load segment: 0x0 (0000:7c00) System type: 0 (0x00) Load Sectors: 8 (0x0008) Load LBA: 514 (0x00000202) Section Header Entry: Header Indicator: 0x91 (Final Section Header Entry) PlatformId: 0xef (EFI) Section Entries: 1 ID: "" Boot Catalog Section Entry: Entry is bootable Boot Media emulation type: no emulation Media load address: 0 (0x0000) System type: 0 (0x00) Load Sectors: 1 (0x0001) Load LBA: 516 (0x00000204) **Modified ISO (dumpet):** $ dumpet -i ./modified.iso Validation Entry: Header Indicator: 0x01 (Validation Entry) PlatformId: 0x00 (80x86) ID: "Microsoft Corporation" Checksum: 0x494c Key bytes: 0x55aa Boot Catalog Default Entry: Entry is bootable Boot Media emulation type: no emulation Media load segment: 0x0 (0000:7c00) System type: 0 (0x00) Load Sectors: 8 (0x0008) Load LBA: 2253 (0x000008cd) Section Header Entry: Header Indicator: 0x91 (Final Section Header Entry) PlatformId: 0xef (EFI) Section Entries: 1 ID: "" Boot Catalog Section Entry: Entry is bootable Boot Media emulation type: no emulation Media load address: 0 (0x0000) System type: 0 (0x00) Load Sectors: 2984 (0x0ba8) Load LBA: 1507 (0x000005e3) **Difference between the above dumpet outputs:** $ diff Load LBA: 2253 (0x000008cd) 24,25c24,25 Load Sectors: 2984 (0x0ba8) > Load LBA: 1507 (0x000005e3) I have written a script to completely reproduce the problem with the same ISO that I'm using: #!/usr/bin/env bash ################################## # Download the Windows 10 x64 ISO WIN10_IMG_DESTINATION="./windows.iso" WIN10_IMG_ARCH="x64" if [ ! -f "${WIN10_IMG_DESTINATION}" ]; then if [[ "$WIN10_IMG_ARCH" == "x86" ]] || [[ "$WIN10_IMG_ARCH" == "i386" ]] ; then echo "Retrieving the x86 Windows 10 iso URL..." WINDOWS_10_ISO_URL=$(curl -LsI -o /dev/null -w %{url_effective} "https://windows101tricks.com/1903-iso-32 ") else echo "Retrieving the x64 Windows 10 iso URL..." WINDOWS_10_ISO_URL=$(curl -LsI -o /dev/null -w %{url_effective} "https://windows101tricks.com/1903-iso-64 ") fi echo "Making sure the URL comes from a trusted Microsoft (sub)domain..." if [[ $WINDOWS_10_ISO_URL == https://software-download.microsoft.com/* ]] ; then echo "Downloading the Windows 10 installation iso..." wget "$WINDOWS_10_ISO_URL" -O "$WIN10_IMG_DESTINATION" else echo "URL validation failed. Please download the Windows 10 iso manually." exit 1 fi else echo "Windows 10 iso already exists. Skipping download..." fi # ################################## # Variable containing the path to the windows.iso WIN10_IMG="$WIN10_IMG_DESTINATION" TMP="./tmp" ISO_FILES="${TMP}/iso-files" ISO_MP="${TMP}/iso-mountpoint" # Remove ./tmp if it already exists, then create ./tmp/iso-files and ./tmp/iso-mountpoint rm -rf "${TMP}" mkdir -p "${ISO_FILES}" mkdir -p "${ISO_MP}" # Extract the files fromt he ISO to ./tmp/iso-files sudo mount -t udf "${WIN10_IMG}" "${ISO_MP}" sudo cp -Rva ${ISO_MP}/* "${ISO_FILES}" sudo umount "${ISO_MP}" # Make modifications to the Windows ISO #BOOT_DIR="${ISO_FILES}/efi/microsoft/boot" #sudo mv "${BOOT_DIR}/cdboot.efi" "${BOOT_DIR}/tmp.efi" #sudo mv "${BOOT_DIR}/cdboot_noprompt.efi" "${BOOT_DIR}/cdboot.efi" #sudo mv "${BOOT_DIR}/tmp.efi" "${BOOT_DIR}/cdboot_noprompt.efi" # Extract the boot.img (didn't help at all) #BOOT_SECTOR_LENGTH="$(isoinfo -d -i "${WIN10_IMG}" | grep "Nsect " | grep -o "[^ ]*$")" #STARTING_SECTOR="$(isoinfo -d -i ./vm-files/windows10.iso | grep "Bootoff " | grep -o "[^ ]*$")" #dd if="${WIN10_IMG}" of="${ISO_FILES}/boot.img" bs=2048 count="${BOOT_SECTOR_LENGTH}" skip="${STARTING_SECTOR}" # Extract boot load segment address and size BOOT_LOAD_SEG="$(dumpet -i "${WIN10_IMG}" | grep "Media load segment: " | cut -d ':' -f2 | cut -d ' ' -f2)" BOOT_LOAD_SIZE="$(dumpet -i "${WIN10_IMG}" | grep "Load Sectors: " | grep -o "[^:]*$" | cut -d ' ' -f2 | head -1)" # Extract meta data : SYSTEM_ID="$(isoinfo -d -i "${WIN10_IMG}" | grep "System id: " | cut -d ' ' -f3-)" VOLUME_ID="$(isoinfo -d -i "${WIN10_IMG}" | grep "Volume id: " | cut -d ' ' -f3-)" VOLUME_SET_ID="$(isoinfo -d -i "${WIN10_IMG}" | grep "Volume set id: " | cut -d ' ' -f4-)" #PUBLISHER_ID="$(isoinfo -d -i "${WIN10_IMG}" | grep "Publisher id: " | cut -d ' ' -f3-)" # Always uppercase PUBLISHER_ID="$(isoinfo -d -i "${WIN10_IMG}" | grep "ID '" | cut -d "'" -f2)" DATA_PREPARER_ID="$(isoinfo -d -i "${WIN10_IMG}" | grep "Data preparer id: " | cut -d ' ' -f4-)" APPLICATION_ID="$(isoinfo -d -i "${WIN10_IMG}" | grep "Application id: " | cut -d ' ' -f3-)" COPYRIGHT_FILE_ID="$(isoinfo -d -i "${WIN10_IMG}" | grep "Copyright file id: " | cut -d ' ' -f4-)" ABSTRACT_FILE_ID="$(isoinfo -d -i "${WIN10_IMG}" | grep "Abstract file id: " | cut -d ' ' -f4-)" BIBLIOGRAPHIC_FILE_ID="$(isoinfo -d -i "${WIN10_IMG}" | grep "Bibliographic file id: " | cut -d ' ' -f4-)" # Create a new ISO image using mkisofs # (.mkisofsrc is necessary, because some options are not available on the cli directly) rm ".mkisofsrc" echo "APPI=${APPLICATION_ID}" >> ".mkisofsrc" echo "COPY=${COPYRIGHT_FILE_ID}" >> ".mkisofsrc" echo "ABST=${ABSTRACT_FILE_ID}" >> ".mkisofsrc" echo "BIBL=${BIBLIOGRAPHIC_FILE_ID}" >> ".mkisofsrc" echo "PREP=${DATA_PREPARER_ID}" >> ".mkisofsrc" echo "PUBL=${PUBLISHER_ID}" >> ".mkisofsrc" echo "SYSI=${SYSTEM_ID}" >> ".mkisofsrc" echo "VOLI=${VOLUME_ID}" >> ".mkisofsrc" echo "VOLS=${VOLUME_SET_ID}" >> ".mkisofsrc" sudo rm "${WIN10_IMG}.tmp.iso" sudo mkisofs \ -no-emul-boot \ -b boot/etfsboot.com \ -boot-load-seg "${BOOT_LOAD_SEG}" \ -boot-load-size "${BOOT_LOAD_SIZE}" \ -eltorito-alt-boot \ -e efi/boot/bootx64.efi \ -no-emul-boot \ -iso-level 2 \ -boot-info-table \ -udf \ -D \ -N \ -relaxed-filenames \ -allow-lowercase \ -o "${WIN10_IMG}.tmp.iso" \ "${ISO_FILES}" rm ".mkisofsrc" # Print the variables that we gathered echo echo "Extracted meta data (form original image):" echo "BOOT_LOAD_SEG: ${BOOT_LOAD_SEG}" echo "BOOT_LOAD_SIZE: ${BOOT_LOAD_SIZE}" echo "-------" echo "SYSTEM_ID: ${SYSTEM_ID}" echo "VOLUME_ID: ${VOLUME_ID}" echo "VOLUME_SET_ID: ${VOLUME_SET_ID}" echo "PUBLISHER_ID: ${PUBLISHER_ID}" echo "DATA_PREPARER_ID: ${DATA_PREPARER_ID}" echo "APPLICATION_ID: ${APPLICATION_ID}" echo "COPYRIGHT_FILE_ID: ${COPYRIGHT_FILE_ID}" echo "ABSTRACT_FILE_ID: ${ABSTRACT_FILE_ID}" echo "BIBLIOGRAPHIC_FILE_ID: ${BIBLIOGRAPHIC_FILE_ID}" # Show difference between new and old image as reported by isoinfo echo echo "-------------- isoinfo diff -----------------" diff <(isoinfo -d -i "${WIN10_IMG}") <(isoinfo -d -i "${WIN10_IMG}.tmp.iso") # Show difference between new and old image as reported by dumpet echo echo " -------------- dumpet diff -----------------" diff <(dumpet -i "${WIN10_IMG}") <(dumpet -i "${WIN10_IMG}.tmp.iso") # Overwrite the original ISO with the new one #sudo rm "${WIN10_IMG}" #sudo mv "${WIN10_IMG}.tmp.iso" "${WIN10_IMG}"

I downloaded the official tails 6.6 image file [here](https://tails.net/install/windows/index.en.html) . And followed all the steps mentioned and made my bootable usb drive. But when I booted it on my laptop it did not boot for hours. I checked the log by pressing Escape and saw this in the console -

134.00170 systemd: modprobe@dm_mod,service: Deactivated successfully. I l34.004731 systemd: Finished modprobe@dm.mod.service - Load Kernel Module dm_mod► t ","N I Finished modprobe@dm.mod.service - Load Kernel Module dm_mod. I 1 .013,S21 systemd: modprobeOefi_pstore.service: Deactivated successfully. I 134.0141111 ,stemd[11: Finished modprobellefi_pstore.service - Load Kernel Module efi.pstore► t I Finished modprobeeefi_pstore.service - Load Kernel Module efi_pstore. [ 1314.01.5.66$1 systemd: modprobeeloop.service: Deactivated successfully. t 134.416171] systemd: Finished modprobe@loop.service - Load Kernel Module loop. t Q I Finished modprobOloop.service - Load Kernel Module loop. t 134.0184831 systemdt11: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmoty./sys/fs/pstore). t 134.018M systemd: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met. t 134.1782451 systemd: Finished ferm.service - ferm firewall configuration. [ OK I Finished ferm.service - ferm firewall configuration. t 134.1796611 skistemdfl]: Reached target network-pre.target - Preparation for Network. I _ I Reached target network-pre.terget - Preparation for Network. 134.236501] systemd: Starting networking.service - Raise network interfaces... Starting networking.service - Raise network interfaces-t 134.3795861 sd 0:0:0:0: Attached scsi generic sg0 type 0 134.526498] systemd: Finished networking.service - Raise network interfaces. [ OK I Finished networking.service - Raise network interfaces. I Job systemd-journald.service/start running (1min 26s / 1min 26s) ] Job systemd-journald.service/start running (1min 31s / lmin 31s) [ 226.102265] systemd: systemd-journald.service: State 'stop-sigterm' timed out. Killing. [ **,] Job sastemd-journald.service/start running (lmin 37s / 1min 37s) [ .1,] Job systemd-journald.service/start running (1min 42s / 1min 42s) [ 236.602216] systemd: systemd-journald.service: State 'final-sigterm' timed out. Killing. I , ] Job systemd-journald.service/start running (lmin 47s / 1min 47s) [ 241.852215] systemd: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode. [ 241.854586] systemd: systemd-journald.service: Failed with result 'timeout'. [ 241.858583] systemd: systemd-journald.service: Unit process 646 (systemd-journal) remains running after unit stopped. [FAILED] Failed to start systemd-journald.service - Journal Service. See 'systemctl status systemd-journald.service' for details. [ 241.865415] systemd: systemd-journald.service: Scheduled restart job, restart counter is at 1. [ 241.866111] systemd: Stopped systemd-journald.service - Journal Service. [ OK ] Stopped systemd-journald.service - Journal Service. [ 241.867922] systemd: systemd-journald.service: Found left-over process 646 (systemd-journal) in control group while starting unit. Ignoring. [ 241.867927] systemd: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 241.905246] systemd: Starting systemd-journald.service - Journal Service... Starting systemd-journald.service - Journal Service... [ 241. 29] systemd-journald: File /run/log/Journal/Bafbee1b601542bb908b095e9aef3d91/system.journal corrupted or uncleanly shut down, renaming and replacing. [ ] Job systemd-journald.service/start running (1min 11s / lain 30s) [ 332.102488] systemd: systemd-journald.service: start operation timed out. Terminating. [ 337.352241] systemd: systemd-journald.service: State 'stop-sigterpe timed out. Killing. [ 337.354842] systemd: systemd-journald.service: Killing process 11 (systemd-journal) with signal SIGKILL. [ ] Job systemd-journald.service/start running (lmin 40s / imin Os) [ ] Job systemd-journald.service/start running (lmin 45s / lmin 45s) [ 347.852233] systemd: systemd-journald.service: State 'final-sigterm' timed out. Killing. [ 347.855173] systemd: systemd-journald.service: Killing process 4031 (systemd-journal) with signal SIGKILL. [ ] Job systemd-journald.service/start running (lmin 50s / imin 50s) [ 353.1019721 systemd: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode. [ 353.104411] systemd: systemd-journald.service: Failed with result 'timeout'. [ 353.107123] systemd: systemd-journald.service: Unit process 646 (systemd-journal) remains running after unit stopped. [ 353.: .1 systemd: systemd-journald.service: Unit process 4031 (systemd-journal) remains running after unit stopped. [FAILED] hailed to start systemd-journald.service - Journal Service. See 'systemctl status systemd-journald.service' for details. [ 353.116852] systemd: systemd-journald.service: Scheduled restart job, restart counter is at 2. [ 353.117378] systemd: Stopped systemd-journald.service - Journal Service. ] Stopped systemd-journald.service - Journal Service. [ 353.124921] systemd: systemd-journald.service: Found left-over process 646 (systemd-journal) in control group while starting unit. Ignoring. [ 353.124934] systemd: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 353.125005] systemd: systemd-journald.service: Found left-over process 4031 (systemd-journal) in control group while starting unit. Ignoring. [ 353.125017] systemd: This usually indicates unclean termination of a previous run, or service implementation deficiencies. 353. 1 systemd: Starting systemd-journald.service - Journal Service... Starting systemd-journald.service - Journal Service... 353.167892] systemd-journald: File /run/log/journalaafbee1b601542bb908b095e9aef3d91/system.journal corrupted or uncleanly shut down, renaming and replacing. 1 Job systemd-journald.service/start running (29s / lmin 30s)

Basically it is stuck in exiting and then retrying to start the systemd-journald.service. I tried different usb slot and drives with no success. When I tried to boot in a different laptop I was greeted with

shim SBAT data failed: Security Policy Violation
Something has gone seriosuly wrong: SBAT self-check failed: Security Policy Violation

I have tried enabling and disabling secure boot and fast startup. I am only booting Windows 11. And my device is Asus ROG Zephyrus G14 2021. Thank You

I have a Kali Linux installation (VM) which I customized so much with custom bash & python scripts plus installing quite a few additional software, I would like to know if it is possible to take this VM and turn it to a bootable media, say USB storage. One way is to install Kali on a usb with persistence option to make the changes permanent, but it's just too much work! "Please note, this is not the usual ISO-to-USB kind of thing, I'm looking for a way to make a bootable media from an already installed OS"

So I just got that new laptop which is DOS free and I'd like to install Windows and Ubuntu for gaming and work. Problem is I don't have any other computer available for now and the only OS I have is Kali Linux on a bootable USB stick. So I'd like to know if it's possible to make a bootable USB stick from Kali Linux and how! I know UNETbootin however I don't know which distribution I should get or even the commands. If I only need the iso file, please teach me the commands I need to use to make it work. (And which commands I should use to install unetbootin if possible) What I have : - The new laptop which doesn't have an OS --> dos free (only have access to bios). - A bootable USB stick with Kali Linux on it. - Another USB stick that I'd like to make bootable with Windows if possible (then I know how to do when I have Windows to get Ubuntu in addition).

I've made a small mistake when trying to install Kali Linux on a smaller partition and erased my Windows 10 installation and I can't get back to my Win10 install. I've made a bootable USB to try and get back onto Win10 using the below command: sudo dd if=/root/Downloads/win10/win10.iso of=/dev/sdc bs=512k and each time I restart and try to reboot from the USB I'm only welcomed by the GRUB menu. I'm really new to using any Linux-based distribution. Would anyone let me know what am I missing here?

I want to install Debian in dual boot with Windows, for this I created a bootable USB key under Linux Lite (Ubuntu based distro), with the **#dd** command. The command I used is:

if=image.iso of=/dev/sdx bs=4M status=progress && syn

At the time of installation I noticed that this iso file does not have the wifi firmware, I know after research that Debian has a non_free iso file, which means that it has non-free firmware ... But the Debian site also offers a second method, and for learning reasons, I wanted to test the second, the second method is to inject firmware that I have already downloaded from the official site into the firmware folder of the USB key which is on the root. The problem is that the dd command created a partition of the exact size of the iso file! with **iso9660 format**! the rest of the USB key is an unallocated partition. i did the same test on **windows with rufus** and everything works fine, refusal to create a partition equal to the total size of the USB key, so i was able to inject files without problems! my question is, how to create a bootable USB key on linux in **command line** with, for example the dd command or another, which would allow me to add a file after creation

I am trying to create a fully functional clone of my Linux system's hard drive - meaning I would be able to replace the original hard drive with a clone, boot from it and continue using it. I have used Rescuezilla and Clonezilla, both of which offer the disk-to-disk cloning option, but both clones - despite the cloning procedure completed successfully - fail to boot taking me to the emergency mode thus making both clones unusable :( I'm running the Rocky Linux 9.2 with KVM hosting a guest OS. I gathered some info from both the source disk: and the cloned disk: I do not see any difference there, but given I am new to the Linux world I could have missed some important detail. I will be extremely grateful for any help resolving this problem. Thank you everyone! Mike To answer telcoM: Hello telcoM, and thank you so much for your explanations. I am sorry in advance for my ignorance, because like I mentioned I am totally new to the Linux world. Anyway, even though I do not have a direct access to the server now I can answer some assumptions and clarify some points as well. 1. You are right: there are no other OSs on this disk (except for the virtual machine-residing guest, which is not bootable certainly) - and no other OS is planned, therefore I am not interested in multibooting; 2. I believe NVRAM is not a reason here because I was trying so far to replace the original disk with the clone in the same computer, thus it is the same; 3. The source disk - at least (like I said I have no access to the clone as of now) already contains the /boot/efi/EFI/BOOT/BOOTX64.efi - that is I do not need to place it there; 4. I did not have both disks inserted at the same time (I tried it first time I ran cloning, but no more :)) The screenshots were taken in succession: one in the rescue mode having the clone disk inserted, while the second - after I reinserted the original drive and rebooted the system. Would you recommend anything else to check/do? I greatly appreciate you help as well as anyone else's! Mike

I am trying to build linux from scratch (LFS) as an educational project using the main LFS book version 12.1 , however, whene i reach the bottable chapter, i found that i have to boot my LFS using EFI support because my main machine is macbook pro 2014, so i follwo the BLFS guide Using GRUB to Set Up the Boot Process with UEFI , and https://www.linuxfromscratch.org/blfs/view/12.1/postlfs/grub-efi.html ; whene i re-boot the machine i get > error disk 'hd0,2' not found I fix it by using > set root=(hd1,gpt4) The next problem is > /boot/vmlinuz-6.7.4-lfs-12.1 not found i checked my boot file and found the file name exists under differnt name **/boot/vmlinuz-6.7.4-lfs-12.1-systemd** so i rename it to **/boot/vmlinuz-6.7.4-lfs-12.1**. No whene i am booting again i get a black screen after selecting the lfs system from booting menu . attached files > **fdisk -l /dev/sda outputs** Device Start End Sectors Size Type /dev/sda1 40 409639 409600 200M EFI System /dev/sda2 411648 17807359 17395712 8.3G Linux swap /dev/sda3 488847608 490117143 1269536 619.9M Apple boot /dev/sda4 19855360 81295359 61440000 29.3G Linux filesystem linux kernel configuration file grub.cfg file any help!