How to examine files of child BE

Owned by Vitaly Shaburov
Jul 05, 2023
2 min read

On installation of the test version on step 6 of this instruction the sequence of actions looks like this:

  • the base stable version is installes (Dilos_BASE in the instruction)

  • the /etc/apt/sources.list file is changed to case the tested version of the system

  • the tested version is installed by the os-upgrade -r command

  • a machine is rebooted

Then the test version should be started. It’s possible that will not be loaded by any reason because it is just a test version. How to examine or correct its files manually?

To do this make reboot. In the appeared menu

select please item 6. Select Boot Environment and choose Dilos_BASE BE as active BE.

Boot to Dilos_BASE. Here you can see the list of existing BEs by the beadm list command. You will see something like this:

root@dilos-bld:~# beadm list BE Active Mountpoint Space Policy Created dilos_2.0.3.10 - - 15.82M static 2023-07-03 17:14 dilos_ISO_orig - - 45.86M static 2023-07-03 20:21 dilos_BASE N / 6.90M static 2023-07-03 20:33 dilos_2.0.3.11-20230629-5-0-int2 R - 744.14M static 2023-07-04 19:19 root@dilos-bld:~#

If you install (like in this example) dilos_2.0.3.11-20230629-5-0-int2 version and it was crashed, you can see its files and probably correct errors manually or make some analysis.

To do this please mount your test BE to any folder, for example, MOUNTDIR.

root@dilos-bld:~# beadm mount dilos_2.0.3.11-20230629-5-0-int2 /MOUNTDIR Mounted successfully on: '/MOUNTDIR' root@dilos-bld:~#

Now all file system of this BE will be visible inside this folder:

root@dilos-bld:~# ls -1 /MOUNTDIR bin boot dev devices etc export home kernel lib media mnt net opt platform proc root rpool run sbin srv system tmp usr var root@dilos-bld:~#

To get back to the tested BE just execute the activate command:

After reboot the dilos_2.0.3.11-20230629-5-0-int2 version will be started.