May 28, 200917 yr My old Motherboard died and I had to replace it. I ended up just building a new little system to house all of my drives for unraid: ASUS P5N-D LGA 775 NVIDIA nForce 750i SLI ATX Intel Motherboard Intel Pentium E2200 Allendale 2.2GHz LGA 775 65W Dual-Core Processor Model BX80557E2200 G.SKILL 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory Model F2-6400CL5D-2GBNQ Rosewill RP500-2 500W ATX12V v2.01 Power Supply - Retail45250519 HEC 6C28BB8S Black Steel ATX Mid Tower Computer Case - Retail46478563 I also have a RocketRaid 1820A controller in there (for extra SATA ports) and an old 8800GT as the video source. I'm running 4.5-beta6. I transferred all my drives into the system, booted 'er up and everything looked fine. All of the drives are recognized correctly and I can access data fine over the network. I ran for about a day like this no problems. Last night, I started a parity check and about 10% in my system just randomly turned off. Tried again this morning, same thing. I've tried swapping out the power supply, this makes no difference. I've tried different RAM, no difference. I'm 99% sure that the CPU/MOBO are fine as they are relatively new and I'd been using them for another little server for a few months with 0 problems. So, as you can imagine, I'm stumped as to why this would happen. I'll post my syslog in a second. Any suggestions are greatly appreciated!@
May 28, 200917 yr Author Syslog here: http://www.sendspace.com/file/tjhuz2 I notice some read errors. Hmmmmm.
May 28, 200917 yr Author Whoops, it seems like that's an old syslog, I'll get a new one a little later.
May 28, 200917 yr Author Here's a new syslog: http://www.sendspace.com/file/12l50i This is before running a parity check. Not sure how easy it will be to get one during a parity check given that the machine shuts off?
May 28, 200917 yr That first syslog was one sick puppy! The second seems OK, nothing particularly bad stands out, but it only covers the boot up. ACPI reports some warnings, you might want to check for a BIOS update. If you can, monitor the server console. Perhaps use a digital camera to capture the last messages that display before it appears to be terminating.
May 29, 200917 yr Author Yeah, I saved a syslog within ~30 seconds of it crashing a second ago. Nothing in the syslog that looks bad--weird. I had issues with it freezing after loading bzroot...so I had disabled ACPI as mentioned in another thread. Would that somehow be causing this? I'm thinking it won't boot with ACPI enabled, but I'll try it.
May 29, 200917 yr Yeah, I saved a syslog within ~30 seconds of it crashing a second ago. Nothing in the syslog that looks bad--weird. I had issues with it freezing after loading bzroot...so I had disabled ACPI as mentioned in another thread. Would that somehow be causing this? I'm thinking it won't boot with ACPI enabled, but I'll try it. Is the server crashing... or powering itself off? First and foremost.. when weird things are crashing, perform a memory test... Let it run for a few hours or overnight. Make sure the voltage setting, and timing, and clock frequency are all set properly. (Hint.. many bios get it right with today's RAM, just as many do not) Joe L.
May 29, 200917 yr Is the server crashing... or powering itself off? If it's powering off then it's something to do with the power supply or a cable end. What is the "other" power supplies you tried. I looked at the rosewill 500watt supply and see it specified as +12V1@18A, +12V2@16A, Maybe this new board and/or video card pull more power. In my experience over the years, if a machine powers off on it's own when operating heavily, there is a power supply issue. If the machine freezes, it could be power supply, bus or IRQ issues. I;ve had issues where I had to turn off certain Kernel ACPI configurations to keep a system stable, However, it's caused lockups not power issues.
Archived
This topic is now archived and is closed to further replies.