Cessquill

Installed two more drives in the machine yesterday. Whilst it was clearing it crashed, so I re-ran it using the tail -f /var/log/syslog > /boot/syslog command. Find attached the results. Does it say anything? Fortunately, the machine is now at work, so it's easier to get up on the bench and work on.

Thanks for that. I don't know where the parity errors are coming from yet - good point. I left memtest running for the weekend. It got through 173 times with 0 errors. This is at work though and it was crashing at home. I've just added two more drives so I'll start putting it under load again and see what happens.

Hi speeding_ant - quick question (or anybody else running this board in an unRAID system)... What other hardware are you running in your build. I'm getting quite a lot of lockups on mine when writing to it (one every day or so), and several parity check errors. Trying to nail down if any of my hardware is faulty/incompatible. Thanks

I have done exactly the same thing, and wondered what was going on. Oddly enough my machine has been up for a few days now without problem, although I'm only copying files via an old machine with pre-USB2 interface. Hopefully over the weekend I'll lift the lid and see whether all cables are snug. I'm a bit worried that it's a general incompatibility with the motherboard (although I did clear it with another user on here, so I'll check what memory/power supply they have).

By the way, are you the same yodine from the MyMovies forum?

Thanks again Joe. Yes, that's the tail command I've left running in the background, and as far as I can remember it hasn't listed anything after a ROOT LOGIN line. It's running again now though, so I'll see what happens later. All mounting screws were used when building, but I can't vouch for the quality of the PSU - one that came with the case.

After a disasterous weekend, I'm still none the wiser (disasterous, since I got two windows mixed up and emptied one of the drives, Anyway...) - I've been keeping the tail command open in a telnet window, and it's not reporting anything, right up until a kernel panic. Should it show anything? - I had it copying files for a whole day without failure (albeit rebooting several times, and only copying from one location) - On other occasions, it can crash out on me straight into a kernel panic half way through the first DVD copy - When I'm copying it's always off a USB drive on a networked machine, and it's only ever a couple of DVDs at a time (max 7). Sometimes it'll copy the lot, sometimes it'll stop at any point in between. - When it works, it's working fine. When it crashes, it's going straight to kernel panic without letting me create a syslog I'm not sure whether this is of use to anybody - I'm partly thinking out loud here Should I copy as much as I dare, then create a syslog?

It seems to have been stable for the past 24 hours, which it hasn't done before. Over the weekend I'm going to see if I can delve in a bit deeper, Since I'd just like to be able to throw stuff at it, and it copes (or at least doesn't fall on its back). Adding two more drives next week too. I was following your threads too, yodine, for exactly the same reasons.

OK, I've got that running over telnet now. I've just started it on a 13 DVD copy which normally angers it. I let the memory test run through 1 1/2 times last night - is there any worth in leaving it on for a long time?

Thanks for your patience guys - I'll look into the tail commands when I get home. Find attached a syslog taken just now (via RDC->telnet), just at the end of copying 4 dvds over the network.

Thanks - I've read that, and I'm currently waiting to get a syslog. Now I've got a screen and keyboard on the machine it'll be much easier. I had meant to put that in the previous post, but forgot - sorry. However, I'm assuming that taking a syslog after a power cycle or before the problem starts will not be of much use? I'm copying over files and trying to catch the system in a crashed-but-not-frozen state. Unfortunately, the last couple of times have been whilst at work or in bed. Have I understood correctly - apologies if not. I've gone round and round reading so much information recently.

Thanks for that guys. Apologies for the delay in getting back to you, the unRAID server is in a rack under my stairs with no keyboard or screen. I've therefore had to do a lot of shifting about. I've disabled user shares. I'm only copying from one location at a time. I'm copying to either \\tower\disk1\dvds or \\tower\disk2\dvds. I ran memtest and it passed fine. It's still going down around once a day, and when I looked at the screen last night, it was locked up completely (see attached photo - sorry, it's a bit of a mess!). Haven't been able to telnet into it since the original post, but now I've got a screen/keyboard there I can keep an eye on it. Kit is... Gigabyte GA-G33-DS3R motherboard Intel Pentium Dual-Core, E2180 processor 2GB (2x1GB) Corsair TwinX XMS2 DDR2 memory 3 x 1TB (1000 GB) Western Digital WD10E (green power) drives GAH! Thanks

Ahh, thanks. I'll do that.

Thanks for that guys - very helpful. I performed a manual restart on this occasion, but I'll post a syslog up next time. Something's not right, since it's happening quite often. Hope it's not memory, since there's 2x1gb in there.

Hi - bit of a noob question, but... I'm copying lots of files to my new unRAID server from various machines on the network. Twice now I appear to overloaded it, whereby I can't reach the server from the web interface or network browser. However, I can still ping and telnet onto the box. The first time I turned it off and on again, which obviously sparked off a parity sync. It's now sitting there again, and I'm wondering whether there is a clean way I can restart it? Be gentle - I know nothing about linux!

Believe me, it's all productive for an unRAID (and linux) noob. You guys have saved me about $100 from the first spec I put together, which is a big deal to me. Thank you

WOW! Thanks guys That's given me a load to look into. I've built my share of machines in the past, but never gone to *that* much trouble in eeking out every bit of performance. First unRAID system though. I am planning on getting 2x1mb sticks initially, and whilst the hop up from 800 to 1066 is only about £15 ($30?), it all adds up when you're building a new system - I'm also re-evaluating my CPU to try and shave some more off. I'll have another look around later. Thanks again - I'll have a good read up.

Would there be any noticable difference between 800 and 1066 DDR2 Memory? Putting together a fairly low cost setup, but don't want to cut the wrong corners...

I'm running that board in my box, and it runs wonderfully. No need for a separate NIC or what have you, it works well out of the box. Has great features, and has been wonderfully stable for me over the last 4-6 months. It has my recommendation. Thanks for that - order going in today

Hi - just to confirm, the network port on this board works fine with unRAID? I'm looking at this one for my first build, and the 8xSATA ports and onboard VGA are a big pull. It's also available in the UK. Thanks, Simon