Virtual Disk will not repair after replacing failed disk - solved
server 2012 r2 storage pool 4tbx4,one 10.9tb parity virtual disk using of space in pool.
one disk failed , removed - status shows "lost communication".
replaced new disk (same size, same model), set auto allocation. new disk physicaldisk11.
set usage of failed disk retired.
cannot repair virtual disk. physical disks test (no errors or bad blocks). no errors in event log.
in gui, goes 0% 100% in couple of seconds still shows degraded. in ps, command
repair-virtualdisk -friendlyname 'vdisk1'
also fails.
get-storagepool pool1 | get-physicaldisk
friendlyname canpool operationalstatus healthstatus usage size
--------------- --------- -------------------- --------------- ----- ----
physicaldisk-1 false lost communication warning retired 3.64 tb
physicaldisk11 false ok healthy auto-select 3.64 tb
physicaldisk4 false ok healthy auto-select 3.64 tb
physicaldisk5 false ok healthy auto-select 3.64 tb
physicaldisk6 false ok healthy auto-select 3.64 tb
get-virtualdisk vdisk1
friendlyname resiliencysettingname operationalstatus healthstatus ismanualattach size
--------------- -------------------------- -------------------- ------------ -------------- ----
vdisk1 parity degraded warning false 10.91 tb
*update* - allocation of physicaldisk11 went 256mb 3.64gb virtual disk still shows degraded. rebuilding/repairing? how can tell?
this problem resolved.
i cleaned new disk using seatools (diskpart couldn't see it). moved same daughterboard other disks in pool connected (it had been connected motherboard sata port).
after restarting server, the pool now showed 2 disks "lost communication" (the original bad disk, , "old" version of new disk). cleaned version of new disk in primordial pool.
i added new disk pool , allocation correct time (friendlyname of new disk in 7 rather 11). repairing vdisk1 worked also.
friendlyname allocatedsize size
------------ ------------- ----
physicaldisk4 3999151423488 3999956729856
physicaldisk5 3999151423488 3999956729856
physicaldisk6 3999151423488 3999956729856
physicaldisk7 3999151423488 3999956729856
two lessons learned:
#1 - don't allocate storage pool virtual disks. leave few gb of free space on each physical disk.
#2 - "allocated size" can different identical disks, depending on controller connected to. (still know why case - anyone?)
Windows Server > File Services and Storage
Comments
Post a Comment