<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Hello dear friends,<br>
<br>
let me add some info which may help you to find the missing dot
(hopefully) more easily.<br>
<br>
The <font size="+2" face="monospace"><b>lsblk</b></font> command
after having booted puts out:<br>
<br>
<font size="+2" face="monospace">NAME MAJ:MIN RM SIZE RO TYPE
MOUNTPOINTS<br>
loop0 7:0 0 643.1M 1 loop /image<br>
loop1 7:1 0 521.8M 1 loop /.ro<br>
sda 8:0 0 298.1G 0 disk <br>
├─sda1 8:1 0 512M 0 part<br>
└─sda2 8:2 0 297.6G 0 part<br>
sdb 8:16 1 7.5G 0 disk <br>
└─sdb1 8:17 1 7.5G 0 part <br>
</font><br>
And the <font size="+2"><b>df</b></font> command puts out:<br>
<br>
<font size="+2" face="monospace">Filesystem Size Used Avail
Use% Mounted on<br>
udevfs 861M 0 861M 0% /dev<br>
runfs 900M 696K 899M 1% /run<br>
/dev/loop0 644M 644M 0 100% /image<br>
/dev/loop1 522M 522M 0 100% /.ro<br>
none 900M 64K 900M 1% /.rw<br>
overlay 900M 64K 900M 1% /<br>
tmpfs 900M 0 900M 0% /tmp<br>
shmfs 900M 0 900M 0% /dev/shm<br>
</font><br>
<br>
/dev/loop0 which is mounted on /image shows the contents of the
ISO-image and<br>
/dev/loop1 which is mounted on /.ro shows the contents of the
file "rescue" which is located at the root of the ISO-image.<br>
<br>
But the kernel parameters do not tell the boot process where the
ISO-image can be found thus is asking for it.<br>
<br>
I hope this addintional info can help you to get more closely to the
correct solution?<br>
<br>
Thank you very for your attention.<br>
Thank you very much in advance.<br>
<br>
Yours truly<br>
<br>
richard<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">Am 29.10.21 um 20:29 schrieb Richard
Gantz online:<br>
</div>
<blockquote type="cite"
cite="mid:c0ffa8d8-5303-58a0-58d8-aca9c720cc40@online.de">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Hello dear friends,<br>
<br>
i copied the file regular-rescue-latest-x86_64.iso to the root of
an 8GB USB stick, formatted with FAT32 file system.<br>
<br>
I added the following menuentry to the /boot/grub/grub.cfg on the
stick:<br>
<br>
<font size="+2" face="monospace">menuentry "Rescue LiveCD" {<br>
set linux_suffix='efi'<br>
set isofile="/regular-rescue-latest-x86_64.iso"<br>
loopback loop (hd0,1)${isofile}<br>
echo "Loading Linux vmlinuz ..."<br>
linux$linux_suffix (loop)/boot/vmlinuz \<br>
boot=boot \<br>
live \<br>
root=bootchain \<br>
bootchain=fg,altboot \<br>
automatic=method:(loop),uuid:2021-10-20-05-31-11-00 \<br>
stagename=rescue \<br>
ramdisk_size=534345 \<br>
nosplash \<br>
showopts \<br>
findiso=$isofile \<br>
iso-scan/filename=${isofile} \<br>
lowmem<br>
echo "Loading initial ramdisk ..."<br>
initrd$linux_suffix (loop)/boot/initrd.img<br>
}<br>
</font><br>
The parameters <font size="+2" face="monospace">findiso</font>=
and <font size="+2" face="monospace">iso-scan/filename=</font>
may be superfluous, the first worked for CloneZilla and the second
works for Linux Mint, but i could not yet find the corresponding
parameter name for the regular-rescue ISO image.<br>
<br>
The parameter <font size="+2" face="monospace">boot=boot</font>
may also be wrong. but the system boots up with an interruption
and asks for the exact location of the ISO image.<br>
<br>
So i guess that the parameters <font size="+2" face="monospace">root=bootchain</font>
and <font size="+2" face="monospace">bootchain=fg,altboot</font>
have to be changed that the system can find the ISO image without
asking interactively.<br>
<br>
This is what happens:<br>
<br>
1. The system boots up to the point where it says: <br>
<font size="+2" face="monospace">[ 7.754545] Starting
chaind services: [ DONE]</font><br>
<br>
2. Then the first dialog with the title "Please choose the
installation method or special action" shows up and offers the
following options:<br>
- NFS server<br>
- FTP server<br>
- HTTP server<br>
- SAMBA server<br>
- CD/DVD-ROM Drive<br>
- Local Disk Drive<br>
- Reboot the computer<br>
- Turn off the computer<br>
Here i choose the option "<b>Local Disk Drive</b>", because the
ISO file is on the USB stick, the system already started to boot
from.<br>
<br>
3. The next dialog says "Please choose the partition with the ALT
regular-rescue/x86_64 on the boot media or cancel and try again"
and gives me among others the opportunity to choose<br>
- sda1 (Part #1: 512 MiB, vfat, UUID=AAAA-BBBB)<br>
- sda2 (Part #2: 297 GiB, ext4,
UUID=01234567-AAAA-BBBB-CCCC-ba9876543210)<br>
- sdb1 (Part #1: 7 GiB, vfat: 'MAX-FELIX')<br>
Here again i choose the USB stick "<b>sdb1 (Part #1: 7
GiB, vfat: 'MAX-FELIX')</b>", becaus e the ISO image is located
there in the root directory<br>
<br>
4. Then the last dialogbox appears and asks:<br>
"Please enter the full path to an ISO-image containing the ALT
regular-rescue/x86_64 or leave this field blank to use mounted
partition 'as is', or cancel to return step back."<br>
I input the path in the field "ISO-image"; <b>/regular-rescue-latest-x86_64.iso</b><br>
<br>
After choosing < OK >, the system boot continues with<br>
<font size="+2">[ 80.123456] INIT: Entering runlevel:
2 [ DONE ]</font><br>
and finally ends up with the root prompt, waiting for commands.<br>
<br>
Could anyone please help to correct the kernel boot parameters the
the root filesystem can be found in the ISO-image at the end of
the bootchain process that the interruption for user input is not
needed?<br>
<br>
Thank you very for your attention.<br>
Thank you very much in advance.<br>
<br>
Your truly<br>
<br>
richard<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
community-en mailing list
<a class="moz-txt-link-abbreviated" href="mailto:community-en@lists.altlinux.org">community-en@lists.altlinux.org</a>
<a class="moz-txt-link-freetext" href="https://lists.altlinux.org/mailman/listinfo/community-en">https://lists.altlinux.org/mailman/listinfo/community-en</a></pre>
</blockquote>
<br>
</body>
</html>