02-15-2007
My Ultra 10 has an external SCSI disk & two internal disks attached to ide interface
probe-scsi-all
/pci@1f,0/pci@1scsi@2,1
probe-ide
Device 0 (primary master)
ATA model: st39140a
Device 1 (primary slave)
ATA model: 1BB-DTLA-305010
Device 2 (secondary master)
Not present
Device 3 (secondary slave)
Not present
still not booting from cdrom at ok prompt
10 More Discussions You Might Find Interesting
1. 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
2. Red Hat
my redhat 9 will not boot. We had a power failure and when the power came back, my redhat linux will not boot.
The machine come up to grub prompt.
I tried the following from grub prompt
root (hd0, then press tab key
partition num:0 filesystem type unknown, partition type 0x83... (7 Replies)
Discussion started by: hassan2
7 Replies
3. 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
4. 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
5. 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
6. 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
7. 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
8. Solaris
Server need to have the OS reinstalled (5.10 SPARC) and I cannot get it to the OK prompt. I also do not have the ALOM password and I've tried several different methods to zero out the NVRAM but to no avail. There is no ALOM battery that I can pull. I'm connecting via Cutecom (like minicom) and... (18 Replies)
Discussion started by: LittleLebowski
18 Replies
9. 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
10. UNIX for Beginners Questions & Answers
Good Afternoon,
I'm trying to boot from cdrom so I:
bash-2.05# init 0
{1} ok boot cdrom -s and I get:
Rebooting with command: boot cdrom -s
Boot Device: /pci@1e,600000/ide@d/cdrom@2,0:f File and args: -s
Can't read disk label.
Can't open disk label package
Evaluating:
Can't open boot... (13 Replies)
Discussion started by: Stellaman1977
13 Replies
LEARN ABOUT OSF1
atapi_ide
atapi_ide(7) Miscellaneous Information Manual atapi_ide(7)
NAME
atapi_ide - Interface for ATAPI or IDE (PC) devices
SYNOPSIS
PCI bus CMD/Acer ATAPI/IDE adapter:
bus pci0 at *
bus ata0 at *
controller scsi0 at ata0 slot 0
controller scsi1 at ata0 slot 1
PCI bus Cypress ATAPI/IDE adapter:
bus pci0 at *
bus ata0 at *
bus ata1 at *
controller scsi0 at ata0 slot 0
controller scsi1 at ata1 slot 0
PCMCIA bus ATA/IDE disk card:
bus pcmcia0 at *
bus ata0 at pcmcia?
controller scsi0 at ata0
DESCRIPTION
Devices commonly known for their use on PC devices as ATA or IDE devices are supported using the SCSI CAM device driver. The ATA standard
has also been expanded to include what are known as ATAPI devices. The SCSI CAM device driver is also used for those disks and CD-ROM
devices. These devices may also be known under the names EIDE, ATA-2, Fast-ATA, or Ultra-ATA.
Beacuse the ATA/IDE standard was not developed until after many of the devices that used this standard were produced, there are many
devices which do not strictly comply with the standard. While it is possible some industry standard devices may appear to work, it is also
possible they will cause hang or data corruption cases when used under more stressful situations. For this reason, it is recommended that
only the supported devices be used. These devices have been tested and are certified for correct operation.
ATAPI/IDE controllers allow the connection of two devices. These two devices are known as the master device and the slave device. If only
one device is connected, that device must be the master (slave-only configurations are not supported). When used by the SCSI CAM device
driver, the IDE master device is assigned SCSI id 0 for that controller. The slave device is assigned SCSI id 1 for that controller. No
other SCSI ids are assigned on that controller. Most ATAPI/IDE adapters contain two channels (known as the primary and secondary). Each
of these channels may contain their own master and slave devices. Therefore, a dual channel ATAPI/IDE controller may contain up to 4
devices (a master and slave pair on each channel). These 4 devices are then accessed as SCSI id 0 and 1 on each channel.
Many SCSI operations translate perfectly for use on IDE. For example, read and write operations are the same. However, many SCSI disk
mode pages are emulated by the IDE device driver. For example, you can display the SCSI inquiry mode pages using the following command: %
scu show inq pages pages are created by the device driver to contain the long (full IDE) form of the device name, serial number, revision,
and the operational modes of the device. Only a shortened version of this information is available with the standard SCSI inquiry command.
Note also that the following command: % scu show pages Shows that the SCSI mode pages contain only partial information. Only that informa-
tion (such as geometry) that the drive reports to the system is able to be reformatted into these emulated SCSI mode pages. Much of the
information (such as RPM) is simply not available from the drive, and therefore not accurately reported.
ATAPI devices are much more closely related to SCSI devices, and as such contain their own mode pages. Therefore, for these devices, the
mode page values reported are those from the device, and no emulation is involved.
ATAPI tape devices are not supported at this time.
FILES
/dev/disk/dsk??? /dev/disk/dsk???
RELATED INFORMATION
SCSI(7), rz(7), and disklabel(8) delim off
atapi_ide(7)