linux-kernel - Re: Faulty seagate drives, are going to be blacklisted?

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] [day] [month] [year] [list]

Message-ID: <497BBC92.5090208@gmail.com>
Date:	Sun, 25 Jan 2009 10:12:50 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Patrick Horn <patrick.horn@...il.com>
CC:	Diego Calleja <diegocg@...il.com>, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org
Subject: Re: Faulty seagate drives, are going to be blacklisted?

Hello, Patrick.

Patrick Horn wrote:
...
> Is this error just coincidence, or did Seagate forget to mention my drive?
> (And what happened to the firmware updates--they seem to be "In
> Validation")
> Is seagate the only site with information about this? Any public
> blacklist of every affected drive? What can I see in dmesg that
> indicates that NCQ is the cause?

I think it's coincidental.  AFAIK, there was no report of increased
transmission failures.  Two known problems with these firmwares are

1. timeout on FLUSH if NCQ is in use on certain drives

2. bricking after power off (so, the failure is almost always during
   BIOS probing during boot)

> (I'll paste my dmesg as I don't know enough to tell if this is the same
> issue as the other seagate drives--I trimmed the repetitive parts)
> 
> [ 7520.699730] ata2.00: exception Emask 0x10 SAct 0x7ff4f SErr 0x400100
> action 0x6 frozen
> [ 7520.699734] ata2.00: irq_stat 0x08000000, interface fatal error
> [ 7520.699738] ata2: SError: { UnrecovData Handshk }

This is transmission error.  Most common causes are power related or
unreliable connection especially if backplanes are involved.  Is the
problem still reproducible?  If so, can you please try to move it to
different power connector and SATA port and see what changes?

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/