jimwhite
-
Posts
597 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by jimwhite
-
-
I could probably use a spare... count me in.
-
Anything but Debian or Debian based distros like ubuntu !!
-
Turn Your server off and go get a life!!!
-
Log on to the server as root.
Then type: MC and hit enter...
-
I'm old and very patient
-
Please report back!
-
The "silver" stuff is tin-plated copper.
-
Why not use it? There doesn't appear to be anything wrong with it.
-
Update the firmware first. Do a search and you'll find a thread with the links to the firmware. I used the Japanese version since it changes the firmware number, the English one doesn't.
-
It's all about the instant gratification generation.... sound like spoiled teenagers.
-
Point made.
-
A drive is only red-balled if a write to the drive fails. You can argue or believe anything you want but that is still the way it is.
What do you base this on ??
-
I think it would be more useful if parity check speeds were accompanied by the number of drives in the array.
-
What do we have here... two versions?
-
Thanks Peter. Now I can try b14 with my LSI 1015's !!!
-
Yeah, drives being red-balled when waking up.
On LSI controllers
-
Any Samsungs in the drive pool?
-
Again you're asking when? !!!
-
If you're going to spam the board, at least learn some grammar/spelling!!
-
Be prepared for "May Grey" and "June Gloom"
-
Yes, the driver doesn't exist in the kernel used in 4.7
-
I had a lot of trouble with both Crucial and Corsair. Went to CAS-6 400mhz stuff off the wall at BestBuy and had no more problems....
-
FWIW, this board is one of the few of its generation that will run reliably with all four slots populated.... I echo the suggestion for an older version of memtest or try memtest86+ or whatever... I remember running memtest on mine when I had it, so don't give up!
-
The answer is the Samsung drive. I upgraded my server to two M1015's and 16 Samsung 2TB drives. Initially, (running Beta9) when the drives were always awake as I was moving data I had no problems, but once I set the drives to spin down after a short time, most times I went to access a drive, it red-balled. Going through a divorce, down sizing and then moving, so I just turned it off in hopes that the kernel issues with LSI controllers highlighted in the Beta14 thread would eventually solve the issue. I had no issues with the previous Seagate drives. I REALLY hope this issue gets solved or I'm in deep shit!
OSX VM ?
in Virtual Machines - Xen
Posted
GOOGLE is your friend...