For what it is worth, I ended up using Linux to dd the Solaris partition from
an identical machine.
I realize that ZFS is a huge step forward on a huge number of fronts, but the
boot process has got to improve, or else it should not be offered as a root
filesystem. Even in the "bad old days" o
Neal Pollack wrote:
> Simple, the equiv of failsafe for OpenSolaris is to boot the live-cd,
> then manually mount your disk drive.
Yuck. The lack of a failsafe is a *huge* step backwards, considering how
fragile the ZFS root seems to be. The idea of having to have somebody on-site
at a datac
On 10/22/08 09:02 AM, Andrew Gallatin wrote:
Johan Hartzenberg wrote:
Reboot to the grub menu
Move to the failsafe kernel entry
Ugh. This is OpenSolaris (Indiana), and there *is* no failsafe
as far as I can tell. There is one grub entry for Solaris:
#-- ADDED BY BOOTADM - DO
Johan Hartzenberg wrote:
> Reboot to the grub menu
> Move to the failsafe kernel entry
Ugh. This is OpenSolaris (Indiana), and there *is* no failsafe
as far as I can tell. There is one grub entry for Solaris:
#-- ADDED BY BOOTADM - DO NOT EDIT --
title OpenSolaris 2008.05 snv_86_
Reboot to the grub menu
Move to the failsafe kernel entry
tap "e" to edit entry.
go to the kernel entry and tap "e" again
Append -kv to the end of the line
Accept and tap "b" to boot the line.
After some output you will be prompted to mount the root pool on /a - Enter
y to accept.
You will then g
Hi,
I have a triple boot amd64 Linux/FreeBSD/OpenSolaris box used for Q/A. It is
in a data center where I don't have easy physical access to the machine. It
was working fine for months, now I see this at boot time on the serial console:
SunOS Release 5.11 Version snv_86 64-bit
Copyright 19
