Skip to content

Solaris boot environment and lost changes

wordpress meta

title: 'Solaris Boot Environment And Lost Changes'
date: '2018-12-07T09:20:58-06:00'
status: publish
permalink: /solaris-boot-environment-and-lost-changes
author: admin
excerpt: ''
type: post
id: 1275
    - Solaris
tag: []
post_format: []

Maybe you have similarly been perplexed like me when you are missing a file after a new boot environment(BE) was activated.

In my example I know I created a file in my /root/Desktop folder and after pkg update and the resulting new BE was automatically activated and I rebooted I noticed my file was missing.

This can be quite nasty if you have made system changes and not noticed they all were lost. For example updating /etc/hosts etc…

Sequence that is faulty

After OS initial installation and before updates (pkg update)
Save a text file /root/Desktop/20181206-pkg-update
Current BE is openindiana

File is gone

Sequence that works

Save a text file /root/Desktop/20181206-pkg-update<br></br>beadm create new BE and activate<br></br>reboot immediately<br></br>pkg update<br></br>


Is there an easier way to update to avoid this problem? Maybe passing parms?

Read here also....

Tip: If just restoring a file you can just use beadm mount to find a specific file for retrieval or comparison with existing files.