April 21, 201214 yr I lost power to my house. After this, my unraid server will work for a while (about 20 minutes or so), then it completely disconnects from the network. The server "box" is still running, but there is a flashing green light and an orange light for the network connection to the machine. I took a screenshot of the server's user interface. The server does not respond to keyboard inputs. Does anyone know what this error is?
April 21, 201214 yr It almost sounds like a mainboard problem. Is your NIC built onto the mainboard or is it an addon card?
April 21, 201214 yr when its not responding to keyboard inputs, have you tried to CTRL+C? Not saying that its going to fix your problems, but if it can get you back under control you can provide us with syslogs,
April 21, 201214 yr Author I didn't know about control-C. I'll give that a try. (I set this system up over a year ago and haven't had to do anything since. I can't even remember how to log in -- I just checked the status via a web browser.) It certainly could be a hardware problem. The network "card" is on the motherboard. It's just strange that everything works for 20-30 minutes and operates normally, then becomes unresponsive.
April 21, 201214 yr Author Yikes! A different set of error messages. And, control-C does not work. If it is a hardware problem, do you think it might just be limited to network interface? That is, could I try a NIC card first? Unraid works for a while, then fails. I'd hate to have to buy a new motherboard, because that likely entails memory, processor, etc. And the motherboard isn't that old, only a little older than a year if that.
April 21, 201214 yr Author And is there a way to get the server to store the syslog on the memory stick? At least this way, I could see what's going on. As it is now, I don't have any way to determine whether it's software or hardware.
April 28, 201214 yr Author Run memtest overnight. Shoot, had I known how easy this is to do, I definitely would've done this. On my home theater computer, I got bad RAM, ran Memtest, and it never found anything. But I kept having random reboots until I replaced the RAM. Anyway, I ordered a new motherboard, processor, and memory, only because my time is so valuable -- if memtest didn't work, I'd have to start real debugging.
Archived
This topic is now archived and is closed to further replies.