Well, I do not think that your system had a panic reboot and there's nothing to worry.
# lvlnboot -v is a command to print information on root, boot, and swap logical volumes. It also prints information about dump lv's.
#lvlnboot is a command to prepare lv's to be root, boot, swap or dump.
==> #man lvlnboot would give you more information!
If you need to know how this works, just type in "# lvlnboot -v" and you'll know it.
Second.
There are 2 cases.
1) Panic reboot (Which happens automatically)
2) Manual TOC (We do it when the system hungs and do not respond)
As system administrator, we would know if the system had a panic reboot or a manual TOC.
If you want to analyze it anyway (After a panic or TOC), you can go ahead and run a tools on to it to collect a output to analyze.
Like,
crashinfo (Latest)
q4 (Kinda old, though good)
Its actually run on "/var/adm/crash"
When you collect the output from the tool, and analyze it along with shutdownlog.log, rc.log, oldshutdownlog.log, ts99, etc.. you can find information on why the system went panic. May be a HPMC, hardware or software (It depends on servers and issues anyways)
Once you find the reason for the crash, you can fix it to make sure that the server does not reboot the second time because of the same problem.
However, analyzing it properly gives you those information! So, now in your case, I do not see any clue for system being panic since lvlnboot does not mean that the system went panic!
