hdds physically Post: 302072205

Sponsored Content

Operating Systems HP-UX hdds physically Post 302072205 by buffoonix on Friday 28th of April 2006 07:51:13 PM

04-28-2006

Registered User

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.

buffoonix

View Public Profile for buffoonix

Find all posts by buffoonix

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!

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. 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...

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...

LEARN ABOUT OPENSOLARIS

installboot

installboot(1M) 														   installboot(1M)

NAME

       installboot - install bootblocks in a disk partition

SYNOPSIS

       installboot bootblk raw-disk-device

       The boot(1M) program, ufsboot, is loaded from disk by the bootblock program which resides in the boot area of a disk partition.

       The  ufs  boot objects are platform-dependent, and reside in the /usr/platform/platform-name/lib/fs/ufs directory. The platform name can be
       found using the -i option of uname(1).

       The installboot utility is a SPARC only program. It is not supported on the  architecture.  users should use installgrub(1M) instead.

       bootblk	       The name of the bootblock code.

       raw-disk-device The name of the disk device onto which the bootblock code is to be installed; it must be a character device which is  read-
		       able and writable. Naming conventions for a SCSI or IPI drive are c?t?d?s? and c?d?s? for an IDE drive.

       Example 1: Installing UFS Boot Block

       To install a ufs boot block on slice 0 of target 0 on controller 1 of the platform where the command is being run, use:

	      example# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk 
		   /dev/rdsk/c1t0d0s0

       /usr/platform/platform-name/lib/fs/ufs

	   directory where ufs boot objects reside.

       /platform/platform-name/ufsboot

	   second level program to boot from a disk or CD

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+

       od(1), uname(1), boot(1M), init(1M), kadb(1M), kernel(1M), monitor(1M), reboot(1M), rpc.bootparamd(1M), init.d(4), attributes(5)

WARNINGS

       The installboot utility fails if the bootblk or openfirmware files do not exist or if the raw disk device is not a character device.

								    11 Apr 2005 						   installboot(1M)