Don't even know what to title this as

[Bman26]

Hey folks,

Just built another FreeNAS box and the shit has been hitting the fan since.
The very first boot, everything went smoothly. I shut it down properly, it seemed all good.

Next day I boot the machine and I can't connect to it via HTTP(S) or SSH. Wtf, right?
So I sit there dicking around with ifconfig and route add default and DHCP and all that and I still can't get the thing to connect.
So I decided to do a factory reset because maybe something got all garbled or something.
It gets better! :D

Now, the machine won't even show the FreeNAS menu once everything's all loaded and fine and dandy.
It just keeps cycling through some weird stack dump that's going on about messed up lines in some Python code incessantly.
I tried connecting via HTTP(S) and got all this crap that you can see in the attached .txt file.


I have no clue as to what the thing's belly-aching about.


Cheers!

 

[Nick2253]

Almost guarantee that your problem is a bad USB stick.

 

[Bman26]

Almost guarantee that your problem is a bad USB stick.

I'm using a hard-disk here man.
Not a USB stick.

 

[joeschmuck]

What are your system specs?

 

[Bman26]

1.50Ghz P4
384MB RAM (168-pin)
7GB HDD (IDE)

 

[dlavigne]

Are you sure it's not nas4free that you want? That isn't anywhere near close the minimum requirements for freenas.

 

[cyberjock]

384MB of RAM isn't even the minimum for NAS4Free(2GB is last time I checked).

That machine is MUCH too old to support a NAS with ZFS bro.

My cell phone has more RAM than that!

 

[Bman26]

384MB of RAM isn't even the minimum for NAS4Free(2GB is last time I checked).

That machine is MUCH too old to support a NAS with ZFS bro.

My cell phone has more RAM than that!

Trying to put these old machines to use.
The thing's from like... 2001-ish
I can smell the PVC.

I was using UFS btw.
I could just keep it simple and throw on some light-weight GNU/Linux distribution on there or something.
Maybe put FreeBSD on there itself.

Any OS recommendations?
I'd like to explore with BSD-based distributions some more.

 

[cyberjock]

Even with UFS the minimim is 2GB, with 3GB a much better idea...

No recommendations at all for a system that old.

 

[joeschmuck]

Sell it for the gold content.

 

[solarisguy]

@Bman26, yes you can still use old hardware. However, you cannot deploy new software on it. So you would need to get an OS that is at least 10 years old.

And given its 7GB of disk space, it might be a DNS server and not much more in current computing environments.

 

[anodos]

I set up an OpenBSD samba server on similar hardware not long ago (P4 celeron, 256MB RAM). Worked fine. Don't try compiling code on it.

 

[solarisguy]

And Gigabit Ethernet interface? That is what I mean by current computing environments (for example, of course).

You say that such a hardware is not good for compilations, because they would take very long time, I am adding. And to me, the same with Samba, it would be too slow (at least ten times slower than more recent hardware). But OK for serving small files? But OK for small compilations? ;)