Hard Drive Install on X-6000

wallabybob

Concerning the attempt to install the full pfSense:

4. Follow installation and complete the build process. If I change the heads or cylinders it will not accept the change. It forces you to expand the to the full size before it will continue.

Is there a word missing between expand the and to the full size?

@fastcon68:

So I am back to the begining a reboot does not help. The mount command shows up. I have tried everything possible.

Take heart. You almost certainly haven't yet tried everything possible. :)

Did you attempt the reboot with the hard drive connected by USB or connected to an IDE socket?

I presume by "mount command shows up" you mean the warning that the startup can't find the root filesystem.
From which disk is the startup trying to mount the root file system? Often its possible to get the startup to proceed by telling it the correct filesystem. (Note that your fstab you displayed earlier is from a nanobsd install rather than a full install. Here's the fstab on my 'full install' 2.0-RC3 pfsense which has been upgraded multiple times from a :```

more /etc/fstab

Device Mountpoint FStype Options Dump Pass#

/dev/ad0s1a / ufs rw 1 1
/dev/ad0s1b none swap sw 0 0

Are you messing around with fstab after doing the full install? If so, why?

Have you removed the Compact Flash?

fastcon68

WallyBob,
I have tried the full version & embedded version on the two different functioning hard drives. I have tried the one in the x-500 (20 GB) and the x-6000 (40 GB). Both yield the same result. They will not mount the disk properly. This is with the the flash drive removed.

This is the error I am getting.

ROOT MOUNT ERROR:
If you have invalid mount options, reboot, and first try the following from
the loader prompt:

set vfs.root.mountfrom.options=rw

and then remove invalid mount options from /etc/fstab.

Loader variables:
vfs.root.mountfrom=ufs:/dev/da0s1a
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>

To clarify when I loaded the both the drives, I had to give the disk size, in sectors. I make the default size smaller that using the full size of the disk. The next screen that shows up forces you to use the maximum size of the disk. From there I created the mount points and installed the rest of the pfSense.

Disconnected the hard drive from the usb adapter and then connected it to powered off x-6000. I removed the flash drive and started the system up. I gave the above error message, that I am getting on the x-500 & x-6000. I pop my flash drive back in and it works fine as well as now offering me the choice of booting slice 1 or slice 2 and the hard drive.

I am really trying to read the forums and look at my book(ultimate Guide to Pfsense). I am no unix/linuix guru. I know I could use a different product but I have been using it so long I have no desire to change products. If somebody has a disk image of a working x-6000 on hard drive and they are will to make a disk image I will ship a drive to you or even download it via some method.

I even do a crossloop session with somebody if they are willing to give me a hand. I getting to point of great frustration. On top of that I found a capacitor that is slightly raised in my x-6000. Look's like I will be doing repair surgery once I order a capacitor. I trying to get on a HD so that I can doing additional monitoring and get people out. My daughters computer got hacked. I caught it in time before any damage was done but they trashed her machine.

I spent the better part of 30 + hours reading building and rebuilding the disks and my firewall just to try to get the HD working. I trying to get as data out to the forum as possible.

Many Thanks to everybody.
RC

This is the full demesg from the x-6000:
Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x899e7c data=0x3c9bf4+0x9b6a0 syms=[0x4+0x93bf0+0x4+0xca936]
|

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ ³
³ ³
³ ³
³ Welcome to pfSense! ³
³ ³ ______
³ ³ /
³ 1. Boot pfSense [default] ³ / f
³ 2. Boot pfSense with ACPI enabled ³ / \ /
³ 3. Boot pfSense using USB device ³ / p _/ Sense
³ 4. Boot pfSense in Safe Mode ³ \ /
³ 5. Boot pfSense in single user mode ³ _____/
³ 6. Boot pfSense with verbose logging ³ \ /
³ 7. Escape to loader prompt ³ ______/
³ 8. Reboot ³
³ ³
³ ³
³ ³
³ Select option, [Enter] for default ³
³ or [Space] to pause timer 0 ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

Copyright 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.1-RELEASE-p4 #0: Tue Jun 21 16:27:49 EDT 2011
sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386 i386
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2800.11-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0xf29 Family = f Model = 2 Stepping = 9
Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0x4400 <cnxt-id,xtpr>real memory = 536870912 (512 MB)
avail memory = 506286080 (482 MB)
ACPI Error: A valid RSDP was not found (20100331/tbxfroot-309)
MPTable: <oem00000 prod00000000="">ioapic0: Assuming intbase of 0
ioapic1: Assuming intbase of 24
ioapic0 <version 2.0="">irqs 0-23 on motherboard
ioapic1 <version 2.0="">irqs 24-47 on motherboard
wlan: mac acl policy registered
ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_bss_fw, 0xc0708970, 0) error 1
ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc0708a10, 0) error 1
wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (wpi_fw, 0xc087b830, 0) error 1
ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc0708ab0, 0) error 1
ACPI Error: A valid RSDP was not found (20100331/tbxfroot-309)
ACPI: Table initialisation failed: AE_NOT_FOUND
ACPI: Try disabling either ACPI or apic support.
cryptosoft0: <software crypto="">on motherboard
padlock0: No ACE support.
pcib0: <mptable host-pci="" bridge="">pcibus 0 on motherboard
pci0: <pci bus="">on pcib0
pcib1: <pci-pci bridge="">at device 1.0 on pci0
pci1: <pci bus="">on pcib1
pcib2: <mptable pci-pci="" bridge="">at device 3.0 on pci0
pci2: <pci bus="">on pcib2
em0: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3="">port 0xb000-0xb01f mem 0xfd800000-0xfd81ffff,0xfd820000-0xfd83ffff irq 18 at device 1.0 on pci2
em0: [FILTER]
pcib3: <mptable pci-pci="" bridge="">at device 28.0 on pci0
pci3: <pci bus="">on pcib3
pci3: <encrypt decrypt,="" network="" computer="" crypto="">at device 13.0 (no driver attached)
em1: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3="">port 0xc000-0xc03f mem 0xfd9e0000-0xfd9fffff,0xfd900000-0xfd93ffff irq 26 at device 14.0 on pci3
em1: [FILTER]
em2: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3="">port 0xc100-0xc13f mem 0xfd9c0000-0xfd9dffff,0xfd940000-0xfd97ffff irq 27 at device 14.1 on pci3
em2: [FILTER]
uhci0: <uhci (generic)="" usb="" controller="">port 0xe100-0xe11f irq 16 at device 29.0 on pci0
uhci0: [ITHREAD]
usbus0: <uhci (generic)="" usb="" controller="">on uhci0
uhci1: <uhci (generic)="" usb="" controller="">port 0xe000-0xe01f irq 19 at device 29.1 on pci0
uhci1: [ITHREAD]
usbus1: <uhci (generic)="" usb="" controller="">on uhci1
pci0: <base peripheral=""> at device 29.4 (no driver attached)
ehci0: <intel 6300esb="" usb="" 2.0="" controller="">mem 0xfdc00000-0xfdc003ff irq 23 at device 29.7 on pci0
ehci0: [ITHREAD]
usbus2: EHCI version 1.0
usbus2: <intel 6300esb="" usb="" 2.0="" controller="">on ehci0
pcib4: <mptable pci-pci="" bridge="">at device 30.0 on pci0
pci4: <pci bus="">on pcib4
fxp0: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xd000-0xd03f mem 0xfdbe0000-0xfdbe0fff,0xfdb00000-0xfdb1ffff irq 19 at device 9.0 on pci4
miibus0: <mii bus="">on fxp0
inphy0: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: [ITHREAD]
fxp1: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xd100-0xd13f mem 0xfdbe4000-0xfdbe4fff,0xfdb20000-0xfdb3ffff irq 18 at device 10.0 on pci4
miibus1: <mii bus="">on fxp1
inphy1: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus1
inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: [ITHREAD]
fxp2: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xd200-0xd23f mem 0xfdbe2000-0xfdbe2fff,0xfdb40000-0xfdb5ffff irq 17 at device 11.0 on pci4
miibus2: <mii bus="">on fxp2
inphy2: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus2
inphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp2: [ITHREAD]
fxp3: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xd300-0xd33f mem 0xfdbe6000-0xfdbe6fff,0xfdb60000-0xfdb7ffff irq 16 at device 12.0 on pci4
miibus3: <mii bus="">on fxp3
inphy3: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus3
inphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp3: [ITHREAD]
fxp4: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xd400-0xd43f mem 0xfdbe1000-0xfdbe1fff,0xfdb80000-0xfdb9ffff irq 19 at device 13.0 on pci4
miibus4: <mii bus="">on fxp4
inphy4: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus4
inphy4: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp4: [ITHREAD]
fxp5: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xd500-0xd53f mem 0xfdbe3000-0xfdbe3fff,0xfdba0000-0xfdbbffff irq 18 at device 14.0 on pci4
miibus5: <mii bus="">on fxp5
inphy5: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus5
inphy5: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp5: [ITHREAD]
fxp6: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xd600-0xd63f mem 0xfdbe5000-0xfdbe5fff,0xfdbc0000-0xfdbdffff irq 17 at device 15.0 on pci4
miibus6: <mii bus="">on fxp6
inphy6: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus6
inphy6: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp6: [ITHREAD]
isab0: <pci-isa bridge="">at device 31.0 on pci0
isa0: <isa bus="">on isab0
atapci0: <intel 6300esb="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.1 on pci0
ata0: <ata 0="" channel="">on atapci0
ata0: [ITHREAD]
ata1: <ata 1="" channel="">on atapci0
ata1: [ITHREAD]
pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached)
cpu0 on motherboard
atrtc0: <at realtime="" clock="">at port 0x70-0x71 irq 8 pnpid PNP0b00 on isa0
unknown: <pnp0c01>can't assign resources (memory)
ppc0: <ecp parallel="" printer="" port="">at port 0x378-0x37f,0x778-0x77f irq 7 drq 3 pnpid PNP0401 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppc0: [ITHREAD]
ppbus0: <parallel port="" bus="">on ppc0
ppi0: <parallel i="" o="">on ppbus0
uart0: <non-standard ns8250="" class="" uart="" with="" fifos="">at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
uart0: [FILTER]
uart0: console (9600,n,8,1)
uart1: <non-standard ns8250="" class="" uart="" with="" fifos="">at port 0x2f8-0x2ff irq 3 on isa0
uart1: [FILTER]
unknown: <pnp0c01>can't assign resources (memory)
Timecounter "TSC" frequency 2800111936 Hz quality 800
Timecounters tick every 10.000 msec
IPsec: Initialized Security Association Processing.
fxp0: link state changed to DOWN
fxp1: link state changed to DOWN
fxp2: link state changed to DOWN
fxp3: link state changed to DOWN
fxp4: link state changed to DOWN
fxp5: link state changed to DOWN
fxp6: link state changed to DOWN
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
ugen0.1: <intel>at usbus0
uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
ugen1.1: <intel>at usbus1
uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
usbus2: 480Mbps High Speed USB v2.0
ad2: 19077MB <toshiba mk2016gap="" u0.30="" a="">at ata1-master UDMA66
ugen2.1: <intel>at usbus2
uhub2: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus2
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
GEOM: ad2s1: geometry does not match label (255h,63s != 16h,63s).
Root mount waiting for: usbus2
Root mount waiting for: usbus2
uhub2: 4 ports with 4 removable, self powered
Trying to mount root from ufs:/dev/da0s1a
ROOT MOUNT ERROR:
If you have invalid mount options, reboot, and first try the following from
the loader prompt:

set vfs.root.mountfrom.options=rw

and then remove invalid mount options from /etc/fstab.

Loader variables:
vfs.root.mountfrom=ufs:/dev/da0s1a
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></empty></fstype></device></device></fstype></intel></intel></toshiba></intel></intel></intel></intel></pnp0c01></non-standard></non-standard></parallel></parallel></ecp></pnp0c01></at></serial></ata></ata></intel></isa></pci-isa></i82555></mii></intel></i82555></mii></intel></i82555></mii></intel></i82555></mii></intel></i82555></mii></intel></i82555></mii></intel></i82555></mii></intel></pci></mptable></intel></intel></uhci></uhci></uhci></uhci></intel(r)></intel(r)></encrypt></pci></mptable></intel(r)></pci></mptable></pci></pci-pci></pci></mptable></software></version></version></oem00000></cnxt-id,xtpr></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe></empty></fstype></device></device></fstype>

fastcon68

Just for more information is is the fdisk command with the Flash Card and HD installed:

FreeBSD/i386 (fw1.cartersweb.net) (console)

*** Welcome to pfSense 2.0-RC3-nanobsd (i386) on fw1 ***

WAN (wan) -> fxp0 -> 65.40.106.250
LAN_EM_LAGG (lan) -> lagg0 -> 192.168.14.1
OPT1 (opt1) -> em0 -> 192.168.15.1
OPT2 (opt2) -> fxp1 -> NONE
OPT3 (opt3) -> fxp2 -> NONE
OPT4 (opt4) -> fxp3 -> NONE
OPT5 (opt5) -> fxp4 -> NONE
OPT6 (opt6) -> fxp5 -> NONE
OPT7 (opt7) -> fxp6 -> NONE
FXP_BR_100 (opt8) -> bridge0 -> 192.168.16.1

Logout (SSH only) 8) Shell
Assign Interfaces 9) pfTop
Set interface(s) IP address 10) Filter Logs
Reset webConfigurator password 11) Restart webConfigurator
Reset to factory defaults 12) pfSense Developer Shell
Reboot system 13) Upgrade from console
Halt system 14) Disable Secure Shell (sshd)
Ping host

Enter an option: 8

[2.0-RC3][root@fw1.cartersweb.net]/root(1): ?
?: No match.
[2.0-RC3][root@fw1.cartersweb.net]/root(2): disk
disk: Command not found.
[2.0-RC3][root@fw1.cartersweb.net]/root(3): fdisk
******* Working on device /dev/ufs/pfsense0 *******
parameters extracted from in-core disklabel are:
cylinders=1886 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=1886 heads=16 sectors/track=63 (1008 blks/cyl)

fdisk: invalid fdisk partition table found
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 1901025 (928 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 861/ head 15/ sector 63
The data for partition 2 is:
<unused>The data for partition 3 is:
<unused>The data for partition 4 is:
<unused>[2.0-RC3][root@fw1.cartersweb.net]/root(4):

I am guessing that there is a problem with the way that FreeBSD is handling the initlization of the drive prior to the actual formatting and partitioning.
RC</unused></unused></unused>

wallabybob

@fastcon68:

I am guessing that there is a problem with the way that FreeBSD is handling the initlization of the drive prior to the actual formatting and partitioning.

I'd suggest the the problem is that the disk is changing name between the time you install the software and the time you boot from the disk. The name change is because you change the point of connection of the drive (usb to ide).

Your dmesg output shows:```
Trying to mount root from ufs:/dev/da0s1a

/dev/da0s1a is a USB connected drive (or a SCSI drive).

But your boot drive is ad2 (a drive connected through an IDE controller) hence the startup should be showing```
Trying to mount root from ufs:/dev/ad2s1a

When you see the prompt```
mountroot>


> usf:/dev/ad2s1a

and the boot should proceed. Then you will probably have to login and edit /etc/fstab to change _da0_ to _ad2_ on two lines (one for the root filesystem and one for the swap space).

Reboot and verify the system comes up without manual intervention.

fastcon68

WalleyBob,
I have learned alot from this. I still got a ways to go with linux. So far it is working with the x-500. I make the big change tonight with the x-6000. That is my primary firewall. I glad that it was simple. I guess when you only work with ms products on a day end and out basis translation between O/S's gets difficult.

Many Many thanks.

From my experience this write on how to add a hard drive might be good to add in for manual for watchguard one of the users is writing.

Again thank you.
Ron Carter

wallabybob

Glad you got it working.

@fastcon68:

I still got a ways to go with linux.

To help avoid future unpleasant surprises: pfSense is built on the FreeBSD operating system, which is similar to Linux in many area (for example, it is possible to run quite a number of Linux programs on FreeBSD) but is quite different in other areas (device names, disk partitioning and more)

fastcon68

wallabybob,
I been on vacation but still tinkering. As far as the HD installation it has been a total bust. I planning a second attempt next week. What I found out so far is that you have to have a flash card in the x-6000. It modifies the boot files and adds the HD as disk 5 in the boot order.

So I trashed to HD in the process. I have to format and remove all partitions and clean them up before I can do anything else.

My last attempt end a complete disaster. I learned a few tricks and I think I be able to complete my installation. I keeping notes and should be able to post my results.
RC

fastcon68

wallabybob,
I have finally gotten around to trying to re-install a hard drive in my x-6000. When PFSense boots it comes up with 1 - PFSENSE, 2 - PFSENSE, 5 - HD

I select HD and it does not do anything except site there like a lump on a log. I waited a full five minutes. Do you have any Ideas what could be causeing this issue. My we need to get a few active packages running. My 13 year old got into some contect she she should not have by accident. I need to install a few packages.

ANy help would be benefitical.
Ron Carter

fastcon68

Here is what I just completed, I took 2 ide laptop and loaded it with the base 2 pfsense beta 3. I select disk5 to boot. It just hanges and never even boots.

I am have stuck, any thoughts??

RC

wallabybob

The standard FreeBSD bootmanager lists the bootable drives and waits a few second for a response then boots the drive last booted if no response. From memory, it looks for a "Fn" key (e.g. F1, F2 etc) rather than a numeric key (1, 2 etc). I wonder if you are booting into the FreeBSD bootmanager.

From the dmesg output you posted earlier I presume you are installing the embedded version of pfSense. (I didn't see a VGA device in the system startup output.)

I'm not familiar with the peculiarities of the X-6000. It is not clear me what you have done (what you installed on the CF, what you installed on the hard drive and how you installed them) nor what version you want to run (full or embedded).

What happens if you hit the F1 key as soon as that output appears? F2 key? F5 key?

fastcon68

Going from 2gb to full installation on a 40 hd. I give the function key a try when I get home.
RC

stephenw10

Sorry to see your still having trouble. :(
I only ever tried booting from HD on my X6000 as a test, I never did a full install. However if I remember correctly I had to have a CF card in the slot in order to boot from HD. Some bios bug perhaps.

One other thing you might try is to load a CF card with a memstick install image, boot from that and then install to the HD from there. That would require serial console access from the memstick image though, I don't know if that's present.

Steve

fastcon68

I am working on my watchguard. I have relized that you have to have a flash card in the slot. Now I have 2 partions on the FC. The HD is a full base build. I going from embedded to Full installation.

Is there a way bypass the auto startup and so that I can specify the volume that I want to boot from??
RC

stephenw10

You mean choose to boot from the CF or the HD?

fastcon68

If i select the hard drive it constanly tries to start.

dev/da0s1a is a USB connected drive (or a SCSI drive).

But your boot drive is ad2 (a drive connected through an IDE controller) hence the startup should be showing
Code:

Trying to mount root from ufs:/dev/ad2s1a

When you see the prompt

mountroot>
type
Quote

usf:/dev/ad2s1a and the boot should proceed. Then you will probably have to login and edit /etc/fstab to change da0 to ad2 on two lines
RC

fastcon68

Since I know that the HD was formatted it comes up at da0 but once installed in the x-6000 it shows up as ad2s1a. I trying to mount the disk so that I can modify the /etc/fstab and correct the name of the HD. I can't get the mount command correct.

Here is what I am using:
mount -rw -t ufs -o /ad2s1a /mnt/tmp/

With no luck.
RC

wallabybob

@fastcon68:

I can't get the mount command correct.

Try mount -rw -t ufs -o /dev/ad2s1a /mnt/tmp/ and it it doesn't work report back with the mount command the system response.

fastcon68

Here you go:
I had to run a disk check it just finished of the hard drive.
results: 1
[2.0-RC3][root@fw1.cartersweb.int]/(35): mount -rw -t ufs -o /dev/ad2s1a/mnt/tm
[2.0-RC3][root@fw1.cartersweb.int]/(35): /tmp/md1 on /var ( ufs, local )
[2.0-RC3][root@fw1.cartersweb.int]/(35): mount -rw -t ufs -o /dev/ad2s1a /mnt/tmp/
usage: mount [-adflpruvw] [-F fstab] [-o options] [-t ufs | external_type]
mount [-dfpruvw] special | node
mount [-dfpruvw] [-o options] [-t ufs | external_type] special node
[2.0-RC3][root@fw1.cartersweb.int]/(36):

results: 2
[2.0-RC3][root@fw1.cartersweb.int]/root(26): cd /
[2.0-RC3][root@fw1.cartersweb.int]/(27): mount -rw -t ufs -o /dev/ad2s1a/mnt/tmp
/dev/ufs/pfsense0 on / (ufs, local, noatime, synchronous)
/dev/md0 on /tmp (ufs, local)
/dev/md1 on /var (ufs, local)
/dev/ufs/cf on /cf (ufs, local, noatime, synchronous)
[2.0-RC3][root@fw1.cartersweb.int]/(28):

Mount results
[2.0-RC3][root@fw1.cartersweb.int]/(34): mount
/dev/ufs/pfsense0 on / (ufs, local, noatime, synchronous)
devfs on /dev (devfs, local)
/dev/md0 on /tmp (ufs, local)
/dev/md1 on /var (ufs, local)
/dev/ufs/cf on /cf (ufs, local, noatime, synchronous)
devfs on /var/dhcpd/dev (devfs, local)
[2.0-RC3][root@fw1.cartersweb.int]/(35):

Any thoughts on a boot option that I can do that? I really like to get the disk mounted so I could fix it.
RC

fastcon68

I think this took care of it. I was able to modify the fstab in the etc folder. Once I get a change to reboot, I need to set eveything back up.

results:
[2.0-RC3][root@fw1.cartersweb.int]/(44): mount -w -t ufs /dev/ad2s1a /tmp/mnt
[2.0-RC3][root@fw1.cartersweb.int]/(45): mount
/dev/ufs/pfsense0 on / (ufs, local, noatime, synchronous)
devfs on /dev (devfs, local)
/dev/md0 on /tmp (ufs, local)
/dev/md1 on /var (ufs, local)
/dev/ufs/cf on /cf (ufs, local, noatime, synchronous)
devfs on /var/dhcpd/dev (devfs, local)
/dev/ad2s1a on /tmp/mnt (ufs, local)
[2.0-RC3][root@fw1.cartersweb.int]/(46): cd tmp
[2.0-RC3][root@fw1.cartersweb.int]/tmp(47): cd mnt
[2.0-RC3][root@fw1.cartersweb.int]/tmp/mnt(48): ls
.rnd boot dev lib root var
.snap cf etc libexec sbin
COPYRIGHT conf home lost+found tmp
bin conf.default kernels mnt usr
[2.0-RC3][root@fw1.cartersweb.int]/tmp/mnt(49):

I know this is a little off topic but can anyone recommed a good doc to set up ip 6. I really want to try the connectivity. I got a x-500 I am going to setup for my brother. I like to run ip6 for the vpn/

stephenw10

In order to run IPv6 you need to be following the mainline development branch now that the new IPv6 code has been merged there. See:
http://forum.pfsense.org/index.php/topic,38896.0.html
I'm not running IPv6 so I can't really help you. Clearly it's the future though and sooner or later we'll all be using it.
Just when I though I had a grip on IPv4! ::)

Steve