Readonly volume on Windows Vista and Windows 7 reboots

Approximately every time I reboot my computer I got drive D: in read only mode.
To turn read only mode off I run the following:

1) Open RUN (Win button + R button)
2) cmd
3) diskpart
4) select volume d
5) attributes volume clear reaonly

Sometimes this still does not work and I'm doing 5) several times until it works.

The main question is: what needs to be done so that every time I turn on my computer to see read only turned off?

Optional question: why do I need to do 5) several times.

Optional question: is in general RAIID from Motherboard reliable? I'm using frequently Visual Studio (like a text editor) and I'm used to make a lot of saving (Ctrl-S) over short periods. During these short periods I am prompted with a Save As... file dialog because it seems that the file is blocked. I'm sure that this is not from Visual Studio because I use it also at work (no RAID) and it does not give me Save As... dialog. If you consider that MB RAID is a bad idea then can you propose a better solution (for budget ~100$)?

I'm a web software developer (ASP.NET) and I'm not familiar with system administration.

My system config:
MB: Gigabyte 965P-DQ6
HDD: 2 x WD RE3 250GB (RAID 0 - from MB) + 1 x WD 2500KS 250GB
OS: Windows 7 x64
CPU: Intel E6600
RAM: Kingston 6GB (dual channel)

HDD Partitions:
C: and D: on RAID0 --> D: volume is the problem here! C: works and has Windows on it
E: on WD2500KS

Let me know if you need additional system details or other things.
This is a problem reported, not so frequently, across some forums but I haven't seen any solution until now. So I'm still keeping in writing those lines.
I encountered the same problem on Window Vista so this is the reason I wrote also Window Vista in addition to Windows 7.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I have done some digging around and found that certain RAID controllers (Promise and JMicron) cause the issue you are talking about.  You might want to check with the motherboard vendor to see if there are updated RAID controller drivers.  If not here was a way to "fix" your issue without you having to manually do it each time.  The site below talks indepth of users having the same issue.  In one part one of the users created a batch file that checks the state of the drive and if is read-only changes it, if is normal, then skips the steps.

I'm having the same issue, although I didn't use a jmicron raid controler but a promise tech one.

I figured to create a workaround, that doesn't bother me with having to mount the volume each time i start.

I created a batch file, which checks whether or not the volume is read-only and dismounts it if neccessary.

I named this batch file "programme.cmd" and saved it in my user folder, it mounts the drive with the letter p.
The source is as following:

@echo off
echo test > p:\p_test_file.tmp
if exist p:\p_test_file.tmp goto ende
fsutil volume dismount p:
goto mount

del p:\p_test_file.tmp

After that, I created a task that starts the script each time windows starts up (autorun shortcut won't work due to missing admin privileges). I followed the instructions on to do that.
As action (Figure F) i choosed to start the program cmd (C:\Windows\SysWOW64\cmd.exe in my case) with the parameters
/C ""C:\Users\MY USER NAME\programme.cmd"

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
omacarenaAuthor Commented:
Thank you. You've confirmed my doubts about RAID being the cause of all these. I've searched the vendor and I found a release from 2009 (though the driver is from 2008) but still is newer. I think that now I have all info to solve my problem. I installed the new controller driver and now I'm waiting for this problem to occur.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.