2.2 to 2.1.4
-
yes there is that utility there to update the bios…but ive also used that to boot on a usb and install the 2.2 to the msata using gzip...
-
Ok, well if you're just un-gziping the file onto the msata disk then there will be no version checking etc. It will simply overwrite whatever is there.
Steve
-
just one more thing…i dont know the boot order of the APU...incase it will prioritize the msata, how can i change that to USB? thanks
-
this is the result of doing the gzip command from the tinyCore.
Root mount waiting for: usbus6 usbus3 usbus1
uhub6: 4 ports with 4 removable, self powered
uhub1: 5 ports with 5 removable, self powered
uhub3: 5 ports with 5 removable, self powered
ugen6.2: <generic>at usbus6
umass0: <generic 0="" 2="" flash="" card="" readerwriter,="" class="" 0,="" rev="" 2.01="" 1.00,="" addr="">on usbus6
umass0: SCSI over Bulk-Only; quirks = 0x4001
umass0:0:0
Attached to scbus0
Trying to mount root from ufs:/dev/ufs/pfsense0
WARNING: / was not properly dismounted
da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
da0: <multiple card ="" reader="" 1.00="">Removable Direct Access SCSI-4 device
da0: 40.000MB/s transfers
da0: Attempt to query device size failed: NOT READY, Medium not present
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=1710063
ad4: TIMEOUT - READ_MUL retrying (0 retries left) LBA=1710063
ad4: FAILURE - READ_MUL timed out LBA=1710063
g_vfs_done():ufs/pfsense0[READ(offset=875511808, length=53248)]error = 5
vnode_pager_getpages: I/O read error
vm_fault: pager read error, pid 24 (sh)
pid 24 (sh), uid 0: exited on signal 11
Jul 30 02:50:35 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode
Enter full pathname of shell or RETURN for /bin/sh:
?</multiple></generic></generic> -
reinstalled again and here is what ive got
Trying to mount root from ufs:/dev/ufs/pfsense0
da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
da0: <multiple card ="" reader="" 1.00="">Removable Direct Access SCSI-4 device
da0: 40.000MB/s transfers
da0: Attempt to query device size failed: NOT READY, Medium not present
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2489919
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2490015
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=1243943
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=1710063
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2255727
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2253879
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2258919
Configuring crash dumps…
Mounting filesystems...
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=3436359
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=934231
Setting up memory disks...ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2255527
done.
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2258623
Disabling APM on /dev/ad4___
/ f
/ p _/ Sense
_/
__/Welcome to pfSense 2.1.4-RELEASE ...
Creating symlinks......ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2491295
done.
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2803655
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2943431
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=3133047
ad4: TIMEOUT - READ_MUL retrying (0 retries left) LBA=3133047
ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=3130375</multiple> -
Hmm, well that doesn't look happy. As I said I don't have an APU but I know there were some issues with the mSATA modules originally being supplied by PCengines. ESF/Netgate stopped using them because of this. What mSATA do you have?
There appears to be no obvious cause or workaround for this particular error.Steve
-
well it works straight away during fresh install of 2.2…it si the msata16c (Phison)...the latest version of their msata...maybe it needs formatting before installing...i want to try that but i dont know how...
-
Ok, so what are you installing, full or Nano? Which image are you using exactly?
The msata16c listed by PCEngines doesn't appear to say 'Phison' on it. :-
Edit: The part number could be one of theirs though.Steve
-
i dont know the boot order of the APU…in case it will prioritize the msata, how can i change that to USB?
The boot order can be changed, and saved during bootup of the APU. You need serial console though… press 12 immediately when booting.
maybe it needs formatting before installing…i want to try that but i dont know how
Easiest way it to make it boot a live install (install pfSense image on usb stick, boot from that). During pfSense boot, you have options for creating partitions manually, not 100% sure but I would think you can delete them there as well.
Note here: I encountered quite some challenges when manually fiddling with the partitions on a mSata. It was on the other hand very easy to install pfSense if I just let the installer take care of that part… And yes it deletes existing partitions if you take the easy way. -
=nano install amd64 4g
=msata16c is phison…counterchecked it with another board with vga..it shows on the boot order -
Just a relabelled drive then.
When 2.1.4 was first released there were some images the weren't correctly labelled, nano+vga labelled as nano. That has been fixed but if you downloaded your image a while ago you may have a bad one. Seems unlikely though.Steve
-
iam facing the same issue with fresh install on a msata16c
same procedures works on a msata16b
