VNX: Pool's internal FLU's go offline during a single SP reboot

Summary: Pool's internal FLU's go offline during a single SP reboot, thus bringing pools offline and causing DU.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Pool's internal FLU's go offline during a single SP reboot, thus bringing pools offline and causing DU.

In this example, SPA reboots first.

B 06/28/18 20:40:07 SP B 944 Hard Peer Bus Error 13 0 0
B 06/28/18 20:40:07 SP A a23 Peer SP Down. 3 0 0

Pool's FLU's are then trespassed to SPB, but the FLU's do not get ready on SPB, thus FLUs going offline.
B 06/28/18 20:40:09 MLU 712d85xx A problem was detected while accessing the Storage Pool. Please resolve any hardware problems. FLU 0x400000xxx went offline causing Pool 0xx00000011 to go offline.
B 06/28/18 20:40:09 MLU 712d8dxx LUN 6006016055113600:8192074aab21xxxx is unable to service IO due to a storage pool problem. LUN OID A000000xx. 00000400xxxx [ALU 148]

After SPA goes up, FLUs are online automatically and DU is recovered.

Cause

The FLU's go offline due to signature errors reported from SPB. Engineering confirms it is triggered by a known code issue since Inyo MR1 SP6 [05.32.000.5.xxx] which is a side effect of another code fix brought in R32.225.
The reason for partition signature ok flag missing on one SP is that FLU rebuild got set on SP that was rebuilding the FLU while it got cleared on peer. 

20:38:43.748 2 FFFFFA801C69Fxxx 0 std:NTFE: Lun 457 is having bad fru signature errors
20:38:43.748 1 FFFFFA801C69Fxxx 0 std:NTFE: Lun 456 is having bad fru signature errors
20:38:43.748 1 FFFFFA801C69Fxxx 0 std:NTFE: Lun 459 is having bad fru signature errors
20:38:43.748 2 FFFFFA801C69Fxxx 0 std:NTFE: Lun 461 is having bad fru signature errors
20:38:43.748 2 FFFFFA801C69Fxxx 0 std:NTFE: Lun 462 is having bad fru signature errors
20:38:43.748 2 FFFFFA801C69Fxxx 0 std:NTFE: Lun 464 is having bad fru signature errors 20:38:43.749 1 FFFFFA801C69Fxxx 0 std:NTFE: Lun 503 is having bad fru signature errors <<<<<<


As it finds the FLU has fru signature error, NotReady status was returned as true on FLU.

20:38:43.733 2 FFFFFA801C69Fxxx 0 std:CM:_fru_physical_powerdown_needs_rebuild: fru 208, state 0x4, peer state 0xffffffff
20:38:43.733 3 FFFFFA801C69Fxxx 0 std:NTFE: ntfeLuConvertDeviceControlIrp: exit_idx:11: LU 503 NotReady=TRUE Attrib=0x4034, TE=FALSE....... 20:38:43.748 2 FFFFFA801C69Fxxx 0 std:NTFE: Lun 457 is having bad fru signature errors
20:38:43.748 2 FFFFFA801C69Fxxx 0 std:NTFE: Lun 464 is having bad fru signature errors 20:38:43.749 1 FFFFFA801C69Fxxx 0 std:NTFE: Lun 503 is having bad fru signature errors <<<<<<


Resolution

After the rebooting SP finishes reboot, FLUs will get online automatically and pools will be online as well.

Affected Products

VNX1 Series

Products

VNX1 Series
Article Properties
Article Number: 000056972
Article Type: Solution
Last Modified: 17 Apr 2026
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.