Menu
I have installed RHEL AS 4 update 5 on a HP DL740 server and presented 1024MB from the SAN (EVA3000) to the server.
The server has two Qlogic HBA cards installed with
# less /proc/scsi/qla2xxx/0
QLogic PCI to Fibre Channel Host Adapter for QLA2340:
Firmware version 3.03.19 IPX, Driver version 8.01.07.25
BIOS version 1.45
I am seeing a lot of device I/O errors for sda. See below.
How do I fix these errors?
[root@megaclite osinst]# pvscan
/dev/sda: read failed after 0 of 4096 at 0: Input/output error
/dev/sda: read failed after 0 of 4096 at 1099511562240: Input/output error
/dev/sda: read failed after 0 of 4096 at 0: Input/output error
/dev/sdd: read failed after 0 of 4096 at 0: Input/output error
/dev/sdd: read failed after 0 of 4096 at 1099511562240: Input/output error
/dev/sdd: read failed after 0 of 4096 at 0: Input/output error
PV /dev/cciss/c0d0p2 VG vg_os lvm2 [67.72 GB / 29.72 GB free]
Total: 1 [67.72 GB] / in use: 1 [67.72 GB] / in no VG: 0 [0 ]
[root@megaclite osinst]#
cat: /dev/sda: Input/output error
[root@megaclite osinst]#
[root@megaclite osinst]# tail /var/log/messages
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 9
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 10
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 11
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 12
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 13
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 14
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 15
Apr 3 12:10:13 megaclite kernel: Device sda not ready.
Apr 3 12:10:13 megaclite kernel: end_request: I/O error, dev sda, sector 0
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 0
The server has two Qlogic HBA cards installed with
# less /proc/scsi/qla2xxx/0
QLogic PCI to Fibre Channel Host Adapter for QLA2340:
Firmware version 3.03.19 IPX, Driver version 8.01.07.25
BIOS version 1.45
I am seeing a lot of device I/O errors for sda. See below.
How do I fix these errors?
[root@megaclite osinst]# pvscan
/dev/sda: read failed after 0 of 4096 at 0: Input/output error
/dev/sda: read failed after 0 of 4096 at 1099511562240: Input/output error
/dev/sda: read failed after 0 of 4096 at 0: Input/output error
/dev/sdd: read failed after 0 of 4096 at 0: Input/output error
/dev/sdd: read failed after 0 of 4096 at 1099511562240: Input/output error
/dev/sdd: read failed after 0 of 4096 at 0: Input/output error
PV /dev/cciss/c0d0p2 VG vg_os lvm2 [67.72 GB / 29.72 GB free]
Total: 1 [67.72 GB] / in use: 1 [67.72 GB] / in no VG: 0 [0 ]
[root@megaclite osinst]#
cat: /dev/sda: Input/output error
[root@megaclite osinst]#
[root@megaclite osinst]# tail /var/log/messages
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 9
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 10
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 11
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 12
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 13
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 14
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 15
Apr 3 12:10:13 megaclite kernel: Device sda not ready.
Apr 3 12:10:13 megaclite kernel: end_request: I/O error, dev sda, sector 0
Apr 3 12:10:13 megaclite kernel: Buffer I/O error on device sda, logical block 0
The issue occurs in a scenario that involves multiple DHCP Relay interfaces (multiple interfaces facing multiple subnets that sent DHCP Discover packets).
Hi, We were using AIX 5.3 on Power Servers. Now we installed few machines with AIX 7.1. On which we are facing that most of the ssh client (like RHEL 5 ssh client, secure shell client) are unable to login to AIX 7.1 box via ssh whereas putty client is able to login on same AIX 7.1 hosts.
When a DHCP Offer is sent from the DHCP Server to DHCP Relay agent, it is sent to ClusterXL VIP address. By default, on Active member this DHCP Offer packet undergoes ClusterXL NAT 'Fold' - the Destination IP address of the DHCP Offer packet is changed from ClusterXL VIP to the physical IP address of the receiving interface (the interface facing the DHCP Server), which is not the IP address of the DHCP Relay interface (the interface facing the Host that sent a DHCP Discover).
- Description:UDP Data store does not start. It fails with the error, 'Failed to start the data store because an invalid Windows user name or an invalid password was provided.
- FhirBlocks SDK. FhirBlocks is a sovereign trust framework for healthcare applications. FhirBlocks enables qualified parties to establish trust across different actors, apps, and devices so that they may access broadly distributed 'pools' of healthcare data, all while preserving data access permissions and chain of custody audit mechanisms.
- My application tries to evaluate a server trust certificate for a self signed certificate. This is working fine with SecPolicyCreateBasicX509 but not working for SecPolicyCreateSSL Here is my code.
This creates following connection link in Check Point kernel tables:
Osstatus Key Generation Failed 25293 Windows 7
[DHCP Server -> DHCP Relay interface agent's VIP address] -> [Translated: DHCP Server -> Physical IP address of receiving interface]
Key Generator
Once additional DHCP packets from different DHCP Relay interfaces are received, link collisions occur in Check Point kernel tables because additional DHCP packets will be translated to same physical IP address of the receiving interface (the interface facing the DHCP Server).