NASLite Network Attached Storage

I just built a new storage server that will be a replacement for my current NASLite machine (motherboard getting old and acting funny.) It is an ECS Goal3+ 754 SiS 761 GX Micro ATX Motherboard and an AMD Sempron 3000+ cpu; 1.0GB of DDR400 memory; a 2.0GB SanDisk Ultra II Compact flash with a cf-ide adapter is the primary drive connected to IDE1; 2 - SATAII 1TB 7200rpm harddrives fulfilling the storage side. There is an IDE CDRW drive connected to IDE2 temporarily for the purpose of installing NASLite 2.10 to the cf card. All unnecessary items in the bios have been turned off with the exception of the onboard video card (have to see what I'm doing initially ). When I boot from the cdrw, I get the option screen to choose run from cd, installation utility, and memtest, however, whether I choose to run from cd or enter the installation utility, I get:

<0> kernel panic: Attempted to kill init!

It stays there and the caps lock and scroll lock lights on my keyboard flash in sync.

Any suggestions?




Here is some information concerning what is displayed on the screen with the error screen:

Unable to handle kernel NULL pointer dereferences at virtual address 00000010
*pde = 00000000
Oops: 0000
cpu: 0
EIP: 0010:[<c010b0aa>] Not tainted
EFLAGS: 0001002
eax: 00000000 ebx: 00000297 ecx: fffffff0 edx: c047d8f0
esi: ffffffff edi:00000000 ebp: ffffffff esp: f7f5ff68
Process swapper (pid: 1, stackpage = f7f5f000
Stack: fffffff c04a7b60 c03f1fb0 c024ddfe ffffffff c04a7b60 c04a7b60 c03f1fb0 00000000 00000000 c024e6dd
c04a7b60 00000001 00000001 00000001 00000001 00000001 00000001 00000001 00000001 00000001
00000001 c03f1fb0 c0105000
Call Trace: [<c024ddfe>] [<c024e6dd>] [<c010898f>] [<c0105000>] [<c0105000>] [<c0105058>] [<c010898f>]
[<c0105051>]
Code: ff 50 10 58 53 9d 83 3d d4 83 48 c0 00 75 10 f3 90 89 f0 c1

<0> Kernel panic: Attempted to kill init!

A simple 64MB CF card will more than due.

Just build the CF card in another machine and then move it to the new one, should be a work around for your problem.

Mike

I got a great deal on the 2gb card pricewise. Couldn't pass it up. Got 2 of them , the other is going to be in a standard linux machine. Now a question (probably a dumb one, but what the heck) how do I go about building it on another machine?

pull the ide/cf adaptor and fit it in another machine and install the Naslite software to the cf card - best to disconnect any other hard drives to be sure - you dont want to delete those

once you have the naslite software on the cf card - rebuild into your original machine and [hopefully] boot up - then add the serial number - unlock code etc

run memtest to check thge ram and turn off all the stuff you don't need in the bios. Every kernel panic i've had with naslite has been a ram or acpi issue.

Memtest is already running....I had considered that (even though it is a brand new stick from Crucial). I made sure that everything was turned off (and I turned off EVERYTHING) that wasn't necessary before I even started trying to install it. I beat ya to it . I think I have a machine that I can do that on...... . Thanks...I'll give it a try and let you know what happens.

Okay....I put the cf card in a different machine and successfully loaded NASLite-2 on to the cf card. When I plug it back into the machine that is to be the new server, I get the same error as in my first post. Any suggestions?

did it boot in the machine you loaded it on - if so then with my very limited knowledge i would suggest checking in the hardware compatibility guide and seeing if things like your motherboard [well the chipset] are ok

usual things after that are bios - irqs - switch everything off in bios that you dont need

then if that does not work wait for the experts to drop in

The only thing I can find that doesn't specify whether it is supported or not is the onboard NIC which uses a Realtek 8201CL chipset. The northbridge is Sis761GX and the southbridge is Sis 965L. Aside from that. The onboard sata controller I can't find any information on. I have it set in the bios to read each of the two terabyte drives as separate drives and not in any raid configuration.

just wanted to provide an update to the issue I was having. I got it taken care of. It actually ended up being a problem with the mainboard itself. I purchased a new mainboard, moved everything that was hooked up to the bad one to the new one, and it fired right up and has been running like a dream. Now if I can just figure out what was actually wrong with the other board and whether it is usable or not. Thanks for all the input!!

did you replace like for like with the mainboard - if so then it may be faulty - if not and it is a different make and more importantly a different chipset it may just be a compatibility issue

Turn PnP and ACPI off in the BIOS temporarily and give it a try.

The mainboards are different, yet they have almost the same chipsets. I just tried the old board with debian installer cd and it gave the same kind of kernel panic partway into it. So I definitely think the old board is garbage. I just wish I knew why.