search for: 2000e86b62db27169cc9307358ebf10e

...9;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 sti...

...thirteen-230 dhclient[1272]: DHCPACK from 192.168.5.58 (xid=0x48d081b6) Feb 16 04:30:31 thirteen-230 dhclient[1272]: bound to 192.168.13.230 -- renewal in 9224 seconds. > > >> What do you get for > >> smartctl -x <dev> > > > > http://client.pdinc.us/smartctl-2000e86b62db27169cc9307358ebf10e.log > > OK no smart extended test has been done, but also no pending bad or > relocated sectors, and no phy event errors either. So the write (10) > error seems isolated but it's still really suspicious, so I'd start > replacing hardware. Dell tech is enroute. New system bo...

...wrote: >> I'd post the entire dmesg somewhere > > http://client.pdinc.us/panic-341e97c30b5a4cb774942bae32d3f163.log At least part of the problem happens before this log starts. >> What do you get for >> smartctl -x <dev> > > http://client.pdinc.us/smartctl-2000e86b62db27169cc9307358ebf10e.log OK no smart extended test has been done, but also no pending bad or relocated sectors, and no phy event errors either. So the write (10) error seems isolated but it's still really suspicious, so I'd start replacing hardware. > I have replaced the drive (and reinstalled) already, t...

...id=0x48d081b6) > Feb 16 04:30:31 thirteen-230 dhclient[1272]: bound to 192.168.13.230 -- renewal in 9224 seconds. Doesn't seem related. > >> >> >> What do you get for >> >> smartctl -x <dev> >> > >> > http://client.pdinc.us/smartctl-2000e86b62db27169cc9307358ebf10e.log >> >> OK no smart extended test has been done, but also no pending bad or >> relocated sectors, and no phy event errors either. So the write (10) >> error seems isolated but it's still really suspicious, so I'd start >> replacing hardware. > > Dell te...

...]: bound to > 192.168.13.230 -- renewal in 9224 seconds. > > Doesn't seem related. > > > > > >> > >> >> What do you get for > >> >> smartctl -x <dev> > >> > > >> > > http://client.pdinc.us/smartctl-2000e86b62db27169cc9307358ebf10e.log > >> > >> OK no smart extended test has been done, but also no pending bad or > >> relocated sectors, and no phy event errors either. So the > write (10) > >> error seems isolated but it's still really suspicious, so I'd start > >> replac...

> -----Original Message----- > From: Jason Pyeron > Sent: Sunday, February 08, 2015 0:00 > > > -----Original Message----- > > From: Jason Pyeron > > Sent: Saturday, February 07, 2015 22:54 > > > > NOTE: this is happening on Centos 6 x86_64, > > 2.6.32-504.3.3.el6.x86_64 not Centos 5 > > > > Dell PowerEdge 2970, Seagate SATA drive,