PorteuX data not found - Resolved

[Ed_P]

Code: Select all

menuentry " PorteuX 2.0 ISO - Cinnamon AF"  --class slackware   --class user-icon-porteux  {
#    https://github.com/porteux/porteux/releases & https://github.com/porteux/porteux/blob/main/boot/boot/docs/cheatcodes.txt

     set linux_folder=/porteux
     set iso="/ISOs/PorteuX/porteux-v1.8-current-cinnamon-6.4.2-x86_64.iso"
     set iso="/ISOs/PorteuX/porteux-v1.9-current-cinnamon-6.4.6-x86_64.iso"
     set iso="/ISOs/PorteuX/porteux-v2.0-current-cinnamon-6.4.9-x86_64.iso"
     
     search -f $iso --set=root
     loopback loop $iso
     linux (loop)/boot/syslinux/vmlinuz      from=$iso 
     initrd (loop)/boot/syslinux/initrd.zst
     }

Code: Select all

PorteuX - The Next Experience

^ checking PorteuX data...
^ device not ready yet? delaying 1 seconds

PorteuX data not found.

[SEMERENDO.cr]

Two things
> Doesn't booting the ISO speed up the process?
> Why keep updating Porteux if there's nothing new except for the MB increase?

I only decided today to see if I could change the path to the changes folder, but it had no effect. I wonder why the heck?
## Tell porteux where the changes folder is

I think Slackware could be considered the only LTS distribution in the Linux world, and that's wonderful, because it takes many years to jump: 14-15... 16?

[Ed_P]

\boot\docs\cheatcodes.txt]from=/mnt/partition
from=/path/folder
from=/path/porteux.iso

... Loads PorteuX from the specified partition, folder or ISO file.
Examples:
'from=/mnt/sdb2' will attempt to load unpacked PorteuX ISO from
the second partition on your second drive.
'from=/mnt/sda2/linux-testing' will attempt to load unpacked ISO
from the 'linux-testing' folder placed on the second partition.
'from=/mnt/sda1/porteux-test.iso' will attempt to load the PorteuX
data from 'porteux-test.iso'.

NOTE: if the destination partition is not provided with this
cheatcode, the booting script will search through all available
devices for your data.

grub2 menu

Code: Select all

menuentry " PorteuX 2.0 ISO - Cinnamon AF+"  --class slackware   --class user-icon-porteux  {
#    https://github.com/porteux/porteux/releases

     set linux_folder=/porteux
     set iso="/ISOs/PorteuX/porteux-v1.8-current-cinnamon-6.4.2-x86_64.iso"
     set iso="/ISOs/PorteuX/porteux-v1.9-current-cinnamon-6.4.6-x86_64.iso" 
     set iso=/ISOs/PorteuX/porteux-v2.0-current-cinnamon-6.4.9-x86_64.iso    

     set bootparms="volume=33 reboot=cold extramod=$linux_folder/Modules;$linux_folder/modsavedat \
       kmap=us norootcopy noload=-test;myc;MyC   # noload mate if mycinnamon mod in play"

     search -f $iso --set=root
     loopback loop $iso
     linux (loop)/boot/syslinux/vmlinuz      from=$iso  # $bootparms
     initrd (loop)/boot/syslinux/initrd.zst
#     linux  /ISOs/PorteuX/vmlinuz      from=$iso  # $bootparms
#     initrd /ISOs/PorteuX/initrd.zst
     }

Not working. Help!!

[SEMERENDO.cr]

Sir, but wouldn't it be better if you unzipped the ISO image and booted it normally? I think the philosophy of Porteus isn't to be a "live CD." All versions of Porteus have booted without problems on all my computers; the problem was with the installer and LILO.

[Ed_P]

Porteus and porteux have been ISO bootable for years. No CD, no USB, no disk space. Just download and boot.

[beny]

hi Ed_P, try to write a grub entry more simple, you have three index of cinnamon ,try to # what you don't need,maybe work,also the iso have to boot with a whole path or am i wrong...

[Ed_P]

Yes, I could comment out the prior ISO settings but the last one is the only one that counts (and the prior ISOs worked). In that root is set to the drive the ISO is on I normally don't have to include it in the from= parm but maybe this release needs it. I'll give it a shot. Thanks beny.

Added in 3 hours 2 minutes 30 seconds:
Adding the root parm didn't help beny.

Code: Select all

     linux (loop)/boot/syslinux/vmlinuz   from=$root$iso

Same result.

BTW This is my normal grub2 porteux menu.

Code: Select all

menuentry " PorteuX 2.0 ISO - Cinnamon"  --class slackware   --class user-icon-porteux  {
#    https://github.com/porteux/porteux/releases

     set linux_folder=/porteux
     set iso="/ISOs/PorteuX/porteux-v1.4-cinnamon-6.2.0-current-x86_64.iso"
     set iso="/ISOs/PorteuX/porteux-v1.5-cinnamon-6.2.7-current-x86_64.iso"
     set iso="/ISOs/PorteuX/porteux-v1.6-cinnamon-6.2.9-current-x86_64.iso"
     set iso="/ISOs/PorteuX/porteux-v1.7-current-cinnamon-6.2.9-x86_64.iso"
     set iso="/ISOs/PorteuX/porteux-v1.8-current-cinnamon-6.4.2-x86_64.iso"
     set iso="/ISOs/PorteuX/porteux-v1.9-current-cinnamon-6.4.6-x86_64.iso"
     set iso="/ISOs/PorteuX/porteux-v2.0-current-cinnamon-6.4.9-x86_64.iso"

     set bootparms="volume=33 reboot=cold extramod=$linux_folder/Modules;$linux_folder/modsavedat \
       kmap=us norootcopy noload=-test"         

     search -f $iso --set=root
     loopback loop $iso
     linux (loop)/boot/syslinux/vmlinuz      from=$iso $bootparms
     initrd (loop)/boot/syslinux/initrd.zst
     }

Yes, I've been doing this awhile.



Added in 1 day 49 minutes 2 seconds:
This is not a porteux problem guys, it's tied to my new computer problems.

I tried to boot the 1.9 iso which worked on my old computer and it doesn't boot here either. Same problem.

Thank God the porteus isos boot.

[Ed_P]

OK, what the heck is the cause of this problem?? It's not a PorteuX problem specifically rather a problem on my new Acer impacting Porteux ISOs that work on my Dell. Porteus ISOs boot but not the 1.8, 1.9 or 2.0 PorteuX ISOs. The ISOs are on Windows 11 NTFS drives on both systems, and on the Dell boot with:

Code: Select all

 search -f $iso --set=root
 loopback loop $iso
 linux (loop)/boot/syslinux/vmlinuz      from=$iso   # $bootparms
 initrd (loop)/boot/syslinux/initrd.zst

but on the Acer with same code fail. The Acer has twice the RAM as the Dell.

Any clues as to why???? Or how to debug? Very frustrating.

Added in 15 hours 49 minutes 59 seconds:
I'm leaning toward the problem being grub2 on the Acer doesn't know how to unzip the .zst file. Why I don't know.

Another thought, it would be nice if there was a cheatcode that when used would help debug booting problems.

[beny]

hi Ed_P,if someone of the crew give you an initrd script to change zst to xz or tar.gz or img so you can debug the boot of your notebook ok try if work or maybe you can boot in legacy mode

[Otto]

I think your problem is "search -f $iso --set=root".
I use UUID and porteux/s.iso work fine.

[Ed_P]

Update:

If I copy the ISOs to a USB drive, "copy" not "install", and use a similar folder structure, tweak the grub2 iso= parm to match the USB folder's name, porteux 1.9 and 2.0 boot on the Acer.

For some reason zstd files don't work on my new Acer's harddrive.

Added in 3 hours 4 minutes 6 seconds:
I suspect a blocksize/clustersize problem on the Acer's harddrive. Too big for grub2's loop function or too big for grub2's deblock function. Or a bad combination. Looking for a way to show what they are on the Acer and Dell harddrives.
Any Linux commands?

Added in 9 hours 2 minutes 16 seconds:
fdisk is interesting. All Acer drive's sector sizes are 512 bytes.

[Otto]

The ISOs are on Windows 11 NTFS drives on both systems, and on the Dell boot with:

I dont use windows for many years.
W11 with active-Bitlocker may influence the iso boot process and Most files(particular ISOs) need to be contiguous (in sequential sectors/clusters on the disk), that file may not boot or work correctly!
I am sure, ext4 has no problem with disk fragmentation.

"search -f $iso --set=root" without uuid wont work on my machine.
What Grub2 version do you have?

[Ed_P]

"search -f $iso --set=root" without uuid wont work on my machine.
What Grub2 version do you have?

I believe it's version 2.12. Grub2Win upgraded to it in Feb. But I've used that line for years. It only fails for me when the same iso file name is on the harddrive and USB drive.

Most files(particular ISOs) need to be contiguous (in sequential sectors/clusters on the disk), that file may not boot or work correctly!

Just not sure how to do that with SSD drives and Windows 11. Not sure Windows' Defrag and Optimize Drive does it like Mark Russinovich's
Contig v1.7 did with harddrives and earlier versions of Windows. You got any suggestions?

Added in 5 hours 30 minutes 14 seconds:
This update didn't help.

Code: Select all

Contig v1.83 - Contig
Copyright (C) 2001-2023 Mark Russinovich
Sysinternals

Summary:
     Number of files processed:      3
     Number of files defragmented:   0
     Number unsuccessfully procesed: 3
     All files were either already defragmented or unable to be defragmented.

[SEMERENDO.cr]

Super Grub2 Disk
> Bootable ISOs (in /boot-isos or /boot/boot-isos
https://github.com/supergrub/supergrub/ ... -549118247
https://www.supergrubdisk.org/super-grub2-disk/

PorteuX data not found.

[Otto]

Not recommended to defrag an SSD.

Tested many defrag-tools in the past, but only one worked(forgot the name).
Just use ext4 partition(you do not need to defrag the disk).