Login or Register to Ask a Question and Join Our Community


AIX

Problem with a SSA drive

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems AIX Problem with a SSA drive
# 1  
Old 01-11-2006
Problem with a SSA drive
I've a problem with an IBM StorageWorks - Seagate SSA drive, model ST373453LC (IBM P/N 24P3733, Type S53D073, 72,8 GB 15K - USCSI 4 - 320 SSA). I bought this disk used but working; it came from an unknown IBM SSA storage array. I've removed the SCA - SSA adapter (IBM 18P3051 - 001 - R0) and i tried to install the drive with a "normal" SCA tray in my NetFinity 5500 M20. The RAID controller is an IBM ServeRAID 4M. The problem is that the disk is "seen" by the controller, but I can't access it in any way. If I connect it to an Adaptec 29160, at the CTRL + A prompt, after the spinup, the controller says "SCSI ID0: device connected but not ready" (and the disk can't be accessed, of course).
Some ideas regarding this problem...?
Thanks in advance!!!
I apologize for my poor English...
Paolo C., ITALY
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

enclosure2 SRN 80210 SSA Enclosure

Hi all, How to view more info about this error message that i am keep on getting. Tried "errpt -a" but the output is huge. Thanks in advance! (2 Replies)
Discussion started by: lramsb4u
2 Replies

2. AIX

add SSA pdisk to array to become hdisk

May I know how can I add a new SSA pdisk into array and become usable hdisk? I have inserted a 36GB SSA disk into enclosure and done the "cfgmgr" and I can see it already been regconized as pdisk47. I would like to make it a system disk in order for me to add to my volume group. Please let me... (3 Replies)
Discussion started by: kwliew999
3 Replies

3. AIX

Removing Faulty Disk SSA

Hi Experts, I have configured A D40 Array. There is an faulty disk which is not part of an raid volume but shows fault in the diagnostics. pdisk15 U0.1-P1-I1/Q1-W40AA83CC2400D SSA160 Physical Disk Drive ( MB) Is there a way to stop this... (2 Replies)
Discussion started by: vuppala360
2 Replies

4. AIX

Procedure for removing SSA array

Hi All, What's the proper procedure for removing SSA arrays? Is the procedure like these? - rmdev ssa disk - physical turn off the ssa - cfgmgr There's no more filesystem or logical volume on it. It's just pdisk and hdisk. Thanks in advance, itik (3 Replies)
Discussion started by: itik
3 Replies

5. AIX

mirroring ssa to san

Hi guys, I'd like to share my migration/mirroring of ssa to san. No downtime for users, probably I/O performance. here's the step: 1 After the lun had been carved on the SAN and the connections had been done on AIX fiber card 2 “lspv” and look for the new SAN hdisk? on the bottom, say... (1 Reply)
Discussion started by: itik
1 Replies

6. AIX

migrate from ssa to san

Hi, Do you have procedures to migrate ssa disks to san disk? I don't have testing environment and I want my file system be migrated one at a time. I want it to be fast, I have only 15-20 hours to do it on every sunday 1PM till monday 7am. My largest file system is about 150G. The AIX is... (0 Replies)
Discussion started by: itik
0 Replies

7. AIX

Can not increase capacity of the vg using raid5 with ssa disks

hi all, i have an p620 server. it has 2 scsi 18gb disks for aix4.3 OS and 3 ssa disks for database and an serialRAID adapter. 3 ssa disks configured raid level 5. to increase capacity of the datavg, i buy 2 ssa 18gb disks. but i can not add them to the existing datavg. i did the following... (1 Reply)
Discussion started by: tinhlx
1 Replies

8. AIX

updating ssa

I am in the process of updating ssa adapters, drives and enclosures and wanted to know if there are any caveats that anyone would like to share. The documentation is not very clear on the ordering of the updates. Any tips would be appreciated. (1 Reply)
Discussion started by: chosie
1 Replies

9. AIX

ssa performances

Helo: We updated form AIX 4.3.3 to AIX 5.1-7 and after this we spent more than double time in read from external disks. Aparently the ssa cards microcode is at last level and all the ptf and apars are instaled. Out backups expent more than double time, but curiously in read only, if we write in... (0 Replies)
Discussion started by: Javier Gutierre
0 Replies

10. AIX

RS6000 SSA Raid question

Hi Can I add disks on the fly to extend the capacity of an existing RAID 5 volume? It's created on a 4P Advanced SSA Raid Adapter. I need to extend a volume group, so I figured it would be easiest to extend the "physical disk" which is a RAID5 volume. Thanks. (1 Reply)
Discussion started by: osee
1 Replies
Login or Register to Ask a Question

LEARN ABOUT REDHAT

hd

HD(4)							     Linux Programmer's Manual							     HD(4)

NAME

       hd - MFM/IDE hard disk devices

DESCRIPTION

       The  hd*  devices  are block devices to access MFM/IDE hard disk drives in raw mode.  The master drive on the primary IDE controller (major
       device number 3) is hda; the slave drive is hdb.  The master drive of the second controller (major device number 22) is hdc and	the  slave
       hdd.

       General	IDE block device names have the form hdX, or hdXP, where X is a letter denoting the physical drive, and P is a number denoting the
       partition on that physical drive.  The first form, hdX, is used to address the whole drive.  Partition numbers are assigned  in	the  order
       the  partitions	are  discovered, and only non-empty, non-extended partitions get a number. However, partition numbers 1-4 are given to the
       four partitions described in the MBR (the `primary' partitions), regardless of whether they are unused or extended.  Thus, the first  logi-
       cal  partition  will be hdX5.  Both DOS-type partitioning and BSD-disklabel partitioning are supported.	You can have at most 63 partitions
       on an IDE disk.

       For example, /dev/hda refers to all of the first IDE drive in the system; and /dev/hdb3 refers to the third DOS `primary' partition on  the
       second one.

       They are typically created by:

	      mknod -m 660 /dev/hda b 3 0
	      mknod -m 660 /dev/hda1 b 3 1
	      mknod -m 660 /dev/hda2 b 3 2
	      ...
	      mknod -m 660 /dev/hda8 b 3 8
	      mknod -m 660 /dev/hdb b 3 64
	      mknod -m 660 /dev/hdb1 b 3 65
	      mknod -m 660 /dev/hdb2 b 3 66
	      ...
	      mknod -m 660 /dev/hdb8 b 3 72
	      chown root:disk /dev/hd*

FILES

       /dev/hd*

SEE ALSO

       mknod(1), chown(1), mount(8), sd(4)

Linux								    1992-12-17								     HD(4)