-----Original Message----- From: Chris Murphy Sent: Tuesday, February 17, 2015 3:58
I think the panic is the consequence of drive write failure. So the actual problem is before the panic call trace.
Most of the time it panics without any warning, but once there was:
-----Original Message----- From: Jason Pyeron Sent: Sunday, February 08, 2015 0:00
-----Original Message----- From: Jason Pyeron Sent: Saturday, February 07, 2015 22:54
Feb 8 00:10:21 thirteen-230 kernel: mptscsih: ioc0: attempting task abort! (sc=ffff880057a0a080) Feb 8 00:10:21 thirteen-230 kernel: sd 4:0:0:0: [sda] CDB: Write(10): 2a 00 1a 17 a1 6f 00 00 01 00 Feb 8 00:10:51 thirteen-230 kernel: mptscsih: ioc0: WARNING - Issuing Reset from mptscsih_IssueTaskMgmt!! doorbell=0x24000000 Feb 8 00:10:51 thirteen-230 kernel: mptbase: ioc0: Initiating recovery Feb 8 00:11:13 thirteen-230 kernel: mptscsih: ioc0: task abort: SUCCESS (rv=2002) (sc=ffff880057a0a080)
I'd post the entire dmesg somewhere
http://client.pdinc.us/panic-341e97c30b5a4cb774942bae32d3f163.log
wrap safe (either you mail agent or the forum is hard wrapping and is a pain to read).
What do you get for smartctl -x <dev>
http://client.pdinc.us/smartctl-2000e86b62db27169cc9307358ebf10e.log
In the meantime check or replace cables, usually it's the connectors that
It is a backplane, no "cables". I have reseated the parts.
are faulty not the cable itself. Or replace the drive.
I have replaced the drive (and reinstalled) already, the panics still happen once ever 30-40 hours.
Chris Murphy _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.