Muilt Boot

felipeortega

Hello guys,
Hopefully someone can help me!
My problem is to boot by using a USB key boot using various MuiltBoot Iso
All my ISO usually loads the boot he pfsense but also for the error:

set vfs.root.mountfrom.options=rw
and then remove invalid mount options from /etc/fstab.

Loader variables:
vfs.root.mountfrom=cd9660:/dev/iso9660/pfsense
vfs.root.mountfrom.options=rw

Manual root filesystem specification:
<fstype>:<device> Mount <device>using filesystem <fstype>eg. ufs:/dev/da0s1a
eg. cd9660:/dev/acd0
This is equivalent to: mount -t cd9660 /dev/acd0 /

? List valid disk boot devices
<empty line=""> Abort manual input

mountroot>

I seen people saying to use command kern.cam.boot_delay=1000 or 15000
but did not work….
Will I have to run pfsense with muilt boot from USB??</empty></fstype></device></device></fstype>

stephenw10

The ISO image expects to find the root filesystem on the CD device but you are booting from USB.
You have to tell it where root is. Unfortunately I can't remember the command right now! ::)

Maybe: cd9660:/dev/da0s1a ???

Steve

Edit: What does it list as valid devices if you enter '?'

What mulitboot script are you using?

jimp

You should really be using the "official" memstick boot image and not a CD. I think we went over this before (in another thread or on IRC), something in your multiboot code is not working as it should with pfSense. Just use a dedicated memory stick for pfSense installs and it will work that way.

felipeortega

Thanks for helping me
I use a stick with a GRUB boot with various systems
now let me add this PFSense to ease my
work on machine with no CD / DVD
main.ist that calls the pfsense this with this command:
title pfSense 2.0 RC1
find –set-root /pfSense.iso
map /pfSense.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)

It boots normal but he in error

set vfs.root.mountfrom.options=rw
and then remove invalid mount options from /etc/fstab.

Loader variables:
vfs.root.mountfrom=cd9660:/dev/iso9660/pfsense
vfs.root.mountfrom.options=rw

Manual root filesystem specification:
<fstype>:<device>Mount <device>using filesystem <fstype>eg. ufs:/dev/da0s1a
eg. cd9660:/dev/acd0
This is equivalent to: mount -t cd9660 /dev/acd0 /

? List valid disk boot devices
<empty line="">Abort manual input

mountroot>

mountroot> ?

show me

List of GEOM managed disk devices:
msdosfs/MULTIBOOT da0s1 da0 iso9660/plop_bootmanager acd0t01 acd0 ad0 fd0</empty></fstype></device></device></fstype>

jimp

It's hard to say if it should be da0 or ad0 based on that output, but either way you'd have to manually enter that every time you boot from there.

What you're trying to do just isn't a supported config and isn't an easy thing to fix in that way.

felipeortega

Truth Jimp
what you said really works
but I'm wanting to do everything in one
to use only one stick
as it loads the boot I think that works
the problem that it emulates the ISO file
so I'm lost ;D

jimp

The problem is that it doesn't emulate a CD-ROM, it's making it think the ISO is a hard drive.

It may be da0 where the root resides, but maybe not, that may just be the USB stick itself. And ad0 is probably the hard drive of the target machine.

You'll have to try each of the things in that list to see if any of them work.

ufs:/dev/da0s1
ufs:/dev/da0
cd9660:/dev/acd0t01
ufs:/dev/acd0
ufs:/dev/ad0

It could be any or none of those.

felipeortega

Jimp thanks for helping me
Excuse my lack of experience
In the case says you try to run these commands in

mountroot>

jimp

yes

felipeortega

None of them nothing happens just returns me the error
but if I run
msdosfs: / dev/da0s1a
it returns me an error

Trying to mount root from msdosfs:/dev/da0s1
lookup of /dev for devfs, erro:2
init: not found in path /sbin/init:/sbin/oinit:/sbin/init.bak:/rescue/init:/stand/sysinstall
panic: no init

jimp

If none of those work then it can't load the root fs of the "cd" and it can't continue, and you're back to what I told you before about it not working and you'll need either a separate USB stick.

If you're lucky then perhaps you can get grub to load the memstick disk image directly, though I'm not sure if it can do that.

felipeortega

maybe I'm wrong
then correct me
if the grub is called an ISO file
he will emulate my da0 as a cd
at boot time when he is recognizing my hardware
he found my flash drive and not been able to ride because it is in use?
If so I unzip the iso file to a folder in my flash drive will do what I can call the grub boot?

jimp

I really have no idea what grub is doing, what it wants or what it's capable of in that regard.

Perhaps someone who is more familiar with grub can offer some input there.

felipeortega

Thank you Jimp
Yesterday've sent an email to support them even more now nothing
perhaps you or someone can help me when I use this program
http://www.pendrivelinux.com/boot-multiple-iso-from-usb-multiboot-usb/

I'm trying to boot the ISO drawing on the stick

Some examples

title Ubuntu 10.04.1 (GNOME Desktop x86)
find –set-root /ubuntu-10.04.1-desktop-i386.iso
map /ubuntu-10.04.1-desktop-i386.iso (0xff)
map --hook
root (0xff)
kernel /casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper persistent iso-scan/filename=/ubuntu-10.04.1-desktop-i386.iso splash
initrd /casper/initrd.lz

title BackTrack 4 Final (Penetration Testing)
find --set-root /bt-boot/vmlinuz
kernel /bt-boot/vmlinuz BOOT=casper boot=casper persistent rw splash
initrd /bt-boot/initrd.gz
boot

How could properly call the boot pfsense?

stephenw10

There are no examples of booting any BSD distro using pendrivelinux anywhere on their site (that I could find).

The script is designed for booting a linux kernel and pfSense isn't linux.

Steve

felipeortega

You're right!
but I saw people trying it and telling people that and
possible to do this work.
The boot is fine, but I think in Escape to
loader prompt can manually enter any command
To successfully continue the boot
maybe:

vfs.root.mountfrom = cd9660: / dev/da0s1a
and since he runs through a ISO that the
pendrive

Something is missing

felipeortega

Hello everyone

I returned to report that I had a small evolution in my problem but is not complete
The solution would be a dirty

at the time of mountroot> I apply the command msdosfs: da0s1 to automate or do I insert the file loarder.conf

set vfs.root.mountfrom=msdosfs:da0s1
set vfs.root.mountfrom.options=rw

An important detail and make the iso image extracted at the root of the pendrive

This will load normally but still a problem occurs later on

Trying to mount root from msdosfs:ad0s1a

___

___/ f \

/ p ___/ Sense

_/
_/

Welcome to pfSense 2.0 RC1 …
Mounting filesystems... done.
Creating symlinks......done.
Launching the init system...

At this point it freezes completely stopped what can be done?