The system will always boot the GRUB in the Solaris partition regardless of which fdisk partition is active. Do not use the installgrub command to install the boot loader on systems that have GRUB 2 installed, otherwise you can render the system unbootable.
For more information, see the bootadm 1M man page. Exit Print View. Search Scope:. This Document Entire Library. Documentation Home » Oracle Solaris The following is a description of the device naming convention that is used by the findroot command for various GRUB implementations:. This section describes how multiple operating systems that are on the same disk are supported with GRUB.
The Solaris slice must be the active partition. Also, do not indicate makeactive under the Windows menu. Doing so causes the system to boot Windows every time.
The inability to access the Solaris boot option occurs whether or not you designate it as the active partition. Chain-loading is a mechanism for loading unsupported operating systems by using another boot loader.
Replace the master boot block with the Solaris GRUB by running the installgrub command with the -m option:. See the installgrub 1M man page for more information. The contents of the menu.
For a description of the menu. The following are various examples of a menu. Because the miniroot is mounted as the real root file system, the entry for failsafe booting in the menu. The ZFS dataset is not accessed after the boot loader reads the miniroot. The following are examples of a menu. You can run the Solaris OS as a virtualized control domain, with the hypervisor.
To run the Solaris release with this support, there must be an entry in menu. This entry can either be the default boot menu item, or you can select this entry manually at boot time. After you upgrade your system for the first time to a Solaris release that includes this support, the bootadm command automatically adds a GRUB menu.
Note that the path to UNIX in the menu. If you choose to run the Solaris release as a stand-alone OS, you can continue to use the same GRUB menu entries that you used previously. Booting Solaris from Grub now resulted in the system freezing shortly after displaying the copyright notice. Booting the system with the -a and -v flags showed me that it was pausing right after asking for the path to the "retire store".
After some intense googling, this is what I came up with as a solution. At this point the system no longer froze up after showing the copyright notice. Instead, it teased me by making it a little bit further but then, quicker than you could read, it flashed up a bunch of text on the screen and instantly rebooted itself. I tried a few different tricks to be able to read the text but eventually had to settle on recording the boot up on my camera and playing it back frame by frame.
The very last line was the key. Somewhere, Solaris was still configured to boot from the device path that pointed to the boot slice under the old hardware. Booting from the live CD once again, I used the format 1m command to determine the proper device path to the boot drive.
At this point the system was booting normally from the hard drive. The last step was to import the ZFS pools using zpool import. ZFS successfully scanned the drives, determined the new paths to the pool members, and mounted all of the file systems.
Read other posts.
0コメント