• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Openindiana Crash help

barbz

Weaksauce
Joined
Apr 25, 2010
Messages
85
Hi all,

I have a new storage server in the making.

Its currently a Intel S1200bts with a e3 1230 xeon, 8gb ecc ram (memtested), and two 320gb OS drives mirrored running openindiana 151a with Nappit, Nappit-afp and transmission-daemon installed (from SFE).

I have had this crash a few times over the last couple of weeks but I am unable to find out why its happening.

It lasted for 6 days (not always the same amount of time), when it happens the console is frozen and the network drops.

Last entries in the logs are
Code:
Dec 14 00:05:39 Indiana mDNSResponder: [ID 702911 daemon.error] ERROR: getOptRdata - unknown opt 4
Dec 14 00:12:15 Indiana last message repeated 60 times
Dec 14 00:12:36 Indiana mDNSResponder: [ID 702911 daemon.error] ERROR: getOptRdata - unknown opt 4
Dec 14 00:18:56 Indiana last message repeated 63 times
Dec 14 00:19:17 Indiana mDNSResponder: [ID 702911 daemon.error] ERROR: getOptRdata - unknown opt 4
Dec 14 00:25:25 Indiana last message repeated 66 times
Dec 14 00:25:46 Indiana mDNSResponder: [ID 702911 daemon.error] ERROR: getOptRdata - unknown opt 4
Dec 14 00:26:57 Indiana last message repeated 16 times

where do I start looking to track this down?

Cheers
Paul
 
a frozen console is mostly due to a sudden hardware failure mostly
a failed disk or disk controller or RAM problems

if its a disk problem and if there is no log entry,
look at the disks if you have a always on led

or hot-unplug all disks to see if its working
otherwise remove half of memory, run it, try the other half
(memtest is not always finding all problems)
 
Back
Top