Unsolved
This post is more than 5 years old
2 Intern
•
356 Posts
0
5361
January 11th, 2017 08:00
Isilon - Cancel node firmware upgrade
Community,
I have ran into a problem where the node I kicked the whole sale firmware update from appears to be stuck. It was to start at node 1 but node one appears to have panicked during the firmware update process and rebooted itself. So my thinking is that it left the node that I originally kicked the whole sale update on out of sync. So I ran a single instance to just update the firmware on Node 1 with the hopes that node 9 would move on to the update node 2 when node 1 came back online, but node 9 is still stuck. How do I cancel the update process?
Node 9 console:
drc-9# isi firmware update
Update Summary:
Nodes 1-9, QLogic-NX2 : old: 7.6.55
new: 7.13.0
Update Schedule:
1. Node 1, QLogic-NX2 : old: 7.6.55
new: 7.13.0
2. Node 2, QLogic-NX2 : old: 7.6.55
new: 7.13.0
3. Node 3, QLogic-NX2 : old: 7.6.55
new: 7.13.0
4. Node 4, QLogic-NX2 : old: 7.6.55
new: 7.13.0
5. Node 5, QLogic-NX2 : old: 7.6.55
new: 7.13.0
6. Node 6, QLogic-NX2 : old: 7.6.55
new: 7.13.0
7. Node 7, QLogic-NX2 : old: 7.6.55
new: 7.13.0
8. Node 8, QLogic-NX2 : old: 7.6.55
new: 7.13.0
9. Node 9, QLogic-NX2 : old: 7.6.55
new: 7.13.0
Continue with update? (yes/no)[no]: yes
Updating Node 1
Updating Device QLogic-NX2
Updating Firmware QLogic-NX2-BCM57810 : old: 7.6.55
new: 7.13.0
<0.0> syslogd: /var/log/isi_audit_syslog.log: No such file or directory
Node 1 Console:
drc-1# isi firmware status
Device Type Firmware Nodes
-- ------------ --------- --------------------------------------- -------------
CAR_Colossus CAR 01.04 1-9
CFFPS1_Ramjet CFFPS 06.06 1-9
CFFPS2_Ramjet CFFPS 06.06 1-9
CMCSDR_Colossus CMCSDR 00.08 1-9
CMC_Colossus CMC 01.04 1-9
CMD_Colossus CMD 02.0b+49+01 1-9
IsilonFPV1 FrontPnl UI.01.36 1-9
LOx2-MLC-YD Nvram rp180c01+rp180c01 1-9
Lsi DiskCtrl 17.00.01.00 1-9
Mellanox Network 2.30.8020+ISL1090110018 1-9
PMC8056 CDES2 0.11.1+0.7.0+00.15-transfr 1-9
QLogic-NX2 10GigE 7.13.0 1
* QLogic-NX2 10GigE 7.6.55 2-9
WARNING: Firmware marked with * does not match installed firmware package
drc-1#
drc-1# [kernel:sched_switch+0x814][kernel:mi_switch+0x21a][kernel:sleepq_wait+0x30][kernel:_sleep+0x2e2][kernel:lbm_read+0xdd][kernel:lbm_read_cgblock_helper+0xd7][kernel:lbm_read_cgblock+0x85][kernel:lbm_scan_read_cg+0x3a][kernel:lbm_scan+0x30e][kernel:_sys_ifs_collect_drive+0x570][kernel:isi_syscall+0xaf][kernel:syscall+0x325][kernel:sched_switch+0x814][kernel:mi_switch+0x21a][kernel:sleepq_wait+0x30][kernel:_sleep+0x2e2][kernel:lbm_read+0xdd][kernel:lbm_read_cgblock_helper+0xd7][kernel:lbm_read_cgblock+0x85][kernel:lbm_scan_read_cg+0x3a][kernel:lbm_scan+0x30e][kernel:_sys_ifs_collect_drive+0x570][kernel:isi_syscall+0xaf][kernel:syscall+0x325] <0.0>
Thank you,
philippspohr
1 Rookie
•
107 Posts
0
January 17th, 2017 00:00
Why do you want to cancel the update process?
I would try to restart the overall update process that all Nodes can update the QLogic-NX2 from 7.6.55 to 7.13.0. At the moment only Node 1 seems to be updated.
The other way would be killing the update process itself. You can list all currently running processes with 'ps' or 'top'. E.g. 'ps -auxw'. But I don't know what will happen if you kill the process this way on one Node....
chjatwork
2 Intern
•
356 Posts
0
January 24th, 2017 06:00
The process stalled, but I will able to reboot that node from a remote node, and was able to restart the process.