Drive letter disappear after reboot

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?

sibbil said:

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?

No I haven't checked for a driver update... I think I'm just going to bail until the next time I do a disk upgrade.. lol

nick james said:

sibbil said:

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?

No I haven't checked for a driver update... I think I'm just going to bail until the next time I do a disk upgrade.. lol

Well that's fine, I guess. But I think I would worry about why something is not working the way it's supposed to. Especially when it comes to storing my data. Do you have backups of the data on that RAID1?

sibbil said:

nick james said:

sibbil said:

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?

No I haven't checked for a driver update... I think I'm just going to bail until the next time I do a disk upgrade.. lol

Well that's fine, I guess. But I think I would worry about why something is not working the way it's supposed to. Especially when it comes to storing my data. Do you have backups of the data on that RAID1?

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!

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?

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.

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.

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.

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?

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.
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.

F5ing said:

nick james, post back if you've still got this problem. I've got something else in mind to check on.

Sorry I was so late to respond- I have left the problem as is until I find another hard drive to back the RAID on too

grimacedface said:

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.

I'm having a hard time following what your saying. I read it as you changed the drive letter and Windows started recognizing it upon restarting it?

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.