- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- 3Par replcament disk show the failed disk and the ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2021 07:29 AM
02-08-2021 07:29 AM
Hello.
we tried to replace a failed disk (position 39) and it still shows as failed
ran the showinvenotory commands and saw that the disk that we replaced in a different position
and the old disk showing as failed as if still in the system:
39 1:19:0? failed 5000C50068570638 SEAGATE SYJKT0300GBAS15K 6XN3ZJBS 3P01 SAS Magnetic 2013-09-19 23:00:18 BST
64 1:19:0 normal 5000C5007637CA8C SEAGATE SYJKT0300GBAS15K 6XN6M1EE 3P01 SAS Magnetic 2021-02-04 07:55:09 GMT
anybody got an idea?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2021 08:05 AM
02-08-2021 08:05 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Looks normal so far.
Please post
servicemag status -d
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2021 08:39 AM
02-08-2021 08:39 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
The failed Disk should go away, if recovery is complete.
"servicemag status" will show the recovery state

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2021 01:06 AM - edited 02-09-2021 01:07 AM
02-09-2021 01:06 AM - edited 02-09-2021 01:07 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
servicemag status -d
Cage 1, magazine 19:
A servicemag resume command failed on this magazine.
The command completed at Thu Feb 4 17:55:44 2021.
The output of the servicemag resume was:
servicemag resume 1 19
... mag 1 19 already onlooped
... checking for valid disks...
... disks in mag : 1 19
... warning: chunklet 64:0 is used
... warning: chunklet 64:1 is used
... warning: chunklet 64:2 is used
... warning: chunklet 64:3 is used
... warning: chunklet 64:4 is used
... warning: chunklet 64:5 is used
... warning: chunklet 64:6 is used
... warning: chunklet 64:7 is used
... warning: chunklet 64:8 is used
... warning: chunklet 64:9 is used
... warning: chunklet 64:10 is used
... warning: chunklet 64:11 is used
... warning: chunklet 64:12 is used
... warning: chunklet 64:13 is used
... warning: chunklet 64:14 is used
... warning: chunklet 64:15 is used
... warning: chunklet 64:16 is used
... warning: chunklet 64:17 is used
... warning: chunklet 64:18 is used
... warning: chunklet 64:19 is used
... warning: chunklet 64:20 is used
... warning: chunklet 64:21 is used
... warning: chunklet 64:22 is used
... warning: chunklet 64:23 is used
... warning: chunklet 64:24 is used
... warning: chunklet 64:25 is used
... warning: chunklet 64:26 is used
... warning: chunklet 64:27 is used
... warning: chunklet 64:28 is used
... warning: chunklet 64:29 is used
... warning: chunklet 64:30 is used
... warning: chunklet 64:31 is used
... warning: chunklet 64:32 is used
... warning: chunklet 64:33 is used
... warning: chunklet 64:34 is used
... warning: chunklet 64:35 is used
... warning: chunklet 64:36 is used
... warning: chunklet 64:37 is used
... warning: chunklet 64:38 is used
... warning: chunklet 64:39 is used
... warning: chunklet 64:40 is used
... warning: chunklet 64:41 is used
... warning: chunklet 64:42 is used
... warning: chunklet 64:43 is used
... warning: chunklet 64:44 is used
... warning: chunklet 64:45 is used
... warning: chunklet 64:46 is used
... warning: chunklet 64:47 is used
... warning: chunklet 64:48 is used
... warning: chunklet 64:49 is used
... warning: chunklet 64:50 is used
... warning: chunklet 64:51 is used
... warning: chunklet 64:52 is used
... warning: chunklet 64:53 is used
... warning: chunklet 64:54 is used
... warning: chunklet 64:55 is used
... warning: chunklet 64:56 is used
... warning: chunklet 64:57 is used
... warning: chunklet 64:58 is used
... warning: chunklet 64:59 is used
... warning: chunklet 64:60 is used
... warning: chunklet 64:61 is used
... warning: chunklet 64:62 is used
... warning: chunklet 64:63 is used
... warning: chunklet 64:64 is used
... warning: chunklet 64:65 is used
... warning: chunklet 64:66 is used
... warning: chunklet 64:67 is used
... warning: chunklet 64:68 is used
... warning: chunklet 64:69 is used
... warning: chunklet 64:70 is used
... warning: chunklet 64:71 is used
... warning: chunklet 64:72 is used
... warning: chunklet 64:73 is used
... warning: chunklet 64:86 is used
... warning: chunklet 64:87 is used
... warning: chunklet 64:88 is used
... warning: chunklet 64:89 is used
... warning: chunklet 64:90 is used
... warning: chunklet 64:91 is used
... warning: chunklet 64:92 is used
... warning: chunklet 64:93 is used
... warning: chunklet 64:94 is used
... warning: chunklet 64:95 is used
... warning: chunklet 64:96 is used
... warning: chunklet 64:97 is used
... warning: chunklet 64:98 is used
... warning: chunklet 64:99 is used
... warning: chunklet 64:100 is used
... warning: chunklet 64:101 is used
... warning: chunklet 64:102 is used
... warning: chunklet 64:103 is used
... warning: chunklet 64:104 is used
... warning: chunklet 64:105 is used
... warning: chunklet 64:106 is used
... warning: chunklet 64:107 is used
... warning: chunklet 64:108 is used
... warning: chunklet 64:109 is used
... warning: chunklet 64:110 is used
... warning: chunklet 64:111 is used
... warning: chunklet 64:112 is used
... warning: chunklet 64:113 is used
... warning: chunklet 64:114 is used
... warning: chunklet 64:115 is used
... warning: chunklet 64:116 is used
... warning: chunklet 64:117 is used
... warning: chunklet 64:118 is used
... warning: chunklet 64:119 is used
... warning: chunklet 64:120 is used
... warning: chunklet 64:121 is used
... warning: chunklet 64:122 is used
... warning: chunklet 64:123 is used
... warning: chunklet 64:124 is used
... warning: chunklet 64:125 is used
... warning: chunklet 64:126 is used
... warning: chunklet 64:127 is used
... warning: chunklet 64:128 is used
... warning: chunklet 64:129 is used
... warning: chunklet 64:130 is used
... warning: chunklet 64:131 is used
... warning: chunklet 64:132 is used
... warning: chunklet 64:133 is used
... warning: chunklet 64:134 is used
... warning: chunklet 64:135 is used
... warning: chunklet 64:136 is used
... warning: chunklet 64:137 is used
... warning: chunklet 64:138 is used
... warning: chunklet 64:139 is used
... warning: chunklet 64:140 is used
... warning: chunklet 64:141 is used
... warning: chunklet 64:142 is used
... warning: chunklet 64:143 is used
... warning: chunklet 64:144 is used
... warning: chunklet 64:145 is used
... warning: chunklet 64:146 is used
... warning: chunklet 64:147 is used
... warning: chunklet 64:148 is used
... warning: chunklet 64:149 is used
... warning: chunklet 64:150 is used
... warning: chunklet 64:151 is used
... warning: chunklet 64:152 is used
... warning: chunklet 64:153 is used
... warning: chunklet 64:154 is used
... warning: chunklet 64:155 is used
... warning: chunklet 64:156 is used
... warning: chunklet 64:157 is used
... warning: chunklet 64:158 is used
... warning: chunklet 64:159 is used
... warning: chunklet 64:160 is used
... warning: chunklet 64:161 is used
... warning: chunklet 64:162 is used
... warning: chunklet 64:163 is used
... warning: chunklet 64:164 is used
... warning: chunklet 64:165 is used
... warning: chunklet 64:166 is used
... warning: chunklet 64:167 is used
... warning: chunklet 64:168 is used
... warning: chunklet 64:169 is used
... warning: chunklet 64:170 is used
... warning: chunklet 64:171 is used
... warning: chunklet 64:172 is used
... warning: chunklet 64:173 is used
... warning: chunklet 64:174 is used
... warning: chunklet 64:175 is used
... warning: chunklet 64:176 is used
... warning: chunklet 64:177 is used
... warning: chunklet 64:178 is used
... warning: chunklet 64:179 is used
... warning: chunklet 64:180 is used
... warning: chunklet 64:181 is used
... warning: chunklet 64:182 is used
... warning: chunklet 64:183 is used
... warning: chunklet 64:184 is used
... warning: chunklet 64:185 is used
... warning: chunklet 64:186 is used
... warning: chunklet 64:187 is used
... warning: chunklet 64:188 is used
... warning: chunklet 64:189 is used
... warning: chunklet 64:190 is used
... warning: chunklet 64:191 is used
... warning: chunklet 64:192 is used
... warning: chunklet 64:193 is used
... warning: chunklet 64:194 is used
... warning: chunklet 64:195 is used
... warning: chunklet 64:199 is used
... warning: chunklet 64:200 is used
... warning: chunklet 64:201 is used
... warning: chunklet 64:202 is used
... warning: chunklet 64:203 is used
... warning: chunklet 64:204 is used
... warning: chunklet 64:205 is used
... warning: chunklet 64:206 is used
... warning: chunklet 64:207 is used
... warning: chunklet 64:208 is used
... warning: chunklet 64:209 is used
... warning: chunklet 64:210 is used
... warning: chunklet 64:211 is used
... warning: chunklet 64:212 is used
... warning: chunklet 64:213 is used
... warning: chunklet 64:214 is used
... warning: chunklet 64:215 is used
... warning: chunklet 64:216 is used
... warning: chunklet 64:217 is used
... warning: chunklet 64:218 is used
... warning: chunklet 64:219 is used
... warning: chunklet 64:220 is used
... warning: chunklet 64:221 is used
... warning: chunklet 64:222 is used
... warning: chunklet 64:223 is used
... warning: chunklet 64:224 is used
... warning: chunklet 64:225 is used
... warning: chunklet 64:226 is used
... warning: chunklet 64:227 is used
... warning: chunklet 64:228 is used
... warning: chunklet 64:229 is used
... warning: chunklet 64:232 is used
... warning: chunklet 64:233 is used
... warning: chunklet 64:234 is used
... warning: chunklet 64:235 is used
... warning: chunklet 64:236 is used
... warning: chunklet 64:269 is used
... warning: chunklet 64:270 is used
... warning: chunklet 64:271 is used
... verifying spare space for disks 64 and 64
... All chunklets played back / relocated.
... cleared logging mode for cage 1 mag 19
... relocating chunklets from spare space
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
... chunklet 67:257 - move_error,duplicate_dest, failed move
... chunklet 69:257 - move_error,duplicate_dest, failed move
... chunklet 63:253 - move_error,duplicate_dest, failed move
... chunklet 65:258 - move_error,duplicate_dest, failed move
Failed --
giving up after 101 attempt
servicemag resume 1 19 -- Failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2021 01:17 AM
02-09-2021 01:17 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
i ran this as well :
showpd -state 39
Id CagePos Type -State- -------------------------Detailed_State------------------------- -SedState-
39 1:19:0? FC failed vacated,missing,invalid_media,smart_threshold_exceeded,servicing unknown
---------------------------------------------------------------------------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2021 06:36 AM
02-10-2021 06:36 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Hello Luke_Y,
It is expected that the replacement disk will take a new ID and the old disk will be in failed state. The old PD ID will be removed automatically once the servicemag resume completes for that position.
Now, in this case, it seems the servicemag resume failing and from the errors, it looks the array is missing some OS updates. What is the Inform OS version and patch level?
Regards,
Veeyaarvi
I work for HPE
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2021 10:22 AM
02-10-2021 10:22 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Release version 3.2.2 (MU4)
Patches: P56,P59,P60,P74,P80,P85
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2021 12:29 AM
02-15-2021 12:29 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Hello Luke_Y,
Thank you .
The array should be at a minimum of 3.2.2 MU6 with Patch 149. Without that version we need to do a lot of manual work to get this resolved.
Please reach support if you need help with workaroud if the OS cannot be updated.
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2021 02:07 AM
02-15-2021 02:07 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Hello.
i opened a ticket with support
they told me to run :
#servicemag unmark 1 19
#servicemag clearstatus 1 19
#servicemag resume 1 19
that didnt work , still got :
Failed --
giving up after 101 attempt
servicemag resume 1 19 -- Failed
waiting on answer from HPE support on what is the next step.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2021 02:15 AM
02-15-2021 02:15 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Hi Luke,
Thank you. I beleive the support will take care of it further.
You may private message me the case ID if you want me to follow this up.
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2021 06:45 AM
02-16-2021 06:45 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Hello Luke,
I understand the issue is resolved. Please confirm.
Also, please plan to get the Inform OS upgraded to 3.2.2 MU6 + patches to avoid a lot of such issues in the future
Regards,
Veeyarvi
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2021 06:47 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2022 02:35 PM - edited 09-03-2022 03:07 PM
09-03-2022 02:35 PM - edited 09-03-2022 03:07 PM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Hello - I'm having this exact issue. Support has done the initial steps that you've done:
servicemag unmark
servicemag clearstatus
servicemag resume
I can see already when I do a servicemag status -d that it is going to fail again.
Could you please share the ultimate solution if you had one? (Yes, I'm missing the OS patches as well)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2022 12:09 AM
09-06-2022 12:09 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Hi Phodges,
Without knowing details and exact status, I doubt we can comment further on this. I assume you are already working with support. But, yes - we need some manual work to get the things back in track if the array is not running on the recommended OS version and patch levels.
Veeyaarvi
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2024 05:35 AM - last edited on 10-13-2024 11:51 PM by Sunitha_Mod
10-11-2024 05:35 AM - last edited on 10-13-2024 11:51 PM by Sunitha_Mod
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2024 12:55 AM
10-14-2024 12:55 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Hi akochuev88,
I do not think there are any standard or pre-defined steps. I assume the support validate the current status/state and decide on the next steps.
Regards,
Veeyaarvi
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2024 02:19 AM
10-14-2024 02:19 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Hi @veeyarvi !
Unfortunately, this 3PAR is very old, so we don't have support for it and our management team cannot buy it right now. But this problem is very important for us and we really need to fix it...
Maybe we can upgrade 3PAR OS to 3.2.2 MU6 as described here earlier? Is it possible and safe to make 3PAR OS update with failed disk? Maybe using upgradesys with "-f" key?
Or maybe we can move chunklets with move error manually to new disk? Right now some chucklets on new disk have status "Unavailable", is it possible to move data there?
72 782 ---- --- none unavailable valid N N --- ---
72 783 ---- --- none unavailable valid N N --- ---
72 784 ---- --- none unavailable valid N N --- ---
72 785 ---- --- none unavailable valid N N --- ---
72 786 ---- --- none unavailable valid N N --- ---
72 787 ---- --- none unavailable valid N N --- ---
I can provide more information if needed.
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2024 04:36 AM
10-14-2024 04:36 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Hi akochuev88
Could you elaborate the issue more? Is the new disk unable to admit? But as far as I read, the disk is admitted it apepars. Am I right on that?
PS: Any OS upgrade is not allowed normally if any hardware failure in the array. If the servicemag start already completed, need to move the reference chunklets from the failed PD manually and then dismiss the PD. After this, you will be able to install the necessary patch/OS and then admit the new disk.
Regards,
Veeyaarvi
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-15-2024 02:56 AM
10-15-2024 02:56 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Hi @veeyarvi !
Of course, here is more detailed description:
We tried to replace failed disk 61, but with new disk in position 72 we have problems in servicemag process.
72 2:13:0 normal 5000CCA02DC86D43 HGST HCBF1200S5xeN010 06KK71TA 3P05 SAS Magnetic 2024-10-08 16:54:06
61 2:13:0? failed 5000C500B85488F8 SEAGATE STHB1200S5xeN010 W402BBFM 3P03 SAS Magnetic 2018-09-07 12:16:59
In servicemag we have such notes:
... cleared logging mode for cage 2 mag 13
... relocating chunklets from spare space
... chunklet 3:776 - move_error,duplicate_dest, failed move
... chunklet 3:777 - move_error,duplicate_dest, failed move
... chunklet 3:778 - move_error,duplicate_dest, failed move
... chunklet 3:779 - move_error,duplicate_dest, failed move
... chunklet 7:777 - move_error,duplicate_dest, failed move
... chunklet 7:778 - move_error,duplicate_dest, failed move
... chunklet 7:779 - move_error,duplicate_dest, failed move
... chunklet 7:780 - move_error,duplicate_dest, failed move
...
So some chunklets cannot relocate to new disk.
Also on new disk we have chunklets in status "Unavailable":
72 782 ---- --- none unavailable valid N N --- ---
72 783 ---- --- none unavailable valid N N --- ---
72 784 ---- --- none unavailable valid N N --- ---
72 785 ---- --- none unavailable valid N N --- ---
72 786 ---- --- none unavailable valid N N --- ---
72 787 ---- --- none unavailable valid N N --- --
As I can understand from your previous message, our plan will be like this:
- run servicemag unmark 2 13
- run servicemag clearstatus 2 13
- move all data chunklets from bad replacement disk 72 using movech -f -perm command
- run dismisspd 72
- remove disk 72 physically from enclosure
- make 3PAR OS upgrade to 3.2.2 MU6 + Patch 149
- Install new disk in cage 2 magazine 13
- run admithw and tunesys for data rebalancing with new disk
What do you think about this plan? Is it correct?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-15-2024 03:30 AM
10-15-2024 03:30 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Hi akochuev88,
Yes, that looks the correct plan.
Regards,
Veeyaarvi
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2024 12:17 AM
10-17-2024 12:17 AM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
Hi @veeyarvi !
Thank you for help, we'll plan implementation of these actions, hope it will fix our problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2024 09:49 PM
12-08-2024 09:49 PM
Re: 3Par replcament disk show the failed disk and the replaced disk in different position
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2024 05:49 AM
12-10-2024 05:49 AM