ERROR: Can't open boot-device

tt155 · November 17, 2005, 11:16am

Hi i need help pls ...

Server type sun fire 3800 I need to install solaris 9 .
When i boot the system i recieve the following :

System Controller 'sunfire3800':

Type  0  for Platform Shell

Type  1  for domain A console
Type  2  for domain B console
Type  3  for domain C console
Type  4  for domain D console

Input: 1

Connected to Domain A

Halting system...

syncing file systems... done
NOTICE: f_client_exit: Program terminated!
debugger entered.

{9} ok
{8} ok devalias
Alias Device Path
--------------------------------------------------
xdisk /ssm@0,0/pci@1c,700000/pci@2/SUNW,isptwo@4/sd@0,0
xnet /ssm@0,0/pci@1c,700000/pci@2/SUNW,hme@0,1
vx-rootdisk /ssm@0,0/pci@18,700000/pci@2/SUNW,isptwo@4/sd@0,0
vx-disk01 /ssm@0,0/pci@18,700000/pci@2/SUNW,isptwo@4/sd@1,0
diskc /ssm@0,0/pci@1c,700000/pci@1/SUNW,isptwo@4/sd@0,0
netc /ssm@0,0/pci@1c,700000/pci@1/SUNW,hme
cdrom /ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo@4/sd@6,0:f
disk /ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo@4/sd@0,0
disk0 /ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo@4/sd@0,0
disk1 /ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo@4/sd@1,0
disk2 /ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo@4/sd@2,0
disk3 /ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo@4/sd@3,0
disk4 /ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo@4/sd@4,0
disk5 /ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo@4/sd@5,0
def-cn /sgcn
diskifp /ssm@0,0/pci@19,700000/SUNW,ifp@1/ssd@0,0
diskglm /ssm@0,0/pci@18,700000/scsi@2/disk@0,0
scsi /ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo
net /ssm@0,0/pci@18,700000/pci@1/SUNW,hme

{8} ok setenv boot-device cdrom

{8} ok boot cdrom

ERROR: Can't open boot-device
Why i receive this error message ?????

Grazie/tnks

RTM · November 18, 2005, 1:07pm

From sunsolve

When booting from cdrom from a Sun Fire[TM] server, you receive the message:

ok> boot cdrom -s
ERROR: Can't open boot-device

Document Body: Top

Resolution:

The common resolution to this problem points to an incorrect devalias entry for
the cdrom. This is very common especially for configurations with the D240 with
split backplanes. It is therefore a good idea not to trust the default entries
and verify/correct the cdrom entry in the OBP.

Procedure:

I. Issue the probe-scsi-all and sift through the outputs until you see the
removable read-only device. In our example the device path from an E6900 is at:

/ssm@0,0/pci@1e,700000/pci@1/scsi@2, target 6

{4} banner

Sun Fire E6900
OpenFirmware version 5.17.0 (03/05/04 11:27)
Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
SmartFirmware, Copyright (C) 1996-2001. All rights reserved.
32768 MB memory installed, Serial #50823586.
Ethernet address 0:3:ba:7:81:a2, Host ID: 830781a2.

{4} ok probe-scsi-all

/ssm@0,0/pci@1f,700000/SUNW,qlc@2,1
/ssm@0,0/pci@1f,700000/SUNW,qlc@2
************************* Fabric Attached Devices ************************
Adapter portId - 10000
Device PortId 11055 DeviceId 1 WWPN 5005076300617dec
Lun 0 TAPE IBM ULTRIUM-TD2 38D0
Device PortId 11155 DeviceId 2 WWPN 500507630061779a
Lun 0 TAPE IBM ULTRIUM-TD2 38D0

/ssm@0,0/pci@1e,700000/pci@1/scsi@2,1

/ssm@0,0/pci@1e,700000/pci@1/scsi@2
Target 0
Unit 0 Disk HITACHI DK32EJ72NSUN72G PQ08
Target 3
Unit 0 Processor Sun D240 1.09
Target 6
Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011009

/ssm@0,0/pci@1b,700000/SUNW,qlc@2,1

------------------ end of output --------------------

II. Set the alias for the removable read only device using nvalias and append
disk@6,0:f. Save the entry using the nvstore command.

{4} ok nvunalias cdrom
{4} ok nvalias cdrom /ssm@0,0/pci@1e,700000/pci@1/scsi@2/disk@6,0:f

III. Reissue the command to boot the domain
{4} ok boot cdrom -s

See SRDB 71504 for related info.

tt155 · November 21, 2005, 6:03am

Hi..... tnks for your help ....

Could you tell me how i have to set my cdrom nvalias please ???

{7} ok banner

Sun Fire 3800
OpenFirmware version 5.15.2 (08/04/03 10:27)
Copyright 2001-2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
SmartFirmware, Copyright (C) 1996-2001. All rights reserved.
4096 MB memory installed, Serial #15261890.
Ethernet address 8:0:20:e8:e0:c2, Host ID: 80e8e0c2.

{8} ok probe-scsi-all

/ssm@0,0/pci@1c,700000/pci@2/SUNW,isptwo@4
Target 1
Unit 0 Disk SEAGATE ST336704LSUN36G 0326
Target 2
Unit 0 Disk SEAGATE ST336704LSUN36G 0326
Target 3
Unit 0 Disk SEAGATE ST336704LSUN36G 0326
Target 4
Unit 0 Disk SEAGATE ST336704LSUN36G 0326
Target 5
Unit 0 Disk SEAGATE ST336704LSUN36G 0326
Target 6
Unit 0 Disk SEAGATE ST336704LSUN36G 0326

/ssm@0,0/pci@18,700000/pci@2/SUNW,isptwo@4
Target 0
Unit 0 Disk SEAGATE ST318404LSUN18G 4203
Target 1
Unit 0 Disk SEAGATE ST318404LSUN18G 4203
Target 2
Unit 0 Processor SUN D240 2
Target 3
Unit 0 Processor SUN D240 2
Target 4
Unit 0 Removable Tape HP C5683A C005
Target 6
Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011007

___________________________

{9} ok nvalias cdrom /............................................

tnks in advance !!!!!!!!!!!!!!!!!!!!!

RTM · November 21, 2005, 9:40am

If you had followed the instructions given, you should have found that the following is correct for your server in this case
/ssm@0,0/pci@18,700000/pci@2/SUNW,isptwo@4/disk@6,0:f

tt155 · November 21, 2005, 11:43am

I asked because with the above alias path i received the same error :

{8} ok devalias
Alias Device Path
--------------------------------------------------
netc /ssm@0,0/pci@1c,700000/pci@1/SUNW,hme
cdrom /ssm@0,0/pci@18,700000/pci@2/SUNW,isptwo@4/disk@6,0:f

{8} ok printenv boot-device
boot-device cdrom
{8} ok boot cdrom
ERROR: Can't open boot-device

__________________________________________

instead with :

ok nvalias cdrom /ssm@0,0/pci@18,700000/pci@2/SUNW,isptwo@4/sd@6,0:f

it's ok !!!

_______________________________________________

thank's a lot for you help !!!!!!!!

knodel · June 20, 2006, 10:39am

You can determine what the last portion of the command should be by cd'ing into the device path and doing an ls.

In the above example, if you executed 'cd /ssm@0,0/pci@18,700000/pci@2/SUNW,isptwo@4' then 'ls' you would have seen something like:

{0} ok cd /ssm@0,0/pci@18,700000/pci@2/SUNW,isptwo@4
{0} ok ls
0x00000000f133b800 st
0x00000000f133cf10 sd

This tells you that the device driver choices are SD - scsi disk or ST - scsi tape. The 'Disk' device type is an older device type. So its sd@6,0 (target, unit). The :f is just PFM for CDROM's.