installing a LUN on CentOS

Hi,

I have installed an HBA card , model qla2340 , on a 64 bit CentoOS 5.3 machine. The card is working fine. The following contains more information:
http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/SearchByProduct.aspx?ProductCategory=39&Product=253&Os=65

I installed SANsurfer Linux Driver Installer (x86/x64/IA64) version 8.02.14.01-1 from the above link.

My computer does not detect the LUN unit. I am using HP A6250AZ. This is an FC  2gb/s Disk Array. I don't know if I have to enable a service/program in order for the HBA to see the LUN. Please, any help is appreciated.

Thanks
vielkacarolina1239Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

joolsSenior Systems AdministratorCommented:
if the correct driver is loaded then you should see any lunc that are presented. if you get none showing then you should first look at the configuration of your Surestore unit and make sure that it is configured to show the disks down the fabric you are using and if it needs to be configured via a switch or just direct connect.
0
vielkacarolina1239Author Commented:
I found the following link on hp web site:
http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=321654&lang=en&cc=us&taskId=135&prodTypeId=12169&prodSeriesId=81150
This drivers are for Servers booting from a LUN. This is not the configuration that I need. My machine does not needs to boot from a LUN.

Is there an RPM package installer that would contain FC driver support?

Thanks.
0
vielkacarolina1239Author Commented:
SANsurfer software provides configuration for the connection type, direct connect or switch. I have set this configuration to direct connect to the server. But, the LUN is not visible to the SANsurfer software or the OS.
I have disabled the firewall incase any ports were blocked. Do I need to run an RPC program for port mapping so that the LUN have a path to the OS/SANsurfer software?

Thanks,
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

joolsSenior Systems AdministratorCommented:
No, I meant the drivers for the FC card (loaded as modules for your kernel) which allow you to see the attached drives on your storage array out on the fabric.

Can you post the output to `lsmod` and `cat /etc/modprobe.conf` please.

Did kudzu run and detect the qlogic card and configure it for you?

0
vielkacarolina1239Author Commented:
Hi,

I have attached the directory etc/modprobe.d.

Please, review the attached files.

Thanks.
0
vielkacarolina1239Author Commented:
Please, see attachment. The previous post did not attached the file. I have manually post fix the file name with .zip so that the website would let me upload the file. Please, manually remove .zip from the file name and this would let you decompress the file.

Thanks,

modprobe.d.tar.gz.zip
0
vielkacarolina1239Author Commented:
I don't think I have provided you with the information you have request on the previous post. Please, see the attachment for commands  lsmod and modprobe -all
0
vielkacarolina1239Author Commented:
The attachment did not work on the previous post, sorry. Please remove the .zip from the .tar file. I have manually postfix the file name with .zip to upload to the website.

Thanks,
mod-files.tar.gz.zip
0
joolsSenior Systems AdministratorCommented:
The driver is loaded, can you post the output to `cat /proc/scsi/scsi`, no need to attach the file, just cut/paste from a terminal session.
0
joolsSenior Systems AdministratorCommented:
>> I have disabled the firewall incase any ports were blocked.
That should not stop you seeing the devices out on the fabric.
0
martin_2110Commented:
Have you tried a reboot. Or a rescan of the scsi bus.
0
martin_2110Commented:
How to rescan scsi bus.(do not bother with this if you have already rebooted.)
http://kbase.redhat.com/faq/docs/DOC-3942
0
vielkacarolina1239Author Commented:
sorry for the long wait, I just got back home from work.

[root@localhost scsi]# cat scsi
Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: MAXTOR   Model: ATLAS10K5_73WLS  Rev: JNQ0
  Type:   Direct-Access      

_________________________________________________________________________

Also, I ran the QLogic LUN Discovery util:
[root@localhost Desktop]# cd LinuxTools/
[root@localhost LinuxTools]# cd ql-dynamic-tgt-lun-disc-2.6
[root@localhost ql-dynamic-tgt-lun-disc-2.6]# ./ql-dynamic-tgt-lun-disc.sh -cl

DEVICE
[H:C:T:L]
[root@localhost ql-dynamic-tgt-lun-disc-2.6]# ./ql-dynamic-tgt-lun-disc.sh -is
Please make sure there is no active I/O before running this script
Do you want to continue: (yes/no)? yes
QLogic Host not found...
Please check if QLogic module is loaded or not...
[root@localhost ql-dynamic-tgt-lun-disc-2.6]# ./ql-dynamic-tgt-lun-disc.sh -s
Please make sure there is no active I/O before running this script
Do you want to continue: (yes/no)? yes
Scanning HOST: host0
.............
No devices attached to HOST: host0
No changes discovered in existing devices.
[root@localhost ql-dynamic-tgt-lun-disc-2.6]# ./ql-dynamic-tgt-lun-disc.sh --scan
Please make sure there is no active I/O before running this script
Do you want to continue: (yes/no)? yes
Scanning HOST: host0
.............
No devices attached to HOST: host0
No changes discovered in existing devices.

________________________________________________________________________

I have reboot the system many times and no luck, drives are not detected

Thanks,
0
joolsSenior Systems AdministratorCommented:
you must re check your configuration on the HP disk system.

as far as I can see from what has been posted there is nothing wrong with the linux server configuration. The qlogic modules are loaded into the kernel but the disk does not seem to be presenting disk, you should start the disk configuration from scratch.
0
martin_2110Commented:
I agree. Perhaps check your cabling. Also check on the array, it should have some kind of a web gui or cli that you can asign the hba's wwn to a disk or volume. Or perhaps you need to create volumes in the array still.
0
joolsSenior Systems AdministratorCommented:
it would definately be worth making sure the fibre pairs are round the right way or trying another fibre cable.
0
martin_2110Commented:
make sure you dont have the wrong type of fibre also. single vs multi mode.
0
vielkacarolina1239Author Commented:
the cable I am using has the following print:
OPTICAL FIBER CABLE MM 50/125UM <UL>

I have two of the same cable. I have switch them, but, nothing.
0
vielkacarolina1239Author Commented:
The HBA SANsurfer software has the following application events. Looks like an RPC application is failing. But it has a time stamp of the 5/18/2009.

file:/opt/QLogic_Corporation/SANsurfer/skins/power/error.gif      Mon May 18 21:15:07 EDT 2009      RPC request 25 for Host 127.0.0.1 failed.
file:/opt/QLogic_Corporation/SANsurfer/skins/power/error.gif      Mon May 18 21:15:07 EDT 2009      Retrying RPC request 25 for Host 127.0.0.1.
file:/opt/QLogic_Corporation/SANsurfer/skins/power/error.gif      Mon May 18 21:15:27 EDT 2009      RPC request 0 for Host 127.0.0.1 failed.
file:/opt/QLogic_Corporation/SANsurfer/skins/power/error.gif      Mon May 18 21:15:27 EDT 2009      Retrying RPC request 0 for Host 127.0.0.1.
file:/opt/QLogic_Corporation/SANsurfer/skins/power/error.gif      Mon May 18 21:16:07 EDT 2009      RPC request 1 for Host 127.0.0.1 failed.
file:/opt/QLogic_Corporation/SANsurfer/skins/power/error.gif      Mon May 18 21:16:07 EDT 2009      Retrying RPC request 1 for Host 127.0.0.1.
file:/opt/QLogic_Corporation/SANsurfer/skins/power/error.gif      Mon May 18 21:16:27 EDT 2009      RPC request 1 for Host 127.0.0.1 failed.
file:/opt/QLogic_Corporation/SANsurfer/skins/power/error.gif      Mon May 18 21:16:27 EDT 2009      Retrying RPC request 1 for Host 127.0.0.1.
0
joolsSenior Systems AdministratorCommented:
OK, youre not seeing the disk on the fibre card, the san surfer software will need to see the disk first before you can use it.

Have you checked the disk configuration, please confirm.
Have you checked the orientation of the cables, you may need to cross over tx/rx depending on your cable.

Regards the error above, is rpc running???
0
vielkacarolina1239Author Commented:
The cables that I am using are the following. Please, click the link below
http://www.amazon.com/gp/product/B000JC4QC2/ref=ox_ya_oh_product

Please, could you explain a little more what you mean by checking the disk configuration?

I don't have the HP utility software for the disk array. I called HP inquiring about a compatable software and they will get back to me since HP discontinued this product some time ago.

I will check the cables orientation as soon as I get off from work.

Thanks.
0
joolsSenior Systems AdministratorCommented:
On most disk systems (I don't know your model and cant find any specific manuals) you have to configure the disk, this is sometimes using a disk configuration utility that connects from a pc, perhaps over the LAN or perhaps using a telnet or web front end. This is used to configure the raid and how it connects to the server.... it's different for pretty much all systems I've used, yours may well be different too.

You will need to make sure the disk system you have can be connected directly to an Intel server with a qlogic card, there may be an application you can use to do this or there may even be jumper settings. As you are connecting directly, the system will need to work with a direct connect, most systems used fibre switches and nearly all allow you to connect to both types.

If you can supply information about your disk unit we may be able to help point you in the right direction.

Until you know the disk is OK you may not be able to get it to work...

Has the disk been used before? On what systems? How was it connected?
0
vielkacarolina1239Author Commented:
The HP web page for the product is the following:
http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp?locale=en_US&prodTypeId=12169&prodSeriesId=81150

On the web, I found that OpenView Network Node Manager Software can be used to operate the device. I have contacted HP about this product. They say they will let me know if this software is compatile. The link for this software is https://h10078.www1.hp.com/cda/hpms/display/main/hpms_content.jsp?zn=bto&cp=1-11-15-119%5E1155_4000_100__

They have the following software edition on the above link and might be compatible with my OS:
HP NNM for RHEL 7.53 Evaluation




0
joolsSenior Systems AdministratorCommented:
so what are your LCC's configured as at the moment then?
0
joolsSenior Systems AdministratorCommented:
BTW, NNM is used for monitoring, usually by SNMP, you still need to make sure the disk is seen on the system first BEFORE you can setup any monitoring.
0
vielkacarolina1239Author Commented:
Hi,

I'm a newbie on the FC world and linux as I am shifting away from windows os. I have never played around with FC technology before. Please, could explain what you mean by LLC configuration. Sorry if the question is too elementary.

thanks,
0
vielkacarolina1239Author Commented:
The controllers are set to:
Link Active contains a green light.
LCC Active contains a green light
The port address is set to 0.

Thanks.
0
vielkacarolina1239Author Commented:
I have ordered another HBA card, QLA2344. I should be getting it early next week. I will try with this card and will post comment on whether it worked with QLA2344. If it does not work, I will contact the seller and exchange/return the Disk Array.

Thanks,
0
joolsSenior Systems AdministratorCommented:
I will have a look to see if I have a unit in our warehouse and give it a go myself.
0
vielkacarolina1239Author Commented:
That it is great, thanks alot for the extra mile you taking to help me with this problem. I really appreciated. Let me know how it goes please.

Thanks
0
vielkacarolina1239Author Commented:
Hi,

I have received the new HBA card model QLA2344. I installed it on a windows server 2003 box and the FC Drives were detected. I saw the drives under hardware->drives. The disk array works fine.

I am trying to install the hba card on CentOS 5.3 but it is not working. I have created another thread titled "how to install a kernel on CentOS5.3(rhel)" for this. Please, could you help with this?


Thanks,
0
joolsSenior Systems AdministratorCommented:
thats a good test...

RHEL 5.3 should automatically configure the kernel for you.
Can you `chkconfig --list kudzu` and make sure its set to run, then reboot the server
0
vielkacarolina1239Author Commented:
Please, could you tell me how to set on? This is what I have.

[root@localhost delbin]# /sbin/chkconfig --list kudzu
kudzu           0:off   1:off   2:off   3:on    4:on    5:on    6:off
0
joolsSenior Systems AdministratorCommented:
It's already on for run levels 3 4 and 5, I'm guessing you use a graphical login so it should run anyway. kudzu helps configure modules for you.

Can you cat /etc/modprobe.conf, I cant remember seeing it from my post http:#a24469276

We may need to manually pass params to the kernel module, you need to look for a qla2??? module and then run;
   modinfo qla2???


0
joolsSenior Systems AdministratorCommented:
This is really strange, I've just hooked up a fibre disk (ds4700) on a linux system in the office and it just works.

Still hunting for a HP fibre disk model like yours. I think I have a few models about.

0
vielkacarolina1239Author Commented:
The HBA QLA2344 is using the default drivers provided by CentOS

[root@localhost qla2xxx-8.02.23]# /sbin/lsmod
Module                  Size  Used by
autofs4                57033  2
hidp                   83521  2
rfcomm                104809  0
l2cap                  89281  10 hidp,rfcomm
bluetooth             118597  5 hidp,rfcomm,l2cap
sunrpc                197897  1
ip_conntrack_netbios_ns    36033  0
ipt_REJECT             38849  1
xt_state               35265  2
ip_conntrack           91109  2 ip_conntrack_netbios_ns,xt_state
nfnetlink              40457  1 ip_conntrack
iptable_filter         36161  1
ip_tables              55329  1 iptable_filter
ip6t_REJECT            38849  1
xt_tcpudp              36289  10
ip6table_filter        36033  1
ip6_tables             50049  1 ip6table_filter
x_tables               50377  6 ipt_REJECT,xt_state,ip_tables,ip6t_REJECT,xt_tcpudp,ip6_tables
dm_multipath           55257  0
scsi_dh                41665  1 dm_multipath
video                  53197  0
backlight              39873  1 video
sbs                    49921  0
i2c_ec                 38593  1 sbs
button                 40545  0
battery                43849  0
asus_acpi              50917  0
acpi_memhotplug        40133  0
ac                     38729  0
ipv6                  424609  21 ip6t_REJECT
xfrm_nalgo             43333  1 ipv6
crypto_api             42945  1 xfrm_nalgo
parport_pc             62313  0
lp                     47121  0
parport                73165  2 parport_pc,lp
sr_mod                 50789  0
sg                     69993  0
k8temp                 39105  0
i2c_amd756             40389  0
ide_cd                 73825  0
floppy                 95465  0
e100                   70097  0
amd_rng                36041  0
tg3                   151621  0
i2c_amd8111            39233  0
hwmon                  36553  1 k8temp
libphy                 53825  1 tg3
k8_edac                50693  0
cdrom                  68713  2 sr_mod,ide_cd
i2c_core               56129  3 i2c_ec,i2c_amd756,i2c_amd8111
mii                    38849  1 e100
serio_raw              40517  0
edac_mc                60193  1 k8_edac
pcspkr                 36289  0
dm_raid45              99025  0
dm_message             36161  1 dm_raid45
dm_region_hash         46145  1 dm_raid45
dm_mem_cache           38977  1 dm_raid45
dm_snapshot            51465  0
dm_zero                35265  0
dm_mirror              53065  0
dm_log                 44865  3 dm_raid45,dm_region_hash,dm_mirror
dm_mod                100369  11 dm_multipath,dm_raid45,dm_snapshot,dm_zero,dm_mirror,dm_log
qla2xxx              1107173  1
scsi_transport_fc      73801  1 qla2xxx
sata_sil               44361  0
libata                208721  1 sata_sil
shpchp                 70637  0
mptspi                 54737  2
mptscsih               69697  1 mptspi
mptbase               113637  2 mptspi,mptscsih
scsi_transport_spi     59841  1 mptspi
sd_mod                 56385  3
scsi_mod              196569  11 scsi_dh,sr_mod,sg,qla2xxx,scsi_transport_fc,libata,mptspi,mptscsih,scsi_transport_spi,sd_mod
ext3                  168017  2
jbd                    94257  1 ext3
uhci_hcd               57433  0
ohci_hcd               55925  0
ehci_hcd               65741  0
[root@localhost qla2xxx-8.02.23]# cat /etc/modprobe.confalias eth0 tg3
alias eth1 tg3
alias eth2 e100
alias scsi_hostadapter mptbase
alias scsi_hostadapter1 mptspi
alias scsi_hostadapter2 sata_sil
alias scsi_hostadapter3 qla2xxx
install qla2xxx /sbin/modprobe qla2xxx_conf; /sbin/modprobe --ignore-install qla2xxx
remove qla2xxx /sbin/modprobe -r --first-time --ignore-remove qla2xxx && { /sbin/modprobe -r --ignore-remove qla2xxx_conf; }
[root@localhost qla2xxx-8.02.23]# /sbin/modinfo qla2xxxmodinfo: could not find module qla2xxx
[root@localhost qla2xxx-8.02.23]# cat /proc/scsi/scsi
Attached devices:
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: MAXTOR   Model: ATLAS10K5_73WLS  Rev: EG0D
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: TSSTcorp Model: CDDVDW SH-S223F  Rev: SB00
  Type:   CD-ROM                           ANSI SCSI revision: 05
[root@localhost qla2xxx-8.02.23]# /sbin/chkconfig --list kudzu
kudzu           0:off   1:off   2:off   3:on    4:on    5:on    6:off
[root@localhost SANsurfer FC HBA Manager (x86_x64)]# ls -l  /lib/modules/2.6.18-128.el5/kernel/drivers/scsi/qla2xxx/total 1184
-rwxr--r-- 1 root root 1202712 Jan 21 12:11 qla2xxx.ko.dist.org
[root@localhost SANsurfer FC HBA Manager (x86_x64)]# /sbin/modinfo qla2xxxmodinfo: could not find module qla2xxx
[root@localhost SANsurfer FC HBA Manager (x86_x64)]#


The HBA card is not detecting the disks.



0
joolsSenior Systems AdministratorCommented:
do you have a /etc/qla2xxx_conf ??

if so what is in it?
0
vielkacarolina1239Author Commented:
Sorry for the long wait. I have been getting home too late from work and have not gotten a chance to give this a try. I will definitely give this a try over the weekend. Thanks again.
0
joolsSenior Systems AdministratorCommented:
Me too... I found that we had one of the disk units but it's in use until Thursday anyway.

0
vielkacarolina1239Author Commented:
Hello,

[root@localhost /]# ls -l qla2*
ls: qla2*: No such file or directory

I played around to much with the kernels and had to reinstall the OS. the current kernel version that I have is
[root@localhost ~]# rpm -qa | grep $(uname -r)
kernel-devel-2.6.18-128.el5
kernel-headers-2.6.18-128.el5
kernel-2.6.18-128.el5



I have run the QLogic utility that collects information about the system/scsi/HBA card.
This utility is found on http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/SearchByProduct.aspx?ProductCategory=39&Product=339&Os=65 
The name of the download is "HBA Collect Utility"

To get to this link, please, go to:
 http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/default.aspx.
Then select Fibre Channel HBAs. The card model is QLA2344 and the OS is Linux Red Hat 64bit.

The name of the download is "HBA Collect Utility"
Also, I have updated the default CentOS drivers for QLogic with
"FC & FCoE Driver (x86/x64/IA64)" from the same link.

[root@localhost qla2xxx-8.02.23]# ./extras/build.sh install

QLA2XXX -- Building the qla2xxx driver, please wait...
Installing intermodule.ko in /lib/modules/2.6.18-128.el5/kernel/kernel/
QLA2XXX -- Build done.

QLA2XXX -- Installing the qla2xxx modules to
/lib/modules/2.6.18-128.el5/kernel/drivers/scsi/qla2xxx/...
[root@localhost qla2xxx-8.02.23]#

[root@localhost ~]# ls -l /lib/modules/2.6.18-128.el5/kernel/drivers/scsi/qla*
-rwxr--r-- 1 root root 161344 Jan 21 12:11 /lib/modules/2.6.18-128.el5/kernel/drivers/scsi/qla1280.ko

/lib/modules/2.6.18-128.el5/kernel/drivers/scsi/qla2xxx:
total 6976
-rw-r--r-- 1 root root  428450 Jun  7 16:40 qla2xxx_conf.ko
-rw-r--r-- 1 root root  428474 Jun  7 04:31 qla2xxx_conf.ko.dist.org
-rw-r--r-- 1 root root 5037827 Jun  7 16:40 qla2xxx.ko
-rwxr--r-- 1 root root 1202712 Jan 21 12:11 qla2xxx.ko.dist.org

/lib/modules/2.6.18-128.el5/kernel/drivers/scsi/qla4xxx:
total 136
-rwxr--r-- 1 root root 130768 Jan 21 12:11 qla4xxx.ko


Please, see the attachment. It has a log directory/files that might help to identify the problem.
I have post fixed the name of the file with .zip in order to upload the file. Please, remove .zip from the file name to decompress.


Please, let me know if you were able to install VA7410 on your system?

Thanks,
QLogicDiag-060709-151823-1.9.tgz.zip
0
joolsSenior Systems AdministratorCommented:
Do you have a /etc/qla2xxx.conf file?

There may be some settings in there that *could* be causing the problems.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
vielkacarolina1239Author Commented:
[root@localhost /]# ls -l /etc/qla2*
ls: /etc/qla2*: No such file or directory
[root@localhost /]#

I don't have this file.
0
joolsSenior Systems AdministratorCommented:
ok.

The disk at work should be available on Wednesday, I'll install Centos 5.3 and see if I get the same problems you get.
0
vielkacarolina1239Author Commented:
great, thanks.
0
joolsSenior Systems AdministratorCommented:
Back again, I managed to get Centos 5.3 64bit onto one of our ML370 G5 servers then connect the HP Fibre disk we have, the disk wasnt in use but the rack the server in was and I wasnt able to go near the rack.

It looks like the disk unit is a little different to yours, it reports as a A6189B... This is the 1st time I've used it as it only has 36GB Disks in... We've not used it for a couple of years.

Anyway, I connected the jbod port on the back of the disk to the fibre HBA in the server and it sprang to life kinda as I expected.

The /proc/scsi/scsi file got populated. (see below)

The server had some differences in the modprobe.conf file as follows;
   cat /etc/modprobe.conf
   alias eth0 bnx2
   alias eth1 bnx2
   alias eth2 e1000e
   alias eth3 e1000e
   alias scsi_hostadapter mptbase
   alias scsi_hostadapter1 mptspi
   alias scsi_hostadapter2 cciss
   alias scsi_hostadapter3 ata_piix
   alias scsi_hostadapter4 qla2xxx

It's rather simpler than your file, no options or anything.... May be worth a try.

Alas it's not all good news, I wasnt able to list any of  the disks with fdisk -l, or address them as /dev/sda...sdn. I think this was due to the configuration of the Disk Array, it had been used on HPUX previously but no one here really knows much about it and its a bit of a forgotton unit.

I will see if I can take the unit apart to see if there is some obvious configuration I need to do but I'm not sure now how far I will get.




[root@localhost ~]# cat /proc/scsi/scsi
Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: HP       Model: A6189B           Rev: A130
  Type:   RAID                             ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 00 Lun: 16384
  Vendor: HP       Model: A6189B           Rev: A130
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 01 Lun: 00
  Vendor: HP 36.4G Model: ST336605FC       Rev: HP08
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 02 Lun: 00
  Vendor: HP 36.4G Model: ST336704FC       Rev: HP12
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 03 Lun: 00
  Vendor: HP 36.4G Model: ST336605FC       Rev: HP08
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 04 Lun: 00
  Vendor: HP 36.4G Model: ST336607FC       Rev: HP05
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 05 Lun: 00
  Vendor: HP 36.4G Model: ST336605FC       Rev: HP09
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 06 Lun: 00
  Vendor: HP 36.4G Model: ST336605FC       Rev: HP08
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 07 Lun: 00
  Vendor: HP 36.4G Model: ST336605FC       Rev: HP08
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 08 Lun: 00
  Vendor: HP 36.4G Model: ST336704FC       Rev: HP12
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 09 Lun: 00
  Vendor: HP 36.4G Model: ST336605FC       Rev: HP08
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 10 Lun: 00
  Vendor: HP 36.4G Model: ST336607FC       Rev: HP03
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 11 Lun: 00
  Vendor: HP 36.4G Model: ST336607FC       Rev: HP05
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 12 Lun: 00
  Vendor: HP 36.4G Model: ST336704FC       Rev: HP12
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 13 Lun: 00
  Vendor: HP 36.4G Model: ST336605FC       Rev: HP08
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 14 Lun: 00
  Vendor: HP 36.4G Model: ST336607FC       Rev: HP03
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 15 Lun: 00
  Vendor: HP 36.4G Model: ST336605FC       Rev: HP09
  Type:   Direct-Access                    ANSI SCSI revision: 03

Open in new window

0
joolsSenior Systems AdministratorCommented:
Rather interestingly, I just checked the messages file and it was saying that the drives are smart capable, so when I used smartctl I got this;

[root@localhost ~]# smartctl -a /dev/sda
smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

Device: HP 36.4G ST336605FC       Version: HP08
Serial number: xxxxxxxxxx
Device type: disk
Transport protocol: Fibre channel (FCP-2)
Local Time is: Fri Jun 12 07:31:25 2009 BST
Device supports SMART and is Enabled
Temperature Warning Enabled
SMART Health Status: OK

Current Drive Temperature:     22 C
Drive Trip Temperature:        65 C
Elements in grown defect list: 0
Vendor (Seagate) cache information
  Blocks sent to initiator = 2329090702
  Blocks received from initiator = 1370920827
  Blocks read from cache and sent to initiator = 203370933
  Number of read and write commands whose size <= segment size = 948228832
  Number of read and write commands whose size > segment size = 98490608
Vendor (Seagate/Hitachi) factory information
  number of hours powered up = 34197.53
  number of minutes until next internal SMART test = 110

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:    3611055        0         0   3611055    3611055     197976.871           0
write:         0        0         0         0          0      14512.382           0
verify:       25        0         0        25         25        139.134           0

Non-medium error count:        1
No self-tests have been logged

But if I fdisk /dev/sda I get;
   Unable to read /dev/sda

But anyway, thats my disk, not yours!
0
joolsSenior Systems AdministratorCommented:
Does you system have a serial port on the back of the LCC?
Ive connected a terminal to mine and I can configure the system.

0
vielkacarolina1239Author Commented:
hello,

The LCC that I have does not contain a serial port. The only connector that It has is a LC. The following link is an image of the item that my disk array contains:
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=400025147754&ssPageName=ADME:B:EOIBSA:US:1123

I tried to plug back the disk array into a Windows OS machine. However, this time, the disks and the disk array is not detected at all. It is like the device is not connected to the computer. I have ordered a set of LCC. Also, I ordered the cables just in case one or the other stopped functioning. Hopefully, I might receive it by the end of the week.
0
vielkacarolina1239Author Commented:
I have found the cause of the problem. The problem was not the cables or the disk array. The problem was the HBA bios settings. I have changed the HBA Bios settings and when I applied the default settings, I was not saving them. Therefore, the HBA bios were misconfigured. This has caused the HBA card to not recognize the disk array since it was not configured properly. After I have realized this and save the HBA default bios settings, the disk array was detected with no problems and the disk are presented to the server.
For instance the disks are presented to the server as sg# where pound is a digit assigned to the disk.

Now that the disk array is detected and the disks are presented to CentOS, please, could you help create some LUNs?

For example, I have two Seagate hard drives that are 72GB unformatted.
1) I would like to format the drives.
2) Create a striped1 (mirrored) on the two drives
3) Create 2 LUN on the drive.

Sorry for the long wait.

Thanks

0
joolsSenior Systems AdministratorCommented:
use cat /proc/scsi/scsi and fdisk -l and post the results.

It would be worth mentioning here what settings you changed for future reference. The only thing I can thing of is that it expected to be connected to a switch rather than direct. curious you had to set an entry in the hba bios though, there are usually set to just work.



0
vielkacarolina1239Author Commented:
nice to hear back from you my friend.

There are 7 hd total.
There are 3 X 36GB HP drives.
There are 4 X 72GB Seagate drives.

This is what the above command issued. The

[root@localhost ~]# cat /proc/scsi/scsi
Attached devices:
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: MAXTOR   Model: ATLAS10K5_73WLS  Rev: JNQ0
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi3 Channel: 00 Id: 00 Lun: 00
  Vendor: TSSTcorp Model: CDDVDW SH-S223F  Rev: SB00
  Type:   CD-ROM                           ANSI SCSI revision: 05
Host: scsi9 Channel: 00 Id: 00 Lun: 00
  Vendor: HP 36.4G Model: ST336607FC       Rev: HP05
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi8 Channel: 00 Id: 00 Lun: 00
  Vendor: HP 36.4G Model: ST336607FC       Rev: HP05
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi9 Channel: 00 Id: 01 Lun: 00
  Vendor: HP 36.4G Model: ST336607FC       Rev: HP05
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi8 Channel: 00 Id: 01 Lun: 00
  Vendor: HP 36.4G Model: ST336607FC       Rev: HP05
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi9 Channel: 00 Id: 02 Lun: 00
  Vendor: SEAGATE  Model: ST373453FC       Rev: 0005
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi8 Channel: 00 Id: 02 Lun: 00
  Vendor: SEAGATE  Model: ST373453FC       Rev: 0005
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi9 Channel: 00 Id: 03 Lun: 00
  Vendor: SEAGATE  Model: ST373453FC       Rev: 0005
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi8 Channel: 00 Id: 03 Lun: 00
  Vendor: SEAGATE  Model: ST373453FC       Rev: 0005
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi9 Channel: 00 Id: 04 Lun: 00
  Vendor: SEAGATE  Model: ST373453FC       Rev: XR03
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi8 Channel: 00 Id: 04 Lun: 00
  Vendor: SEAGATE  Model: ST373453FC       Rev: XR03
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi9 Channel: 00 Id: 05 Lun: 00
  Vendor: HP 36.4G Model: ST336607FC       Rev: HP05
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi8 Channel: 00 Id: 05 Lun: 00
  Vendor: HP 36.4G Model: ST336607FC       Rev: HP05
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi9 Channel: 00 Id: 06 Lun: 00
  Vendor: SEAGATE  Model: ST373453FC       Rev: 0005
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi8 Channel: 00 Id: 06 Lun: 00
  Vendor: SEAGATE  Model: ST373453FC       Rev: 0005
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi8 Channel: 00 Id: 07 Lun: 00
  Vendor: HP       Model: A6255A           Rev: HP05
  Type:   Enclosure                        ANSI SCSI revision: 03
Host: scsi9 Channel: 00 Id: 07 Lun: 00
  Vendor: HP       Model: A6255A           Rev: HP05
  Type:   Enclosure                        ANSI SCSI revision: 03
[root@localhost ~]# fdisk -l

Disk /dev/sda: 73.5 GB, 73557090304 bytes
255 heads, 63 sectors/track, 8942 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   83  Linux
/dev/sda2              14        8942    71722192+  8e  Linux LVM

Disk /dev/sdf: 73.4 GB, 73407868928 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdf doesn't contain a valid partition table

Disk /dev/sdg: 73.4 GB, 73407868928 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdg doesn't contain a valid partition table

Disk /dev/sdh: 73.4 GB, 73407868928 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdh doesn't contain a valid partition table

Disk /dev/sdi: 73.4 GB, 73407868928 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdi doesn't contain a valid partition table

Disk /dev/sdj: 73.4 GB, 73407868928 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdj doesn't contain a valid partition table

Disk /dev/sdk: 73.4 GB, 73407868928 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdk doesn't contain a valid partition table

Disk /dev/sdn: 73.4 GB, 73407868928 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdn doesn't contain a valid partition table

Disk /dev/sdo: 73.4 GB, 73407868928 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdo doesn't contain a valid partition table
[root@localhost ~]#


It is weird because I was able to detect the drives on the Windows machine but would not work on linux. After setting the bios to the default on all 4 ports that the card contains, everything started to work on linux and windows.

I changed the bios on multiple occasions and most likely I misconfigured the HBA. Therefore, the HBA card stopped working on Windows as well. Also, the first  HBA card(qla2340) was new and I could not get it to work. Then I bought the second HBA card(qla2344) which was a refurbish item and this is the one I am using now.

thanks,
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage

From novice to tech pro — start learning today.