SEO

#1 (**permalink**) 01-16-2008, 01:23 PM

Hi,

I have one Blade 1500 which worked well before, but now it's complaining
about

#boot cdrom

I get error msg after issue boot cdrom, I called Sun Micro support, they
didn't find any answer till now.

I also updated the PROM firmware to the latest one. Same thing happens.

Boot device: /pci@1f,0/pci@1/1/ide@3/cdrom@2,0:f File and args: [[ -nowin]]
Can't read disk label
Can't read disk label package
Evaluating: boot cdrom [[ -nowin]]
Can't open boot device

Any clue ?

Thanks in advance.

#2 (**permalink**) 01-16-2008, 01:23 PM

Daniel Huang wrote:
> Hi,
>
> I have one Blade 1500 which worked well before, but now it's complaining
> about
>
> #boot cdrom

If that's the command from a root shell, then you have no
chance. To reboot from a root shell you should use something
like "reboot -- cdrom"

> I get error msg after issue boot cdrom, I called Sun Micro support, they
> didn't find any answer till now.

What question did you ask?

> I also updated the PROM firmware to the latest one. Same thing happens.

Did Sun recommend that?

> Boot device: /pci@1f,0/pci@1/1/ide@3/cdrom@2,0:f File and args: [[ -nowin]]
> Can't read disk label
> Can't read disk label package
> Evaluating: boot cdrom [[ -nowin]]
> Can't open boot device
>
> Any clue ?
>
> Thanks in advance.
>
>

From the OBP ok> prompt, can you type "set-default
boot-file" (without the quotes), and then try "boot cdrom"?

I assume that you are actually trying to reinstall this
system. If it "worked well before", why do you need to
reinstall?.....

Also are you installing from Sun media, or home-burned? You
might have a burning issue...

#3 (**permalink**) 01-16-2008, 01:23 PM

In article <cmb2vh$686u$1@netnews.upenn.edu>, "Daniel Huang" <danielhuang@hotmail.com> writes:
> Hi,
>
> I have one Blade 1500 which worked well before, but now it's complaining
> about
>
> #boot cdrom

You certainly mean

OK> boot cdrom

>
> I get error msg after issue boot cdrom, I called Sun Micro support, they
> didn't find any answer till now.
>
> I also updated the PROM firmware to the latest one. Same thing happens.
>
> Boot device: /pci@1f,0/pci@1/1/ide@3/cdrom@2,0:f File and args: [[ -nowin]]
> Can't read disk label
> Can't read disk label package
> Evaluating: boot cdrom [[ -nowin]]
> Can't open boot device
>
> Any clue ?
>
> Thanks in advance.
>
>

Maybe the cables are wrong, or the jumper on the CD drive is wrong.
Look at the hardware manual (delivered on CD...).

--
Michael Tosch
IT Specialist
HP Managed Services
Technology Solutions Group
Hewlett-Packard GmbH
Phone: +49 2407 575 313
Mail: michael.tosch:hp.com

#4 (**permalink**) 01-16-2008, 01:23 PM

Thanks for the reply. All these command were issued in PROM. Have nothing to
do with Sun OS.

I tried several installation CDs, these disks were duplicated from oregional
Sun solaris cd disk. And the cd worked well before.

The problem is we now have two Sun Blade have same problem like this, and
they are all like 6 months new.

I have swap the cd drive and cable, so we are sure the drive and cable are
good.

I guess some thing wrong with the NVRam or Prom.

Still waiting for Sun's support call.

"Michael Tosch" <eedmit@NO.eed.SPAM.ericsson.PLS.se> wrote in message
news:cmb5hq$nmd$1@aken.eed.ericsson.se...
> In article <cmb2vh$686u$1@netnews.upenn.edu>, "Daniel Huang"
> <danielhuang@hotmail.com> writes:
>> Hi,
>>
>> I have one Blade 1500 which worked well before, but now it's complaining
>> about
>>
>> #boot cdrom
>
> You certainly mean
>
> OK> boot cdrom
>
>>
>> I get error msg after issue boot cdrom, I called Sun Micro support, they
>> didn't find any answer till now.
>>
>> I also updated the PROM firmware to the latest one. Same thing happens.
>>
>> Boot device: /pci@1f,0/pci@1/1/ide@3/cdrom@2,0:f File and args:
>> [[ -nowin]]
>> Can't read disk label
>> Can't read disk label package
>> Evaluating: boot cdrom [[ -nowin]]
>> Can't open boot device
>>
>> Any clue ?
>>
>> Thanks in advance.
>>
>>
>
> Maybe the cables are wrong, or the jumper on the CD drive is wrong.
> Look at the hardware manual (delivered on CD...).
>
> --
> Michael Tosch
> IT Specialist
> HP Managed Services
> Technology Solutions Group
> Hewlett-Packard GmbH
> Phone: +49 2407 575 313
> Mail: michael.tosch:hp.com
>
>

#5 (**permalink**) 01-16-2008, 01:23 PM

On Wed, 03 Nov 2004 18:26:42 -0500, Huang, Daniel wrote:

> Thanks for the reply. All these command were issued in PROM. Have nothing to
> do with Sun OS.
>
> I tried several installation CDs, these disks were duplicated from oregional
> Sun solaris cd disk.

You cannot do that with Windows and it is a PITA to do it using Solaris.

Can you boot the original Software CD 1/2?

#6 (**permalink**) 01-16-2008, 01:23 PM

Dave Uhring wrote:
> On Wed, 03 Nov 2004 18:26:42 -0500, Huang, Daniel wrote:
>
>
>>Thanks for the reply. All these command were issued in PROM. Have nothing to
>>do with Sun OS.
>>
>>I tried several installation CDs, these disks were duplicated from oregional
>>Sun solaris cd disk.
>
>
> You cannot do that with Windows and it is a PITA to do it using Solaris.

Why not?

There are no Solaris machines with recorders in our shop, so I have no
choice but to duplicate on Windows. Never had a problem with a Solaris
CD made using the 'copy disc' or equivalent function in any Windows
recording package.

> Can you boot the original Software CD 1/2?
>

#7 (**permalink**) 01-16-2008, 01:23 PM

On Wed, 03 Nov 2004 19:35:56 -0500, Triffid wrote:

> Dave Uhring wrote:

>> You cannot do that with Windows and it is a PITA to do it using Solaris.
>
> Why not?

Windows can read neither the CD's VTOC nor the UFS filesystems on Software
CD 1/2.

> There are no Solaris machines with recorders in our shop, so I have no
> choice but to duplicate on Windows. Never had a problem with a Solaris
> CD made using the 'copy disc' or equivalent function in any Windows
> recording package.

Perhaps a utility which can read the bits on a CD might be able to
generate an ISO image. My own experience with Windows CD utilities has
been decidedly negative.

>> Can you boot the original Software CD 1/2?

That remains the operative question.

#8 (**permalink**) 01-16-2008, 01:23 PM

Dave Uhring wrote:
> On Wed, 03 Nov 2004 19:35:56 -0500, Triffid wrote:
>
>
>>Dave Uhring wrote:
>
>
>>>You cannot do that with Windows and it is a PITA to do it using Solaris.
>>
>>Why not?
>
>
> Windows can read neither the CD's VTOC nor the UFS filesystems on Software
> CD 1/2.

Nor does it need to in order to copy a disc.

>>There are no Solaris machines with recorders in our shop, so I have no
>>choice but to duplicate on Windows. Never had a problem with a Solaris
>>CD made using the 'copy disc' or equivalent function in any Windows
>>recording package.
>
>
> Perhaps a utility which can read the bits on a CD might be able to
> generate an ISO image. My own experience with Windows CD utilities has
> been decidedly negative.

The copy disc function typically reads the bits from the source disc and
writes them to the destination disc, and therefore requires no
understanding of the data format or content. AFAIK no Windows utility is
able to correctly generate an ISO9660 image of a Solaris CD.

>>>Can you boot the original Software CD 1/2?
>
>
> That remains the operative question.
>
>

#9 (**permalink**) 01-16-2008, 01:23 PM

No sure what you talking about, I've beening using CDRW software on both
windows and solaris platform to burn solaris installation disk 1 & 2, they
all use iso9660 FS, never have any problem

"Dave Uhring" <daveuhring@yahoo.com> wrote in message
news

an.2004.11.03.23.43.53.546610@yahoo.com...
> On Wed, 03 Nov 2004 18:26:42 -0500, Huang, Daniel wrote:
>
>> Thanks for the reply. All these command were issued in PROM. Have nothing
>> to
>> do with Sun OS.
>>
>> I tried several installation CDs, these disks were duplicated from
>> oregional
>> Sun solaris cd disk.
>
> You cannot do that with Windows and it is a PITA to do it using Solaris.
>
> Can you boot the original Software CD 1/2?
>

#10 (**permalink**) 01-16-2008, 01:23 PM

On Wed, 03 Nov 2004 22:00:20 -0500, Triffid wrote:

> The copy disc function typically reads the bits from the source disc and
> writes them to the destination disc, and therefore requires no
> understanding of the data format or content. AFAIK no Windows utility is
> able to correctly generate an ISO9660 image of a Solaris CD.

I wonder what that 600MB file which gets created in one of the TEMP
direc^H^H^H^H^H folders was. As I had only one CD device in the machine
and 512MB of memory I wonder how the copy was done bit by bit from one CD
to the other.

>>>>Can you boot the original Software CD 1/2?
>>
>>
>> That remains the operative question.

Let's just keep ignoring that question.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

can't open boot label On Blade 1500