Asked by:
No Access to Files on a Shared Folder, and Hard Drive Failure

Question
-
I experienced a hard drive failure, but fortunately I have enabled folder duplication on all my shared folders. I have installed a 2nd Home Server (HP) and am trying to copy my files from my 1st Home Server to the 2nd one. During the copy process, I get errors on files that say either the file is not available or the device is not connected. I have tried rebooting the server, but those files still remain unavailable. I can see the icons for them just fine, but whenever I try to open the file or copy it, I get the error. According to my console, all my shared folders are Healthy. I've also noticed that my Storage Tab continuously states it is Calculating Sizes....
Thanks for your help.Sunday, March 15, 2009 11:53 PM
All replies
-
ATJ3 said:
I experienced a hard drive failure, but fortunately I have enabled folder duplication on all my shared folders. I have installed a 2nd Home Server (HP) and am trying to copy my files from my 1st Home Server to the 2nd one. During the copy process, I get errors on files that say either the file is not available or the device is not connected. I have tried rebooting the server, but those files still remain unavailable. I can see the icons for them just fine, but whenever I try to open the file or copy it, I get the error. According to my console, all my shared folders are Healthy. I've also noticed that my Storage Tab continuously states it is Calculating Sizes....
Thanks for your help.
Did you remove the drive from the server through the WHS Console?Monday, March 16, 2009 12:04 AMModerator -
I tried to remove it, but it says I may lose files permanently, and so was a little hesitant to do so. Should I just go ahead and remove it?Monday, March 16, 2009 12:17 AM
-
ATJ3 said:
I tried to remove it, but it says I may lose files permanently, and so was a little hesitant to do so. Should I just go ahead and remove it?
Before you do that, can you check the component numbers of your server (Settings button, Resources tab) and post them here?Monday, March 16, 2009 1:36 AMModerator -
Windows Home Server Console: 6.0.1800.0
Windows Home Server Backup & Restore: 6.0.1800.36
Windows Home Server Drive Extender: 6.0.1800.24
Windows Home Server Remote Access: 6.0.1800.0
Windows Home Server Storage Manager: 6.0.1800.24Monday, March 16, 2009 1:47 AM -
ATJ3 said:
Windows Home Server Console: 6.0.1800.0
Windows Home Server Backup & Restore: 6.0.1800.36
Windows Home Server Drive Extender: 6.0.1800.24
Windows Home Server Remote Access: 6.0.1800.0
Windows Home Server Storage Manager: 6.0.1800.24
Good, you're up to date. :) It should be ok to remove the drive through the Console (at that point, the secondary shadows will be promoted to the primary shadows and your error messages should disappear). However, if you are concerned, you could always shut down the server, disconnect the failing drive (if it's still there), then power up the server and perform the removal. (This way, you would still have a copy of whatever files can be salvaged on the failing drive.)Monday, March 16, 2009 2:40 AMModerator -
I tried removing the failed drive, and I got the error saying File Conflicts Prevented the Hard Drive Removal.Monday, March 16, 2009 3:32 AM
-
ATJ3 said:
I tried removing the failed drive, and I got the error saying File Conflicts Prevented the Hard Drive Removal.
Is the bad drive still connected to the server? If so, you should power down the server, unplug the drive, then power up the server and try the removal again. If the drive is no longer connected and you get that error, you might want to file a bug report on Connect.- Edited by kariya21Moderator Monday, March 16, 2009 4:54 AM added hyperlink
Monday, March 16, 2009 4:53 AMModerator -
Yes, the drive is not connected and I still get the error. I will try to report the bug.Monday, March 16, 2009 2:41 PM
-
I'm going to need a little helpe navigating where on Connect I should be reporting a bug for this. Any suggested paths?Monday, March 16, 2009 2:46 PM
-
Once you've registered on Connect, you will follow the link kariya21 provided, then select "Feedback". You will have to perform a search to see if there are any other product suggestions similar to yours; perform a search and then choose to create a new bug.When you submit your bug, provide a server CAB # (collected using the Windows Home Server toolkit). Microsoft will review the bug report and get back to you with any questions they may have. If they don't get back to you within a couple of days, that probably means that the bug is an obvious dulplicate of one they already have. Eventually they'll update your bug with that information. :)
I'm not on the WHS team, I just post a lot. :)Monday, March 16, 2009 3:17 PMModerator -
ATJ3 said:
I tried removing the failed drive, and I got the error saying File Conflicts Prevented the Hard Drive Removal.
Do you have any clients that are watching shares on the server or do you have any files open when trying to remove the drive?
Usually it's a File is Open conflict.
Thanks
Lara Jones [MSFT] | Program Manager
Community Support and Beta | Windows Home Server Team
Windows Home Server Team Blog
Connect Windows Home Server
Windows Home ServerMonday, March 16, 2009 4:41 PMModerator