Error: Storage Status
- Suddenly has appeared this message: Storage Status - Volume with name Primary Volume is failing. Please try to run repair to fix errors for disk ST3320620AS
But when i go to the Contro Pannel and Storage Manager everything seems to be ok.
CAB 352223776
Any help?
Regards
All Replies
- Yeah, I've gotten that message too regarding my primary drive. Then it goes away. It only happens when I reboot and not every time either. Not sure if it's because the WHS may take too long to boot or data transfer is slower than it expects or what. Ken Warren may be able to shed some light on it.
Personally, I've just ignored it. My 200 gig primary is fairly new. Besides, I have two new WD 16 mb cache, 500 gig drives coming in from NewEgg on Monday. So, I'll be replacing both drives in WHS with these new WD drives. Then I'll see if I get the same message or not.
Any ideas??? I'm having similar problems.
I've just completed a "restore", replacing an 80gig WD primary with a 500gig WD primary. I believe that my last primary volume had genuine problems on the basis of the Seagate diagnostic tools which I ran on it. Both drives are SATA based.
The new primary volume (500 gig WD) has passed all of the tests in the Western Digital Data Lifeguard diagnostics........ and yet I receive the following error.
"Volume with name primary volume is failing. Please try to run Repair to fix errors for disk WDC WD5000AAKS-07TMA0"
I'm not quite sure who to believe here.
Note: The PC is a Dell Dimension 8400. I have two of them, and I've never seen these issues on the other unit (which is currently running my Vista Media Center).
- Fully,
What version of WHS are you using? Here's the version information.
Windows Home Server Console: 6.0.1500.0
Windows Home Server Backup & Restore: 6.0.1500.6
Windows Home Server Drive Extender: 6.0.1500.0
Windows Home Server Remote Access: 6.0.1500.0
Windows Home Server Storage Manager: 6.0.1500.0Since I've posted, the error message has gone away. (It stoppped after a reboot.) However, it has repeated twice so far and I suspect that it will happen again in the future.
- Are you sure about those version numbers? They should all be 6.0.1500.6.
Yes, they were copied directly out of the WHS console. Also, all of the Microsft Updates have been applied.
- Hmm. When did you receive your media, and is there a date marked on the disks? Supposedly, the update was included on all disks manufactured after 9/21 (I think) and I can tell you that on the test server I have set up with RTM installed (I haven't built a production server yet) everything is at 6.0.1500.6. I'm suspicious of whether you might have a version mismatch between components.
Hmmmmm... perhaps I need to apply the "update package" / hotfix? It looks like the appropriate file version info is on the files in that package.
An update package is available to improve the setup and configuration of Windows Home Server
http://support.microsoft.com/default.aspx?scid=kb;EN-US;941913My CD came from a boxed copy of WHS. Genuine media..... certainly looked RTM to me.
- Fully
I have the same Primary failure errors, and I have the same resource versions (the .0 not .6) I get "Update does not apply to installed version" error when I try and run the hotfix. I have the RTM official copy, Genuine Media.
Ian
I get the same thing. I'm running a version with disks dated 9/27. I had none of these problems with the earlier release (beta 2, etc.) As soon as I finally get the RTM release (and drop my $s for it) I'm having this problem along with a few others. I have 2 brand new drives in my machine so I tend to believe it isn't the drives. I justed started seeing this with the latest release.
Very frustrating... if you can't feel comfortable with your backup software (the primary purpose of this OS) than what good is it.
