NASLite Network Attached Storage

morning guys,

I am having a problem with one of my naslite 2x64 core3 server's

every morning it appears to have crashed the normal screen that is attached to it is black with a load of error messages on it , i can reboot it but the next morning the same has happened .

the drives pass smart and disk checks ok
new cables have been fitted to the drives

bit of a loss now just waiting for a new cf card holder going to try that
next would be two raid cards (running in jobd) mode

any ideas / suggestions please

Steve

The only thing that happens at night is time checking. Try setting the time server to 0.0.0.0 and see if something changes.

Another point is the disks going to sleep and not waking up rapidly.

Robby

have you run mem tests or changed memory - or again try removing one stick of memory at a time - assuming you have more than one stick in there

thanks for the replies...

Robby i am not using a time server , the disk's do go to sleep they are wd green's how can i prove that this is not the problem


Tony if i can remember the core 3 hardware support tool does memory checks? will have to look for it or download it again

Steve

Can you take a picture of the screen with the errors ? It might help.

As for the disks going to sleep, you'll need to do a big backup, check disk or some other disk activity during the night to see if the disks don't go to sleep, will the the server crashes again. Or, do a clean boot in the morning and do not use at all the server. The disks will go to sleep and you'll see what happens.

Another trail to follow would be resetting the BIOS and then stopping all the unnecessary stuff in the BIOS ans see what happens.

Robby

Hello Robby,

Turned it back on this morning to see what happens

in server logs I found these entrys

•Aug 26 09:51:39 [4] sdd1
•Aug 26 09:51:39 [3] sd 7:0:0:0: [sdd] Attached SCSI disk
•Aug 26 09:52:23 [5] hda: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
•Aug 26 09:52:23 [5] hda: task_pio_intr: error=0x04 { DriveStatusError }
•Aug 26 09:52:23 [5] hda: possibly failed opcode: 0xa1
•Aug 26 09:52:23 [5] hda: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
•Aug 26 09:52:23 [5] hda: task_pio_intr: error=0x04 { DriveStatusError }
•Aug 26 09:52:23 [5] hda: possibly failed opcode: 0xa1
•Aug 26 09:52:23 [5] hda: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
•Aug 26 09:52:23 [5] hda: task_pio_intr: error=0x04 { DriveStatusError }
•Aug 26 09:52:23 [5] hda: possibly failed opcode: 0xa1
•Aug 26 09:52:27 [2] sky2 eth0: enabling interface
•Aug 26 09:52:29 [2] sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
•Aug 26 09:52:37 [5] hda: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
•Aug 26 09:52:37 [5] hda: task_pio_intr: error=0x04 { DriveStatusError }
•Aug 26 09:52:37 [5] hda: possibly failed opcode: 0xa1
•Aug 26 09:52:42 [2] kjournald starting. Commit interval 5 seconds



could this be the problem ? how do I know which one it is ?

Steve

after about 3 hours or so it's crashed again.

took a pic of error messages

steve

Hi Steve

Error 5 is never good for hard drives You may try to unplug all drives except one and see what happens. Then you change the plugged drive and so on.

Sorry but you'll need other people for more precise information on the problem.

Robby

ok thanks for your help, i have also noticed that the ethernet leds are flashing like mad and on my router so there is lot of traffic somewhere nothing else is active ??

steve

retitle the thread 'problems on my mac' - the use of the mac word usually gets a response from ralph -

the onboard lan has died

New build required I thinks , no point in putting any more money into that one

Steve

Maybe that explains the frozen computer but what about the errors in the log about the drives ?

Robby

not sure about that robby not had chance to have another go since last weekend going to unplug a drive at a time to see which one faulty .

got to sort another board out first

Steve

Robby,

After removing each drive in turn and restarting the machine the error [5] on the drives turned out to be the CF card Disk - 0

I replaced the card the error still there , replaced the holder error still there
Just replaced with a Sata CF adaptor machine won't boot from that

Bit of a loss now

Steve

It may be an IRQ problem with the CF reader but that is a wild guess...

If you have a small spare drive, take off all the data drives, put in that small drive and install NL on it. Boot and look at the logs. Then add one data drive and look at the logs etc.

Robby