2012-08-10 05:57 AM
We recently updated a FAS2240 from Ontap 8.1 to 8.1P2.
Everything went fine, version -b shows:
sinhfas> version -b
/cfcard/x86_64/freebsd/image1/kernel: OS 8.1
/cfcard/x86_64/freebsd/image2/kernel: OS 8.1P2
/cfcard/x86_64/firmware/excelsio/firmware.img: Firmware 1.9.0
/cfcard/x86_64/firmware/DrWho/firmware.img: Firmware 2.5.0
/cfcard/x86_64/firmware/SB_XV/firmware.img: Firmware 4.4.0
/cfcard/x86_64/firmware/SB_XVI/firmware.img: Firmware 5.1.1
/cfcard/x86_64/firmware/SB_XVIII/firmware.img: Firmware 7.1.2
/cfcard/x86_64/firmware/SB_XIX/firmware.img: Firmware 8.0.0
/cfcard/common/firmware/zdi/zdi_fw.zpk: Flash Cache Firmware 2.2 (Build
/cfcard/common/firmware/zdi/zdi_fw.zpk: PAM II Firmware 1.10 (Build
/cfcard/common/firmware/zdi/zdi_fw.zpk: X1936A FPGA Configuration PROM 1.0
But the system still boots Ontap 8.1 from image1.
What went wrong and how can we switch to image2?
Solved! SEE THE SOLUTION
2012-08-10 06:29 AM
do a software install & download again, then version -b should have both kernels overwritten.
otherwise "halt" the machine and do a "boot_secondary" or "boot_backup" to boot from image2.
2012-08-10 06:36 AM
thanks for the input
But isn't the meaning of having 2 images that I can manually go back to a "save harbour" in case of issues?
Therefor just writing into both images the same version is a workaround that makes me feel unhappy
And boot manually into the second image does not help when the storage boots itself after eg a panic.
Aren't there some boot args to tamper with? So it automatically chooses the right version?
2012-08-10 07:34 AM
Normally software update makes all required adjustments in environment to automatically boot new version. If it did not happen it could mean either deviation from update procedure or a bug. The former we do not know (do you have any logs of this?) and if you are sure everything was done correctly, you need to open support case so possible bug can be investigated.
2012-08-10 07:59 AM
Unfortunately we have not logged the steps ...
but we took the right version and package and then ... well, I mean updating is really straight forward: software update 81P2_q_image.tgz ; not much, that one could do wrong ...
Case is open at NetApp - but according to my experience: cases other than P1 have rather long response times ... therefore any further comments are still appreciated.
2012-08-10 08:25 AM
I don't have an experience (yet ), but from loader promt >printenv
You are able to see from where ontap boots up, and with other commands you can change it.
i dont think that's the final solution, but example, you can now determine, from where filer boots, image1 or image2..
P2 cases should be fine
2012-08-10 12:53 PM
sounds very interesting ... eager to know what env variables I have to change (printenv -> show; setenv -> set) - there are several dealing with booting the system ...
have to check them in a quiet minute