Unsolved
This post is more than 5 years old
8 Posts
0
6275
October 19th, 2009 15:00
Red Hat 5.4 I/O Error on boot, iSCSI PowerPath
Hi,
I have a Red Hat 5.4 64 bit system with latest PowerPath, it is connected to a CX3-10 via iSCSI. Two paths, one to each SP. PowerPath finds the paths and i have /dev/emcpowera. But upon boot i recieve a lot of error messages, because it tries to access /dev/sdc for some reason. Which is the stand-by device for the LUN.
The error i see is
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
I have tried:
1. Stop PowerPath
2. Logout iSCSI Targets
3. Remove iSCSI Targets from open-iscsi database, this should remove any persistent mappings right?
4. Reboot
5. Login to iSCSI targets
6. Reboot and watch the error messages
Any clues about why the system tries to acces the /dev/sdc device upon boot?
I have a Red Hat 5.4 64 bit system with latest PowerPath, it is connected to a CX3-10 via iSCSI. Two paths, one to each SP. PowerPath finds the paths and i have /dev/emcpowera. But upon boot i recieve a lot of error messages, because it tries to access /dev/sdc for some reason. Which is the stand-by device for the LUN.
The error i see is
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
I have tried:
1. Stop PowerPath
2. Logout iSCSI Targets
3. Remove iSCSI Targets from open-iscsi database, this should remove any persistent mappings right?
4. Reboot
5. Login to iSCSI targets
6. Reboot and watch the error messages
Any clues about why the system tries to acces the /dev/sdc device upon boot?
0 events found
No Events found!
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
October 19th, 2009 17:00
pm2
4 Posts
0
February 10th, 2010 08:00
I have RHEL5.3 using native MPATH(DM), receiving similar messages. Did you guys find any workaround to supress these messages. Any filter applied ?
Thanks,
Priten
pm2
4 Posts
0
May 14th, 2010 10:00
Any updates on this topic ? message file filling up with these messages.
benno1
1 Message
0
August 3rd, 2010 07:00
Hi,
I have similar issue with RHEL5.5 and EMC AX4-5i.
Got lotof errors in dmesg.
/proc/partitions shows 16 partitions , altought only 4 is acctually in EMC.
How to get iSCSI work correctly with EMC AX4-5i?
Thanks..
end_request: I/O error, dev sdm, sector 0
sd 2:0:0:3: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sdm, sector 0
unable to read partition table
SCSI device sdn: 52428800 512-byte hdwr sectors (26844 MB)
sdn: Write Protect is off
sdn: Mode Sense: 7d 00 00 08
SCSI device sdn: drive cache: write through
sdn: sdn1
SCSI device sdo: 52428800 512-byte hdwr sectors (26844 MB)
sdo: Write Protect is off
sdo: Mode Sense: 7d 00 00 08
SCSI device sdo: drive cache: write through
sdo: unknown partition table
SCSI device sdp: 52428800 512-byte hdwr sectors (26844 MB)
sdp: Write Protect is off
sdp: Mode Sense: 7d 00 00 08
SCSI device sdp: drive cache: write through
sdp: sdp1
sd 1:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sdb, sector 0
sd 3:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sdd, sector 0
sd 0:0:0:2: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sdg, sector 0
sd 1:0:0:1: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
kelleg
6 Operator
•
4.5K Posts
0
August 5th, 2010 14:00
What is the failover mode set for the host on the array - is it failover mode 1? Have you checked the E-Lab on PowerLink to see if the host configuration you are using is supported?
Have you looked at the EMC Host Connectivity Guide for Linux to ensure that all the settings are correct?
glen
Nollaig1
1 Rookie
•
137 Posts
0
August 6th, 2010 00:00
Hello Frejen,
Check out the knowledgebase article emc201545 which may be helpful if you have Emulex HBA's. This solution mentions the document:
EMC Host Connectivity with Emulex Fibre Channel Host Bus Adapters (HBAs) and Converged Network Adapters (CNAs) for the Linux v2.6.x Kernel Environment and the v8.x-Series Drive
Which you can access from Powerlink, Menu options Support -> Tech Doc and Adviseries -> Host Connectivity/HBA's
Also to add to the last update, you might be interested in running a grabfile on your host (available from ftp.emc.com/pub/emcgrab/Unix) and running it through the Host Analysis Tool HEAT (also available in powerlink) to verify your timeout settings HBA driver level etc.
Hope this helps,
Nollaig
Arun_lyca
1 Message
0
October 7th, 2020 08:00
facing same issue. any suggestion to fix it?
DELL-Sam L
Moderator
•
7.9K Posts
•
36 Points
0
October 7th, 2020 12:00
Hello Arun_lyca,
Which system do you have? What is the current OE level or flare of your system?