Operating System - Linux
1829863 Members
2268 Online
109993 Solutions
New Discussion

FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

 
SOLVED
Go to solution
Luk Vandenbussche
Honored Contributor

FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

Hi,

I am running Redhat Entreprise Edition V3 update3, with the Qlogic driver

QLogic PCI to Fibre Channel Host Adapter for QLA2340 :
Firmware version: 3.02.28, Driver version 7.00.03-RH1
Entry address = f88dc060
HBA: QLA2312 , Serial# R07449
Request Queue = 0x3630000, Response Queue = 0x3620000
Request Queue count= 512, Response Queue count= 512
Total number of active commands = 0
Total number of interrupts = 1185947
Total number of IOCBs (used/max) = (0/600)
Total number of queued commands = 0
Device queue depth = 0x10
Number of free request entries = 500
Number of mailbox timeouts = 0
Number of ISP aborts = 0
Number of loop resyncs = 0
Number of retries for empty slots = 0
Number of reqs in pending_q= 0, retry_q= 0, done_q= 0, scsi_retry_q= 0
Host adapter:loop state= , flags= 0x6860813
Dpc flags = 0x0
MBX flags = 0x0
SRB Free Count = 4096
Link down Timeout = 008
Port down retry = 064
Login retry count = 016
Commands retried with dropped frame(s) = 0
Configured characteristic impedence: 50 ohms
Configured data rate: 1-2 Gb/sec auto-negotiate


SCSI Device Information:
scsi-qla0-adapter-node=200000e08b1ab90d;
scsi-qla0-adapter-port=210000e08b1ab90d;
scsi-qla0-target-0=50001fe15003e889;
scsi-qla0-target-1=50001fe1500425dc;
scsi-qla0-target-2=100000e00222dff3

I have added two luns and also reboot my server.
fdisk doesn't work on my new luns

fdisk /dev/sdd : Cannot read /dev/sdd

output of lssd

sda 0,0,0,1 HP HSV100 2001 5000-1fe1-5003-e889
sdb 0,0,0,2 HP HSV100 2001 5000-1fe1-5003-e889
sdc 0,0,1,1 HP HSV100 2001 5000-1fe1-5004-25dc
sdd 0,0,1,2 HP HSV100 2001 5000-1fe1-5004-25dc

Any idea's
18 REPLIES 18
Ivan Ferreira
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

What is the output of fdisk -l? Did you try using parted instead of fdisk?
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Ivan Ferreira
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

Also, ensure that the OS TYPE in the host definition is correct.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Luk Vandenbussche
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

HOST Type is Sun Solaris (OK for LX)
fdisk in neither working
Ivan Ferreira
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

Do you have multiple HBA? Do you have a multipath software installed?
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Luk Vandenbussche
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

Mpio is embedded in the Qlogic driver.
This is not the issue because my other Luns are working fine
Ivan Ferreira
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

It may be that this disk is active on the other controller (?).

Any other error, like cannot read, not such file, or I/O error. Any log on /var/log/messages.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Luk Vandenbussche
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

This is the only relevant info in messages

Nov 23 11:20:18 san-leandro kernel: sdd:<6>Device 08:30 not ready.
Nov 23 11:20:18 san-leandro kernel: I/O error: dev 08:30, sector 0
Nov 23 11:20:18 san-leandro kernel: Device 08:30 not ready.
Nov 23 11:20:18 san-leandro kernel: I/O error: dev 08:30, sector 0
Nov 23 11:20:18 san-leandro kernel: unable to read partition table
Ivan Ferreira
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

Just for testing, can you turn off one of the controllers? I want to be sure that all disks are on presented by the same controller.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Luk Vandenbussche
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

Ivan, I have one card in by server.
Two controllers on my EVA3000, no I cannot turn this of, this is a production environment
Uwe Zessin
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

"# lssd" shows that the MPIO is working. I suggest you check and make sure that the proper failover policy ("Path A/B-Failover only") is set on the virtual disks.
.
Luk Vandenbussche
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

On the eva3000, it is set
PathA / Failover only

This is the output of lssd

sda 0,0,0,1 HP HSV100 2001 5000-1fe1-5003-e889
sdb 0,0,0,2 HP HSV100 2001 5000-1fe1-5003-e889
sdc 0,0,1,1 HP HSV100 2001 5000-1fe1-5004-25dc
sdd 0,0,1,2 HP HSV100 2001 5000-1fe1-5004-25dc

the output off fdisk

fdisk /dev/sdd

cannot read /dev/sdd
Ivan Ferreira
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

Just to clarify, you should be able to power off one controller even in production, what about if the controller fails? But as you have only one HBA this is not the issue.

Is the zoning configuration correct?
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Luk Vandenbussche
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

Zoning is 100 % correct.
sda en sdc are working fine.
I have added sdb en sdd, I cannot format those luns
Ivan Ferreira
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

Are these luns presented to another host. Maybe you have a FC RESERVATION problem. All posts with FC reservation problems where solved by powering off the storage device.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Luk Vandenbussche
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

Ivan,
These lun are prestented only to one host.
Restarting the EVA is not an issue at this moment.
It is a production environment with
10 servers
Uwe Zessin
Honored Contributor
Solution

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

That doesn't look right to me:

> On the eva3000, it is set PathA / Failover only
>
>This is the output of lssd
>
...
>sdd 0,0,1,2 HP HSV100 2001 5000-1fe1-5004-25dc

Normally, controller A owns WWPNs that end in 8+9. If that is true on your system, |/dev/sdd| is owned by controller B or the MPIO driver has choosen a wrong path.

Can you try and select "PathB / Failover only"" ?
.
Luk Vandenbussche
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

Uwe,

You were right.

PathB / Failover only solved my problem
Ivan Ferreira
Honored Contributor

Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT

That means that in case of failover you won't be able to access the lun?
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?