Skip to main content
NetApp Knowledge Base

Failed dm-devices visible after Upgrade of Trident from pre-22.07 to 22.10

Last Updated:

Applies to

Astra Trident versions  22.10 to 23.04 as upgrade targets


The following effects are visible after the upgrade to Trident version 22.10 (or higher):
| sddj: couldn't get target port group
| sdbv: couldn't get target port group
multipath -ll  shows the following for a lot of /dev/sd... devices and multipathing devices:

3600a098038305654752b503177444141 dm-64 NETAPP  ,LUN C-Mode
size=SIZE_IN_G features='3 pg_init_retries 50 retain_attached_hw_handler' hwhandler='1 alua' wp=rw
|-+- policy='round-robin 0' prio=0 status=enabled
| `- 3:0:0:45 sddj 71:16  failed faulty running
`-+- policy='round-robin 0' prio=0 status=enabled
  `- 2:0:0:45 sdbv 68:144 failed faulty running
Additionally, syslog on the node shows the following errors for the underlying disk devices as well:

multipathd[991]: 3600a098038305654752b503177444141: sddj - tur checker reports path is down
multipathd[991]: 3600a098038305654752b503177444141: sdbv - tur checker reports path is down

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
Scan to view the article on your device