Cannot boot cdrom -s


 
Thread Tools Search this Thread
Top Forums UNIX for Beginners Questions & Answers Cannot boot cdrom -s
# 8  
Old 01-18-2019
My commands are for the ok> prompt, after an "init 0" from the Solaris OS.
Maybe your prompt is slightly different: {1} ok .
Another useful command is:
Code:
ok> printenv

This User Gave Thanks to MadeInGermany For This Post:
# 9  
Old 01-18-2019
You have two processors there. The service processor and the main processor. You cannot boot from cdrom into single user if the main processor is up and running Solaris. Is your terminal connected to the main console or (or a redirection from the main console port)?

If
Code:
setenv

and
Code:
boot

are "not found" then you are talking to the main processor which is running.

If this is NOT a production box then:

Type these keystrokes:

Code:
#.

which will ensure that you are talking to the service processor. Hit return a couple of times to check you have a
Code:
OK>

prompt from the service processor.

Enter:

Quote:
ok> halt
to ensure that the main processor is down

Then you can:

Code:
ok> boot cdrom -s

Try all the installation cdrom's you have this way.

Yes, this could be a hardware fault but it's not likely.

It's more likely that the main processor is not down (stopped) when you are trying to boot from cdrom.

Last edited by hicksd8; 01-18-2019 at 05:19 PM.. Reason: Correct typo's
These 3 Users Gave Thanks to hicksd8 For This Post:
# 10  
Old 01-22-2019
Quote:
Originally Posted by MadeInGermany
My commands are for the ok> prompt, after an "init 0" from the Solaris OS.
Maybe your prompt is slightly different: {1} ok .
Another useful command is:
Code:
ok> printenv


Thanks.. printenvdid show auto-boot? true true I then changed it to false and it says auto-boot? false true

Quote:
Originally Posted by hicksd8
You have two processors there. The service processor and the main processor. You cannot boot from cdrom into single user if the main processor is up and running Solaris. Is your terminal connected to the main console or (or a redirection from the main console port)?

If
Code:
setenv

and
Code:
boot

are "not found" then you are talking to the main processor which is running.

If this is NOT a production box then:

Type these keystrokes:

Code:
#.

which will ensure that you are talking to the service processor. Hit return a couple of times to check you have a
Code:
OK>

prompt from the service processor.

Enter:



to ensure that the main processor is down

Then you can:

Code:
ok> boot cdrom -s

Try all the installation cdrom's you have this way.

Yes, this could be a hardware fault but it's not likely.

It's more likely that the main processor is not down (stopped) when you are trying to boot from cdrom.

Ok thank you... I did not know there were two different processors.


So when I set auto-boot? false, and start the machine up, it immediately goes to the {1} ok prompt, instead of requiring me to log in and init 0 from a terminal. When I #., I get #. ? and when I halt, I get halt ?


The installation CD gives me a different error than the Operating environment cd:
Code:
Boot device: /pci@1e,600000/ide@d/cdrom@2,0:f File and args: -s
boot: cannot open kernel/sparcv9/unix
Enter filename [kernel/sparcv9/unix

Note- the drive is actually a DVD drive, not a CDROM drive. I don't recall this making a difference in the past. Does it?

--- Post updated at 09:11 AM ---

In printenv, boot-file shows nothing next to it. Is that the problem maybe?

--- Post updated at 09:16 AM ---

Additional note.. when I use reset, I get reset?


and.. this is a standalone machine.. I am logging into it directly.

Last edited by Stellaman1977; 01-22-2019 at 10:36 AM..
# 11  
Old 01-22-2019
I am surprised that reset is an unknown command. Try reset-all. Or power-cycle the box.
I think "Enter filename" means it has run a boot block okay, but it does not find the "platform" (e.g. for your box it is "SUNW,Sun-Blade-2500") on the CD (or DVD).
That means the CD is too old. Usually "Solaris X HW M/Y" is written on it. You must use another CD with a higher M/Y (month/year).
This User Gave Thanks to MadeInGermany For This Post:
# 12  
Old 01-22-2019
Thanks. Haven't tried that yet because I made progress..


After trying all of my opened ROMs that are dated 8/03, 12/03, and 4/04, the 4/04 Operating environment gave me the Can't read disk label error, and all other disks, including the installation and software disks gave me the Can't open kernel error. So I broke the seal on a brand new 4/04 package and the Operating Environment CD worked. So yeah!..



But I am curious about what's going on here.. it had two operating environment CDs in the package I opened that appear identical. I tried the other one and it did not work. I got
Code:
Bad magic number in disk label
Can't open disk label package
Can't open boot device


Combined with the other errors, what could be going on? I doubt its so many bad ROMs.

--- Post updated at 02:29 PM ---

Wait.. Now I see.. One is x86
# 13  
Old 01-22-2019
Quote:
Wait.. Now I see.. One is x86
Aha!
Much different from a Sparc disk label and boot block.
This User Gave Thanks to MadeInGermany For This Post:
# 14  
Old 01-23-2019
Thanks again for the help!
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Hardware

Cannot boot from scsi cdrom

I have a server with a scsi raid controller (for hard drives) and a scsi controller (for tape drive and cd-rom). I am trying to boot from the cd-rom but can't. During boot up, bootable media is detected in the cd-rom but the system will not boot from it. BIOS for the raid controller installs but... (1 Reply)
Discussion started by: powwm
1 Replies

2. Solaris

Boot cdrom - install

Hi community, Does anyone can tell me the difference between "boot cdrom" and "boot cdrom - install" ? Thank you very much:D (3 Replies)
Discussion started by: Sunb3
3 Replies

3. Solaris

can't boot cdrom

iam traying to install o/s in spark machine it showing error ok >boot cdrom is showing error short disk read failed to read superblock the file just loaded does not appear to excutable how to solve this can u help me (6 Replies)
Discussion started by: tirupathi
6 Replies

4. Solaris

not able to boot from cdrom

Hi all am trying to boot the system from cdrom in single user mode , however when i am giving command boot cdrom -s i am getting below error Boot Device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0: f file and args: Can't read disk label Can't open disk label package can,t open boot device ... (17 Replies)
Discussion started by: kumarmani
17 Replies

5. Solaris

Boot from cdrom

i am having a problem when trying to boot from cdrom. I received the below message system is not bootable, boot command is disabledfound how can i fix this. also what is the key combination on ordinary keyboard for STOP+A. Is it ctrl+break? (2 Replies)
Discussion started by: shabu
2 Replies

6. Solaris

Can't boot from cdrom at ok prompt

I want to install Solaris 9 on SUN ULTRA 10. The cdrom is attached to an ide controller. The server is currently running Solaris 2.6 I insert Solaris cd 1 of 2 and at the ok prompt I type boot cdrom i get the error below Boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f file and args:... (11 Replies)
Discussion started by: Msororaji
11 Replies

7. Solaris

cannot find boot device and won't boot off cdrom

I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies

8. UNIX for Dummies Questions & Answers

Cdrom boot problems

Hi Everyone, I have a problem. I'm trying too reinstall sun solaris 8.0 on may Sunfire 280r but solaris 9.0 is all ready installed. I tried to boot from cd rom it keeps telling me that File does not seem executable. I need to get Solaris 8.0 on this system. I have boot all ready in single mode... (4 Replies)
Discussion started by: Peterh
4 Replies

9. UNIX for Dummies Questions & Answers

boot cdrom error

I'm running a Ultra 60 and having problems booting from the cdrom. This is the error I get, Boot device: /pci@1f,4000/scsi@3/disk@6,0:f File and args: The file just loaded does not appear to be executable. Any know what could be the problem here? I've even tried connecting a 2nd cdrom... (3 Replies)
Discussion started by: merlin
3 Replies

10. UNIX for Dummies Questions & Answers

boot from external cdrom

Could some one please tell the command used to boot from an external SCSI cdrom drive? from PROM level. (2 Replies)
Discussion started by: fishman2001
2 Replies
Login or Register to Ask a Question