Skip to main content
NetApp Knowledge Base

E-Series reboot with "Panic Reason: rebootReason 0x42e8001, rebootReasonExtra 0x0" while performing volume expansion

  1. Last updated
  2. Save as PDF
Views:
244
Visibility:
Public
Votes:
0
Category:
e-series-santricity-os-controller-software
Specialty:
esg
Last Updated:

Applies to

  • Controller Firmware Version: 08.70.00.02
  • E-Series E5700
  • 11.70R2
  • SANtricity

Issue

  • The controller resets in the MAJOR-EVENT-LOG:
A:4/5/21, 4:08:15 PM (16:08:15) 57157 400f Controller reset by its alternate - Shelf 99, Bay B
----> Reboot Reason : VTM: REBOOTALT_VTM_UNTIL_FORCED_TRANSFER_COMPLETION
A:4/5/21, 4:08:15 PM (16:08:15) 57156 400c Controller placed offline - Shelf 99, Bay B
----> Reboot Reason : VTM: REBOOTALT_VTM_UNTIL_FORCED_TRANSFER_COMPLETION
  • Core dump captured on controller rebooted in the excLogShow of the STATE-CAPTURE-DATA:
---- Log Entry #10 (Core 0) Apr-05-2021 10:16:26 AM ----
2021-04-05 16:08:06.023174
rebootReason 0x42e8001, rebootReasonExtra 0x0


Backtrace of the crashed thread:
#0  0x00007ff5b170b067 in raise () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1  0x00007ff5b23f6baa in vkiPanic () from /raid/lib/libeos-System.so
No symbol table info available.
#2  0x00007ff5b23f6cea in _vkiReboot () from /raid/lib/libeos-System.so
No symbol table info available.
#3  0x00007ff59a6f1460 in utl::AlternateNmiManager::thisCtlCoreDumpHookRun(int) () from /raid/lib/libeos-RAID.so
No symbol table info available.
#4  0x00007ff59a6f0d73 in utl::AlternateNmiManager::altCtlNmiTask() () from /raid/lib/libeos-RAID.so
No symbol table info available.
#5  0x00007ff5b23fa455 in vkiTask () from /raid/lib/libeos-System.so
No symbol table info available.
#6  0x00007ff5b0c3f064 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
No symbol table info available.
#7  0x00007ff5b17be62d in clone () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.

RegisterValues:
rax            0x0    0
rbx            0x1416ee060    5392752736
rcx            0x7ff5b170b067    140693220667495
rdx            0x13    19
rsi            0xc8b    3211
rdi            0x843    2115
rbp            0x7ff5b24e8e00    0x7ff5b24e8e00
rsp            0x7ff5b24e8de0    0x7ff5b24e8de0
r8             0xffffffff    4294967295
r9             0x6ab854    6994004
r10            0x7ff5b24e8b40    140693235206976
r11            0x202    514
r12            0x7ff59be37f10    140692859092752
r13            0x4    4
r14            0x7ff59bdefb48    140692858796872
r15            0x7ff5b24e9700    140693235209984
rip            0x7ff59a6f1460    0x7ff59a6f1460 <utl::AlternateNmiManager::thisCtlCoreDumpHookRun(int)+64>
eflags         0x202    [ IF ]
cs             0x33    51
ss             0x2b    43
ds             0x0    0
es             0x0    0
fs             0x0    0
gs             0x0    0
  • Stack trace shows the offending task processing:
Thread 53 (Thread 0x7ff5b2506c00 (LWP 3209)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x00007ff5b23f753e in futex (val3=0, uaddr2=0x0, timeout=<optimized out>, val=0, futex_op=128, uaddr=0x24b2b2370) at vkiSync.c:150
#2  _vkiCSemTake (semId=9851052912, tickTimeout=1250) at vkiSync.c:568
#3 0x00007ff59a721d5c in ras::RemotePeerManager::sendRemoteMessage (this=0x145c05670, response=0x7ff5b2505a80, target=0x145e998b0, targetId=10, msg=<optimized out>, msgLength=<optimized out>, timeOut=5000) at rasRemotePeerMgr.cc:1393
#4  0x00007ff599f9e6a9 in domi::MessageBrokerMgr::send (this=<optimized out>, response=response@entry=0x7ff5b2505a80, rac=0x145e998b0, context=context@entry=0x0, classID=classID@entry=domi::CACHECONFIGMANAGER, msg=0x2512e9558 "", msgLen=28, timeoutInMicrosec=5000000) at domiMessageBroker.cc:253
#5  0x00007ff59a71c704 in domi::Agent::send (this=0x145e99850, remoteResponse=0x7ff5b2505a80, context=0x0, classID=domi::CACHECONFIGMANAGER, xdr=0x7ff5b2505a50, timeoutInMicrosec=5000000) at domiAgent.cc:219
#6  0x00007ff59ca87f88 in ccm::CacheConfigManagerAgent::getInitStateAlt2 (this=0x145e99850, toMicrosec=toMicrosec@entry=5000000) at ccmCacheConfigMgrAgent.idfcc:187
#7  0x00007ff59caa16d1 in ccm::CacheConfigManager::getAltInitState (this=this@entry=0x145e99080) at ccmCacheConfigManager.cc:7301
#8  0x00007ff59cab3c9f in ccm::CacheConfigManager::updateHwMismatch (this=0x145e99080, txn=0x2496449a0, peer=<optimized out>) at ccmCacheConfigManager.cc:4560
#9  0x00007ff59ad43248 in vdm::dac::DacstoreVolManager::instantiateDacstoreVolume (this=this@entry=0x160e985e0, txnP=txnP@entry=0x2496449a0, volWWN=600a098000f77da90000018b606ae2ef, ssid=@0x7ff5b2505cdc: 7361, isOwned=isOwned@entry=true, segmentSize=@0x7ff5b2505d78: 1024, readAhead=@0x7ff5b2505d7c: 1, driveList=0x7ff5b2505d80, raidSvc=0x14b175700, usage=vdm::RECONFIGURATION) at vdmDacDacstoreVolMgr.cc:1246
#10 0x00007ff59ad43960 in vdm::dac::DacstoreVolManager::createDacstoreVolume (this=0x160e985e0, txnP=0x2496449a0, driveList=0x7ff5b2505d80, raidSvc=0x14b175700, segmentSize=@0x7ff5b2505d78: 1024, readAhead=@0x7ff5b2505d7c: 1, usage=vdm::RECONFIGURATION) at vdmDacDacstoreVolMgr.cc:921
#11 0x00007ff59adc5add in vdm::exop::ReconfigAgent::createLogVol (this=this@entry=0x24e8ac960, context=context@entry=0x2496449a0) at vdmExopReconfigAgent.cc:2745
#12 0x00007ff59adc6861 in vdm::exop::ReconfigAgent::createObjects (this=this@entry=0x24e8ac960, context=context@entry=0x2496449a0, volGrpPtr=0x248d34f40) at vdmExopReconfigAgent.cc:3086
#13 0x00007ff59adc81e7 in vdm::exop::ReconfigAgent::setupReconfig (this=this@entry=0x24e8ac960, context=context@entry=0x2496449a0, newRAIDLevel=newRAIDLevel@entry=evf::RAIDLabels::RAID_1, addedDrives=addedDrives@entry=0x7ff5b2506060, segmentSize=segmentSize@entry=0, addedCapacity=@0x24e8ad450: 41943040, modifiedVol=0x167d38060) at vdmExopReconfigAgent.cc:2666
#14 0x00007ff59ad8bfa7 in vdm::exop::ExclOpManager::setupReconfigs (this=0x160e9a900, agent=agent@entry=0x24e8ac960, newRAIDLevel=newRAIDLevel@entry=evf::RAIDLabels::RAID_1, addedDrvs=addedDrvs@entry=0x7ff5b2506060, newSegmentSize=newSegmentSize@entry=0, addedCapacity=@0x24e8ad450: 41943040, modifiedVol=0x167d38060, mtrans=0x2496449a0) at vdmExopExclOpMgr.cc:859
#15 0x00007ff59adc3118 in vdm::exop::ReconfigAgent::start (this=0x24e8ac960, context=0x2496449a0) at vdmExopReconfigAgent.cc:1228
#16 0x00007ff59ada4ec9 in vdm::exop::ExclOpManager::findAndStartAgents (this=this@entry=0x160e9a900, context=context@entry=0x2496449a0, startHaltedAgents=startHaltedAgents@entry=false) at vdmExopExclOpMgr.cc:4056
#17 0x00007ff59ada5c3e in vdm::exop::ExclOpManager::handleExclOpMgrEvent (this=this@entry=0x160e9a900, eventType=2, data=0x0, ssid=4294967295, context=context@entry=0x2496449a0) at vdmExopExclOpMgr.cc:7068
#18 0x00007ff59ada6496 in vdm::exop::ExclOpManager::handleEvent (this=0x160e9a900, event=...) at vdmExopExclOpMgr.cc:9362
#19 0x00007ff59a6f4f73 in utl::EventManager::notifyListeners (this=this@entry=0x1415f5150, evt=std::shared_ptr (count 4, weak 0) 0x2493b6f00) at utlEventMgr.cc:425
#20 0x00007ff59a6f5697 in utl::EventManager::processTask (this=0x1415f5150) at utlEventMgr.cc:325
#21 0x00007ff5b23fa455 in vkiTask (pCtrl=0x1415f55e0) at vkiTask.c:1329
#22 0x00007ff5b0c3f064 in start_thread (arg=0x7ff5b2506c00) at pthread_create.c:309
#23 0x00007ff5b17be62d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

 

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.