Hi Yavor,
I replaced the disk on 0:8 location with same 200GB SSD but it gave error resuming serviemag. error is "New disk 146 is smaller than replaced disk 8". Is there a way to force servicemag to use the current disk given its same type? May be the new one is off by few bytes
sanhou01 cli% servicemag status -d 0 8
A servicemag resume command failed on this magazine.
The command completed at Wed Oct 2 16:19:47 2019.
failed to retrieve time that relocation started, no estimate available
The output of the servicemag resume was:
servicemag resume 0 8
... mag 0 8 already onlooped
... firmware is current on pd WWN [5000CCA01331143B]
... firmware is current on pd WWN [5000CCA02231FC5B] Id [ 8]
... firmware is current on pd WWN [5000CCA0131BB443] Id [126]
... checking for valid disks...
... checking for valid disks...
... disks in mag : 0 8
... normal disks: WWN [5000CCA01331143B] Id [146] diskpos [0]
... not normal disks: WWN [5000CCA02231FC5B] Id [ 8]
.................... WWN [5000CCA0131BB443] Id [126]
... verifying spare space for disks 8 and 146
Failed --
New disk 146 is smaller than replaced disk 8
servicemag resume 0 8 -- Failed
sanhou01 cli% showpd -c -failed -degraded
------- Normal Chunklets -------- ---- Spare Chunklets ----
- Used - -------- Unused -------- - Used - ---- Unused ----
Id CagePos Type State Total OK Fail Free Uninit Unavail Fail OK Fail Free Uninit Fail
8 0:8:0? FC failed 408 0 0 0 0 63 326 0 0 0 0 19
95 3:23:0 SSD failed 185 0 0 0 35 0 127 0 0 0 0 23
101 4:5:0 FC failed 408 0 0 0 54 0 336 0 0 0 0 18
109 4:13:0? FC failed 408 0 0 0 90 0 318 0 0 0 0 0
126 0:8:0? SSD degraded 185 0 0 185 0 0 0 0 0 0 0 0
146 0:8:0 SSD degraded 185 0 0 0 0 185 0 0 0 0 0 0
-------------------------------------------------------------------------------------------
6 total 1779 0 0 185 179 248 1107 0 0 0 0 60