OPNsense Forum
English Forums => General Discussion => Topic started by: vergilis on April 08, 2015, 08:57:46 pm
-
Can anyone share installation guidelines for a Netgate RCC-VE 2440 device?
-
If it boots from usb, it should be rather easy to install OPNsense on it.
Have you looked at the wiki page?
https://wiki.opnsense.org/index.php/Manual:Installation_and_Initial_Configuration
In case you use a compact flash or sd card, it's better to enable a ramdisk. You can enable this via https://<machine's ip>/system_advanced_misc.php
and then enable "Use RAM Disks".
Welcome to OPNsense!
Cheers,
Ad
-
Kindly supplied via Netgate: http://www.netgate.com/docs/rcc-ve-2440/opnsense.html
-
Does anyone know what the installation directions would be for the version 16.1.8, the directions from Netgate for 15.7.18 no longer work.
Starting at step 12, there is never a prompt asking what shell to use.
After this in step 13 it is not possible to mount the disks read-write, it gives an error stating that Mounting Failed with Error 19.
I am not an expert by any means so any help or guidance would be appreciated.
-
I tried it it with version 15.7.18 as well and step 12 does not happen. This is the error I receive.
The hardware is the RCC-VE 2440 that originally shipped with a PF Sense image. The bios was updated to the latest version as well.
Mounting from ufs:/dev/da1s1a failed with error 19.
Loader variables:
vfs.root.mountfrom=ufs:/dev/da1s1a
vfs.root.mountfrom.options=rw,noatime
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>
-
if its a flash based version then most likely the flash needs someinitialisation time. Escape to prompt and type:
set kern.cam.boot_delay="10000"
boot
Then after installation add the boot delay to loader.conf.local
That should probably do the trick..
And next time consider buying from us, better hardware withouth those install and boot issues ;)
-
We do have a ticket for kern.cam.boot_delay additions to images for 16.7. I'm just not sure that a fix that hurts every boot of every installation is totally worth adding if the manual workaround works. It's easily added, but it also needs to be stripped afterwards, only afterwards is conditional, on a CF card we don't want that. ;)
https://github.com/opnsense/tools/issues/28
-
I actually got a response from Netgate, here is what they said. The unit I have only has eMMC hence the issue.
Ok, the reason it stops at the mountroot> prompt is that it's trying to mount from da1.
Our guide assumes you are installing to the mSATA (ada0). When you are booting the install media it appears as da0 and the eMMC appears as da1. After installing when you remove the install media the eMMC becomes da0.
At the prompt type:
ufs:/dev/da0s1a
That will allow you to continue. When it has booted completely you will need to edit /etc/fstab to correct the location.
As I am not a Linux guru does this help to explain what is happening. I understand the theory but still need to investigate what the fstab file should look like.
-
jschellevis I meant to mention as well that I would have bought hardware from your organization however I wasn't aware of it until recently. We bought the ADI Engineering box a while ago with PF on it but after trying it out shelved it because of the lack of documentation and overkill for our needs.
-
Hi hanshin,
If you can post the contents of your fstab file here, I can easily point you in the right direction.
From a console type this:
cat /etc/fstab
and post the output here, are you familiar with an editor like vi or nano?
If not, then its probably more practical if I upload an fstab which you can download direct to the machine.
Regards,
Ad
-
@hanshin
Is the install issue resolved now, or do you need more help?
Cheers,
Jos