Answered by:
Add Hard drive failed

Question
-
I have two 500GB eSata drives that I am trying to add to my storage pool. I am receiving the same error with both drives
"Hard Drive initialization failed.
The Wizard was unable to create a volume on the hard drive."
I have tried this with both AHCI enabled and disabled. In both cases the same error occurred for both drives. I also tried attaching the drivers to the USB port. I received a similar error with both drives.
Anything I can try to get this working?Thursday, July 31, 2008 3:29 AM
Answers
-
I am able to format the drives in the WHS machine through disk management. Whether or not they start formatted doesn't seem to affect the outcome of the wizard.Thursday, July 31, 2008 4:43 AM
All replies
-
Mathew wrote: I have two 500GB eSata drives that I am trying to add to my storage pool. I am receiving the same error with both drives
"Hard Drive initialization failed.
The Wizard was unable to create a volume on the hard drive."
I have tried this with both AHCI enabled and disabled. In both cases the same error occurred for both drives. I also tried attaching the drivers to the USB port. I received a similar error with both drives.
Anything I can try to get this working?You might try hooking it up to a client PC and formatting it using NTFS first.
Thursday, July 31, 2008 4:32 AMModerator -
I am able to format the drives in the WHS machine through disk management. Whether or not they start formatted doesn't seem to affect the outcome of the wizard.Thursday, July 31, 2008 4:43 AM
-
Having the same issue - did you ever resolve?
I have a total of 9 drives as a part of the windows home server. All of them added and working fine except for this one 500GB drive. Brand new drive. Formats and works fine other than adding to the home server array - any thoughts?
DorkboyTuesday, October 14, 2008 12:39 AM -
I am also having the same issue with a 1TB Seagate drive.
This has been going on for months now and I've just been ignoring it, even though I've had a constant Critical Error for the last 6 months telling me that "Volume with name DATA has failed. Please check hard drives and try to run Repair to fix errors for disk Seagate ST31000340AS SCSI Disk Device."
Originally I think the problem occurred when I put the 1TB drive in a shelf on my Sonnet D5P eSATA enclosure (pre PP1); turns out that enclosure does not support 1TB drives (my bad; now I have 5 750GB Seagate drives in it working just fine). Since I couldn't add it to the pool I moved it inside the server (Dell PowerEdge SC440) on the Drive 1 channel of the primary SATA controller and have been using it as a server backup drive (since PP1) with no problems whatsoever. I've recently replaced this backup medium with two 500GB USB drives inside a fireproof safe (yes, paranoid), so I've once again been trying to add this disk to the storage pool . . . with no luck. I've spent many hours on this--reformatting it, moving it to other PC's, other enclosures, etc.; I know the drive is fine . . . but the Home Server just won't take it. I have two others of the identical drive (but 6 months newer) installed in an Icy Dock MB561S-4S eSata enclosure and they were ingested to the pool with no problems and work fine (of course I did try the problem drive in the Icy Dock, to no avail). The error message I get when I try to add the drive is:
The hard drive was not formatted
The hard drive was not formatted because it is being used by another program or service. Restart your home server and add the drive again.
Of course I've reformatted, rebooted, etc., countless times. There is no way the drive is being used by another process. For kicks I changed the name of the volume from "DATA" to "STX 1TBA" at one point, and now, in addition to the months-old critical error message noted above for volume DATA, I have another identical critical error for volume "STX 1TBA." (I have a total of 10 other drives in the system with volume name DATA that all work fine; the server is not nor has exhibited any actual errors apart from the normal occasional-but-rare file inconsistency here and there). I have 2.4TB of free space on the server right now.
To further complicate matters, when I physically remove the drive from the server (it is out now), it still shows up in the "Server Storage" tab of the Home Server Console under "Non Storage Hard Drives" with status "Missing;" the good news is the two critical errors referencing non-existant volume failures are gone, replaced by one critical error saying:
Seagate ST31000340AS SCSI Disk Device has failed. Ensure it is connected. If this problem continues, add a new hard drive and then remove the failed hard drive from your server storage using the console.
When I try to remove the drive in the Server Storage tab, I get the error message: "File conflicts prevented the hard drive removal." Again, it was freshly formatted (the long, multi-hour way) immediately prior; there can be no file conflicts.
Sorry for the long post; I'm at wits end and would greatly appreciate any help. I can gladly just write off that drive and get on with my life, but I'd really love to see the calming green on my Network Status again!
I'm happy to provide any more information if someone would find it helpful! Thanks
Saturday, January 24, 2009 9:41 PM -
Sorry--writing this finally made me think of checking for firmware issues on the Seagate drive, and turns out there is in fact a problem with the firmware on this particular drive. I will attempt to update the firmware and report back . . . (embarrassed!)Saturday, January 24, 2009 11:41 PM
-
Well, I updated the firmware in the offending drive and spent another hour adding/formatting/deleting/creating partitions, etc., with no different result other than I now have a third critical error (identical to the first). So I write off this drive and get on with my life, no big deal. But since I can't force the server to forget it ever met this drive gracefully, can anyone tell me how to get rid of the critical error messages . . . like, are there registry keys I can alter/delete? Any help would be appreciated!Sunday, January 25, 2009 2:45 PM
-
The supported way to get rid of the errors you still have would be a server reinstallation. This will format the system partition (C:) but will not touch the data in your shares, or your home computer backups. For a reinstallation you should leave all your storage drives connected. You will then have to reinstall any add-ins, recreate users (who will be joined back to their personal shares on the server), and rejoin any home computers to the server. This FAQ post offers a bit more detail on the reinstallation process.
I'm not on the WHS team, I just post a lot. :)Sunday, January 25, 2009 3:17 PMModerator -
Thanks, Ken. I was hoping to pique your interest--you are a legend on these pages.
I've done a server reinstallation a few times, and these error messages (somehow) manage to survive the resintallation process. But I had a strange thought: I'm thinking of yanking my system disk (and setting it aside, just in case), and putting this STX 1TB drive in the driver's seat, then doing a server reinstall using this drive as the system disk. Seems like worst case it should be status quo (as I should be able to replace my orignal system disk and be back where I started), and maybe better. What do you think?
Sunday, January 25, 2009 7:18 PM -
OK, well that didn't work. Got almost all the way through installation then failed on the finalizing stage. So enough of that drive. I was able to pop my prior sys disk in and all was right where I left it. Enough for today but I'll do another reinstall later on . . .Monday, January 26, 2009 4:02 AM
-
Kolars said:
OK, well that didn't work. Got almost all the way through installation then failed on the finalizing stage. So enough of that drive. I was able to pop my prior sys disk in and all was right where I left it. Enough for today but I'll do another reinstall later on . . .
You say it "failed on the finalizing stage". Are you getting an error message? Or does it just appear frozen? If the latter, that is normal. You need to let the process run until you get the Welcome screen (which can potentially take days if you have a lot of data on your server).- Edited by kariya21Moderator Monday, January 26, 2009 5:05 AM more info
Monday, January 26, 2009 5:04 AMModerator -
Thanks; it is an error message, something to the effect of "Windows Home Server installation has failed. Invalid operation . . ."
It got all the way through the W2k3 install then failed installing the WHS overlay. I tried to resume from that point (qi.exe) several times, but no good. I assume that even the new firmware in this drive is still enimical to WHS in some way.
So I just ordered a 1.5TB drive. I figure if I've got to do yet another server reinstall I may as well double the size of my system disk while I'm at it. Hopefully that logic is sound, the firmware in the new Seagate drives is good, and the next reinstall will go smoothly.
So, the current status is that the problem STX 1TB drive (which is no longer physically connected to, nor even in sight of, my server) shows up in the "Server Storage" tab under Non Storage Hard Drives with status Missing. Attempting to remove the drive generates the "File conflicts prevented removal" error message. I am down to only one constant critical error, though, which is the more generic "Seagate ST31000340AS SCSI Disk Device has failed" (the other messages reported above for failed volumes don't appear when the drive is not physically connected).
The last couple times I did server reinstalls I still had the offending drive connected, which might explain why the error messages survived (they may have just been regenerated!). Clearly that wasn't the brightest idea. When I get the new drive in two days I'll do another server reinstall without the problem drive. Hopefully that will do it.
Monday, January 26, 2009 2:23 PM -
I would suggest you consider more drastic measures. I'm not clear on exactly what is going on with your server, but a reinstallation with a storage pool drive missing may be impossible (I've had inconsistent results, though I haven't investigated this extensively), and since the drive is causing issues reinstallation with it present probably isn't going to help matters either.Instead, if possible, can you copy all the files currently in your shares to other storage? (Alternatively you could disconnect all the drives except your system drive.) Then perform a new server installation (not a reinstallation). Then connect your drives one at a time and copy the data on them (found in <driveletter>:\DE\Shares\etc.) back into the shares. Finally, add them to the storage pool again. For the drive that's been giving problems, after you copy the files back into the pool, I would use partition management software (even DISKPART will do the job, if you're familiar with that tool, and it's part of your operating system so it's already paid for) and clean the drive off.
I'm not on the WHS team, I just post a lot. :)Monday, January 26, 2009 4:04 PMModerator -
Thanks, Ken. My new drive was supposed to show up today (it hasn't yet), and when it does I'll try a resintallation without the bad drive connected. It was never successfully added, though it's clear the system thinks it was at one point, and while I suspect there's some replicated drive/file allocation table on all the drives that might be read after a reinstalltion that would allow this error to survive reinstallation, I'm hopeful (naive) that a reinstall using a clean sys drive (without the problem attached)will do the trick. So I'll give it a try. If it doesn't work I'll have to do what you suggest, though I'll probably live with the error message for a while again before I muster the will to go to those lengths . . .
Wednesday, January 28, 2009 11:56 PM -
Try going to a command prompt on the WHS and entering,
mountvol /e
Next return to WHS console and try to add the drive again. Worked for me anyway.
Cheers- Proposed as answer by Richard Sanderson Thursday, May 21, 2009 10:31 PM
Thursday, February 19, 2009 10:32 PM -
Try going to a command prompt on the WHS and entering,
mountvol /e
Next return to WHS console and try to add the drive again. Worked for me anyway.
Cheers
Jimbo,
I had the same issue adding new drives and this solution worked for me. Many thanks for the post.
Regards
RichThursday, May 21, 2009 10:33 PM -
Worked for me too Jimbo. That was the answer!Monday, January 14, 2013 12:48 AM