Dieter openbsd at sopwith.solgatos.com writes:
Sigh. I could easily go on a major rant here, but it wouldn't do us
any good. Anyone have information or ideas that could get us closer
to a solution?
Event log counter can be written every once in a while for example if S.M.A.R.T
automatic
please, this is way off topic. could you try and find a better list to
chat about this on...
Has anyone looked into disassembling the firmware?
Hi,
On Tue, 27.01.2009 at 21:37:28 +, Dieter open...@sopwith.solgatos.com
wrote:
Toni writes:
positives and false negatives. After deciding that the results were
far too unreliable, the page was pulled.
That too. For one thing people were entering the serial numbers
using lower
positives and false negatives. After deciding that the results were
far too unreliable, the page was pulled.
That too. For one thing people were entering the serial numbers
using lower case letters and getting false negatives.
this is a joke, right?
As far as I can tell it is not
Hi,
On Mon, 26.01.2009 at 15:39:36 +0100, Raimo Niskanen
raimo+open...@erix.ericsson.se wrote:
How can I know if I have a suspicious drive?
you won't, imho, until Seagate will deliver usable data on this issue.
Their statements so far were a long way from being trust-inspiring,
imho.
My best
Hi,
On Mon, 26.01.2009 at 17:08:51 +, Dieter open...@sopwith.solgatos.com
wrote:
It is easy to set up a slashdot account. Or you can post as anonymous
coward.
yes, but I don't want to set up a /. account right now, and posting as
AC wouldn't likely solve the problem.
that he has
Hi,
On Mon, 26.01.2009 at 17:08:51 +, Dieter open...@sopwith.solgatos.com
wrote:
Your suggestion of smartmontools is helpful, thank you.
thanks - I have just sent an email to them, esp. after seeing that
there are people from big name companies involved, who could procure
at least some of
Dieter openbsd at sopwith.solgatos.com writes:
Recovering from Seagate's problematic 7200.11 firmware.
Most of you have read about the problems with Seagate's
7200.11 disks. For those of you that haven't, the firmware
on many of these drives is buggy, and can brick the drive
when
Nenhum_de_Nos matheus at eternamente.info writes:
where you read that from ?
I have a couple of 750GB ES.2 and now I'm worried !
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931NewLang=en
thanks, yet OT, but I also heard of new firmwares being worse than old
Toni writes:
If we can find out what area
this is (I assume it isn't in the normal space used for user storage)
and how to zero it (if not already zero) there is no need to update
the firmware.
I'd rather say that the (ring) buffer has some external counter, also
stored somewhere,
Hi,
On Sun, 25.01.2009 at 16:27:14 +, Dieter open...@sopwith.solgatos.com
wrote:
I wrote:
You wrote:
Is Maxtorman correct about the 320 log entries?
My dealer told me a similar story, but I don't know where he had it
from.
I guess the next step is to find out if Maxtorman is
Dieter wrote:
Recovering from Seagate's problematic 7200.11 firmware.
Most of you have read about the problems with Seagate's
7200.11 disks. For those of you that haven't, the firmware
on many of these drives is buggy, and can brick the drive
when powering up or rebooting the system. Thus
On Fri, Jan 23, 2009 at 09:28:34PM +, Dieter wrote:
Recovering from Seagate's problematic 7200.11 firmware.
Most of you have read about the problems with Seagate's
7200.11 disks. For those of you that haven't, the firmware
on many of these drives is buggy, and can brick the drive
when
On Sun, January 25, 2009 16:01, Toni Mueller wrote:
Hi,
On Fri, 23.01.2009 at 21:28:34 +, Dieter
open...@sopwith.solgatos.com wrote:
Recovering from Seagate's problematic 7200.11 firmware.
first off, several other product lines are affected, too. In
particular, the popular ES and ES.2
On 2009-01-26, Nenhum_de_Nos math...@eternamente.info wrote:
On Sun, January 25, 2009 16:01, Toni Mueller wrote:
Hi,
On Fri, 23.01.2009 at 21:28:34 +, Dieter
open...@sopwith.solgatos.com wrote:
Recovering from Seagate's problematic 7200.11 firmware.
first off, several other product
On Mon, January 26, 2009 18:48, Stuart Henderson wrote:
On 2009-01-26, Nenhum_de_Nos math...@eternamente.info wrote:
On Sun, January 25, 2009 16:01, Toni Mueller wrote:
Hi,
On Fri, 23.01.2009 at 21:28:34 +, Dieter
open...@sopwith.solgatos.com wrote:
Recovering from Seagate's problematic
Disk families affected:
Barracuda 7200.11, Barracuda ES.2 (SATA), DiamondMax 22, FreeAgent Desk,
Maxtor OneTouch 4, Pipeline HD, Pipeline HD Pro, SV35.3, SV35.4
Barracuda ES.2 SAS drive is not affected
All drives with a date of manufacture January 12, 2009 and later are
not affected by this
Toni writes:
Is Maxtorman correct about the 320 log entries?
My dealer told me a similar story, but I don't know where he had it
from.
I guess the next step is to find out if Maxtorman is correct about this
320 log entries stuff, and if the SMART log entries as reported
Hi,
On Fri, 23.01.2009 at 21:28:34 +, Dieter open...@sopwith.solgatos.com
wrote:
Recovering from Seagate's problematic 7200.11 firmware.
first off, several other product lines are affected, too. In
particular, the popular ES and ES.2 server grade disks are also
affected, to the best of my
Recovering from Seagate's problematic 7200.11 firmware.
first off, several other product lines are affected, too. In
particular, the popular ES and ES.2 server grade disks are also
affected, to the best of my knowledge. Seagate only admits to problems
with ES.2 drives, not ES drives,
Recovering from Seagate's problematic 7200.11 firmware.
Most of you have read about the problems with Seagate's
7200.11 disks. For those of you that haven't, the firmware
on many of these drives is buggy, and can brick the drive
when powering up or rebooting the system. Thus far,
Seagate's
22 matches
Mail list logo
