Hi OpenSuSE Micro Users && Hi Thorsten from SuSE,
I really love the minds and understandings about OpenSuSE MicroOS - so I
prefer also reinstalling the system, if there are any "big" problems.
But my problem doesn't require a reinstall of the OS, when you know how to
restore the MBR, just for example when you use a copied image from
harvester VM.
I fixed this for myself, and it was quite impressive how it works!
This is what I did to restore my OpenSuSE Micro OS:
1) Just boot SuSE Micro from ISO Install Disk
2) Choose "Boot Linux System" (not Rescue, as intended before)
3) Load Kernel and choose the required parameters for your system
4) transactional-update shell
5) grub2-install -v (to re-write mbr because of copied disk)
6) Reboot VM
7) Before normal boot, start VM with rescue mode
8) transactional-update bootloader (to really fix that with grub is all
fine)
For me, the main problem is mostly fixed. I just applied the latest updates
and the system is only running when booting the kernel in rescue mode,
so I got a black screen with a blinking cursor. I think that can be another
problem.
Maybe, my way was not totally correct, but for me the MBR issue at OpenSuSE
MicroOS is fixed - and looks quite easy. (just faster than reinstalling the
OS!)
Kind regards
Torsten
--
torsten@linux.schule
www.behrens.engineer
Thorsten Kukuk
Hi,
On Sat, Feb 04, Torsten Behrens wrote:
Hi OpenSuSE MicroOS Users,
I want to know how to rescue / reinstall grub bootloader.
The standard way of chroot and running grub-install does not work, because of the read-only filesystem.
MicroOS is designed in a way, that is on the one side very robust and it should not be necessary to boot a rescue system to repair it. But if it really breaks, it's much easier and faster to redeploy it then to try to fix it.
Since I really run only container on my server with MicroOS, I only need to enable the containers again, that's all.
I booted the system over CDROM with OpenSuSE MicroOS Rescue Mode, but for me it's totally impossible to rewrite the bootloader to MBR.
transactional-update bootloader does also not work, because it can not write anything to /var/run
If transcational-update bootloader does not work anymore for you, then there is something more serious broken on your system. Before you spend hours on trying to find all the pieces which seems to be broken on your system, redeploy it.
Can maybe someone explain how to rescue systems, e.g. when you created an Image over Harvester and want to boot this system image?
With MicroOS we don't rescue systems, we re-install them.
I don't find a lot of infos at the web about how to rescue systems at opensuse microOS and it will be really helpful - if someone can support me in this Topic.
Because, as written, it's faster to re-install MicroOS then to try to repair it ;)
Thorsten
Thanks a lot Have a lot of Fun.
Kind regards Torsten
-- torsten@linux.schule www.behrens.engineer
-- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany Managing Director: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman (HRB 36809, AG Nürnberg)