Sponsored Content
Full Discussion: hdds physically
Operating Systems HP-UX hdds physically Post 302072205 by buffoonix on Friday 28th of April 2006 07:51:13 PM
Old 04-28-2006
I would rather dd from the raw device and read bigger chunks
e.g.
dd if=/dev/rdsk/c?t?d? of=/dev/null bs=1024k

If your disk is defunct then the command would probably hang and could not be killed.
Therefore better start it as a batch job,
or if run from the console run tsm before
to have another virtual terminal to leave you a prompt.

You could also let the device try to identify

diskinfo -v /dev/rdsk/c?t?d?

If not all fields are populated there might be a problem with the disk.

Also see if ioscan reports loss of hardware

/usr/sbin/ioscan -fCdisk|grep NO_HW

If you have OnlineDiag installed (swlist OnlineDiag)
you could run stm and read info logs of disk.

If you have EMS running you should check its log for any
monitoring events
more /var/opt/resmon/logs/event.log
But if you had it should have warned you by some notification email.
 

4 More Discussions You Might Find Interesting

1. Solaris

How to check if rsc is physically exist

I have a bunch of servers that cant connect via rsc, but supposingly they can connect... Any chance I can check if the rsc card is physically exist in the server by some command? Some of the machines are in overseas, and I won't go datacenter to check anyways... Many Thanks! (6 Replies)
Discussion started by: nicole0404
6 Replies

2. Solaris

Physically identify hard disk.

Hi, I have a failed hard disk in my Sun Fire V240. Unfortunately it does not show up in 'cfgadm -al' or in the format command so I cannot unconfigure it and illuminate the blue light on the front to identify it. Is there any way of iluminating the blue lights on the other disks so I can at... (3 Replies)
Discussion started by: sparcman
3 Replies

3. Solaris

SPARC T4-1/Solaris 11/Add 2 new HDDs in RAID 0 configuration

Hi, Couple of sentences for background: I'm a software developer, whose task was to create a server software for our customer. Software is ready for deployment and customer has a new T4-1 SPARC, but somehow it also became my task also to setup the server. I have managed to get the server is up... (13 Replies)
Discussion started by: julumme
13 Replies

4. AIX

IBM AIX 5.2 cloning Hdds

I have an old IBM Power 5 9111-520 that has data on it but the system is failing. I need to move it to a more reliable server. The current system has two drives and no raid. I would like to setup my "newer" system with raid and two partitions then clone my setup over. What is the best way to do... (2 Replies)
Discussion started by: BDC80
2 Replies
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)
All times are GMT -4. The time now is 02:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy