01-18-2019
Quote:
Originally Posted by
Don Cragun
As noted in the message marked in red above... maybe the boot command is expecting you to provide the pathname of a file on the CD-ROM and not just the -s argument to be passed to it???
What operating system and hardware are you using?
Sorry I left stuff out.. Solaris 9 on a Sun SunBlade 2500 Sparc.
--- Post updated at 08:42 AM ---
Quote:
Originally Posted by
MadeInGermany
The command is correct for Solaris Sparc, and a CD with a Solaris boot block should work.
Is the CD okay? Cloned ones can miss the boot block.
Can also be a defective cdrom drive (does it work otherwise?).
Or a firmware bug: after a couple of boots need a reset at the Ok prompt (maybe first set auto-boot to false).
The CDs I've tried are originals. I've tried the Operating Environment and the "Software 1 of 2" CDs. I've tried about 5 CDs altogether. I've restored this machine before and the drive worked at that time.
Last edited by Stellaman1977; 01-18-2019 at 10:27 AM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
2. UNIX for Dummies Questions & Answers
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
3. UNIX for Dummies Questions & Answers
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
4. Solaris
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
5. Solaris
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
6. Solaris
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
7. Solaris
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
8. Solaris
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
9. Solaris
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
10. Hardware
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
BOOT(8) System Manager's Manual BOOT(8)
NAME
boot - startup procedures
DESCRIPTION
A PDP11/45 and PDP11/70 UNIX system is started by a two-stage process. The first is a primary bootstrap which is able to read in rela-
tively small stand-alone programs; the second (called boot) is used to read in the system itself.
The primary bootstrap must reside in the otherwise unused block zero of the boot device. It can be read in and started by the standard ROM
programs, or if necessary by keying in a small startup routine. This program is capable of loading type 407 executable files (not shared,
not separate I&D). The user types on the system console the name of the program wished, in this case boot, followed by a carriage return;
the named program is retrieved from the file system that starts at block 0 of drive 0 of the boot device. No prompt is given, no diagnos-
tic results if the file cannot be found, and no provision is made for correcting typographical errors.
The second step, called boot, actually brings in the system. When read into location 0 and executed, boot sets up memory management, relo-
cates itself into high memory, and types a `:' on the console. Then it reads from the console a device specification (see below) followed
immediately by a pathname. Boot finds the corresponding file on the given device, loads that file into memory location zero, sets up mem-
ory management as required, and calls the program by executing a `trap' instruction. Normal line editing characters can be used.
Conventionally, the name of the secondary boot program is `/boot' and the name of the current version of the system is `/unix'. Then, the
recipe is:
1) Load block 0 of the boot device by fiddling with the console keys as appropriate for your hardware. If you have no appropriate ROM,
some programs suitable for manual use are given below.
2) Type boot.
3) When the prompt is given, type
hp(0,0)unix
or
rp(0,0)unix
depending on whether you are loading from an RP04/5/6 or an RP03 respectively. The first 0 indicates the physical unit number; the
second indicates the block number of the beginning of the logical file system to be searched. (See below).
When the system is running, it types a `#' prompt. After doing any file system checks and setting the date (date(8)) a multi-user system
is brought up by typing an EOT (control-d) in response to the `#' prompt.
Device specifications. A device specification has the following form:
device(unit,offset)
where device is the type of the device to be searched, unit is the unit number of the device, and offset is the block offset of the file
system on the device. Device is one of the following
rp RP03
hp RP04/5/6
rk RK05
For example, the specification
hp(1,7000)
indicates an RP03 disk, unit 1, and the file system found starting at block 7000 (cylinder 35).
ROM programs. The following programs to call the primary bootstrap may be installed in read-only memories or manually keyed into main mem-
ory. Each program is position-independent but should be placed well above location 0 so it will not be overwritten. Each reads a block
from the beginning of a device into core location zero. The octal words constituting the program are listed on the left.
RK (drive 0):
012700 mov $rkda,r0
177412
005040 clr -(r0) / rkda cleared by start
010040 mov r0,-(r0)
012740 mov $5,-(r0)
000005
105710 1: tstb (r0)
002376 bge 1b
005007 clr pc
RP (drive 0)
012700 mov $rpmr,r0
176726
005040 clr -(r0)
005040 clr -(r0)
005040 clr -(r0)
010040 mov r0,-(r0)
012740 mov $5,-(r0)
000005
105710 1: tstb (r0)
002376 bge 1b
005007 clr pc
FILES
/unix - system code
/usr/mdec/rpuboot, /usr/mdec/hpuboot - copies of primary bootstrap
/boot - second stage bootstrap
SEE ALSO
init(8)
BOOT(8)