RCC-VE installation
-
Three lines in /etc/rc.conf.local, IIRC.
-
@gonzopancho:
https://snapshots.pfsense.org/FreeBSD_releng/10.1/amd64/pfSense_RELENG_2_2/livecd_installer/pfSense-memstick-ADI-2.2.2-DEVELOPMENT-amd64-20150401-1519.img.gz
Thanks for this, I've had quite a few requests from people for a copy of "my" image which I have not fulfilled so as to not violate your trademark :P
It's nice to know that these will have even minimal support for those of us too poor/cheap to buy the pfsense branded version!
Keep up the good work :)
I want to thank you for your restraint. Please get ahold of sdavis@ and let him know that I gave you a free year of pfSense Gold.
-
@gonzopancho:
According to ADI's documentation, there are some utilities installed there you may want to keep.
Yeah, I saw those in the RCC-VE platform documentation. Hopefully the team has made or will make those utilities available from within FreeBSD/pfSense as well. Maybe I should have waited to buy a SG-2440…
You're misinformed. That CentOS factory image is ours, not ADI's.
It's not the first time…
-
@gonzopancho:
Another tweak…
Certain intel igb cards, especially multi-port cards, can very easily exhaust mbufs and cause kernel panics, especially on amd64. The following tweak will prevent this from being an issue:
In /boot/loader.conf.local - Add the following (or create the file if it does not exist):
kern.ipc.nmbclusters="1000000"
That will increase the amount of network memory buffers, allowing the driver enough headroom for its optimal operation.the kernel doesn't panic when you exhaust mbufs, it panics when you set this limit too high (and your number is too high), because
the system runs out of memory.For each mbuf cluster there is “mbuf” structure needed. These each consume 256 bytes, and are used to organize mbuf clusters in chains. An mbuf cluster takes another 2048 bytes (or more, for jumbo frames). There’s possibility to store some additional useful 100B data into the mbuf, but it is not always used.
When there are no free mbuf clusters available, FreeBSD enters the zonelimit state and stops answering network requests. You can see it as the
zonelistate in the output of thetopcommand. It doesn't panic, it appears to 'freeze' for network activity.If your box has 1GB of RAM or more, 25K mbuf clusters will be created by default. Occasionally this is not enough. If it is, then perhaps doubling that value, and maybe doubling again, are in order. But 1M mbuf clusters? Are you serious?
You just advised people to consume 1,000,000 mbuf clusters (at 2K each). Let me know if I need to explain how much RAM you needlessly advised people to allocate for no good purpose.
I am well-aware that someone wrote something completely uninformed here: https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards#mbuf_.2F_nmbclusters
so please don't quote it back to me.Thank you for the education. I'll remove that from the configuration.
-
@gonzopancho:
https://snapshots.pfsense.org/FreeBSD_releng/10.1/amd64/pfSense_RELENG_2_2/livecd_installer/pfSense-memstick-ADI-2.2.2-DEVELOPMENT-amd64-20150401-1519.img.gz
So I just downloaded this image and wrote it to a spare USB thumbdrive I had laying around and booted this on my RCC-VE and ran into this:
SeaBIOS (version SageBIOS-20150314_140038-localhost.localdomain) Found mainboard Intel Mohon Peak Relocating init from 0x000ef1b0 to 0x7fb995f0 (size 26960) Found CBFS header at 0xfffffbe0 CPU Mhz=1750 Found 18 PCI devices (max PCI bus is 04) Copying MPTABLE from 0x7fbe3e00/7fbe3e10 to 0x000f5970 with length 184 Copying ACPI RSDP from 0x7fbe4e00 to 0x000f5940 Copying SMBIOS entry point from 0x7fbf0400 to 0x000f5920 Using pmtimer, ioport 0x408 Scan for VGA option rom EHCI init on dev 00:16.0 (regs=0xdfff5420) Found 2 serial ports ebda moved from 9f000 to 9e800 AHCI controller at 17.0, iobase dfff4000, irq 15 AHCI controller at 18.0, iobase dfff4800, irq 10 Searching bootorder for: /pci@i0cf8/usb@16/hub@1/storage@1/*@0/*@0,0 Searching bootorder for: /pci@i0cf8/usb@16/hub@1/usb-*@1 USB MSC vendor='' product='USB Flash Memory' rev='1.00' type=0 removable=1 USB MSC blksize=512 sectors=7823296 Searching bootorder for: /pci@i0cf8/usb@16/hub@1/storage@4/*@0/*@0,0 Searching bootorder for: /pci@i0cf8/usb@16/hub@1/usb-*@4 USB MSC vendor='Generic' product='Ultra HS-COMBO' rev='1.98' type=0 removable=1 USB MSC blksize=512 sectors=7471104 Initialized USB HUB (2 ports used) All threads complete. Scan for option roms Running option rom at c000:0003 pmm call arg1=1 pmm call arg1=0 pmm call arg1=1 pmm call arg1=0 Running option rom at c100:0003 pmm call arg1=1 pmm call arg1=1 Running option rom at c200:0003 pmm call arg1=1 pmm call arg1=1 Running option rom at c300:0003 pmm call arg1=1 pmm call arg1=1 Searching bootorder for: /pci@i0cf8/*@14 Searching bootorder for: /pci@i0cf8/*@14,1 Searching bootorder for: /pci@i0cf8/*@14,2 Searching bootorder for: /pci@i0cf8/*@14,3 Press F12 for boot menu. Searching bootorder for: HALT drive 0x000f58b0: PCHS=0/0/0 translation=lba LCHS=970/128/63 s=7823296 drive 0x000f5880: PCHS=0/0/0 translation=lba LCHS=926/128/63 s=7471104 Space available for UMB: c4000-f0000, f0000-f5880 Returned 253952 bytes of ZoneHigh e820 map has 8 items: 0: 0000000000000000 - 000000000009e800 = 1 RAM 1: 000000000009e800 - 00000000000a0000 = 2 RESERVED 2: 00000000000f0000 - 0000000000100000 = 2 RESERVED 3: 0000000000100000 - 000000007fbde000 = 1 RAM 4: 000000007fbde000 - 000000007fe00000 = 2 RESERVED 5: 00000000e0000000 - 00000000f0000000 = 2 RESERVED 6: 00000000fee00000 - 00000000fee01000 = 2 RESERVED 7: 0000000100000000 - 0000000180000000 = 1 RAM enter handle_19: NULL Booting from Hard Disk... Booting from 0000:7c00 - __ ____ _ __ / _/ ___| ___ _ __ ___ ___ | '_ \| |_\___ \ / _ \ '_ \/ __|/ _ \ | |_) | _|___) | __/ | | \__ \ __/ | .__/|_| |____/ \___|_| |_|___/\___| |_| +------------Welcome to pfSense-----------+ | | ______ | 1\. Boot Multi User [Enter] | / \ | 2\. Boot [s]ingle User | _____/ f \ | 3\. [Esc]ape to loader prompt | / \ / | 4\. Reboot | / p \______/ Sense | | \ / \ | Options: | \_____/ \ | 5\. [K]ernel: kernel (1 of 2) | \ / | 6\. Configure Boot [O]ptions... | \______/ | | | | | | +-----------------------------------------+ Autoboot in 8 seconds. [Space] to pause To get back to the menu, type `menu' and press ENTER or type `boot' and press ENTER to start pfSense. Type '?' for a list of commands, 'help' for more detailed help. OK set kern.cam.boot_delay="10000" OK boot /boot/kernel/kernel text=0x121d198 data=0x881b18+0x357620 syms=[0x8+0x16e450+0x8+0x16b5c6] Booting... KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2014 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 10.1-RELEASE-p8 #0 9387a83(releng/10.1)-dirty: Wed Apr 1 16:08:38 CDT 2015 root@pfs22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10 amd64 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 CPU: Intel(R) Atom(TM) CPU C2358 @ 1.74GHz (1750.04-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x406d8 Family = 0x6 Model = 0x4d Stepping = 8 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=0x43d8e3bf <sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,sse4.2,movbe,popcnt,tscdlt,aesni,rdrand>AMD Features=0x28100800 <syscall,nx,rdtscp,lm>AMD Features2=0x101 <lahf,prefetch>Structured Extended Features=0x2282 <tscadj,smep,erms>VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 6442450944 (6144 MB) avail memory = 4059717632 (3871 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: <core coreboot=""> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 random device not loaded; using insecure entropy ioapic0 <version 2.0=""> irqs 0-23 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, 0xffffffff8060b270, 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, 0xffffffff8060b320, 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, 0xffffffff8060b3d0, 0) error 1 iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/. iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff80632a40, 0) error 1 iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/. iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff80632af0, 0) error 1 iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/. iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff80632ba0, 0) error 1 random: <software, yarrow=""> initialized module_register_init: MOD_LOAD (vesa, 0xffffffff80fbf2c0, 0) error 19 kbd0 at kbdmux0 cryptosoft0: <software crypto=""> on motherboard padlock0: No ACE support. acpi0: <core coreboot=""> on motherboard acpi0: Power Button (fixed) hpet0: <high precision="" event="" timer=""> iomem 0xfed03000-0xfed033ff on acpi0 hpet0: invalid period device_attach: hpet0 attach returned 6 cpu0: <acpi cpu=""> on acpi0 cpu1: <acpi cpu=""> on acpi0 hpet0: <high precision="" event="" timer=""> iomem 0xfed03000-0xfed033ff on acpi0 hpet0: invalid period device_attach: hpet0 attach returned 6 atrtc0: <at realtime="" clock=""> port 0x70-0x77 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 attimer0: <at timer=""> port 0x40-0x43,0x50-0x53 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: <acpi host-pci="" bridge=""> port 0xcf8-0xcff on acpi0 pci0: <acpi pci="" bus=""> on pcib0 pcib1: <acpi pci-pci="" bridge=""> mem 0xdfec0000-0xdfedffff irq 16 at device 1.0 on pci0 pci1: <acpi pci="" bus=""> on pcib1 pcib2: <acpi pci-pci="" bridge=""> mem 0xdfee0000-0xdfefffff irq 19 at device 2.0 on pci0 pci2: <acpi pci="" bus=""> on pcib2 pcib3: <acpi pci-pci="" bridge=""> mem 0xdff00000-0xdff1ffff irq 20 at device 3.0 on pci0 pci3: <acpi pci="" bus=""> on pcib3 pcib4: <acpi pci-pci="" bridge=""> mem 0xdff20000-0xdff3ffff irq 23 at device 4.0 on pci0 pci4: <acpi pci="" bus=""> on pcib4 pci0: <processor> at device 11.0 (no driver attached) pci0: <base peripheral,="" iommu=""> at device 15.0 (no driver attached) igb0: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.4.0=""> port 0x1000-0x101f mem 0xdff60000-0xdff7ffff,0xdffe4000-0xdffe7fff irq 18 at device 20.0 on pci0 igb0: Using MSIX interrupts with 3 vectors igb0: Bound queue 0 to cpu 0 igb0: Bound queue 1 to cpu 1 igb1: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.4.0=""> port 0x1020-0x103f mem 0xdff80000-0xdff9ffff,0xdffe8000-0xdffebfff irq 19 at device 20.1 on pci0 igb1: Using MSIX interrupts with 3 vectors igb1: Bound queue 0 to cpu 0 igb1: Bound queue 1 to cpu 1 igb2: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.4.0=""> port 0x1040-0x105f mem 0xdffa0000-0xdffbffff,0xdffec000-0xdffeffff irq 20 at device 20.2 on pci0 igb2: Using MSIX interrupts with 3 vectors igb2: Bound queue 0 to cpu 0 igb2: Bound queue 1 to cpu 1 igb3: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.4.0=""> port 0x1060-0x107f mem 0xdffc0000-0xdffdffff,0xdfff0000-0xdfff3fff irq 21 at device 20.3 on pci0 igb3: Using MSIX interrupts with 3 vectors igb3: Bound queue 0 to cpu 0 igb3: Bound queue 1 to cpu 1 ehci0: <intel avoton="" usb="" 2.0="" controller=""> mem 0xdfff5400-0xdfff57ff irq 22 at device 22.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 ahci0: <intel avoton="" ahci="" sata="" controller=""> port 0x10c0-0x10c7,0x10e0-0x10e3,0x10c8-0x10cf,0x10e4-0x10e7,0x1080-0x109f mem 0xdfff4000-0xdfff47ff irq 23 at device 23.0 on pci0 ahci0: AHCI v1.30 with 2 3Gbps ports, Port Multiplier not supported ahci1: <intel avoton="" ahci="" sata="" controller=""> port 0x10d0-0x10d7,0x10e8-0x10eb,0x10d8-0x10df,0x10ec-0x10ef,0x10a0-0x10bf mem 0xdfff4800-0xdfff4fff irq 16 at device 24.0 on pci0 ahci1: AHCI v1.30 with 2 6Gbps ports, Port Multiplier not supported isab0: <pci-isa bridge=""> at device 31.0 on pci0 isa0: <isa bus=""> on isab0 ppc0: cannot reserve I/O port range uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 on isa0 uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 uart1: console (115200,n,8,1) est0: <enhanced speedstep="" frequency="" control=""> on cpu0 p4tcc0: <cpu frequency="" thermal="" control=""> on cpu0 est1: <enhanced speedstep="" frequency="" control=""> on cpu1 p4tcc1: <cpu frequency="" thermal="" control=""> on cpu1 Timecounters tick every 1.000 msec IPsec: Initialized Security Association Processing. random: unblocking device. usbus0: 480Mbps High Speed USB v2.0 ugen0.1: <intel> at usbus0 uhub0: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus0 uhub0: 8 ports with 8 removable, self powered ugen0.2: <vendor 0x8087=""> at usbus0 uhub1: <vendor 2="" 9="" 0x8087="" product="" 0x07db,="" class="" 0,="" rev="" 2.00="" 0.02,="" addr=""> on usbus0 uhub1: 4 ports with 4 removable, self powered ugen0.3: <vendor 0x0930=""> at usbus0 umass0: <vendor 0="" 3="" 0x0930="" usb="" flash="" memory,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus0 ugen0.4: <generic> at usbus0 umass1: <generic 0="" 4="" ultra="" fast="" media,="" class="" 0,="" rev="" 2.00="" 1.98,="" addr=""> on usbus0 da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: < USB Flash Memory 1.00> Removable Direct Access SCSI-2 device da0: Serial Number 001372997D4BC031662922E9 da0: 40.000MB/s transfers da0: 3819MB (7823296 512 byte sectors: 255H 63S/T 486C) da0: quirks=0x2 <no_6_byte>da1 at umass-sim1 bus 1 scbus1 target 0 lun 0 da1: <generic ultra="" hs-combo="" 1.98=""> Removable Direct Access SCSI-0 device da1: Serial Number 000000225001 da1: 40.000MB/s transfers da1: 3648MB (7471104 512 byte sectors: 255H 63S/T 465C) da1: quirks=0x2 <no_6_byte>(da0:umass-sim0:0:0:0): got CAM status 0x50 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: < USB Flash Memory 1.00> s/n 001372997D4BC031662922E9 detached SMP: AP CPU #1 Launched! Timecounter "TSC" frequency 1750043127 Hz quality 1000 (da0:Trying to mount root from ufs:/dev/ufs/pfSense [ro]... umass-sim0:0:mountroot: waiting for device /dev/ufs/pfSense ... 0:0): Periph destroyed Mounting from ufs:/dev/ufs/pfSense failed with error 19. Loader variables: vfs.root.mountfrom=ufs:/dev/ufs/pfSense 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: diskid/DISK-000000225001s3 diskid/DISK-000000225001s2 diskid/DISK-000000225001s1 da1s3 da1s2 da1s1 diskid/DISK-000000225001 da1 mountroot> Will try this with a different USB thumbdrive just to make sure I dont have a bum drive(its sorta old), but it does seem like the bootseq destroys the USB device I'm booting off of. Also, in this 2.2.2 image the pfsense boot menu is missing options I'm used to seeing.[/s]</empty></fstype></device></device></fstype></no_6_byte></generic></no_6_byte></generic></generic></vendor></vendor></vendor></vendor></intel></intel></cpu></enhanced></cpu></enhanced></isa></pci-isa></intel></intel></intel></intel(r)></intel(r)></intel(r)></intel(r)></processor></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></at></at></high></acpi></acpi></high></core></software></software,></version></core ></tscadj,smep,erms></lahf,prefetch></syscall,nx,rdtscp,lm></sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,sse4.2,movbe,popcnt,tscdlt,aesni,rdrand></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> -
I used the content of the /boot/loader.conf of https://snapshots.pfsense.org/FreeBSD_releng/10.1/amd64/pfSense_RELENG_2_2/livecd_installer/pfSense-memstick-ADI-2.2.2-DEVELOPMENT-amd64-20150401-1519.img.gz
to change the content on a USB-stick I created with http://files.nl.pfsense.org/mirror/downloads/old/pfSense-memstick-serial-2.1.5-RELEASE-amd64.img.gz
I was able to install the 2.1.5 on its mSata-drive.
The installed system then needs to get patched with the same /boot/loader.conf. I used the pfsense on the USB-stick to do this.
I loaded the config.xml of my production machine and now it's running and replaced the old trash-PC I was using before.
I also tried the 2.2.2 yesterday evening, but it couldn't replace the old machine with that running config.
The old machine stops working when I upgrade it to 2.2.2 as well, so I think there's something wrong with that config.I want to investigate the reasons for this another time and I'm happy I can now throw that old PC in the trash.
I have about 80 LANS and 3 WANs
Pfsense is running a Zabbix-agent and that agent is pinging many devices that are on these LANs (they are all different families living on a peninsula).
The migration took 10 seconds….. ;-) -
How do you edit the file?
I had some trouble getting it to mount read-write in Ubuntu. Apparently the read-write UFS driver for Linux is still a bit unstable so the Ubuntu kernel has the read-only driver.
I downloaded the FreeBSD 10.1-RELEASE virtual machine image (.vmdk) and created a new VirtualBox VM with that image as the hard drive. Boot it up, attach the USB drive, get the device name from dmesg, mount the slice (when I get home tonight I can work out the exact command for you), and edit the file(s) as needed.
Thank you! I used FreeBSD and have managed to add the line to /boot/loader.conf.
However, I'm stuck again.
this time use the live cd instead of the installer and mount the partition you just installed pfsense to (mine was ada0s1a). Make the same changes to the files like you did on the memory stick this time add the comconsole_port line to [pfsensemountpoint]/boot/loader.conf.local so that it should survive upgrades etc, reboot and unplug the memory stick before it resets and you should be booting up into an installed pfsense with working serial console, set your interfaces like normal and enjoy!
If I choose Live CD, the setup continues and finally I can access it through the browser. But how do "stop" that so I mount my device? And add the line again?
-
So I just downloaded this image and wrote it to a spare USB thumbdrive I had laying around and booted this on my RCC-VE and ran into this:
(da0:umass-sim0:0:0:0): got CAM status 0x50 (da0:umass-sim0:0:0:0): fatal error, failed to attach to deviceWill try this with a different USB thumbdrive just to make sure I dont have a bum drive(its sorta old), but it does seem like the bootseq destroys the USB device I'm booting off of.
Also, in this 2.2.2 image the pfsense boot menu is missing options I'm used to seeing.
Based on this error message, I'd suggest the same: try a different USB stick.
What options you are not seeing?
-
this time use the live cd instead of the installer and mount the partition you just installed pfsense to (mine was ada0s1a). Make the same changes to the files like you did on the memory stick this time add the comconsole_port line to [pfsensemountpoint]/boot/loader.conf.local so that it should survive upgrades etc, reboot and unplug the memory stick before it resets and you should be booting up into an installed pfsense with working serial console, set your interfaces like normal and enjoy!
I think I've managed to move forward a tiny bit on the LiveCD part, however. When trying to mount i get a Operation not permitted error.
[2.2.1-RELEASE][root@pfSense.localdomain]/: /sbin/mount /dev/ada0s1a /mnt mount: /dev/ada0s1a: R/W mount of / denied. Filesystem is not clean - run fsck.: Operation not permitted -
I think I've managed to move forward a tiny bit on the LiveCD part, however. When trying to mount i get a Operation not permitted error.
[2.2.1-RELEASE][root@pfSense.localdomain]/: /sbin/mount /dev/ada0s1a /mnt mount: /dev/ada0s1a: R/W mount of / denied. Filesystem is not clean - run fsck.: Operation not permittedAre you installing to a SATA device or to the internal 4GB flash memory (eMMC)?
-
I think I've managed to move forward a tiny bit on the LiveCD part, however. When trying to mount i get a Operation not permitted error.
[2.2.1-RELEASE][root@pfSense.localdomain]/: /sbin/mount /dev/ada0s1a /mnt mount: /dev/ada0s1a: R/W mount of / denied. Filesystem is not clean - run fsck.: Operation not permittedAre you installing to a SATA device or to the internal 4GB flash memory (eMMC)?
A sata device.
I finally got it to work by running.
fsck -tufs -y /dev/ada0s1a
/sbin/mount /dev/ada0s1a /mnt -
So I just downloaded this image and wrote it to a spare USB thumbdrive I had laying around and booted this on my RCC-VE and ran into this:
(da0:umass-sim0:0:0:0): got CAM status 0x50 (da0:umass-sim0:0:0:0): fatal error, failed to attach to deviceWill try this with a different USB thumbdrive just to make sure I dont have a bum drive(its sorta old), but it does seem like the bootseq destroys the USB device I'm booting off of.
Also, in this 2.2.2 image the pfsense boot menu is missing options I'm used to seeing.
Based on this error message, I'd suggest the same: try a different USB stick.
What options you are not seeing?
As it turns out, it was a bum usb stick. A new one yielded positive results. As for what options I was missing in the boot menu, it looks like in 2.2.2 theyve removed the "Boot from USB media" option probably because I think it looks like theyve just put in the assumptions for that into the default options now. You can see the 2.2.2-DEV menu in my original post. IIt's not a big deal.
One other thing I did run into is, when doing the custom install from a usb memstick image after the install the fstab will be wrong and you'll have to swap da1 with da0
-
So I just downloaded this image and wrote it to a spare USB thumbdrive I had laying around and booted this on my RCC-VE and ran into this:
(da0:umass-sim0:0:0:0): got CAM status 0x50 (da0:umass-sim0:0:0:0): fatal error, failed to attach to deviceWill try this with a different USB thumbdrive just to make sure I dont have a bum drive(its sorta old), but it does seem like the bootseq destroys the USB device I'm booting off of.
Also, in this 2.2.2 image the pfsense boot menu is missing options I'm used to seeing.
Based on this error message, I'd suggest the same: try a different USB stick.
What options you are not seeing?
As it turns out, it was a bum usb stick. A new one yielded positive results. As for what options I was missing in the boot menu, it looks like in 2.2.2 theyve removed the "Boot from USB media" option probably because I think it looks like theyve just put in the assumptions for that into the default options now. You can see the 2.2.2-DEV menu in my original post. IIt's not a big deal.
One other thing I did run into is, when doing the custom install from a usb memstick image after the install the fstab will be wrong and you'll have to swap da1 with da0
Did you report this to someone who can change it?
-
@gonzopancho:
As it turns out, it was a bum usb stick. A new one yielded positive results. As for what options I was missing in the boot menu, it looks like in 2.2.2 theyve removed the "Boot from USB media" option probably because I think it looks like theyve just put in the assumptions for that into the default options now. You can see the 2.2.2-DEV menu in my original post. IIt's not a big deal.
One other thing I did run into is, when doing the custom install from a usb memstick image after the install the fstab will be wrong and you'll have to swap da1 with da0
Did you report this to someone who can change it?
Gonzo I did mention this thread to pfsense help, but i'll send a more specific message about it since current docs assume old pfsense boot menu options.
Also, one semi-related question. Is there a way to know what parts of the XML config import will overwrite the boot options? In attempting to migrate from my old ALIX2D13 system to the RCC-VE I attempted to be clever(read:lazy) and selectively import parts of my old config into the new 2.2.2-DEV system. First time I did this I just dumped the whole file in, reassigned the interfaces, rebooted….and no working pfsense. So I wiped, reinstalled, and then did a selective import and watched the reboot via the console and after the initial boot the console output stops like the serial port mapping had been reverted.
So now I'm on my 3rd wipe, not bothering to import anything and recreating all the rules by hand. Is there a reason why the boot.conf is getting overwritten even on a selective config import or did I forget something about how the config import works here?
-
I am currently running the 2.1.5 in production after doing a live install and replacing the config of the previous machine.
The only thing I did was changing /boot/loader.conf on the USB-stick I used to install it on SATA and then changing that same file again on the SATA.I'm not having the problems the others are having…
Is there really more to it or shouldn't I worry now everything is working?
-
Hi,
I am currently running the 2.1.5 in production after doing a live install and replacing
the config of the previous machine.On what did you install? Soldered on board nand, SSD, HDD, or mSATA?
Did you wipe out the pre installed Linux OS from the nand storage?The only thing I did was changing /boot/loader.conf on the USB-stick I
used to install it on SATA and then changing that same file again on the SATA.What kind of USB stick did you using?
I'm not having the problems the others are having…
Be happy about.
Is there really more to it or shouldn't I worry now everything is working?
- upgrading to 2.2.1 perhaps?
- activating TRIM support for mSATA or SATA SSD if in usage?
- setting up another ether dump buffer for the LAN Ports if this is needed?
-
Activation of TRIM support is semiautomatic now, IIRC.
-
It looks like the QSGs are now available for the Netgate 2440 and 4860 and pfSense 2440 and 2860:
-
To the NetGate pfSense team I believe I found a small typo.
On the SG-2440 QuickStart guide
Under "Initial Configuration" it reads…
Once the system is booted, the attached computer should receive a 192.1.68.1 IP address from the DHCP server that is active on the pfSense appliance.I believe that should be a 192.168.1.x address.
Thanks for all you guys/gals do!
-
Want to know how many times I marked this in red?
