01-10-2016 03:09 AM - edited 03-01-2019 12:32 PM
After a painful recovery downgrade (failed upgrade from 2.2.3d to 2.2.6d) everything is working again, however I see
Partition opt on fabric interconnect a has file system errors (see attachment)
Any hints to fix this nasty error are appreciated.
Solved! Go to Solution.
01-10-2016 05:14 AM
Good morning Walter,
The bug you are running into is;
https://tools.cisco.com/bugsearch/bug/CSCus79160/?reffering_site=dumpcr
I have ran into this issue in the past, TAC will have to load the debug plugin and just check some blocks. As Afroj stated, a initiate system is another fix but that is a longer process, if you open a TAC case be sure to mention the bug listed above and they can attempt that work around first.
Let me know if you have any other questions or need any assistance.
Qiese Dides
01-10-2016 04:44 AM
Hi Walter,
the error you are seeing , looks some /opt got corrupted during the downgrade. you can try this:: connect to Fabric Interconnect using the debug plugin and perform an fscheck of the file system though most of the time , we have to end up replacing the FI.
another possible solution::
We could do an init system on the FI. This would pretty much be a complete
rebuild of this FI and should resolve any file system corruption. That would require
downtime on that half of the fabric, so definitely best during a maintenance window.
**you can raise a TAC case to assist you in performing this activity or for replacement..
Thanks-
Afroz
***Ratings Encourages Contributors ***
01-10-2016 01:56 PM
Thanks Qiese and Afroz
Very much appreciated !
Q. is there any risk doing a fscheck ?
Problem: customer doesn't have a maintenance window for next 6 months.
I think after all, a RMA procedure might be the preferred method, although it requires of course to rack, and cable the RMA box; the synch of the firmware and configuration usually works ok.
Walter.
01-10-2016 09:18 PM
Walter,
Have you consoled in to the fabric interconnect with the issue yet? It might be stuck in the loader prompt / configuration page.
01-10-2016 05:14 AM
Good morning Walter,
The bug you are running into is;
https://tools.cisco.com/bugsearch/bug/CSCus79160/?reffering_site=dumpcr
I have ran into this issue in the past, TAC will have to load the debug plugin and just check some blocks. As Afroj stated, a initiate system is another fix but that is a longer process, if you open a TAC case be sure to mention the bug listed above and they can attempt that work around first.
Let me know if you have any other questions or need any assistance.
Qiese Dides
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide