I have a test server running Solaris 11.2 (on HP Proliant Gen8 Microserver hardware). On October 31st I upgraded the system to Solaris 11.3 as described in Solaris documentation article Updating a System to Oracle Solaris 11.3 and everything seemed to go smoothly. After two weeks I shut down the server with
shutdown -y -i5 -g0
After starting the server again, the state of the rpool has been reverted to the state before the upgrade. Logging in with ssh displayed the last login time being October 31st, even though I logged in on November 14th. Running
uname -a
displays
SunOS nas3 5.11 11.2 i86pc i386 i86pc
and all the files on rpool created after October 31st are gone. The console shows the message
nas3 console login: Nov 15 18:11:34 nas3 genunix: NOTICE: /dev/chassis/.ca/Proliant-MicroServer-Gen8.CZ152300T4/SYS: cannot create shadow directory - error
Unfortunately there are no snapshots of the rpool. Questions:
- What could have caused this?
- Is there any way to get back the data saved on rpool after the upgrade?
What I have tried:
- googling (of course) Google doesn't have a single result for the search query "cannot create shadow directory".
- searching for Solaris documentation, e.g. Issues When Updating to Oracle Solaris 11.3
- checking ZFS snapshots. Unfortunately, none have been made (yes, that was not very wise)
- checking the state of rpool - it is reported being healthy and without errors
Update
Running
beadm list
shows
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
solaris N / 171.47M static 2015-08-16 17:51
solaris-1 R - 14.72G static 2015-10-31 21:52
Solution
As pointed out by Lambert, the boot environment was wrong. Just rebooting with
init 6
fixed the issue. It would still be interesting to find out what caused this.
Update 2:
Apparently running
beadm activate solaris-1
activated permanently the new partition. See Changing the Default Boot Environment.