10 More Discussions You Might Find Interesting
1. AIX
I hope someone has experienced this problem before and can help. I have a P730 (8231-E2D) which is fitted with 8 IBM SAS disks on 2 separate SISSAS controllers. The disk type is ST9146853SS (Seagate SAS 146Gb).
The problem occurs when I try to install the VIO server software at 2.2.3. It... (3 Replies)
Discussion started by: johnf
3 Replies
2. AIX
Hi,
I am facing an issue in vio server. When I run
bosboot -ad /dev/hdisk0
I am getting an error
trustchk: Verification of attributes failed: /usr/sbin/bootinfo
: accessauths
regards,
vjm
Please use code tags next time for your code and data. (8 Replies)
Discussion started by: vjm
8 Replies
3. AIX
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies
4. AIX
I have same lun (hdisk3) assigned to 2 vios server (dual vio server) and this is mapped to the client lpar. I have sddpcm on the VIO.
On the VIOA, the attributes for fscsi1 and fscsi3 are set to fast_fail and dyntrk is set to yes
Now, if I do a lqueryvg -Atp on the hdisk3, I get a "DISK... (4 Replies)
Discussion started by: mk8570
4 Replies
5. AIX
I am planning carving out dual VIO servers on a P750 based and would like to know how to allocate internal disks to the VIOS. This has 4 internal disks and I would to assign 2 disks to each VIO.
This is what I was thinking of assigning . Any advise?
vio1
U5802.001.9K8H757-P1-C1 PCI-E x8... (17 Replies)
Discussion started by: mk8570
17 Replies
6. AIX
Hi Guys,
I'm working on building a new 595 machine.. I'm try to achieve high availability for the VIO clients using 2 VIO servers, The ethernet part is satisfied using SEA failover, Now how do I achieve redundancy for the disks, its the servers internal disk attached to the scsi cards...
... (2 Replies)
Discussion started by: kkeng808
2 Replies
7. AIX
In a dual vio, how will u know one lpar is in which vio? (1 Reply)
Discussion started by: shobhan.murthy
1 Replies
8. AIX
hello Folks,
my vio:
$ lsmap -all
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost0 U9117.MMA.6534BE4-V2-C11 0x00000003
VTD ... (0 Replies)
Discussion started by: filosophizer
0 Replies
9. AIX
Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies
10. AIX
I have a script running remotely using viosvrcmd command on hmc to back up the VIO servers. these are the steps involved
1. Mount the NFS directory on to the VIO server
2. run backupios command
3. un mount the directory
I am stuck up in the 3rd step. I am not able to unmount the nfs... (6 Replies)
Discussion started by: balaji_prk
6 Replies
LEARN ABOUT CENTOS
sane-find-scanner
sane-find-scanner(1) SANE Scanner Access Now Easy sane-find-scanner(1)
NAME
sane-find-scanner - find SCSI and USB scanners and their device files
SYNOPSIS
sane-find-scanner [-h|-?] [-v] [-q] [-p] [-f] [-F filename] [devname]
DESCRIPTION
sane-find-scanner is a command-line tool to find SCSI and USB scanners and determine their Unix device files. Its primary aim is to make
sure that scanners can be detected by SANE backends.
For SCSI scanners, it checks the default generic SCSI device files (e.g., /dev/sg0) and /dev/scanner. The test is done by sending a SCSI
inquiry command and looking for a device type of "scanner" or "processor" (some old HP scanners seem to send "processor"). So
sane-find-scanner will find any SCSI scanner connected to those default device files even if it isn't supported by any SANE backend.
For USB scanners, first the USB kernel scanner device files (e.g. /dev/usb/scanner0), /dev/usb/scanner, and /dev/usbscanner) are tested.
The files are opened and the vendor and device ids are determined, if the operating system supports this feature. Currently USB scanners
are only found this way if they are supported by the Linux scanner module or the FreeBSD or OpenBSD uscanner driver. After that test,
sane-find-scanner tries to scan for USB devices found by the USB library libusb (if available). There is no special USB class for scanners,
so the heuristics used to distinguish scanners from other USB devices is not perfect. sane-find-scanner also tries to find out the type of
USB chip used in the scanner. If detected, it will be printed after the vendor and product ids. sane-find-scanner will even find USB scan-
ners, that are not supported by any SANE backend.
sane-find-scanner won't find most parallel port scanners, or scanners connected to proprietary ports. Some parallel port scanners may be
detected by sane-find-scanner -p. At the time of writing this will only detect Mustek parallel port scanners.
OPTIONS
-h, -? Prints a short usage message.
-v Verbose output. If used once, sane-find-scanner shows every device name and the test result. If used twice, SCSI inquiry informa-
tion and the USB device descriptors are also printed.
-q Be quiet. Print only the devices, no comments.
-p Probe parallel port scanners.
-f Force opening all explicitly given devices as SCSI and USB devices. That's useful if sane-find-scanner is wrong in determining the
device type.
-F filename
filename is a file that contains USB descriptors in the format of /proc/bus/usb/devices as used by Linux. sane-find-scanner tries
to identify the chipset(s) of all USB scanners found in such a file. This option is useful for developers when the output of "cat
/proc/bus/usb/devices" is available but the scanner itself isn't.
devname Test device file "devname". No other devices are checked if devname is given.
EXAMPLE
sane-find-scanner -v
Check all SCSI and USB devices for available scanners and print a line for every device file.
sane-find-scanner /dev/scanner
Look for a (SCSI) scanner only at /dev/scanner and print the result.
sane-find-scanner -p
Probe for parallel port scanners.
SEE ALSO
sane(7), sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1), xsane(1), sane-"backendname"(5)
AUTHOR
Oliver Rauch, Henning Meier-Geinitz and others
SUPPORTED PLATFORMS
USB support is limited to Linux (kernel, libusb), FreeBSD (kernel, libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the vendor
and device ids only works with Linux or libusb.
SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris, FreeBSD, NetBSD, OpenBSD, and HP-UX.
BUGS
No support for most parallel port scanners yet.
Detection of USB chipsets is limited to a few chipsets.
13 Jul 2008 sane-find-scanner(1)