Welcome To Australia's No.1 Media Center Community!
You Are Currently Viewing As A Guest - you'll need to register in order to participate in our community and make this annoying message disappear!
By registering you'll be able to post & reply to questions, set up your own image gallery & blog, communicate privately with other members, create & respond to polls, access downloads and other "members only" features.
Registration is fast, simple and absolutely free so why not join our community today - you'll be glad you did!
For any problems with the registration process or your account, please contact support.
Attention All Brisbane & Gold Coast Members!
Markc3012 has created a local user group for members living in Brisbane & the Gold Coast with the goal of creating a network of users to assist and support each other through information exchange and direct support.
Please see this post for more information and to join the group.
Hi All
Well i've got my WHS system up and running. Well sort of anyway.
My system:
Case: Lian Li PC-201B
PSU: Thermaltake 750W
MB: Gigabyte GA-EX38-DS4
CPU: Core2 Quad 6600
RAM: Corsair 4GB PC-6400
VC: Gigabyte GV-NX73G256D-RH
RAID CARD: Highpoint Rocket Raid 2340
Can't think of anything else. Let me know if i've missed something.
The issue i'm having revolves around the Highpoint raid card. I can't seem to get the system to sleep/ standby or hibernate whilst the card is active. I have the Lights Out add-in installed and have diasbled the SBCore successfully. I have tested the system without the card installed and with the card installed but without it controlling any hdd's and the system is faultless. Sleeps like a baby.
I originally set up the OS using two Seagate 250GB hdd's in Raid0 running off the 2340 card and this is where i first came across the problem. After much mucking around trying to get the bloody thing to sleep, i got it into my head that for some reason it's not wanting to "sleep" the card because the OS was running off it. So i changed the setup to what it currently is - same two drives running in Raid0 off the motherboard. Attached to the 2340 is 4 x 500gb and 3 x 320gb drives. Each drive has been configured at a JBOD raid level so the card can present each drive as a seperate drive to the OS. Have tried it with all the drives pooled into one JBOD array as well, but i get the same results.
When trying to put the system into standby, it has a think about it for about 2-3 seconds then snaps itself out of it and presents the following error message:
"System Standby Failed. The device driver for the "RocketRAID 2340 Controller" is preventing the machine from entering standby. Please close all applications and try again. If the problem persists, you may need to update this driver."
I have the driver updated to the latest version from Highpoint and have changed pretty much every available option in the cards bios.
I'm figuring that if i can get around this sleep issue i can probably go back to my original (preferred) configuration.
At my wits end, any help will be more than appreciated.
Caution It is highly recommended that you not use hardware RAID technologies for your home server. Recovering from hard-drive failures becomes increasingly complex when hardware RAID systems are used. The recommended approach is to use multiple hard drives that are configured as Just a Bunch of Disks (JBOD).
So are you saying i should just give up because Microsoft says it is not recommended because of difficulties faced when trying to recover from a HDD failure? As i said in my above post I have purposely configured each seperate drive as JBOD (as recommended by Microsoft in your extraction above) to sidestep any potential failure issues. eg 5 x drives = 5 x JBOD's presented to the OS.
I did fail to add that i've tried installing the the OS on a single drive, so as to rule out the raid0 set up being at fault. Same probs when trying to sleep though.
Not at all, it's just that as they do not officially support this, there is the potential that the hardware RAID in some way affects your sleep (possibly to do with load balancing).
Also, this does seem a belt and braces approach. WHS with file duplication ensures that duplicate files are kept on different drives to protect against hardware failure (kind of like RAID 0), so putting RAID 0 over this does seem a bit of over-insurance.
You've got me scratching my head now GlenR! I thought WHS was more like raid1? When the file duplication is switched on it creates the same file on a different drive to prevent loss of data if one drive fails. Raid0 splits that same data over 2 or more different drives and a failure in either results in total loss of data. I've gone raid0 on the OS drive to increase read/ write performance, or at least that what i intended to do.
I wonder how it reacts under XP? Different OS=different drivers.........might be worth a test?
I have had a nightmare with sleep and no longer use it. (pun intended) Most people will say that WHS should be 24/7 but I totally disagree! I have made several postings on how to get WHS to be less energy hungry. These were both here and on the Microsoft WHS connect forum. It is fascinating at all the different opinions you get about energy saving. In the end I gave up with sleep and used the BIOS to turn the machine on at a specified time for backups, and WOL when it is off! To turn WHS off, I use the inbuilt at command with shutdown as documented in the link below.
Sure my approach is not perfect, but it is better than nothing, and it does what I need it to do! It may be suitable for you even with your hardware.
If you ever find a solution to WHS sleep, I would love you to let me know!
I just checked my link from last year that I gave you to check the at command, as I suspected it may have been wrong!
I tried to add the following, but the thread was too old to allow additions!
Here it is.
Update to the above listing!
When I wrote the at command listed, I was away from home and did it from memory, as I could not check my computer!
So this is not correct:
at 9:00 /every:m,tu,we,th,fr shutdown -f
In checking my server at command, it should be:
at 9:00 /every:m,tu,we,th,fr tsshutdn /powerdown
You can of course make it every day if you wish
at 9:00 /every:m,tu,we,th,fr,sa,su tsshutdn /powerdown
