Just to share my findings and also to keep reference of the solution for others as well as future use.
Because so far I have not found any one having this problem or no one has come up with the solution yet.
- Panic error occurred when I set **live_media_path=clonezilla/live** **toram=clonezilla/syslinux,clonezilla/live**
- Initially i struggled to understand what caused the Panic error during Initramfs boot up stage.
- Then I started to do `cat boot.log | more` at the initramfs prompt.
- I traced back to the part where **command was given to 'mkdir /run/live/medium/*clonezilla/live*'**
- looks like mkdir was trying to make 2 directories (clonezilla & live) at once. Meaning the mkdir command **FAILED**.
- But after failing, the code did not stop and continued to process the other remaining boot up code.
- So the kernel thinks that actual **live_media_path** is **/run/live/medium/clonezilla/live**.
- But I found out that the path donot exist. But this path exists **/run/live/medium/live** and also i found the**syslinux** folder in there as well.
- As a workaround to the **mkdir**, i could just put the folders **clonezilla/live,clonezilla/syslinux** at root directory but that was not an ideal situation since I have 2 seperate clonezilla versions in the thumbdrive.
- Hence, after testing, I found that by setting **live_media_path=live** I was able to boot up successfully.
Btw as you can see i also managed to run pre and post ocs scripts. And disabled Hpet, apic and lapic to reduce further kernel panics due to old system clock issues.
If you need any pics I can include later.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Attached is the "boot.log" output from Debian Live Boot initramfs.
The issue is not due to mkdir command. Instead it is due to "rsync" command that never replicate the proper directory in "/run/live/medium" according to syslinux cfg file. (required directory - /run/live/medium/clonezillasvr/live , actual directory that was created - /run/live/medium/live )
Below attached is showing I manually listing directories after the initramfs panic terminal appeared:
1) ls /run/live/medium/clonezillasvr/live - result = "No such file or directory"
2) ls /run/live/medium/live - result = ok
This proves that the rsync -a --progress command during boot up did not replicate the desired live directory properly.
Basically what i observed is when clonezilla live is in nested directory
(eg. /Example/live ) rather than in root directory (eg. /Live), the toram function will result in kernel panic due to initramfs unable to
find live medium, due to improper rsync copy to ram bcos rsync did not
replicate the directories as per live_media_path definition in the cfg
file.
I believe this the kernel panic most of the users encounters when using
toram feature.
I believe by making rsync replicate the directory structure in ram is the
best way to resolve this issue.
If would be easier if you can provide the patch file for live-boot package, I believe it's about patching this file:
components/9990-toram-todisk.sh
Then we can try to let the upstream accept that.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If would be easier if you can provide the patch file for live-boot
package, I believe it's about patching this file:
components/9990-toram-todisk.sh
Then we can try to let the upstream accept that.
Oh, sorry, my bad. There is a packge called live-boot: https://salsa.debian.org/live-team/live-boot
It is the one you should modify, and its files are in the live system after booting:
/lib/live/boot/
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh, sorry, my bad. There is a packge called live-boot: https://salsa.debian.org/live-team/live-boot
It is the one you should modify, and its files are in the live system
after booting:
/lib/live/boot/
Hi Steven, All,
Just to share my findings and also to keep reference of the solution for others as well as future use.
Because so far I have not found any one having this problem or no one has come up with the solution yet.
My scenario is :
My customised Boot Parameter looks like this:
Problem Description:
Here is my final (fixed) Boot Parameter:
Btw as you can see i also managed to run pre and post ocs scripts. And disabled Hpet, apic and lapic to reduce further kernel panics due to old system clock issues.
If you need any pics I can include later.
mkdir -p /run/live/medium/clonezilla/live
Will create all parent directories, where necessary, to allow creation of the full path.
The script that ran the mkdir is autoran during boot up. Not my code.
Suggest to edit in boot up code (run_init)?
On Fri, 31 Jan 2020, 02:32 Jeremy Boden, jeremyboden@users.sourceforge.net
wrote:
Hi Steven
Attached is the "boot.log" output from Debian Live Boot initramfs.
The issue is not due to mkdir command. Instead it is due to "rsync" command that never replicate the proper directory in "/run/live/medium" according to syslinux cfg file. (required directory - /run/live/medium/clonezillasvr/live , actual directory that was created - /run/live/medium/live )
Below attached is showing I manually listing directories after the initramfs panic terminal appeared:
1)
ls /run/live/medium/clonezillasvr/live- result = "No such file or directory"2)
ls /run/live/medium/live- result = okThis proves that the
rsync -a --progresscommand during boot up did not replicate the desired live directory properly.Attached is the rsync command during debian live boot up.
Btw the
live_media_path=liveFAILED. As a workaround, I copied clonezillasvr/live contents to root /live.So this issue occurs only when you want to keep two versions of Clonezilla live on the same machine's hard drive?
Steven
Hi Steven
Basically what i observed is when clonezilla live is in nested directory
(eg. /Example/live ) rather than in root directory (eg. /Live), the
toram function will result in kernel panic due to initramfs unable to
find live medium, due to improper rsync copy to ram bcos rsync did not
replicate the directories as per live_media_path definition in the cfg
file.
I believe this the kernel panic most of the users encounters when using
toram feature.
I believe by making rsync replicate the directory structure in ram is the
best way to resolve this issue.
Or if my config is wrong, please let me know.
Thank you Mr Steven Shiau.
On Sun, 23 Feb 2020, 15:43 Steven Shiau, steven_shiau@users.sourceforge.net
wrote:
If would be easier if you can provide the patch file for live-boot package, I believe it's about patching this file:
components/9990-toram-todisk.sh
Then we can try to let the upstream accept that.
Steven
Hi Steven
I am not sure about what you mean by "patch file in
components/9990-toram-todisk.sh" but i will try to find out.
But it will be better if you can guide me.
Thanks.
On Sun, Feb 23, 2020 at 7:51 PM Steven Shiau steven_shiau@users.sourceforge.net wrote:
Oh, sorry, my bad. There is a packge called live-boot:
https://salsa.debian.org/live-team/live-boot
It is the one you should modify, and its files are in the live system after booting:
/lib/live/boot/
Steven
Awesome Steven
Thanks!
Will revert any updates.
On Wed, 26 Feb 2020, 11:48 Steven Shiau, steven_shiau@users.sourceforge.net
wrote: