Saved for later reference

online repository of stuff I had to google for hours to figure out – and random snippets of code

Fixing a RAID1 that suddenly becomes write protected (64 bit Windows)

Tags: , , , ,

Today, after rebooting from some Windows updates, my RAID1 disk suddenly was write protected – but a way to change it was nowhere to be found. After some digging, I found that others have reported the same problem.


As far as I can tell, it seems to be a weakness in the 64-bit drivers for the on-board RAID on some motherboards that causes it. For the record, mine is a Gigabyte GA-EP45-UD3P, and I’m running Windows 7 RC (7100) 64bit, but it seems to be reported for all 64 bit versions of Windows.  Anyhow, the fix itself is simple, and seems to stick over reboots, and hopefully it’s permanently fixed.

Fixing the problem

To solve the problem, we need to open an elevated command prompt; in both Windows 7 and Vista, you do this easily by hitting the Windows button, typing “cmd”, right-clicking the “C:\ cmd” search result, and selecting “Run as administrator”. In Windows 7 you can also find Command Prompt in the Start menu and Ctrl-Shift-click it, to open it elevated.

(Disclaimer: The DISKPART tool can potentially remove/create partitions on your hard drive, so be 100% certain what you’re doing before you hit Enter)

In the elevated Command Prompt, type “diskpart” and press enter:

C:\> diskpart

On the diskpart prompt, list your volumes:

DISKPART> list volume

In my case, the volume on my RAID was volume 4, so I selected it:

DISKPART> select volume 4

…and then I marked it writeable like this:

DISKPART> attributes volume clear readonly

Here’s the entire segment in a screenshot (note that I did a couple of extra steps selecting the disk, this is apparently not necessary):

DISKPART commands for removing read-only

DISKPART commands for removing read-only


Tags: , , , ,

© 2009 Saved for later reference. All Rights Reserved.

This blog is powered by Wordpress and Magatheme by Bryan Helmig.