12-09-2011
Quote:
Originally Posted by
solaris040
The above erros looks to be related with SCSI device. Probe time below states, it was trying to check why it has happened, it failed with timeout.
what operations were you doing there?
thks for ur prompt response.
r u referring to this device?
format
0. c1t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
/pci@0/pci@0/pci@2/scsi@0/sd@0,0
what i found this is a local drive. there is no any amber light or hardware errors.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
:cool: I need some assistance please. I'm setting up a SunOS 5.6 server and sofar I'm able to telnet into the unit but unable to telnet from it. Can anyone help me with this problem. When attempting to telnet from my SunOs to client
terminal I'm receving the following error, "Unable to connect to... (3 Replies)
Discussion started by: sharris82
3 Replies
2. HP-UX
Hi friend,
I'm facing a problem to access the console and telnet to the HP ux 11 server due to the system file is full. How to access this server via single mode and how to mount the folder / and folder /var?
thanks.
vestro (1 Reply)
Discussion started by: vestro
1 Replies
3. AIX
Hi,
I encountered error when I telnet to my server.
Error is as follows:
telnetd: /bin/login: The file access permissions do not allow the specified action
I am able to ssh into my server and I have checked/verified /etc/security and /etc/inetd.conf. I restarted the inetd subsystem via... (1 Reply)
Discussion started by: chongkls77
1 Replies
4. Solaris
Hi guys,
After changing my workstation from domain rsm.renesas.com to my.renesas.local, I was unable to telnet to 1 of our Sun Solaris servers.
There r errors in the messages file:
Aug 15 17:35:26 rsmsso1.svc.rsm.renesas.com inetd: warning: can't verify hostname:... (12 Replies)
Discussion started by: *Jess*
12 Replies
5. UNIX for Dummies Questions & Answers
Dear All,
I have Compaq Alpha server running UNIX OS. with Old Hardware specification.
I had FTP conncetion using IP Switch ( FTP client ) to the Unix server in order to copy some files to my workstation. one day after closing the connection we noted that IT operations are not able to... (8 Replies)
Discussion started by: Arehan
8 Replies
6. SuSE
Hi forum,
I face a strange issue. I'm able to telnet as root with ssh.
But I'm not able to telnet (non-ssh) as root to my Suse 10 machine.
Can someone please point to significant files where I need to make changes for Suse 10 machine and resolve this issue.
Thanks in advance. (2 Replies)
Discussion started by: anilgurwara
2 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have two linux boxes and due to some reasons I have reinstalled OS in one of them. Now Iam unable to telnet one of them. I have included entries in /etc/hosts in both and Iam able to ping each other.
Am I missing anything here or I we need to install/activate telnet server ?
Thanks... (2 Replies)
Discussion started by: ssuhaib
2 Replies
8. UNIX for Dummies Questions & Answers
Hi I am working in Solaris 10 and I want to monitor logs for every telnet/ssh session that tries to connect to the server. I need these logs to be generated in a file that I can fetch using ftp.
I am a new user and a stepwise detail will be great
BR
saGGee (3 Replies)
Discussion started by: saggee
3 Replies
9. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
10. Solaris
hi Everyone
telnet and ssh not working in Solaris 8 .... but it pinging.... i also checked
/etc/services
/etc/inet/inetd.conf
ps -ef | grep telnet
ans default router ... everythinking is ok .... when i connect telnet then suddently closed ... and ssh is connection refused ...
help... (1 Reply)
Discussion started by: coolboys
1 Replies
LEARN ABOUT DEBIAN
scsi-spin
scsi-spin(8) System Manager's Manual scsi-spin(8)
NAME
scsi-spin - spin up and down a SCSI device
SYNOPSIS
scsi-spin [-options...] [device]
DESCRIPTION
scsi-spin let the user to manually spin up and down a SCSI device.
This command is particularly useful if you've got noisy (or hot) drives in a machine that you rarely need to access. This is not the same
as the kernel patch that's floating around that will automatically spin down the drive after some time. scsi-spin is completely manual,
and spinning down a drive that's in use, especially the one containing the scsi-spin binary, is probably a really bad idea.
To avoid running in trouble with such cases, scsi-spin verifies that the device to work on is not currently in use by scanning the mounted
file system description file for a partition living on it and issue an error if this the case.
OPTIONS
-u, --up
spin up device.
-d, --down
spin down device.
-e, --loej
load or eject medium from drive (use along with -u or -d )
-w, --wait=[n]
wait up to n seconds for the spin up/down command to complete. Default is to return immediately after the command was sent to the
device. Either repeat -w n times or set n to define the time to wait before to report a timeout.
-l, --lock
prevent removal of medium from device.
-L, --unlock
allow removal of medium from device.
-I, --oldioctl
use legacy ioctl interface instead of SG_IO to dialog with device (could not be supported on all platforms). -e and -w are not
allowed with this option.
-v, --verbose=[n]
verbose mode. Either repeat -v or set n accordingly to increase verbosity. 1 is verbose, 2 is debug (dump SCSI commands and Sense
buffer).
-f, --force
force spinning up/down the device even if it is in use.
-n, --noact
do nothing but check if the device is in use.
-p, --proc
use /proc/mounts instead of /etc/mtab to determine if the device is in use or not.
device the device is any name in the filesystem which points to a SCSI block device (sd, scd) or generic SCSI device (sg). See section
below.
SCSI devices naming convention
Old kernel naming convention
It is typically /dev/sd[a-z] , /dev/scd[0-9]* or /dev/sg[0-9]*.
scsidev naming convention
It is typically /dev/scsi/s[rdg]h[0-9]*-e????c?i?l? or /dev/scsi/<aliasname>.
devfs naming convention
It is typically /dev/scsi/host[0-9]/bus[0-9]/target[0-9]/lun[0-9]/disc (same for cd and generic devices) or short name
/dev/sd/c[0-9]b[0-9]t[0-9]u[0-9] when devfsd "new compatibility entries" naming scheme is enabled.
SEE ALSO
scsiinfo(8), sg_start(8), sd(4), proc(5),
AUTHORS
Eric Delaunay <delaunay@debian.org>, 2001
Rob Browning <rlb@cs.utexas.edu>, 1998
03 September 2001 scsi-spin(8)