New Netgate 2440 not detecting New mSATA

derekdw

I just purchased a Netgate 2440 and installed a crucial 128GB mSATA SSD

At first I installed it into the wrong slot (oops) and when I put it into the correct slot had to reinstall pfsense.

After putting it into the correct slot and reinstalling pfsense it still does not seem to be recognizing the drive.

I logged the boot process and didn't see any mention of it during boot.

Is there something I am doing wrong?

Here is the output from the boot process.. Any help would be greatly appreciated

Thanks!

Derek

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.07.02 20:53:16 =~=~=~=~=~=~=~=~=~=~=~=
5

pfSense will reboot. This may take a few minutes, depending on your hardware.

Do you want to proceed [y|n]? y

pfSense is rebooting now.

*** FINAL System shutdown message from root@pfsense.****.*** ***   

System going down IMMEDIATELY                                                  

pfSense is now shutting down ...

Jul  2 20:53:34 lighttpd[17059]: (server.c.1558) server stopped by UID = 0 PID = 1 
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...1 0 0 done
All buffers synced.
Uptime: 1m33s
[1;256r[256;256H[6n
Google, Inc.
Serial Graphics Adapter 01/27/15
SGABIOS $Id: sgabios.S 8 2010-04-22 00:03:40Z nlaredo $ (wenwang@localhost.localdomain) Tue Jan 27 18:10:24 UTC 2015
Term: 178x24
O4 0
[2JSeaBIOS (version SageBIOS-20150506_164733-localhost.localdomain)

iPXE (http://ipxe.org) 00:14.0 C100 PCI2.10 PnP PMM+7FB83270+7FAE3270 C100
Press Ctrl-B to configure iPXE (PCI 00:14.0)...                                                                               

iPXE (http://ipxe.org) 00:14.1 C200 PCI2.10 PnP PMM 7FB83270 7FAE3270 C200

iPXE (http://ipxe.org) 00:14.2 C300 PCI2.10 PnP PMM 7FB83270 7FAE3270 C300

iPXE (http://ipxe.org) 00:14.3 C400 PCI2.10 PnP PMM 7FB83270 7FAE3270 C400

Press F12 for boot menu.

F1  pfSense

F6 PXE
Boot:  F1 
-\|/-\|/-\|\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\[H[J[7;46H                             [8;46H                            [9;46H                            [10;46H                ______         [11;46H               /      \        [12;46H         _____/    f   \       [13;46H        /     \        /       [14;46H       /   p   \______/  Sense [15;46H       \       /      \        [16;46H        \_____/        \       [17;46H              \        /       [18;46H               \______/        [19;46H                            [20;46H                            [25;0H[1;2H         __ ____                          [2;2H  _ __  / _/ ___|  ___ _ __  ___  ___     [3;2H | '_ \| |_\___ \ / _ \ '_ \/ __|/ _ \    [4;2H | |_) |  _|___) |  __/ | | \__ \  __/    [5;2H | .__/|_| |____/ \___|_| |_|___/\___|    [6;2H |_|                                      [7;2H                                          [25;0H[10;2H|[11;2H|[12;2H|[13;2H|[14;2H|[15;2H|[16;2H|[17;2H|[18;2H|[19;2H|[20;2H|[21;2H|[10;44H|[11;44H|[12;44H|[13;44H|[14;44H|[15;44H|[16;44H|[17;44H|[18;44H|[19;44H|[20;44H|[21;44H|[9;3H-----------------------------------------[22;3H-----------------------------------------[9;2H+[22;2H+[9;44H+[22;44H+[25;0H|/-\|/-\|/-\|/[9;15HWelcome to pfSense[11;5H1 [11;6H.[11;8HBoot Multi User [Enter][12;5H2 [12;6H.[12;8HBoot [S]ingle User[13;5H3 [13;6H.[13;8H[Esc]ape to loader prompt[14;5H4 [14;6H.[14;8HReboot[16;5HOptions:[17;5H5 [17;6H.[17;8H[K]ernel: kernel (1 of 2)[18;5H6 [18;6H.[18;8HConfigure Boot [O]ptions...[25;0H[23;4HAutoboot in 2 seconds. [Space] to pause[25;0H[23;4HAutoboot in 1 seconds. [Space] to pause[25;0H[23;4H                                       [25;0H-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/boot/kernel/kernel text=0x1223dd0 /-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/data=0x881ae0+0x3576a0 -\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\syms=[0x8+0x16f080|/-\|/-\|/-\|+0x8+0x16c4cc/-\|/-\|/-\]
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-p13 #0 c77d1b2(releng/10.1)-dirty: Tue Jun 23 17:00:47 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 = 4066828288 (3878 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
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, 0xffffffff806345e0, 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, 0xffffffff80634690, 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, 0xffffffff80634740, 0) error 1
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, 0xffffffff8060ce10, 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, 0xffffffff8060cec0, 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, 0xffffffff8060cf70, 0) error 1
random: <software, yarrow="">initialized
module_register_init: MOD_LOAD (vesa, 0xffffffff80fc4880, 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
ahcich0: <ahci channel="">at channel 0 on ahci0
ahcich1: <ahci channel="">at channel 1 on ahci0
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
ahcich2: <ahci channel="">at channel 0 on ahci1
ahcich3: <ahci channel="">at channel 1 on ahci1
isab0: <pci-isa bridge="">at device 31.0 on pci0
isa0: <isa bus="">on isab0
orm0: <isa option="" rom="">at iomem 0xc0000-0xc0fff on isa0
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: <generic>at usbus0
umass0: <generic 0="" 3="" ultra="" fast="" media,="" class="" 0,="" rev="" 2.00="" 1.98,="" addr="">on usbus0
da0 at umass-sim0 bus 0 scbus4 target 0 lun 0
da0: <generic ultra="" hs-combo="" 1.98="">Removable Direct Access SCSI-0 device 
da0: Serial Number 000000225001
da0: 40.000MB/s transfers
da0: 3648MB (7471104 512 byte sectors: 255H 63S/T 465C)
da0: quirks=0x2 <no_6_byte>SMP: AP CPU #1 Launched!
Timecounter "TSC" frequency 1750043568 Hz quality 1000
Trying to mount root from ufs:/dev/ufsid/559450fb9d397cc9 [rw,sync]...
Configuring crash dumps...
Using /dev/label/swap0 for dump device.
/dev/ufsid/559450fb9d397cc9: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/ufsid/559450fb9d397cc9: clean, 604826 free (130 frags, 75587 blocks, 0.0% fragmentation)
Filesystems are clean, continuing...
Mounting filesystems...

     ___
 ___/ f \
/ p \___/ Sense
\___/   \
    \___/

Welcome to pfSense 2.2.3-RELEASE  ...

No core dumps found.
Creating symlinks......ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib
32-bit compatibility ldconfig path: /usr/lib32
done.
External config loader 1.0 is now starting...
Launching the init system... done.
Initializing...................... done.
Starting device manager (devd)...done.
Loading configuration......done.
Updating configuration...done.
Cleaning backup cache..................done.
Setting up extended sysctls...done.
Setting timezone...done.
Configuring loopback interface...done.
Starting syslog...done.
Starting Secure Shell Services...done.
Setting up polling defaults...done.
Setting up interfaces microcode...done.
Configuring loopback interface...done.
Creating wireless clone interfaces...done.
Configuring LAGG interfaces...done.
Configuring VLAN interfaces...done.
Configuring QinQ interfaces...done.
Configuring WAN interface...done.
Configuring LAN interface...done.
Configuring CARP settings...done.
Syncing OpenVPN settings...done.
Configuring firewall......done.
Starting PFLOG...done.
Setting up gateway monitors...done.
Synchronizing user settings...done.
Starting webConfigurator...done.
Configuring CRON...done.
Starting DNS Resolver...done.
Starting NTP time client...done.
Starting DHCP service...done.
Starting DHCPv6 service...done.
Configuring firewall......done.
Generating RRD graphs...done.
Starting syslog...done.
Starting CRON... done.
pfSense (pfSense) 2.2.3-RELEASE amd64 Tue Jun 23 16:37:42 CDT 2015
Bootup complete

FreeBSD/amd64 (pfsense.****.***) (ttyu1)

*** Welcome to pfSense 2.2.3-RELEASE-pfSense (amd64) on pfsense ***

 WAN (wan)       -> igb0       -> 
 LAN (lan)       -> igb1       -> 
 OPT1 (opt1)     -> igb2       -> 
 OPT2 (opt2)     -> igb3       -> 
 0) Logout (SSH only)                  9) pfTop
 1) Assign Interfaces                 10) Filter Logs
 2) Set interface(s) IP address       11) Restart webConfigurator
 3) Reset webConfigurator password    12) pfSense Developer Shell
 4) Reset to factory defaults         13) Upgrade from console
 5) Reboot system                     14) Disable Secure Shell (sshd)
 6) Halt system                       15) Restore recent configuration
 7) Ping host                         16) Restart PHP-FPM
 8) Shell

Enter an option:</no_6_byte></generic></generic></generic></vendor></vendor></intel></intel></cpu></enhanced></cpu></enhanced></isa></isa></pci-isa></ahci></ahci></intel></ahci></ahci></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>

After putting it into the correct slot and reinstalling pfsense it still does not seem to be recognizing the drive.

Do you also changed the boot line in the BIOS?

ivor

Are you saying you added mSATA SSD along the SD card? If so, remove the SD card and just install pfSense on SSD.

derekdw

The flash is soldered to the board I believe that it can't be removed.

How do I update the boot line in the bios ?

ivor

@derekdw:

The flash is soldered to the board I believe that it can't be removed.

How do I update the boot line in the bios ?

You can still update the bios, however you didn't respond to our questions. Did you add mSATA and kept the other boot drive?

How do I update the boot line in the bios ?

I think there will be an option inside of the bios to tell their, from wich media to boot of.

derekdw

@ivor:

@derekdw:

The flash is soldered to the board I believe that it can't be removed.

How do I update the boot line in the bios ?

You can still update the bios, however you didn't respond to our questions. Did you add mSATA and kept the other boot drive?

Actually I did answer it… I said the flash was soldered onto the board so it can't be removed... So yes both are still installed.

Upon checking the bios (er well, hitting F12 for boot device - I don't see a bios option)
This is what I get:

Press F12 for boot menu.

Select boot device:

1. USB MSC Drive Generic Ultra HS-COMBO 1.98
2. iPXE (PCI 00:14.0)
3. iPXE (PCI 00:14.1)
4. iPXE (PCI 00:14.2)
5. iPXE (PCI 00:14.3)

It appears the drive is not being detected at all...
I read somewhere online that this drive is 5v instead of the normal 3.3v for msata... People on Amazon (where I bought it) were having issues with it being discovered by some systems.

So either this is the case, or the drive is DOA... I will have to check to see if any of my other devices have a mSATA slot to test it in

It appears the drive is not being detected at all…

Dude, please stop now and listen please.

If there are three miniPCIe slots and one of them is sorted with a SIM slot, this one with the SIM slot can mostly
not be used for mSATA or staroge devices, point! Not more and not less.
But then you need to use or try out please another one of the three miniPCIe slots and then you need
to change the BIOS boot order, that the board knows from where it should be booting after the install procedure.

But if you are going to install, let us say from an USB Stick, you should be knowing that the USB stick
must be choosen to boot and install from, and after you must once more change the boot order, to boot from
your mSATA.

And please don´t insert two mediums, with an installed pfSense system, from where the board could be booting from
this would be able to cause errors and you will not reach your goal, as an example, SD card and mSATA with an
installed pfSense system.

For sure you will be able to try out what you want but I consider you first some things to do really urgent,
that will help you then out of the most traps you will be able to jump in:

Serial to USB Adapter
pfSense Book
USB Stick or SD Card
Windows PC/Paltop with Putty and writing tool (USB stick & SD card)

Sounds like a little bit strange but will help you out from the mostly situations really glad.

derekdw

@BlueKobold:

It appears the drive is not being detected at all…

Dude, please stop now and listen please.

If there are three miniPCIe slots and one of them is sorted with a SIM slot, this one with the SIM slot can mostly
not be used for mSATA or staroge devices, point! Not more and not less.
But then you need to use or try out please another one of the three miniPCIe slots and then you need
to change the BIOS boot order, that the board knows from where it should be booting after the install procedure.

But if you are going to install, let us say from an USB Stick, you should be knowing that the USB stick
must be choosen to boot and install from, and after you must once more change the boot order, to boot from
your mSATA.

And please don´t insert two mediums, with an installed pfSense system, from where the board could be booting from
this would be able to cause errors and you will not reach your goal, as an example, SD card and mSATA with an
installed pfSense system.

For sure you will be able to try out what you want but I consider you first some things to do really urgent,
that will help you then out of the most traps you will be able to jump in:

Serial to USB Adapter

pfSense Book

USB Stick or SD Card

Windows PC/Paltop with Putty and writing tool (USB stick & SD card)

Sounds like a little bit strange but will help you out from the mostly situations really glad.

I don't think you are understanding what I am saying….

Have you used a 2440 before?

nicholfd

Hello derekdw,

My experience is that the default boot order is:
USB (if present & has bootable OS installed)
mSATA (if present & has bootable OS installed)
Soldered in "SSD" (if present & has bootable OS installed)

If you did an install from USB, and chose the "quick/automatic" (I don't remember the phrasing), then it will overwrite the USB stick you are installing from. It installs to the first disk (which is USB, if you booted from USB).

You have to do the "Advanced" (again don't remember phrasing) install and choose the correct storage device (mSATA).

Oh yeah - you don't have to change anything in the BIOS, once you get a good install on the mSATA, it will boot from it, after you pull the USB stick. AND you don't have to touch the factory installation of whatever is on the soldered in "SSD". Just leave it there. If you ever remove the mSATA, the box will boot from the soldered in "SSD".

Hopefully this helps.

Thanks,
Frank

derekdw

Thanks everyone for your help

My main question was if there was something I was doing wrong on the box itself to enable the mSATA. Apparently the answer is, no there is not.

I have done everything I can think of and it appears the mSATA is either A) DOA, or B) doesn't work with this box (some msatas have issues with some devices)

I will be returning the msata and getting a different brand.

As you can see in the below picture, there is no msata drive detected. (the corsair is the usb thumb drive, the other is the onboard flash)

pfsenseinstaller.JPG_thumb

nicholfd

You are correct - you don't need to do anything to make the system see the mSATA, as long as you have it in the correct slot (the slot directly behind the Ethernet ports).

Either your mSATA is bad, or the socket is bad, if you have it in the right slot.

nicholfd

@derekdw:

B) doesn't work with this box (some msatas have issues with some devices)

Regarding mSATA & compatibility, it is just SATA with power, on a different type of connecter. Unless some manufacturer (board or mSATA) are grossly not following the standards, any should work with any. I have mSATA from 16GB - 512GB, from at least 7 different brands and all have worked in everything I've put them in (even mSATA -> SATA adapters).

I suspect the thought that some "mSATAs have issue with some devices" is that not everyone understands that just because it fits in the slot, does not mean that the slot supports mSATA (which you know from the 2440 you have). The connector for mini PCI-e/mSATA has about eight different types of configuration. These include the possibility of USB in the slot, SATA (supporting mSATA) in the slot, PCIe x 1 lane, different power options in the slot, etc.