RHEL 4, errors with connection to CX300

Thu Jul 28 16:14:59 CDT 2005

I am using powerpath 4.4.0/naviagent 6.16.x and on the RHAS 4.0 u1, kernel 2.6.9-11.ELsmp. HBA is QLE2360, connects to CX300, single path. It's a 6850 server.

I haven't encountered any such messages so far in the last 2 days that this has been installed. 

This looks more like an issue outside of the host. Check to see if there are any 'faults' on the Storage Array, i would suggest check the array's event log. Check to see if the fiber connectors are fully inserted in the switch/front-end port, and swap the cable as well.

anjan

	-----Original Message----- 
	From: Kevin Myer [mailto:kevin_myer at iu13.org] 
	Sent: Thu 7/28/2005 4:50 PM 
	To: linux-poweredge at dell.com 
	Cc: 
	Subject: RHEL 4, errors with connection to CX300

	Hi, 

	Following the release of PowerPath 4.4 and official support from EMC for RHEL 4, 
	we have one PE 6650 server attached to our CX300.  It is a MySQL database 
	server, and based on previous issues with using "newer" kernels that what 
	Dell/EMC officially supported, we've elected to stick with the officially 
	support version, so our kernel is kernel-smp-2.6.9-5.0.5.EL. 

	Off and on, I've been seeing errors: 
	Jul 24 06:09:48 forsterite kernel: Error:Mpc:Path Bus 2 Tgt 0 Lun 0 to 
	APM00042204229 is dead. 
	Jul 24 06:09:48 forsterite kernel: Error:Mpc:Killing bus 2 to CLARiiON  
	APM00042204229 port B1. 
	Jul 24 06:09:58 forsterite kernel: Info:Mpc:Path Bus 2 Tgt 0 Lun 0 to 
	APM00042204229 is alive. 
	Jul 25 23:50:24 forsterite kernel: Error:Mpc:Path Bus 2 Tgt 1 Lun 0 to 
	APM00042204229 is dead. 
	Jul 25 23:50:24 forsterite kernel: Error:Mpc:Killing bus 2 to CLARiiON  
	APM00042204229 port A0. 
	Jul 26 00:08:24 forsterite kernel: Error:Mpc:Path Bus 2 Tgt 0 Lun 0 to 
	APM00042204229 is dead. 
	Jul 26 00:08:24 forsterite kernel: Error:Mpc:Killing bus 2 to CLARiiON  
	APM00042204229 port B1. 
	Jul 26 00:08:29 forsterite kernel: Info:Mpc:Path Bus 2 Tgt 0 Lun 0 to 
	APM00042204229 is alive. 
	Jul 26 00:08:29 forsterite kernel: Info:Mpc:Trespassed volume 
	6006016029401100648F0B7C5DE5D811 to SPB 
	Jul 26 00:08:34 forsterite kernel: Info:Mpc:Path Bus 2 Tgt 1 Lun 0 to 
	APM00042204229 is alive. 
	Jul 26 00:08:34 forsterite kernel: Info:Mpc:Restored volume 
	6006016029401100648F0B7C5DE5D811 to: default SPA 
	Jul 27 17:52:01 forsterite kernel: Error:Mpc:Path Bus 2 Tgt 0 Lun 0 to 
	APM00042204229 is dead. 
	Jul 27 17:52:01 forsterite kernel: Error:Mpc:Killing bus 2 to CLARiiON  
	APM00042204229 port B1. 
	Jul 27 17:52:11 forsterite kernel: Info:Mpc:Path Bus 2 Tgt 0 Lun 0 to 
	APM00042204229 is alive. 
	Jul 28 01:21:58 forsterite kernel: Error:Mpc:Path Bus 2 Tgt 0 Lun 0 to 
	APM00042204229 is dead. 
	Jul 28 01:21:58 forsterite kernel: Error:Mpc:Killing bus 2 to CLARiiON  
	APM00042204229 port B1. 
	Jul 28 01:26:24 forsterite kernel: Error:Mpc:Path Bus 2 Tgt 1 Lun 0 to 
	APM00042204229 is dead. 
	Jul 28 01:26:24 forsterite kernel: Error:Mpc:Killing bus 2 to CLARiiON  
	APM00042204229 port A0. 
	Jul 28 02:02:24 forsterite kernel: Error:Mpc:All paths to 
	6006016029401100648F0B7C5DE5D811 are dead. 
	Jul 28 02:02:24 forsterite kernel: Error:Mpc:6006016029401100648F0B7C5DE5D811 is 
	dead. 
	Jul 28 02:16:21 forsterite kernel: Info:Mpc:6006016029401100648F0B7C5DE5D811 is 
	alive. 
	Jul 28 02:16:21 forsterite kernel: Info:Mpc:Path Bus 2 Tgt 1 Lun 0 to 
	APM00042204229 is alive. 
	Jul 28 02:16:28 forsterite kernel: Info:Mpc:Path Bus 2 Tgt 0 Lun 0 to 
	APM00042204229 is alive. 
	Jul 28 03:43:27 forsterite kernel: Error:Mpc:Path Bus 2 Tgt 0 Lun 0 to 
	APM00042204229 is dead. 
	Jul 28 03:43:27 forsterite kernel: Error:Mpc:Killing bus 2 to CLARiiON  
	APM00042204229 port B1. 
	Jul 28 03:43:37 forsterite kernel: Info:Mpc:Path Bus 2 Tgt 0 Lun 0 to 
	APM00042204229 is alive. 
	Jul 28 05:45:57 forsterite kernel: Error:Mpc:Path Bus 2 Tgt 0 Lun 0 to 
	APM00042204229 is dead. 
	Jul 28 05:45:57 forsterite kernel: Error:Mpc:Killing bus 2 to CLARiiON  
	APM00042204229 port B1. 
	Jul 28 06:03:57 forsterite kernel: Error:Mpc:Path Bus 2 Tgt 1 Lun 0 to 
	APM00042204229 is dead. 
	Jul 28 06:03:57 forsterite kernel: Error:Mpc:Killing bus 2 to CLARiiON  
	APM00042204229 port A0. 
	Jul 28 06:04:07 forsterite kernel: Info:Mpc:Path Bus 2 Tgt 0 Lun 0 to 
	APM00042204229 is alive. 
	Jul 28 06:04:07 forsterite kernel: Info:Mpc:Path Bus 2 Tgt 1 Lun 0 to 
	APM00042204229 is alive. 
	Jul 28 14:23:04 forsterite kernel: Error:Mpc:Path Bus 2 Tgt 1 Lun 0 to 
	APM00042204229 is dead. 
	Jul 28 14:23:04 forsterite kernel: Error:Mpc:Killing bus 2 to CLARiiON  
	APM00042204229 port A0. 
	Jul 28 14:41:04 forsterite kernel: Error:Mpc:Path Bus 2 Tgt 0 Lun 0 to 
	APM00042204229 is dead. 
	Jul 28 14:41:04 forsterite kernel: Error:Mpc:Killing bus 2 to CLARiiON  
	APM00042204229 port B1. 
	Jul 28 14:52:43 forsterite kernel: Error:Mpc:6006016029401100648F0B7C5DE5D811 is 
	dead. 
	Jul 28 15:53:28 forsterite kernel: Info:Mpc:Path Bus 2 Tgt 0 Lun 0 to 
	APM00042204229 is alive. 
	Jul 28 15:53:28 forsterite kernel: Info:Mpc:6006016029401100648F0B7C5DE5D811 is 
	alive. 
	Jul 28 15:53:28 forsterite kernel: Info:Mpc:Path Bus 2 Tgt 1 Lun 0 to 
	APM00042204229 is alive. 

	Then, this morning, mysql had died and I couldn't restart it, because it thought 
	it was trying to chdir to a read-only filesystem.  After unmounting and 
	remounting the partition, mysql started fine, I was able to use it for awhile, 
	but this afternoon, it died again, amidst a flurry of ext3 filesystem errors 
	(actually some are from what appeared to be the timing of the early morning 
	crash of MySQL). 

	Jul 28 02:16:21 forsterite kernel: EXT3-fs error (device dm-6) in 
	ext3_reserve_inode_write: Journal has aborted 
	Jul 28 02:16:21 forsterite kernel: EXT3-fs error (device dm-6) in 
	ext3_dirty_inode: Journal has aborted 
	Jul 28 02:16:21 forsterite kernel: ext3_abort called. 
	Jul 28 02:16:21 forsterite kernel: EXT3-fs error (device dm-6): 
	ext3_journal_start_sb: Detected aborted journal 
	Jul 28 06:47:23 forsterite kernel: SELinux: initialized (dev dm-6, type ext3), 
	uses xattr 
	Jul 28 15:28:43 forsterite kernel: EXT3-fs error (device dm-6): 
	ext3_get_inode_loc: unable to read inode block - inode=28, block=1029 
	Jul 28 15:30:02 forsterite kernel: ext3_abort called. 
	Jul 28 15:30:02 forsterite kernel: EXT3-fs error (device dm-6): 
	ext3_journal_start_sb: Detected aborted journal 
	Jul 28 15:53:28 forsterite kernel: EXT3-fs error (device dm-6) in 
	ext3_reserve_inode_write: Journal has aborted 
	Jul 28 15:53:28 forsterite kernel: EXT3-fs error (device dm-6) in 
	ext3_reserve_inode_write: IO failure 
	Jul 28 15:53:28 forsterite kernel: EXT3-fs error (device dm-6) in 
	ext3_dirty_inode: IO failure 
	Jul 28 15:53:28 forsterite kernel: EXT3-fs error (device dm-6) in 
	ext3_ordered_commit_write: IO failure 
	Jul 28 15:53:28 forsterite kernel: EXT3-fs error (device dm-6) in 
	ext3_dirty_inode: Journal has aborted 

	This is currently a test server, so impact on our production environment is 
	minimal.  But a number of questions: 

	Is anyone successfully using RHEL 4 with the latest PowerPath?  Anything 
	specifically I should look at in troubleshooting? 

	We did run a little bit on RHEL 4, without PowerPath, prior to its release and 
	didn't have any problems at that point.  However, there's always the chance of 
	a bug in the software, or that the cable was jarred a bit, when we reinstalled 
	RHEL4, as it seems to want to install to the SAN partition during install, so 
	we disconnected the patch cable. 

	Summary: 
	PE 6650, quad processor 
	16Gb RAM 
	PowerPath 4.4.0, build 343 
	kernel-smp 2.6.9-5.0.5.EL 
	NaviAgent CLI 6.16.0.4.63 
	HBA is a Qlogic 2340, with BIOS 1.42, using the default Red Hat drivers 

	Thanks, 
	Kevin 

	-- 

	Kevin M. Myer 
	Senior Systems Administrator 
	Lancaster-Lebanon Intermediate Unit 13  http://www.iu13.org 

	_______________________________________________ 
	Linux-PowerEdge mailing list 
	Linux-PowerEdge at dell.com 
	http://lists.us.dell.com/mailman/listinfo/linux-poweredge 
	Please read the FAQ at http://lists.us.dell.com/faq 