[Solved] antiX-19.2-core installation stuck at “restoring service links”

[Member anilkagi]

Hello there,

I am trying to install antix-19.2-x64-core on VBox, but the installation is stuck at;

live-restore-services: restoring service links

I thought the ISO image may have some issue and so I downloaded another ISO file from a different mirror. I have verified the md5sum, sha256sum and the signatures of both the ISO images that I have downloaded. The are fine.

I have not changed any F4 or F5 options. I have done a regular boot.

I have installed antiX-19.2.1-x64-Base on the VB, and it is working fine.

I don’t know what is happening? Please guide.

Thanks & Regards

• This topic was modified 2 years, 8 months ago by anilkagi.

[Member Xecure]

Helpful

Up

0

::

Do you get stuck booting antiX core or does it get stuck installing (cli-installer)? During what step?

if it is the first (booting), boot in failsafe mode (or without splash).
You probably already searched the forum, so maybe this is not what you mean.

Please describe your problem a bit more so others can try to help.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member anilkagi]

Helpful

Up

0

::

Thank you Xecure for resolving the issue.

The failsafe boot succeeded.

I searched the forum with error terms i.e. “live-restore-services: restoring service links”, and got nill results and then a startpage search yielded this.

There I took Dolphin oracle’s suggestion “this is odd, and may indicate a problem with your media.” and downloaded another ISO. When that too failed I browsed through more startpage search results but couldn’t find any related discussion, so had to post. I did not know what is a failsafe boot till now and I don’t know much of what other options mean on the boot screen, so I had to take the guidance of someone knowledgeable in the matter.

Thanks again for coming and suggesting a solution. I will mark this thread solved, though this is the same issue discussed in the link you provided but the title of this thread is more relevant and close to the issue I suppose and would be easy for others searching for solutions to the same issue.

[Member seaken64]

Helpful

Up

0

::

Someone will correct me if I am wrong, but I don’t think you want to rely on a Failsafe boot. It is really a troubleshooting tool. It would probably be best to figure out why the regular boot is not working.

Seaken64

[Moderator christophe]

Helpful

Up

0

::

I ran ito this problem a while back, too. https://www.antixforum.com/forums/topic/version-19-2-core-isos-hang-on-first-boot-in-virtualbox/#post-34650

If I remember right, once I installed X, I then installed virtualbox guest X-server — or maybe some x guest addition thing? — from cli-aptiX. (It was a while ago, and the VM is erased now.)

But others don’t have the problem, so maybe it depends on the video hardware?

• This reply was modified 2 years, 8 months ago by christophe.

confirmed antiX frugaler, since 2019

[Moderator christophe]

Helpful

Up

0

::

“virtualbox-guest-x11” package is probably the one.

• This reply was modified 2 years, 8 months ago by christophe.

confirmed antiX frugaler, since 2019

[Member Xecure]

Helpful

Up

0

::

anilkagi wrote:

I searched the forum with error terms i.e. “live-restore-services: restoring service links”, and got nill results

The forum’s search engine isn’t the best. I usually try to use words describing the problem (core boot fail) and try to avoid “special characters” (like :,”).

seaken64 wrote:

Someone will correct me if I am wrong, but I don’t think you want to rely on a Failsafe boot. It is really a troubleshooting tool. It would probably be best to figure out why the regular boot is not working.

That is the “easy” solution I gave on my previous post. The reason boot “fails” is related to the splash=v option (deleting this boot option and booting will also boot correctly).

When the splash=v option is enabled, rendering text stops after live-restore-services: restoring service links text (as reported above), but the system has loaded correctly (even if you cannot see it). If you change tty (move to Control+Alt+F2) and then return to tty1 (Control+Alt+F1) you will see that it has loaded correctly. If you write stuf, it will look like it isn’t working, but if you change tty again, you will see that what you wrote before is there. You can even execute stuf, but there is no visual feedback until you change tty again.

This is not only related to virtualbox. On some devices, like my desktop PC (mixed UEFI and Legacy_BIOS boot), I experience the same problem.

I don’t know what failsafe does, but with it I can boot core using splash=v boot option, so it is good enough for me before installing any X.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member olsztyn]

Helpful

Up

0

::

Xecure wrote:

This is not only related to virtualbox. On some devices, like my desktop PC (mixed UEFI and Legacy_BIOS boot), I experience the same problem.

MHO is that trying to resolve such issues under VB make only sense if ultimately such system will run under VB in ‘production’ rather than for testing.
VB hardware, particularly that video in VB is much different from real nowadays video hardware therefore resolving such issue in VB does not mean it will work when installed on the actual hardware.
If the final system will be running on actual machine and not in VB then it is better to test it as Live or Frugal instead.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Author]

Posts