Jail preventing startup of nasfree

[rampie]

Hey,

i just installed a jail and tried booting it up. The result: entire server blocked down.

Now i restarted the server and guess what happened: YES it's still blocks. I guess the jail is getting loaded at startup.

Any ideas on how to NOT get it on startp anymore?

Thanks.

[raulfg3]

edit config.xml and find postinit command, delete or disable start of the jail. (if not find in config.xml, perhaps need to edit rc.conf some line related to jail start)

PD: it's safe and recommended to install TheBrig a default jail manager for Nas4Free.

To edit file, you only need to boot from CD-ROM and use embeded file editor in N4F to locate file, load, modify, and save, once done you can reboot without CD-ROM.

[kkd]

try to access /cf/conf/config.xml and delete the jail rows (install a new n4f and mount old n4f drive).
try to restore old config by renaming /cf/conf/config.bk5 to config.xml.
create a new install and restore saves config
create a new install and import disks

[raulfg3]

wow... two responses at same time, this is great.

[kkd]

wow... two responses at same time, this is great.

you were a little faster

[rampie]

To edit file, you only need to boot from CD-ROM and use embeded file editor in N4F to locate file, load, modify, and save, once done you can reboot without CD-ROM.

OK, i booted from USB drive, but how to access the USB drive then?

[kkd]

To edit file, you only need to boot from CD-ROM and use embeded file editor in N4F to locate file, load, modify, and save, once done you can reboot without CD-ROM.

OK, i booted from USB drive, but how to access the USB drive then?

mount old n4f drive

[rampie]

Nvm, found how to do it. I removed the jail from being startup.

I guess my problem lies witht th fact i'm trying to mount a share which is to big

[fsbruva]

More than likely, you are trying to do an illegal nullfs mount. This will cause all manner of issues. Size of share doesn't really matter - but it will choke pretty hard if you try to mount one folder nullfs and then mount a sub folder as a separate mount point. Results in resource deadlock.

[rampie]

just inserted the USB drive in another PC and this one boots fine. Gonna try again tonight on the server and attach screen + CD drive so i can troubleshoot the thing. Gonna disable the jail for now.

PS: any chance of transferring the config from an embedded install to a full install, or is embedded install better? (with full i don't have to do the jail i suppose?)

[raulfg3]

(with full i don't have to do the jail i suppose?)

incorrect, jails is the default / suggested by N4F team way to install packages, and that packages do not affecting the operation of N4F.

Jails using TheBrig have a aditional advantage, survive to N4F upgrades / reinstall, you only need to save N4F config and restore it.

is embedded install better?

embeded is recomended for USB key install due "burn it" problems in USB devices if you write a lot of times on it.

Full is usefull / recommended for install on HD or Professional/industrial grade USB /CF/SD. (If your board have a IDE port and you do not use it, is useful to use an old and cheap /free IDE disk to boot N4F from it)

[rampie]

OK, then i'll stick with embedded. Getting the jail up is a must now