Replaced bad drive, now the entire pool is read-only?

[Knocker]

Hi!

So I had a drive going bad (overheating) and entered into RAW state. I tried restoring the partition, without wiping it, but to no luck, so I decided to replace the drive with the same model and then I'll have to deal with the defective drive later on.
I added it to the pool, removed the missing drive and then I wanted to enable pool file duplication, but was met with an error saying read-only.
I'm not sure how I can remove this, so I can enable the file protection and start to re-balance the pool. Googling gave me nothing, so hopefully someone here knows something, that I can benefit from!

[Shane]

Hmm. Try the following from a command prompt run as an administrator:

• diskpart
• list volume

Then for each volume:

• select volume #
  (e.g. select volume 1)
• attributes volume
• attributes disk

You are looking for any and all volumes and/or disks that are Read-only. Each time you find such, if any, try:

• attributes volume clear readonly
  (and/or as appropriate)
• attributes disk clear readonly
  (then repeat attributes volume and/or attributes disk as above to check that it cleared)

If you don't find any such then I'm currently out of ideas.

[Shane]

My first guess would be that the pool's file permissions have been messed up by the bad disk. I would first try the solutions linked/described here: https://community.covecube.com/index.php?/topic/5810-ntfs-permissions-and-drivepool/#findComment-34550

[Knocker]

Thank you for your suggestion Shane, but I keep getting hit with the write protection, in both methods mentioned in that link.

SetACL finished with error(s):
SetACT error message: The call to SetNamedSecurityInfo () failed
Operating system error message: The media is write protected.

[Christopher (Drashna)]

You can also do this with power shell, and with "two" commands. 

Quote

 

Get-Disk | Where-Object IsReadOnly -eq $true | ForEach-Object { $_ | Set-Disk -IsReadOnly $false } 

Get-Partition | Where-Object { $_.IsReadOnly -eq $true } | ForEach-Object { $_ | Set-Partition -IsReadOnly $false }

 

In both cases, this gets a list of disks -> checks for any items that have the "read only property" -> and for each, run the command to disable read only.  

These are safe to run, and I have verified that they cause no issue on my personal system/server.