"error occurred" during jail pbi install

Status
Not open for further replies.

csh8428

Dabbler
Joined
Nov 5, 2012
Messages
45
So, I was stuck forever on the setup to install the jail pbi. The Jail IP Address field was just "------", so i couldn't get to the step to actually upload the jail pbi file. I'm using 8.2 beta 3 running from a USB key. The drives are UFS. Using chrome to access the GUI.

Global Configuration
Hostname: Freenas
Domain: local
IPv4 Defatul Gateway: 192.168.1.1 This is my router's ip address

I finally figured out to set up an Interface like so:
NIC: re0
Name: LAN
DHCP: checked
all other fields left as unchanged/default

Alias
iPv4 Address: 192.168.1.105 My Freenas ip is 192.168.1.104
ipv4 Netmask: /24 255.255.255.0
all other fields left as unchanged/default
I can ping 192.168.1.105 from within the shell window within freeNAS

Not sure if this has anything to do with it:
System -- Network settings
Name:
re0 192.168.1.104/24
re0 192.168.1.105/24

Name Server: 192.168.1.1

Default route: 192.168.1.1


I assume the above settings are correct?

Here's my problem: Steps 1 and 2 go by quickly. During Step 3 of the jail pbi install the progress bar goes to 100% pretty quickly and then the progress bar changes to that moving one from left to right(no % indicator). I watched youtube videos that show people uploading the jail pbi and step 3 takes a couple of seconds, but I let it go for about 10 minutes. The hard drive in the NAS was making very loud clicking noises so it was kind of scaring me a bit. After about 10 minutes it "finished" and I got an "error occurred" message at the top of my GUI. That'st he only thing it said. I had to reboot the NAS. No plugin jail.

Could it because freeNAS is running off of a USB key? I know you can't just "write" to the usb key.

Is this normal? Any other comments? Is there a way to install the jail via command line?

Thanks for any help!

edited: for more detail

Regards,

Craig
 

csh8428

Dabbler
Joined
Nov 5, 2012
Messages
45
Ok.. I can't really say I figured out WHY I was getting the error, but I changed the drive where the PBIs are installed and it worked.
 
Status
Not open for further replies.
Top