New
#61
not a lot of options here
not a lot of options here
Yeah, not much there. Have you searched for any supplemental software that supports it?
When you assign the H: drive letter do you see the new key for it in reg's mounted devices?
One odd thing in your last reg screenshot is I don't see a volume entry for that disk. There's a one to one match for every volume entry with a drive letter entry. That seems to say that W7 is not properly recognizing it.
Have you checked for an updated driver for that controller?
I appreciate your help. I too worry about something not properly working but (correct me if I'm wrong) after the POST it shows both of the arrays being healthy. Since I've had this RAID die once before and it notified me at the DOS prompt prior to Windows, I would think that my data is safe, or am I wrong?
After reading what others have done to resolve this issue, I wonder if I were to write zeros to the drives if it would solve the problem? I think its ironic that I didn't have this problem until restoring the RAID.
I haven't backed up this RAID1 but I was considering doing so soon since New Egg had sale on 2.5tb drives for $89. I figure making an external drive and a copy of that raid once a week or month wouldn't be a bad idea, right?
Again, thanks for everyone's input!
Safe, to an extent. That notification after POST that you had gotten was likely a report by the SMART program on the failing HD. SMART is fairly good, but no where near foolproof. HD's fail sometimes without SMART ever notifying the user.I appreciate your help. I too worry about something not properly working but (correct me if I'm wrong) after the POST it shows both of the arrays being healthy. Since I've had this RAID die once before and it notified me at the DOS prompt prior to Windows, I would think that my data is safe, or am I wrong?
That's hard to respond to without knowing exactly how it was restored. But it sounds like something was going on, especially if you didn't have the problem before the failure.After reading what others have done to resolve this issue, I wonder if I were to write zeros to the drives if it would solve the problem? I think its ironic that I didn't have this problem until restoring the RAID.
It would be a great idea. RAID1 alone is not a truly complete backup strategy. It protects against a failing hard drive. Nothing more. If the PC gets zapped by a surge (surge suppressors can't stop everything) both drives could die. If a file gets erroneously deleted or corrupted by a virus, it's mirrored to both drives so it's kaput.I haven't backed up this RAID1 but I was considering doing so soon since New Egg had sale on 2.5tb drives for $89. I figure making an external drive and a copy of that raid once a week or month wouldn't be a bad idea, right?
RAID adds complexity, and whenever complexity increases the opportunities for failure also increase.
nick james, post back if you've still got this problem. I've got something else in mind to check on.
Tried pretty much all of these suggestions as well as reformatted. I have two pyros set to RAID 0 and two WD Blues tb drives. One shows up fine but the other disappears after every restart. The drive letter is the culprit as everytime I give it a new one it comes back to my computer again.
Try using Diskpart to check the volume details to see if the attribute nodefaultdriveletter is set to "yes". If so try changing it to "no" to see if that'll let you set a drive letter that sticks across boots.