Install 9.0 release via PXE

Installing and upgrading FreeBSD.

Install 9.0 release via PXE

Postby lory » 23 Jan 2012, 09:22

I have pxe install server with syslinux. Works fine for both i386 and amd64 FreeBSD 8.2 with that conf.

Code: Select all
label fb82
  menu label FreeBSD 8.2
  linux memdisk
  initrd [url]http://1.200.0.1/images/fb82.iso[/url]
  append iso raw nfsroot=1.200.0.1:/data/tftpboot/freebsd/8.2

label fb82_64
  menu label FreeBSD 8.2 64-bit
  linux memdisk
  initrd [url]http://1.200.0.1/images/fb82_64.iso[/url]
  append iso raw nfsroot=1.200.0.1:/data/tftpboot/freebsd/64/8.2

FreeBSD 9.0 amd64 can't boot.
lory
Junior Member
 
Posts: 3
Joined: 23 Jan 2012, 09:12

Postby rhlampe » 25 Jan 2012, 20:41

I'm having the same issue.

It stops at:

Code: Select all
Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...
mountroot: waiting for device /dev/iso9660/FREEBSD_INSTALL ...
Mounting from cd9660:/dev/iso9660/FREEBSD_INSTALL failed with error 19.

Loader variables:
  vfs.root.mountfrom=cd9660:/dev/iso9660/FREEBSD_INSTALL
  vfs.root.mountfrom.options=ro

Manual root filesystem specification:
  <fstype>:<device> [options]
    Mount <device> using filesystem <fstype>
    and with the specified (optional) option list.

   eg. ufs:/dev/da0s1a
       zfs:tank
       cd9660:/dev/acd0 ro
         (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /)

  ?             List valid disk boot devices
  .             Yield 1 second (for background tasks)
  <empty line>  Abort manual input

mountroot> ?   

List of GEOM managed disk devices:
  ada0

mountroot>     


Anyone have any ideas?
rhlampe
Junior Member
 
Posts: 3
Joined: 22 Feb 2011, 17:13

Postby honza801 » 06 Feb 2012, 10:05

I'm experiencing the same problem.
honza801
Junior Member
 
Posts: 10
Joined: 18 Jan 2011, 12:02

Postby SirDice » 06 Feb 2012, 10:10

It's an old article but should still contain some valid pointers.

http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/
Senior UNIX Engineer at Unix Support Nederland
Experience is something you don't get until just after you need it.
User avatar
SirDice
Old Fart
 
Posts: 16195
Joined: 17 Nov 2008, 16:50
Location: Rotterdam, Netherlands

Postby honza801 » 06 Feb 2012, 10:22

SirDice wrote:It's an old article but should still contain some valid pointers.

http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/


This article is about creating nfs root and bootstrapping for pxe boot. I'm trying to use the FreeBSD 9.0 installation ISO image (FreeBSD-9.0-RELEASE-amd64-bootonly.iso) to install [del]freebsd[/del] FreeBSD via pxe.
honza801
Junior Member
 
Posts: 10
Joined: 18 Jan 2011, 12:02

Postby SirDice » 07 Feb 2012, 07:37

I didn't say you should use it literally, I said there are some pointers.

Besides, it's a jumpserver. Jumpservers are used to PXE boot a machine and run an installer.
Senior UNIX Engineer at Unix Support Nederland
Experience is something you don't get until just after you need it.
User avatar
SirDice
Old Fart
 
Posts: 16195
Joined: 17 Nov 2008, 16:50
Location: Rotterdam, Netherlands

Postby honza801 » 08 Feb 2012, 10:00

Actually, the document does not mention booting from *-bootonly CD.

The point is, that this pxe configuration works (sysinstall menu appears after boot)
Code: Select all
label freebsd82
  menu label FreeBSD amd64
  kernel memdisk
  initrd images/FreeBSD-8.2-RELEASE-amd64-bootonly.iso
  append iso raw


and this does not (ending with error above)
Code: Select all
label freebsd90
  menu label FreeBSD amd64
  kernel memdisk
  initrd images/FreeBSD-9.0-RELEASE-amd64-bootonly.iso
  append iso raw


Supposing this procedure was supported in 8.2, I think this a bug in the 9.0 *-bootonly installation media.
honza801
Junior Member
 
Posts: 10
Joined: 18 Jan 2011, 12:02

Postby bunnylover » 10 Feb 2012, 22:16

Have any of you had any success appending "bigraw" instead of "raw"? I was having this exact problem until I changed the option to bigraw. I will say that I'm using mfsBSD, therefore probably a much smaller image than those loading a copy of the distribution CD. Just putting it out there, in case it helps someone.

http://www.syslinux.org/wiki/index.php/MEMDISK#Set_memory_access_method_.28raw.2C_bigraw.2C_int_.2C_safeint.29
bunnylover
Junior Member
 
Posts: 2
Joined: 10 Feb 2012, 17:15

Postby wblock@ » 11 Feb 2012, 00:57

Just tried it in VirtualBox. It gets to "Building the boot loader arguments", shows the spinner slash, and then stops with the CPU at 100%.
User avatar
wblock@
Old Fart
 
Posts: 10212
Joined: 07 Sep 2009, 23:23
Location: Milky Way galaxy

Postby lory » 13 Feb 2012, 07:44

bunnylover wrote:Have any of you had any success appending "bigraw" instead of "raw"? I was having this exact problem until I changed the option to bigraw. I will say that I'm using mfsBSD, therefore probably a much smaller image than those loading a copy of the distribution CD. Just putting it out there, in case it helps someone.

http://www.syslinux.org/wiki/index.php/MEMDISK#Set_memory_access_method_.28raw.2C_bigraw.2C_int_.2C_safeint.29


It tries to [FILE]mountroot[/FILE] from CD, maybe '[FILE]nfsroot[/FILE]' doesn't read.
lory
Junior Member
 
Posts: 3
Joined: 23 Jan 2012, 09:12

Postby valuequest » 13 Feb 2012, 21:28

bunnylover wrote:Have any of you had any success appending "bigraw" instead of "raw"?


In my case passing the 'bigraw' option instead of the 'raw' option to memdisk does not seem make any difference... with both options I get the same stop that rhlampe posted above.

Is there perhaps some option that needs be entered at the loader command line?
valuequest
Junior Member
 
Posts: 21
Joined: 21 May 2010, 20:30
Location: United States : southeastern Virginia

Postby da1 » 14 Feb 2012, 00:48

da1
Member
 
Posts: 738
Joined: 02 Sep 2009, 09:35
Location: Berlin,DE

Postby lory » 14 Feb 2012, 08:25



Yes, but if you want to have 8.2 i386 and amd64 and 9.0 i386 and amd64 PXE boot for install.

You can only have one option root-path in DHCP server. Or every time you must change config and restart service.
lory
Junior Member
 
Posts: 3
Joined: 23 Jan 2012, 09:12

Postby honza801 » 14 Feb 2012, 15:43

lory wrote:Yes, but if you want to have 8.2 i386 and amd64 and 9.0 i386 and amd64 PXE boot for install.

You can only have one option root-path in DHCP server. Or every time you must change config and restart service.


You can simply configure several different groups for the hosts in DHCP config.
honza801
Junior Member
 
Posts: 10
Joined: 18 Jan 2011, 12:02

Postby honza801 » 14 Feb 2012, 15:46



This tutorial also uses NFS root. I'm trying to install directly from bootonly iso via PXE
honza801
Junior Member
 
Posts: 10
Joined: 18 Jan 2011, 12:02

Postby honza801 » 14 Feb 2012, 15:47

bunnylover wrote:Have any of you had any success appending "bigraw" instead of "raw"? I was having this exact problem until I changed the option to bigraw. I will say that I'm using mfsBSD, therefore probably a much smaller image than those loading a copy of the distribution CD. Just putting it out there, in case it helps someone.

http://www.syslinux.org/wiki/index.php/MEMDISK#Set_memory_access_method_.28raw.2C_bigraw.2C_int_.2C_safeint.29


The "bigraw" option ain't working for me.
honza801
Junior Member
 
Posts: 10
Joined: 18 Jan 2011, 12:02

Postby rhlampe » 15 Feb 2012, 21:05

bunnylover wrote:I will say that I'm using mfsBSD, therefore probably a much smaller image than those loading a copy of the distribution CD. Just putting it out there, in case it helps someone.


Booting the mfsBSD ISO from syslinux works great!
rhlampe
Junior Member
 
Posts: 3
Joined: 22 Feb 2011, 17:13

Same issue for me as well

Postby Schorschi » 27 Feb 2012, 03:06

Even after I added the following to [FILE]loader.conf[/FILE]...

[CMD=" "]echo 'vfs.root.mountfrom="ufs:/dev/md0"' >> /tmp/img/boot/loader.conf[/CMD]

Where [FILE]/tmp/img[/FILE] is path to my [FILE]/dev/md0[/FILE] disk image I later zip and use with PXE Linux based PXE/SysLinux/TFTP.

When the failure to find the [FILE]/dev/md0[/FILE] device as [FILE]vfs.root.mountfrom[/FILE] returns error 19, and drops to the 'OK' prompt. Listing the available boot devices, [FILE]md0[/FILE] does not exist.
Schorschi
Junior Member
 
Posts: 2
Joined: 27 Feb 2012, 02:13

Postby brd@ » 23 Mar 2012, 21:01

I have a blog entry that addresses some of this:

http://blogs.freebsdish.org/brd/2012/03/23/pxe-booting-freebsd-9/

Sorry it does not address the use of syslinux, just the native FreeBSD tools.
User avatar
brd@
Member
 
Posts: 284
Joined: 01 Oct 2007, 22:53
Location: Denver, CO, USA

Postby maitre » 04 May 2012, 22:41

I can't even believe this ISO approach isn't the standard for most of you; once you go PXE, you simply do not go back to NFS!

That said, thanks to all who tried to help out with this issue. It took a lot of refined searching to finally find the solution to this, but this blog post seemed to do it for me:

http://zewaren.net/site/?q=node/82

(The basic idea being, fetch a stock mfsBSD ISO, build a smallish 32MB disk image, and copy the boot/root bits over. Then, importantly, you boot the image via MemDisk using the parameters: "harddisk raw".)
maitre
Junior Member
 
Posts: 1
Joined: 03 May 2012, 16:58

Postby fdge » 13 Jun 2012, 00:02

Having to jump through so many hoops to PXE install is the main reason I am not experimenting more with FreeBSD.
fdge
Junior Member
 
Posts: 3
Joined: 21 Oct 2010, 19:19


Return to Installing & Upgrading

Who is online

Users browsing this forum: pathiaki, Yahoo [Bot] and 0 guests