I have 3 (brand new)WD 4gb SATA RED drives set up in a storage space on my windows 2012 essentials R2 preview, and a backup storage space configured (parity mode). Here's the thing - 1 or more of the drives keep on getting marked as retired. Right now i have 2 that are marked. I can't remove the drives from the pool (because its parity) without removing the storage space (before which i have to repoint the backups folder - its a pain!). I did this once, and everything checked out fine with the drives, I even did a complete format of them. I 'repaired the drive' from the windows server dashboard, and that checked out fine - though i have my suspicions that it is doing anything with the hard drives in qn.
I found KB2842575 on microsoft.com which seem to describe my problem but the hotfix/rollup etc won't install as they are 'not applicable'. I can also see a couple posts on this forum which seem similar, though no solution that i can see and apply here.
I sincerely doubt that all 3 drives are faulty (and one time or another they've all been marked as retired). Does anyone know how to 'bring them out of retirement' and why this may be happening?
Sunday, October 13, 2013 7:39 PM
- Moved by Andy QiMicrosoft contingent staff, Moderator Wednesday, October 16, 2013 12:27 PM
If your server is Windows Server 2012 R2 Essentials, the hotfix KB2842575 may not applicable. At this time, I suggest you could try to refer to the following similar threads. Hope it helps.
Drives being retired in my storage pool
Storage Spaces - unmark hard drive as "retired" after SATA controller failure
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Wednesday, October 16, 2013 12:26 PMModerator
Thanks Andy. Yes that hotfix says not applicable, is that fix already included in R2? It did sound entirely like the issue i am having.
I had read both of the posts you linked to before i posted my question, no real answers there.
I think this is likely to be some sort of bug - but what's particularly irksome and worrying to me is that there doesn't seem to be any way to cleanly remove the retired drives, which is patently absurd since the OS is telling me they are faulty and not being used! This leaves me with no choice but to completely delete the storage pool in order to 'free the drives'. So my question is - in a system with 4 drives where 1 is the system drive, and 3 are in a storage pool configured for parity - just how are you supposed to manage a failed drive???? This cannot be right by design, surely?Thursday, October 17, 2013 1:24 AM