Skip to content
This repository has been archived by the owner. It is now read-only.

update problem #28

Closed
bozhikovstanislav opened this issue Jul 1, 2019 · 11 comments
Closed

update problem #28

bozhikovstanislav opened this issue Jul 1, 2019 · 11 comments

Comments

Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@bozhikovstanislav
Copy link

@bozhikovstanislav bozhikovstanislav commented Jul 1, 2019

When trying to update from 19.05 to 19.06 - it get nonworking system.
sudo useres are out - have to re-enable them.
sysadm service do not work
no restart

@beanpole135
Copy link
Member

@beanpole135 beanpole135 commented Jul 1, 2019

You did not apply the pre-update errata/patch which we published in both the release announcement[1] as well as the graphical update manager (19.05+).
You will need to roll back your boot environment and then apply the patch before proceeding with the update again.

https://project-trident.org/post/2019-06-28_19.06_available/

@beanpole135 beanpole135 closed this Jul 1, 2019
@bozhikovstanislav
Copy link
Author

@bozhikovstanislav bozhikovstanislav commented Jul 2, 2019

this do not work at all I try it :(

@maxsteciuk
Copy link
Contributor

@maxsteciuk maxsteciuk commented Jul 2, 2019

Could you please be more specific? What were the steps you tried and what didn’t work?
The steps should’ve been in this order:

  1. Rollback to previous BE, by selecting it via bootmgr (option 7)
  2. Ensure broken BE (U6) is removed; via trident-updatemgr GUI
  3. sudo pkg -fy install sysup
  4. Check & start upgrade via trident-updatemgr GUI

@bozhikovstanislav
Copy link
Author

@bozhikovstanislav bozhikovstanislav commented Jul 2, 2019

@beanpole135
Copy link
Member

@beanpole135 beanpole135 commented Jul 2, 2019

From 19.05 Boot environment:

  1. Run: sudo pkg install -fy sysup
    • This will bootstrap the newer version of the update utility
  2. Run: sudo sysup -update
    • This will perform the updates (previously downloaded files will be re-used, so this should not take long at all)
  3. Run: shutdown -r now
    • This will reboot the system to finish applying updates

@bozhikovstanislav
Copy link
Author

@bozhikovstanislav bozhikovstanislav commented Jul 2, 2019

@bozhikovstanislav
Copy link
Author

@bozhikovstanislav bozhikovstanislav commented Jul 2, 2019

@bozhikovstanislav
Copy link
Author

@bozhikovstanislav bozhikovstanislav commented Jul 2, 2019

@beanpole135
Copy link
Member

@beanpole135 beanpole135 commented Jul 2, 2019

If your users/groups are working properly now, that means the update succeeded, but your system might be one of the ones that is impacted by a bug in the "devmatch" service from upstream TrueOS.

Verify the problem:

  • Run rc-status and see if the "devmatch" and "network" services are listed as "stopped"

Fix the problem:

  • Run sudo edit /etc/rc.conf.d/trident.conf to open up a text editor on that file.
  • Find the line which looks like this: "rc_network_need=devmatch"
  • Put an "#" at the beginning of that line.
  • Hit the escape key and follow the prompts to save and quit the editor.
  • Run "shutdown -r now" to reboot the system.
  • Everything should properly startup again, including the network service and sysadm.

@bozhikovstanislav
Copy link
Author

@bozhikovstanislav bozhikovstanislav commented Jul 2, 2019

@bozhikovstanislav
Copy link
Author

@bozhikovstanislav bozhikovstanislav commented Jul 2, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.