Re: Some help with dd backing up into an iso

["Thomas Schmitt" <scdbackup@gmx.net>]

Hi,

GiaThnYgeia wrote:
> $ ls -l
> /mnt/usb-Kingston_DataTraveler_3.0_08606E69C773BFC06965007B-0:0-part1
> total 0

Oops. I should have proposed

  ls -ld

so that we see the directory's info rather than the one of its content.
Please retry.

(The USB stick seems not to have been mounted at that moment.)

---------------------------------------------------------------------

Do i get it right that your machines boot in EFI non-legacy mode ?

> ftp://ftp.spline.de/pub/siduction/iso/patience/
> I tried the lxqt and lxde

Well then.
  wget ftp://ftp.spline.de/pub/siduction/iso/patience/lxde/amd64_2017-03-05_18-24/siduction-17.1.0-patience-lxde-amd64-201703051824.iso

... having a cup of tea ... "patience" is a good name ...

Please run this xorriso command on the modified ISO (i assume the USB stick
is /dev/sdc) and send the output to me directly:

  xorriso \
  -indev /dev/sdc \
  -pvd_info \
  -report_el_torito plain \
  -report_system_area plain

With the original ISO it reports:

  Volume id    : 'siduction'
  ...
  Preparer Id  : XORRISO-1.4.6 2016.09.16.133001, LIBISOBURN-1.4.6, LIBISOFS-1.4.6, LIBBURN-1.4.6
  ...
  El Torito catalog  : 1531  1
  El Torito cat path : /boot.catalog
  El Torito images   :   N  Pltf  B   Emul  Ld_seg  Hdpt  Ldsiz         LBA
  El Torito boot img :   1  BIOS  y   none  0x0000  0x00      4        3649
  El Torito boot img :   2  UEFI  y   none  0x0000  0x00   5760          90
  El Torito img path :   1  /boot/grub/i386-pc/grub_eltorito
  El Torito img opts :   1  boot-info-table grub2-boot-info
  El Torito img path :   2  /efi.img
  System area options: 0x00004201
  System area summary: MBR protective-msdos-label grub2-mbr cyl-align-off GPT
  ISO image size/512 : 2431468
  Partition offset   : 0
  MBR heads per cyl  : 75
  MBR secs per head  : 32
  MBR partition table:   N Status  Type        Start       Blocks
  MBR partition      :   1   0x00  0xee            1      2431467
  GPT                :   N  Info
  GPT disk GUID      :      d3589faecd219d408a3ac366f4086ac5
  GPT entry array    :      2  248  separated
  GPT lba range      :      64  2431404  2431467
  GPT partition name :   1  4700610070003000
  GPT partname local :   1  Gap0
  GPT partition GUID :   1  d3589faecd219d408a3bc366f4086ac5
  GPT type GUID      :   1  a2a0d0ebe5b9334487c068b6b72699c7
  GPT partition flags:   1  0x1000000000000001
  GPT start and size :   1  64  296
  GPT partition name :   2  450046004900200062006f006f007400200070006100720074006900740069006f006e00
  GPT partname local :   2  EFI boot partition
  GPT partition GUID :   2  d3589faecd219d408a38c366f4086ac5
  GPT type GUID      :   2  28732ac11ff8d211ba4b00a0c93ec93b
  GPT partition flags:   2  0x1000000000000001
  GPT start and size :   2  360  5760
  GPT partition path :   2  /efi.img
  GPT partition name :   3  4700610070003100
  GPT partname local :   3  Gap1
  GPT partition GUID :   3  d3589faecd219d408a39c366f4086ac5
  GPT type GUID      :   3  a2a0d0ebe5b9334487c068b6b72699c7
  GPT partition flags:   3  0x1000000000000001
  GPT start and size :   3  6120  2425284
  
This is the layout of grub-mkrescue. A "protective" MBR partition of
type 0xee and a GUID partition table (aka GPT).
And you got it to boot by setting the boot flag to partition 1 ?
Or was it bit 1 of the GPT partition ?
The GPT flags mean:
  bit0= "System Partition" Do not alter.
  bit2= Legacy BIOS bootable (MBR partition type 0x80)
  bit60= read-only

Now i wonder what changed by your manipulation, MBR partition property
"Status" or GPT property "partition flags".


Have a nice day :)

Thomas