Zarnick
December 14, 2011, 12:37pm
1
Hello guys, I'm going crazy over here with a problem with a LUN created on a EMC CX3.
echo "1" > /sys/class/fc_host/host<n>/issue_lip
and
echo "- - -" > /sys/class/scsi_host/host<n>/scan
then
powermt config
powermt save
I've managed to see the mentioned LUN as device emcpowerf
powermt display dev=all
...
Pseudo name=emcpowerf
CLARiiON ID=CK200074600446 [DBLNX25EC]
Logical device ID=6006016081B11E00F0DD1B23CD24E111 [DBLNX25EC_TST]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0;
Owner: default=SP B, current=SP B Array failover mode: 1
==============================================================================
--------------- Host --------------- - Stor - -- I/O Path -- -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
1 qla2xxx sdb SP A2 active alive 0 0
1 qla2xxx sdh SP B3 active alive 0 0
2 qla2xxx sdn SP B2 active alive 0 0
2 qla2xxx sdt SP A3 active alive 0 0
However, when I try to create a partition, here's the fdisk output:
fdisk /dev/emcpowerf
Unable to read /dev/emcpowerf
What am I missing?
Thanks in advance.
Zarnick
December 14, 2011, 3:06pm
3
# ls -al /dev|grep -i emc*
crw-r--r-- 1 root root 10, 62 Aug 30 16:29 emcpower
brw-r----- 1 root disk 120, 0 Aug 30 16:29 emcpowera
brw-r----- 1 root disk 120, 16 Aug 30 16:29 emcpowerb
brw-r----- 1 root disk 120, 32 Aug 30 16:29 emcpowerc
brw-r----- 1 root disk 120, 48 Aug 30 16:29 emcpowerd
brw-r----- 1 root disk 120, 64 Aug 30 16:29 emcpowere
brw-r----- 1 root disk 120, 80 Dec 13 11:43 emcpowerf
crw-r----- 1 root kmem 1, 1 Aug 30 16:28 mem
crw------- 1 root root 1, 12 Aug 30 16:28 oldmem
crw-r----- 1 root kmem 1, 4 Aug 30 16:28 port
#fdisk -l /dev/sdb
#
So nothing from fdisk -l /dev/sdb. Hmm, can you look at dmeg or /var/log/messages to see if any errors are logged when you run fdisk -l /dev/sdb and also any specific errors logged on fdisk -l /dev/emcpowerf ?
Zarnick
December 15, 2011, 6:00am
6
No problem, here's the output from fdisk -l /dev/sdb:
Dec 15 08:58:58 dblnx25ec kernel: Buffer I/O error on device sdb, logical block 0
Dec 15 08:58:58 dblnx25ec kernel: Buffer I/O error on device sdb, logical block 1
Dec 15 08:58:58 dblnx25ec kernel: Buffer I/O error on device sdb, logical block 2
Dec 15 08:58:58 dblnx25ec kernel: Buffer I/O error on device sdb, logical block 3
Dec 15 08:58:58 dblnx25ec kernel: Buffer I/O error on device sdb, logical block 0
Dec 15 08:58:58 dblnx25ec kernel: Buffer I/O error on device sdb, logical block 524287
Dec 15 08:58:58 dblnx25ec kernel: Buffer I/O error on device sdb, logical block 524287
Dec 15 08:58:58 dblnx25ec kernel: Buffer I/O error on device sdb, logical block 0
Dec 15 08:58:58 dblnx25ec kernel: Buffer I/O error on device sdb, logical block 1
Dec 15 08:58:58 dblnx25ec kernel: Buffer I/O error on device sdb, logical block 2
and from fdisk -l /dev/emcpowerf
Dec 15 08:59:38 dblnx25ec kernel: Buffer I/O error on device emcpowerf, logical block 0
Dec 15 08:59:38 dblnx25ec kernel: Buffer I/O error on device emcpowerf, logical block 1
Dec 15 08:59:38 dblnx25ec kernel: Buffer I/O error on device emcpowerf, logical block 2
Dec 15 08:59:38 dblnx25ec kernel: Buffer I/O error on device emcpowerf, logical block 3
Dec 15 08:59:38 dblnx25ec kernel: Buffer I/O error on device emcpowerf, logical block 0
Dec 15 08:59:38 dblnx25ec kernel: Buffer I/O error on device emcpowerf, logical block 524287
Dec 15 08:59:38 dblnx25ec kernel: Buffer I/O error on device emcpowerf, logical block 524287
Dec 15 08:59:38 dblnx25ec kernel: Buffer I/O error on device emcpowerf, logical block 0
So, basically the same thing...
mark54g
December 15, 2011, 9:14am
7
Here's my silly question...
Zarnick
December 15, 2011, 9:36am
8
Simply put, we don't have support for this storage (at least for that, only for incidents), at least that's what I've being told
mark54g
December 15, 2011, 10:30am
9
No support for storage is a serious situation. They need to fix that or think about not having external storage. When you connect to a SAN, it is the big leagues. This is not the time to play foolish by not supporting your infrastructure.
Zarnick
December 15, 2011, 11:13am
10
Yeah, I know that, but try telling that to my company...I've tried over and over, and it was all the same, we have support for crashes, not implementations...and then it comes to this, when we need a new LUN and can't reboot the server...if I reboot the server, all will be fine, except it's a production server. Anyway, I'm in a big trouble here!
mark54g
December 15, 2011, 1:48pm
11
locate a script online (open source) called rescan-scsi-bus.sh
run it with -l -w -c
See if that helps
Failing that, crack open the manual on powerpath.
Zarnick
December 16, 2011, 5:20am
12
Well, it DID found 8 new devices (???), but still, no luck on trying to use /dev/emcpowerf...
# ./rescan-scsi-bus.sh -l -c -w
Host adapter 0 (megaraid_sas) found.
Host adapter 1 (qla2xxx) found.
Host adapter 2 (qla2xxx) found.
Host adapter 3 (bnx2i) found.
Host adapter 4 (bnx2i) found.
Scanning SCSI subsystem for new devices
Scanning host 0 channels 0 1 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, LUNs 0 1 2 3 4 5 6 7
Scanning host 1 for all SCSI target IDs, LUNs 0 1 2 3 4 5 6 7
Scanning for device 1 0 0 0 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: DGC Model: LUNZ Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 0 1 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 01
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 0 2 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 02
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 0 3 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 03
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 0 4 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 04
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 0 5 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 05
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 0 6 ...
NEW: Host: scsi1 Channel: 00 Id: 00 Lun: 06
Vendor: DGC Model: Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 0 7 ...
NEW: Host: scsi1 Channel: 00 Id: 00 Lun: 07
Vendor: DGC Model: Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 1 0 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 00
Vendor: DGC Model: LUNZ Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 1 1 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 01
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 1 2 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 02
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 1 3 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 03
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 1 4 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 04
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 1 5 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 05
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 1 6 ...
NEW: Host: scsi1 Channel: 00 Id: 01 Lun: 06
Vendor: DGC Model: Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 1 0 1 7 ...
NEW: Host: scsi1 Channel: 00 Id: 01 Lun: 07
Vendor: DGC Model: Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning host 2 for all SCSI target IDs, LUNs 0 1 2 3 4 5 6 7
Scanning for device 2 0 0 0 ...
OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: DGC Model: LUNZ Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 0 1 ...
OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 01
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 0 2 ...
OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 02
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 0 3 ...
OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 03
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 0 4 ...
OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 04
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 0 5 ...
OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 05
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 0 6 ...
NEW: Host: scsi2 Channel: 00 Id: 00 Lun: 06
Vendor: DGC Model: Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 0 7 ...
NEW: Host: scsi2 Channel: 00 Id: 00 Lun: 07
Vendor: DGC Model: Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 1 0 ...
OLD: Host: scsi2 Channel: 00 Id: 01 Lun: 00
Vendor: DGC Model: LUNZ Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 1 1 ...
OLD: Host: scsi2 Channel: 00 Id: 01 Lun: 01
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 1 2 ...
OLD: Host: scsi2 Channel: 00 Id: 01 Lun: 02
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 1 3 ...
OLD: Host: scsi2 Channel: 00 Id: 01 Lun: 03
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 1 4 ...
OLD: Host: scsi2 Channel: 00 Id: 01 Lun: 04
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 1 5 ...
OLD: Host: scsi2 Channel: 00 Id: 01 Lun: 05
Vendor: DGC Model: RAID 10 Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 1 6 ...
NEW: Host: scsi2 Channel: 00 Id: 01 Lun: 06
Vendor: DGC Model: Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning for device 2 0 1 7 ...
NEW: Host: scsi2 Channel: 00 Id: 01 Lun: 07
Vendor: DGC Model: Rev: 0326
Type: Direct-Access ANSI SCSI revision: 04
Scanning host 3 channels 0 1 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, LUNs 0 1 2 3 4 5 6 7
Scanning host 4 channels 0 1 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, LUNs 0 1 2 3 4 5 6 7
8 new device(s) found.
0 device(s) removed.
# sudo /sbin/fdisk -l /dev/emcpowerf
#
.