linux-kernel - Re: 2.6.29 regression: ATA bus errors on resume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 25 Sep 2009 13:11:37 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Berthold Gunreben <b.gunreben@....de>
CC:	"linux.kernel" <linux-kernel@...r.kernel.org>,
	Theodore Tso <tytso@....edu>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Niel Lambrechts <niel.lambrechts@...il.com>
Subject: Re: 2.6.29 regression: ATA bus errors on resume

Hello, Berthold.

Berthold Gunreben wrote:
> I am not quite sure if I am at the right place here, however, I get very
> similar problems with a totally different setup. What I do is the following:
> 
> I added a fourth disk to a software raid5 array and did setup the raid
> completely from scratch (the same disks have been running for about
> 1.5 years without any problems before, the difference is that previously
> one of the disks was setup as hot spare).
> 
> After the software raid was in sync, I started to copy my data back to
> the raid, and after a  less than 5 minutes time, one of the disks failed
> (from /var/log/warn):
> 
> Sep 18 22:04:02 Bacchus kernel: ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
> Sep 18 22:04:02 Bacchus kernel: ata3.00: irq_stat 0x00400000, PHY RDY changed
> Sep 18 22:04:02 Bacchus kernel: ata3: SError: { PHYRdyChg }
> Sep 18 22:04:02 Bacchus kernel: ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
> Sep 18 22:04:02 Bacchus kernel:          res 40/00:0c:3f:6c:d5/00:00:15:00:00/40 Emask 0x10 (ATA bus error)
> Sep 18 22:04:02 Bacchus kernel: ata3.00: status: { DRDY }

The disk is most likely losing power briefly.  After boot, run
"smartctl -a" on the device and record the output.  After triggering
the problem, do it again.  See if Start_Stop_Count, Power_Cycle_Count
or Power-Off_Retract_Count has increased.  If so, take out your PSU,
bury it half-deep in your backyard, apply some gasoline, light it up
and enjoy the sight of perishing evil with a can of beer.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/