Windows 7 - Slave HDD Write Protected

rjtaylor · 10-26-2009

Hey,

After EVERY boot since installing Windown 7 64 (previously on Vista 64 with no issues), slave hard drive goes in to read only mode..
After EVERY boot, I have to use diskpart to clear readonly status.

While diskpart sorts the isse on a temp basis, its a real pita to have to do it on every boot. Any ideas on the cause of this issue so it can be resolved once and for all??

Thanks.

torrentg · 10-26-2009

Copy everything you need off of the drive to another one. Format the drive to NTFS using "quick." Replace files and folders on the drive.

That's the quick and dirty way to proceed on this one.

Before you format and after you copy stuff off of it though, open an elevated command prompt. Type takeown /f D: and hit enter. Change D to the drive letter of the HDD. See if this fixes first.

rjtaylor · 10-26-2009

Thanks - giving it a go now - will let you know if this fixes it...

rjtaylor · 10-26-2009

Nope, just the same. First reboot after format and its read only....

Its weird - when in read only mode won't even play mp3's in itunes??

**Jordus** · 10-26-2009

Were you screwing with the drives in the case before you installed 7?

Is it possible you changed a jumper on the drive to set it to read-only?

Would have to be a pretty old drive to have this but its possible

rjtaylor · 10-26-2009

Quote: Originally Posted by Jordus

Were you screwing with the drives in the case before you installed 7?

Is it possible you changed a jumper on the drive to set it to read-only?

Would have to be a pretty old drive to have this but its possible

No, didn't even go in the case....

torrentg · 10-26-2009

I know this sounds like a pain after your efforts and it is not guarantee of anything good, but you can try the above only with a low level format instead.

rjtaylor · 10-30-2009

Just in case anyone searches this post with a similar problem... rolled back the IDE controller drivers from the mobo manufacturer version (abit for the IP 35 PRO) to the default M$ drivers. Has been stable for a couple of days now so looks like it is resolved...