My P6 server is with dual vio servers. From the below output we could see that cd devices(cd0 and cd1) has been mapped to the vio client named prdsapfi1.
When we execute "lsdev -Cc cdrom" in prdsapfi1 there are 2 cd devices named cd0 and cd1 showing up in available state.
My question is how to find out if cd0 showing up in prdsapfi1 has been coming from vioprd01p or vioprd01i?
Hi,
I tried to install Magneto-Optical (MO) drive Fujutsu to COMPAQ Proliant ML350 with SCO Openserver 5.0.5. Harddisk and MO are connected to Adaptec UW-SCSI-3 (driver ad160).
During boot process system shows me that MO is connected to host adapter 1, bus 0, SCSI ID 1 and LUN 0. But when I... (2 Replies)
Trying to get my unix system to recognize an optical drive, it was delivered to us, so we assumed it worked, in the 2 years since no one ever has used it, we want to now. However, even running probe-scsi-all doesn't bring up that drive. It's a scsi address of 3, at the end of the chain, all... (1 Reply)
hi folks here is my case
Storage XP24K
Business copy setup
OS Solaris 10
Verital 4.1
Business copy is running between a production server and backup server using xp24k
when the disk groups are imported back on backup server after BC from the prduction server
following error is reported... (0 Replies)
Hi guys,
I have not connected optical cable to the Dual port HBA before. My integrator used to do that for me all the time. Can someone explain to me how can I physically connect optical cable to the HBA port in P570.
The optical cable has two connectors and right now the HBA port has just a... (7 Replies)
Not really a newbie, but I have a strange problem and I'm not sure how to further troubleshoot it.
I have to log out of a virtual terminal by typing exit, then exit again as in:
woodnt@toshiba-laptop ~ $ exit
logout
woodnt@toshiba-laptop ~ $ exit
logout
I DON'T have to do this when I'm... (1 Reply)
hello,
someone gave me a set of electronic gadgets 'Brookstone' which has mini optical mouse. This mouse label doesn't have model or etc. Mouse does not work properly i.e. pointer is moving right but left/right buttons work opposite and not always could open or close controls.
I suggest it might... (3 Replies)
Trying to set or modify the randomly set hostID of a Solaris 10 virtual/guest machine that I installed on a Windows-XP host machine (using Virtual Box 4.1.12).
I was able to set/modify the hostname of the Solaris 10 virtual/guest machine during installation as well as via the Virtual Box... (4 Replies)
Hi All,
Is there any way I can prioritize my VMs when there is resource crunch in host machine so that some VMs will be allocated more vcpu, more memory than other VMs in kvm/qemu hypervisor based virtual machines?
Lets say in my cloud environment my Ubuntu 16 compute hosts are running some... (0 Replies)
Discussion started by: SanjayK
0 Replies
LEARN ABOUT FREEBSD
atapicam
ATAPICAM(4) BSD Kernel Interfaces Manual ATAPICAM(4)NAME
atapicam -- CAM XPT (transport) module for ATAPI devices
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device scbus
device ata
device atapicam
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
atapicam_load="YES"
DESCRIPTION
The ATAPI/CAM module allows ATAPI devices (CD-ROM, CD-RW, DVD drives, floppy drives such as Iomega Zip, tape drives) to be accessed through
the SCSI subsystem, cam(4).
ata(4) and scbus(4) must be configured in the kernel as well. The SCSI target drivers (cd(4), da(4), or st(4)) can then be used to access
the devices. The generic passthrough device, pass(4), can also be used to send SCSI commands directly to the devices through the CAM API.
A separate CAM bus is created for each ATA bus in the system. On each of these buses, target ID 0 is assigned to the master device, and ID 1
is assigned to the slave (provided they are ATAPI devices).
IMPLEMENTATION NOTES
Some SCSI commands are intercepted by the driver, and undergo special processing in order to work around limitations of ATAPI devices. Such
limitations can be consequences of the ATAPI specification. For example, ATAPI devices do not implement the 6-byte versions of MODE_SELECT,
MODE_SENSE, READ, or WRITE. They can also be common bugs, such as hanging when queried for extended INQUIRY information.
EXAMPLES
device ata
device atapicam
device scbus
device cd
device pass
Add the atapicam driver to the kernel.
camcontrol devlist
Print the list of all devices available through CAM.
mount -t cd9660 /dev/cd0 /mnt
Mount a CD-ROM from an ATAPI CD-ROM drive (the command above assumes that the ATAPI drive is the only CD-ROM unit).
SEE ALSO ata(4), cam(4), scsi(4), atacontrol(8), camcontrol(8)HISTORY
The ATAPI/CAM driver first appeared in FreeBSD 4.8 and FreeBSD 5.0.
AUTHORS
The ATAPI/CAM driver was written by Thomas Quinot <thomas@FreeBSD.org>.
BUGS
atapicam and ATAPI-specific target drivers (acd(4), ast(4), and afd(4)) can be configured in the same kernel. Simultaneous access to the
same device through the SCSI generic drivers and the ATAPI-specific drivers may cause problems and is strongly discouraged.
BSD October 22, 2009 BSD