Plimsoul

Thanks, Joe Yep, there's a Dell involved.

I've been noticing the following syslog entries at almost exactly 10 minute intervals, for example: Jan 27 15:54:18 Server unmenu[1358]: bad method - 15619 29590 276657 8863510 15072 8184 186048 14115260 0 216840 2297877015619-^M Jan 27 16:04:29 Server unmenu[1358]: bad method - 15619 29590 276657 8863510 15072 8184 186048 14115260 0 216840 2297877015619-^M Jan 27 16:14:30 Server unmenu[1358]: bad method - 15619 29590 276657 8863510 15072 8184 186048 14115260 0 216840 2297877015619-^M Jan 27 16:24:47 Server unmenu[1358]: bad method - 15619 29590 276657 8863510 15072 8184 186048 14115260 0 216840 2297877015619-^M Apart from adding lines to my syslog, is there any harm here? If anyone has solved this, what is up? Thanks!

Well, I aborted the first preclear while it was still writing 36 hours later at about 10MB/s. Then took out the other drives and moved this guy to a slot in the rack that successfully supported another drive's preclear. Started another preclear session and now, 23 hours later, it is only 24% done with the Disk Pre-Read at 3.5 MB/s. Guess it is back to Newegg with this one! The syslog and SMART reports don't seem to show any obvious problem.

Started to preclear 3 drives (2TB Hitachi & two 2TB WD20EARS) at the same time. The Hitachi and one of the EARS seem to be progressing nicely, but the other EARS is really, really slow. We're talkling 12 MB/s on Step 2. I'm thinking this isn't normal. This is a new build with the Sempron 140 and the drives housed in the Supermicro 5-in-3 rack. I did jumper the EARS drives before installation. Is there anything I can do to diagnose this before the preclear script finishes? Thanks