- Products
- Learn
- Local User Groups
- Partners
- More
Maestro Masters
Round Table session with Maestro experts
Hi Checkmates,
I face the issue about rescue boot right now for device mho140.
before we upgrade the mho140 from r81.10 to R82 and after that we rollback using the snapshot(auto snapshot) but when revert snapshot finish the mho140 not back to normal: interface show only interface lopback, try reboot the mho140 (hard reboot) cannot boot to OS R81.10 but stuck at rescue boot.
maybe you have suggestion for my issue, I see from SK the grub boot for r81.10 and r82 is different, grub r81 and grub2 r82,
when I try to check the boot location, find error below:
grub rescue> ls
(hd0) (hd0,gpt4) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1) (lvm/vg_splat-lv_current) (lvm
/vg_splat-lv_log) (lvm/vg_splat-lv_fcd_GAIA)
grub rescue> normal
Unknown command `normal'.
grub rescue> ls (hd0,gpt3)
(hd0,gpt3): Filesystem is unknown.
grub rescue>
@Anatoly @Lari_Luoma can you please assist?
Looks like file system is corrupted. You can try to revert to factory image, but that wouldn't have your earlier configurations. Follow instructions in sk174202. It guides you through the process of backing up and restoring the files from the other, working orchestrator. If you need assistance, I suggest you open a TAC case.
Hi Lari,
Can you describe how to revert to factory image from rescue boot mode?
Command boot or reboot not available from rescue boot
This is the set view from rescue boot:
I try to change the set boot from the rescue boot and plug the flash disk and try with hard reboot but stil stuck cannot show option boot from flash disk to reimage
rub rescue> set prefix=(lvm/vg_splat-lv_current)/boot
grub rescue> set root=(lvm/vg_splat-lv_current)
grub rescue> set
prefix=(lvm/vg_splat-lv_current)/boot
root=lvm/vg_splat-lv_current
You could revert it from the boot menu, but if you don't have access to power-cycle the box, it's more complicated. I'll ask about this internally. I will post the response.
Thank you Lari,
I try hard reboot want to access boot menu, but is not available always direct to "grub rescue"
maybe you have any tips and trick to bypass the grub rescue to access the boot menu, like usually we want to reimage with flashdsik.
I talked with our R&D. This is the grub shell. It usually means that the BIOS couldn't find the OS boot script. Maybe something went wrong during the roll back process.
The only way to fix this is to install it from a USB (if you can get into the boot menu you can of course test the fcd revert first).
Thank you Lari for take good care my case,
I Already have guiding by @Anatoly , I mis the keyboard to access BIOS, I try access BIOS using ctrl S, f10,f11,f12, del,
The corect key to access MHO is using ctrl B and I already reimage the mHO140,
Once again thank you Anatoly, Lary and Val.
Have a great day always for you guys, RESPECT.
Happy to help!
A couple of comments still...
Hit ESC+7 to enter the boot menu on MHO. It will ask for a password that is not publicly available, but if Anatoly is already helping you, that's is great (otherwise open a TAC case). CTRL+B enters BIOS where the boot order can also be changed, but the boot menu I explained first is enough.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
User | Count |
---|---|
18 | |
3 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY