Hello,
Antergos won't run after a Update. I don't know, if it is the Antergos-Update or the VBox-Update or both...
But I can give you the report, VBox give me out, when I start unsuccessfull Antergos on my Antergos-Host.
One last tip. When I start an older protection point, a protection point from 22.02.2019, then Antergos start perfekt. The problem appears in that case after die date.
I hope you could help, because so I could not import any Update of Antergos and/or VBox and the system is UNSAFE! In my eyes, this is a big catastrophe.
This problem is also here posted: https://forum.antergos.com/topic/11432/ ... ter-update
No start of Antergos after Update
No start of Antergos after Update
- Attachments
-
- Fehler.jpg (14.9 KiB) Viewed 1802 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: No start of Antergos after Update
The error message highlighted is caused by upgrading VirtualBox while the VM was in a suspended state. Right click the VM in the manager and discard the saved state: the VM will behave like a physical PC after a power cut.
Re: No start of Antergos after Update
@ mpack: Sorry, but so clever I also was.
When I delete the protection point which makes problems, then I take the working protection point vom 22.02.2019, then I make Updates and a reboot, then safing the new state of the maschine, then I close the maschine, then I start the new protection point and the problem is the same.
ONLY the old protection point works, but I am not allowed to update the old working state, because then the problem appears.
When I delete the protection point which makes problems, then I take the working protection point vom 22.02.2019, then I make Updates and a reboot, then safing the new state of the maschine, then I close the maschine, then I start the new protection point and the problem is the same.
ONLY the old protection point works, but I am not allowed to update the old working state, because then the problem appears.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: No start of Antergos after Update
It isn't clear to me what you are saying. The error is with a saved state file trying to restore a state that is incompatible with the upgraded version of VirtualBox. If the saved state is discarded then the error cannot occur.
Re: No start of Antergos after Update
Update:
1. I take the working protection point (the machine did not boot, the working protection point is a running (!) machine) and start all updates
2. I reboot the machine
3. I save the new state of the machine with the updates
The rest would be important:
4. I turn off the machine completely (so that the machine have to boot after starting)
5. The machine boot
6. Now Antergos ist running, without problems -> I make a new protection point of the RUNNING machine
7. I close the machine
8. I start the machine without problems
WORKAROUND
1. I take the working protection point (the machine did not boot, the working protection point is a running (!) machine) and start all updates
2. I reboot the machine
3. I save the new state of the machine with the updates
The rest would be important:
4. I turn off the machine completely (so that the machine have to boot after starting)
5. The machine boot
6. Now Antergos ist running, without problems -> I make a new protection point of the RUNNING machine
7. I close the machine
8. I start the machine without problems
WORKAROUND
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: No start of Antergos after Update
Take a look at the Known Issues in the "Discuss the 6.0.0 release" post.
You are seeing the effects of saved states not being restored in 6.0.x. There are three of them (and many, many duplicates):
You are seeing the effects of saved states not being restored in 6.0.x. There are three of them (and many, many duplicates):
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.