This morning I woke up to this:
Not something anybody likes to see. If this happens to you, these are the steps you need to repair the situation:
- Click on the Server Storage Tab in the Windows home Server Console.
- You should see on of the drives with a status of "Unhealthy".
- Right click on the drive and select Repair (or highlight the drive and click the Repair button).
- You should see the following dialog box:
- Click "next" and you will see a scary looking screen something like this:
- Click "Finish" to begin the repair. Thee screen said that this could take "several minutes" when in fact this took me about 14 minutes (I consider 2 to be "a couple" and 3-7 "several").
- When finished you will be prompted to reboot.
After several minutes, and a lot of red flashing from my HP EX470's "health indicator" LED, the systems comes back to life. If you look at the Server Storage tab now, you should see a status of "Healthy".
Hey Microsoft. How about a hot link on the initial error message that would launch the Repair Wizard directly. Remember that this is for home users. I'm sure that the instructions "run Repair" are not enough for Mom and Dad to figure out.
**** Update ****
There is some speculation on the Windows Home Server MSDN forum that this is caused by a faulty UPS. I'll keep you informed as things progress.
Stumble Upon
Bookmark on Microsoft Social
Subscribe to RSS
7 comments:
You may want to check your event viewer on the WHS box. I have not installed any plugins or made any non-standard configuration changes and I have an HP EX470, and since January have been getting that message at least once a week. For me the message is issued because of a memory leak in the Volume Shadow Copy Service that is part of Win2003. Everytime I get that message there is an event in the event viewer in the system log that says the VolSnap had to abort because there was not enough memory avaliable. I no longer click the repair button, I just reboot the WHS box and everything is fine. But it really sucks for me to have to reboot my home server a couple times a week. I did some searching and found that there was a memory leak in VSS on Win2003 that has a patch avaliable, but I've not attempted to patch it, hoping that the issue will be resolved with the next patch for WHS. I had at one point enabled shadow copy on the data drive, but since then I have disabled that. Before I disabled it I was getting the message almost daily.
Are you still getting the message since disabling the VSS service again?
I have also received 3 of these messages. About once per week. After the 3rd time I contacted HP support. They had me download some server tools and addin to the mediasmart server. I created a log and then emailed it to them. I'm starting to notice that there seems to be an association between ripping music and advanced tag editing with WMP. I have no UPS.
This morning (3/23) I got the error message again. I haven't done anything to the server all week so I think the Windows Media player is not involved.
Will, I still get the message. I did not disable the Volume Shadow Copy service, I set it to manual. Right this second it is not running, but I rebooted the PC earlier today because it got the message again, so something must turn it on at some point. I was afraid that if I disabled it then it would not allow the server to function properly. What I did disable was shadow copies on all the drives. I can't remember, but I don't think I did anything to the VSS service when I originally turned on the shadow copy, I think I just had to check the drive to tell it to shadow copy that drive. The tutorial I followed was from We Got Served and it is no longer there, so I don't remember the steps I took.
I have recently migrated to a mediasmart server. Ever since, I seem to get this message about every week as well. Not just the sys volume, but the other two drives I added as well.
I had never seen this error before on my old home-built whs. One thing I will note is that it seems to come up any time I make a new album or add pictures to the Photo Webshare. It may just be coincidence however...
yep, reboot solved it. Must be the UPS. Will monitor and report.
Post a Comment