I am getting kernel panics on my Unraid setup. To be fair to the guys at Lime - I am 99% sure my problems are related to junky hardware. So I have a few questions for the forum...

 

1) Is there some sort of crash log I could attempt to parse through?

 

2) Is a 300w power supply too low? It's a Seasonic - but i think the wattage might be low. It is powering 4 7200 rpm drives and a Athlon XP 2500. The rig will run fine for a few days, then panic out while idle.

 

3) How long *should* it take to boot up? Is 7-10 minutes normal, or is this old jacked board of mine somehow only communicating to the flash at USB 1.1.

 

 

Thanks. What I need to do is rebuild the box, as soon as funds permit.

> Is 7-10 minutes normal,

I've personally not see something this long. 3 minutes maybe.

Where is the pause... are the dots just printing slowly or is it uncompressing linux?

 

As far as power supply.

 

I've run up to six drives on a 300 watt cheapo jinco power supply with a dual PIII and 2 GB of ram.

Never had a kernel panic because of power supply.

Although I do not know how much power your cpu and mobo use.

 

I might suspect the CPU's getting hot or memory errors.

 

Are you on a UPS. in that case, power could be an issue.

 

Also you say it is while the machine is idle.. could it be when drives spin up?

If they all spin up at the same time that could create a surge the power supply cannot handle.

 

 

 

 

 

1) Is there some sort of crash log I could attempt to parse through?

 

To obtain a copy of your current syslog, at the unRAID console or in a Telnet session, type the command:

 

  cp  /var/log/syslog  /boot

 

This will make a copy of the system log in the root directory of your flash drive, which you can either copy directly from the flash share of your server, or plug the flash drive into your PC and access the syslog there.  Any file manager such as Windows Explorer can access the file across the network.  For example, if your unRAID server name is Tower, then you can access your newly created syslog as \\Tower\flash\syslog.  I recommend renaming it with the date and time and the .txt extension, for example syslog2007-08-28-1630.txt.

 

A helpful Wiki link:  http://lime-technology.com/wiki/index.php?title=Viewing_the_System_Log

 

 

Your boot up time does seem too long, perhaps the reason will show in the syslog.

 

I've had a PSU give me a Kernel panic.

 

When I upgraded to drives 11&12 using a 600w toughpower PSU the startup sound changed.  Knew straight away the PSU was under load from the new additions, but it continued to function as it should.  Then I replaced the parity drive with a 1TB one so I could add a 1tb data drive and during the parity calc it faulted with a kernel panic.  I got a shock at first, because parity had sync'd when I'd last updated.  I figured the PSU had finally reached it's tolerance with the extra loading of the ongoing parity sync.  I expected this and had brought a new PSU (850W).  It doesn't even whimper with 14 drives.  I still have output for the full 16 though, but have to figure a way of installing them as my case only has holders for 14 HDD's.

Thanks for the help guys. I think the issue might be moot though - as it will no longer physically power on. I guess that will teach me not to try to cook up a raid array out of tripe.

 

I need to build a real unraid box. Newegg here I come