linux-kernel - Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17

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: <m3ab4pba4p.fsf@intrepid.localdomain>
Date:	Wed, 03 Jun 2009 17:38:30 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Markus <M4rkusXXL@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17

Markus <M4rkusXXL@....de> writes:

>> > I tried that one (compared md5sum). It does not work. It only works 
>> > for "ST31500341AS,  9JU138-300 or -336, SD15 through SD1A ONLY!"
>
> Of course I did. They told me, my drives are not affected and drives 
> with "good" serial numbers will not be upgraded.
> And they now told me I have OEM drives (???) which they do not provide 
> firmware upgrades for, although my drives are ok. I dont understand 
> those support-people.

Well, they might be right. Or the drives may be affected but they don't
support OEM versions anyway and may not know.

Obviously one could try updating anyway (I'm sure a simple hack in
version/SN checking routine would do). It may be risky.
You should, in theory, contact the OEM partner, not the manufacturer.
Could be hard.

OTOH I think the update fixes unrelated problem (a drives failing to
start), that would need checking.
-- 
Krzysztof Halasa
--
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/