02-14-2007
do a:
setenv auto-boot? false
reset-all
probe-scsi-all
probe-ide
and post the output of the last two commands!
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 DEBIAN
tapset::scsi
TAPSET::SCSI(3stap) TAPSET::SCSI(3stap)
NAME
tapset::scsi - systemtap scsi probe points
DESCRIPTION
This family of probe points is used to probe the SCSI activities. It contains the following probe points:
scsi.ioentry
Fires when SCSI mid layer prepares a SCSI request
Arguments:
disk_major
The major number of the disk
disk_minor
The minor number of the disk
device_state
The current state of the device. The possible values could be:
SDEV_CREATED = 1, /* device created but not added to sysfs
* Only internal commands allowed (for inq) */
SDEV_RUNNING = 2, /* device properly configured
* All commands allowed */
SDEV_CANCEL = 3, /* beginning to delete device
* Only error handler commands allowed */
SDEV_DEL = 4, /* device deleted
* no commands allowed */
SDEV_QUIESCE = 5, /* Device quiescent. No block commands
* will be accepted, only specials (which
* originate in the mid-layer) */
SDEV_OFFLINE = 6, /* Device offlined (by error handling or
* user request */
SDEV_BLOCK = 7, /* Device blocked by scsi lld. No scsi
* commands from user or midlayer should be issued
* to the scsi lld. */
scsi.iodispatching
Fires when the SCSI mid layer dispatches a SCSI command to the low level driver
Arguments:
host_no
The host number
channel
The channel number
lun
The lun number
dev_id
The scsi device id
device_state
The current state of the device.
data_direction
The data_direction specifies whether this command is from/to the device.
The possible values could be:
DMA_BIDIRECTIONAL = 0,
DMA_TO_DEVICE = 1,
DMA_FROM_DEVICE = 2,
DMA_NONE = 3,
request_buffer
The request buffer address
req_bufflen
The request buffer length
scsi.iodone
Fires when a SCSI command is done by low level driver and enqueued into the done queue.
Arguments:
host_no
The host number
channel
The channel number
lun
The lun number
dev_id
The scsi device id
device_state
The current state of the device
data_direction
The data_direction specifies whether this command is from/to the device.
scsi.iocompleted
Fires when SCSI mid layer runs the completion processing for block device I/O requests
Arguments:
host_no
The host number
channel
The channel number
lun
The lun number
dev_id
The scsi device id
device_state
The current state of the device
data_direction
The data_direction specifies whether this command is from/to the device.
goodbytes
The bytes completed.
SEE ALSO
stap(1), stapprobes(3stap)
IBM
TAPSET::SCSI(3stap)