Skip to Main Content

Hardware

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Sun Fire V100: "Can't read disk label." when "boot cdrom" is entered

807557Apr 22 2010 — edited Apr 23 2010
Connecting via LOM port to Sun Fire V100 I did a poweron:

lom>poweron
lom>
LOM event: +1h26m40s host power on
, no parity (configured from lom)

...................

lomp
Probing Memory Bank #0 0 Megabytes
Probing Memory Bank #1 0 Megabytes
Probing Memory Bank #2 256 Megabytes
Probing Memory Bank #3 256 Megabytes
Probing /pci@1f,0 Device 7
Probing /pci@1f,0 Device 3
Probing /pci@1f,0 Device c ethernet
Probing /pci@1f,0 Device 5 ethernet
Probing /pci@1f,0 Device a usb
Probing /pci@1f,0 Device d ide disk cdrom
todm5819 Sun Fire V100 (UltraSPARC-IIe 500MHz), No Keyboard
OpenBoot 4.0, 512 MB memory installed, Serial #51624041.
Ethernet address 0:3:ba:13:b8:69, Host ID: 8313b869.



Environment monitoring: disabled
Boot device: disk File and args:
Can't read disk label.
Can't open disk label package
Evaluating: boot

Can't open boot device

=============================

ok boot cdrom
Boot device: /pci@1f,0/ide@d/cdrom@3,0:f File and args:
Can't read disk label.
Can't open disk label package

Can't open boot device

=========================

ok show-disks
a) /pci@1f,0/ide@d/cdrom
b) /pci@1f,0/ide@d/disk
c) /pci@1f,0/ide@d/cdrom
d) /pci@1f,0/ide@d/disk
e) /pci@1f,0/isa@7/SUNW,lomh@0,8010
q) NO SELECTION
Enter Selection, q to quit: a
/pci@1f,0/ide@d/cdrom has been selected.
Type ^Y ( Control-Y ) to insert it in the command line.
e.g. ok nvalias mydev ^Y
for creating devalias mydev for
/pci@1f,0/ide@d/cdrom
ok nvalias cdrom /pci@1f,0/ide@d/cdrom
ok boot cdrom
Boot device: /pci@1f,0/ide@d/cdrom File and args:

Can't open boot device

ok setenv boot-device cdrom
boot-device = cdrom

ok probe-all
Probing /pci@1f,0 Device 7
Probing /pci@1f,0 Device 3
Probing /pci@1f,0 Device c ethernet
Probing /pci@1f,0 Device 5 ethernet
Probing /pci@1f,0 Device a usb
Probing /pci@1f,0 Device d ide disk cdrom
todm5819
ok probe-ide
Device 0 ( Primary Master )
Not Present

Device 1 ( Primary Slave )
Not Present

Device 2 ( Secondary Master )
Not Present

Device 3 ( Secondary Slave )
Not Present

=========================
My Question is WHY IS THERE NO DEVICE RECOGNIZED? (I HAVE CDROM AND SEAGATE BARRACUDA 40GB HDD inside.

And so I added an additional MAXTOR myself:

ok probe-all
Probing /pci@1f,0 Device 7
Probing /pci@1f,0 Device 3
Probing /pci@1f,0 Device c ethernet
Probing /pci@1f,0 Device 5 ethernet
Probing /pci@1f,0 Device a usb
Probing /pci@1f,0 Device d ide disk cdrom
todm5819
ok probe-ide
Device 0 ( Primary Master )
ATA Model: MAXTOR 6L040J2

Device 1 ( Primary Slave )
Not Present

Device 2 ( Secondary Master )
Not Present

Device 3 ( Secondary Slave )
Not Present

Now the MAXTOR is recognized. WHY? From the jumper on the seagate, I can see that it is set to Master. But I did not check the cdrom - just bought this from someone, I assumed everything is default.

--
Regards,
Peter Teoh
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on May 21 2010
Added on Apr 22 2010
3 comments
1,893 views