It sure is quiet in this forum...
I have a previously-reliable Naslite system that suffered an extended power failure (UPS ran out, Thank-you Ontario Hydro), and now, it reboots at the point the system is going online. It boots, finds and mounts the four disks OK, there is a quick message about 'Server initialized' and ' Network initialized (I think; they go by very quickly), and then, Poof!, it beeps 2x and reboots.
The system has a 1.7 G Pentium, 768 Mb of memory and about 1.3 Tb of disk space distributed over 4 disks. It has been a reliable runner (barring power failures) for several years.
I had to re-learn how to do a filesystem check with a bootable CD. This takes 30-45 minutes, but it's faster than letting NasLite grind through on its own. e2fsck runs and exits without reporting errors.
I have tested it with only 2 - 250 Gb disks connected, with the same result.
I initially tried different (larger/more) memory to see if Naslite could struggle through it's own e2fsck on it's own, thinking that was the problem (mentioned in an older post).
I have tested it with NO disks connected, and it behaves the same way (???), so it could be hardware related. I've set the bios to halt on ALL errors, but I don't get any info beside the 2 strangled beeps. This isn't one of the listed Naslite beep codes.
I have let it reboot repeatedly, hoping a useful message might pop up, but no....
After Naslite mounts the disks sucessfully, the system reboots, and the disks are 'dirty' (not cleanly unmounted).
I'm using a RIPLinux bootable CD for cleanup, and I've been able to e2fsck the disk sucessfully, and browse the internet (Lynx ) to verify the Ethernet card is operational. I've run the memory tester, with no issues found.
I've reset the BIOS, and made sure it's reporting 'None' for disk IDs (had to boot system with drives disconnected to get this).
I've disabled everything I can think of in BIOS.
Th one thing I haven't done is tried a new boot disk, because it was such a pain to make. I suspect this isn't an issue since the image uncompresses and starts without complaint (I think).
Does this ring a bell with anyone? Or am I looking at a replacement box? Anything else I can try, besides a fresh boot disk?
Thanx in advance.