[SOLVED] Error can't access webgui / Fix damaged system.

[Kiss239]

First of all, sorry for bad english (my native language is russian).

Situation:

I've tried to setup OpenVPN web gui on my NAS4Free server, and while installing "session" from article 2.9 of HOW-TO, i've made a mistake and install "session2" from FreeBSD ftp server with all it's dependings. And after it web gui of NAS4Free became unavailable with the error with "gettext" and error in file "session.inc". And i've delete them both...

After that became the new error:

Code: Select all

Warning: require_once(session.inc): failed to open stream: No such file or directory in /usr/local/www/auth.inc on line 46

Fatal error: require_once(): Failed opening required 'session.inc' (include_path='.:/etc/inc:/usr/local/www') in /usr/local/www/auth.inc on line 46

and web gui still be unavailable.

I've got back-up config file from my system, which was made before my experimets.

Can anybody help me with this situation (I'm new in BSD systems and can do anything only by books and information from the web)??

Thanks in advance.

[armandh]

1] assuming embedded, re load the OS from the CD to your boot media
2] reboot and set the NIC and LAN [options 1,2]
3] reboot and at a client computer using the GUI restore the config

It reboots and should function

I have no experience with the full install but it should not be too different

[Kiss239]

Thaks for an answer!

I thought about that way, but there is another question: will disks, file systems and datasets mount correctly (data on these disks is very impotant for me)?

[armandh]

so far the simple 3 steps above have always worked for me
even when I switched 4 drives from a 966 P-III to 2.4 Ghz P-4 hardware
[freenas-7 with 500 Gb and 320 Gb ZFS mirrors]
the embedded OS rebuilds the hardware profile at each boot
the config file rebuilds the setup.

as long as you do not format the drives your data will likely be OK
NAS4Free and the earlier FreeNAS-7 were designed to preserve data
even through a hardware failure necessitating a change of hardware

about the only thing that screws things up is a power failure during writes
[incomplete file journal entry?] a good UPS is highly recommended
HOWEVER
no matter how secure a backup is [and NAS4Free is very secure]
it should never be the only copy of valued data.
BECAUSE
a single NAS4Free or more co-located are not immune to physical damage
however unlikely fire/flood or the odd meteor strike

LASTLY
I avoid hardware raid
with hardware raid ones data recovery may require the EXACT hardware
here one may be hampered by obsolescence and availability
soft raid or zfs only requires a copy of the NAS4Free and config

[Kiss239]

Thanks!

WebGUI is working correctly now.