Yes, I'll send you the console info in a separate e-mail.
Rob
Rob,
Would it be possible for me to get console access to the machine? I'd
like to try out a test program to see if you're hitting a known issue.
-Drew
On 10/26/11 10:18 AM, Rob Lagunas wrote:
Trying to install 175b on a SPARC box and it fails with:
16:00:49 7% target-discovery completed.
16:00:49 === Executing Target Selection Checkpoint ==
16:00:49 Error occurred during execution of 'target-selection'
checkpoint.
16:00:49 Failed Checkpoints:
16:00:49
16:00:49 target-selection
16:00:49
16:00:49 Checkpoint execution error:
16:00:49
16:00:49 Unable to locate the disk '[boot-disk]' on the system.
16:00:49
16:00:49 Automated Installation Failed. See install log at
/system/volatile/install_log
Automated Installation failed
Please refer to the /system/volatile/install_log file for details
Here is what format on the system shows:
AVAILABLE DISK SELECTIONS:
0. c0t5000C50042DB863Bd0 <SUN300G cyl 46873 alt 2 hd 20 sec 625> solaris
/scsi_vhci/disk@g5000c50042db863b
/dev/chassis//SYS/HDD0/disk
1. c0t5000C50042BAB4FBd0 <SUN300G cyl 46873 alt 2 hd 20 sec 625> solaris
/scsi_vhci/disk@g5000c50042bab4fb
/dev/chassis//SYS/HDD4/disk
Here is the eeprom output from the system:
root:/system/volatile# eeprom
ttya-rts-dtr-off=false
ttya-ignore-cd=true
keyboard-layout=US-English
reboot-command: data not available.
security-mode=none
security-password: data not available.
security-#badlogins=0
verbosity=min
diag-switch?=false
local-mac-address?=true
fcode-debug?=false
scsi-initiator-id=7
oem-logo: data not available.
oem-logo?=false
oem-banner: data not available.
oem-banner?=false
ansi-terminal?=true
screen-#columns=80
screen-#rows=34
ttya-mode=9600,8,n,1,-
output-device=virtual-console
input-device=virtual-console
auto-boot-on-error?=false
load-base=16384
auto-boot?=false
network-boot-arguments: data not available.
boot-command=boot
boot-file: data not available.
boot-device=/pci@400/pci@1/pci@0/pci@4/scsi@0/disk@p0
multipath-boot?=false
boot-device-index=0
use-nvramrc?=false
nvramrc: data not available.
error-reset-recovery=boot
Note - 'boot-device' was set to 'disk net' and we changed it to what
you see now.
Here is what is between the 'target' tags in the manifest:
<target>
<disk whole_disk="true">
<disk_keyword key="boot_disk"/>
</disk>
<logical noswap="false" nodump="false">
<zpool name="rpool" is_root="true">
<vdev name="vdev" redundancy="none"/>
<be name="s11_175b"/>
</zpool>
</logical>
</target>
The system is factory new and has S10 installed on the disk.
What needs to be done to make AI happy enough to install?
Rob
PS - Let me know if you want to see the complete install_log; I can
make it available internally.
_______________________________________________
caiman-discuss mailing list
caiman-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
caiman-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
