Thanks @dr__Dan and @jamesbond> Yes, I did find the TOC entry and the parm within.
I am revisiting this boot problem I had a while back; I gave up on it, then, in favor of a direct pointer in the savefile parm. I am now trying to work out correct use of the search= parm on the linux line.
In my limited reading, I am to understand that when the search parm is set, it tell the boot process how many levels from the root of ALL drives for a FD session. But this is not working for me, thus I believe I may be mis-understanding or mis-using the parm.
Environment
I have a drive whose label is Persistence which has a folder Sessions where a prior FD session within. The folder is "/Sessions/FD/v901"
Tests
vmlinux rootfstype=ramfs search=5 (does not find the prior session)
vmlinux rootfstype=ramfs search=5 savefile=ram:multiPersistence (does not find the prior session)
vmlinux rootfstype=ramfs search=5 savefile=ram:multiPersistence:/Sessions/ (DOES find the prior session)
I recognize that test #3, above, relieves me having to "point" the savefile parm all the way to the prior session, but I am clueless why search needed "5" to get there.
Questions
Should I be able to find the prior sessions merely with only the search parm?
With the savefile identifying the device label good enough for the search parm to direct the boot to find the prior session?
Am I using the search parm correctly in directing how many levels deep it is to search, starting at the root?
Thanks in advance for guidance to proper parm use for booting by adding correct entry(s) at boot time's menu to find the prior session. Your help can clear my understanding of search for prior session and any indirect relationship of the search parm to the savefile parm.
Even as this is not a high priority for me, I do hope to get any help in understanding this proper parm usage.
The following is a failed example where the prior session was NOT found. To find the session in the Sessions folder, I needed to do test #3, above
- A failed example where the prior session was NOT found
- xscreenshot-20240614T073928.png (252.66 KiB) Viewed 555 times