02-20-2009 09:22 AM
02-20-2009 09:37 AM
Bloodknight41 wrote:
@anxxous,why is your floppy first ? (I always put it last as it just take boot time) (but that comment is out of the subject)
hummm weird problem indeed...
Did you try to switch the drive to another sata port ? like switch the sata with the one of the DVD.
Another thing you could try, download seatools dos, boot on it, and run some test on the HDD
You will maybe need to RMA it :\
02-20-2009 09:54 AM
@howardrg. I've just sent mine back too. I have my fingers crossed that I won't just get another identical drive back with the same firmware fault (this wouldn't suprise me!).
I'd much rather get back a different model with the equivalent specification.
Also, is seagate willing to pay for my postage, and the 3 CDs (1 per firmware version!) that I've used to update the flash the firmware?
02-20-2009 10:07 AM
@howardrg
Reading some info on your readynas ... wow I love this features :
Embedded BitTorrent™ client for direct downloading from the Internet
Officially licensed BitTorrent client allows downloading to occur without the need for an additional computer. A Web-based interface facilitates download management from computers, and a special NETGEAR Digital Entertainer interface allows management from the EVA8000.
really interesting ![]()
As for hotswap for RAID I'm not too familiar with those.
I know that for RAID 0 , you can't do that
For RAID 1 which is mirroir surely you could. Maybe you will need to acces the netgear and then say "mirroir it"
The only lead I got is that :
" How do I configure a RAID 1 or RAID 5 volume with a spare disk?
02-20-2009 10:28 AM
02-20-2009 11:28 AM
howardrg wrote:
Thanks Bloodknght41. I have decided to send the drive back to Seagate for replacement. I think its the best solution because it avoids potential problems with new errors induced by the firmware update (I have read a few postings about such). The drive is one of two identical models, one with the firmware issue and one without. They are in my Netgear ReadyNAS Duo in RAID 1 (mirrored data) configuration. My plan is to swap the new drive for the old one and then the RAID should rebuild itself, correct? In any event, I have a big external storage drive (WD MyBook 750GB) to which I will copy all the NAS data first in case the NAS data gets lost in the drive swap.
Since you are using RAID 1, all the NAS needs to do is copy the contents of the remaining drive to the replaced new drive. Just make sure it actually does that, so that you are back with two mirrored drives.
It is possible you can still update the firmware using your Vista PC, but if you'd rather send it back for replacement, go ahead. I hope it goes well and fast.
02-20-2009 01:43 PM
Sham63 wrote:
I have new issue now. I opened a chat window and the tech said he couldn't help me, and I had to call support for this issue. So I call support, give my s/n and model number and tell him the problem(bricked drive). He says my drive qualifies for a replacement and not data recovery. So we go to warranty and returns and enter the info and a different drive comes up, a st3500641as. He said that is what he has listed, but on my drive it is shown as a st3500320as. He said the 641 is a better drive and I could still do the return even the model numbers do not match. My s/n # is 9QM68L9J. There is a Q as part of the number, so I tried using a 0 and O, but those were invalid part #, so I did not misread the number. The st3500641as is not shown as one of the drives affected by this issue. I just searched the site, and it is a 7200.9 series drive. So what the heck is going on here? Is the label on my drive wrong or is Seagate wrong?
Jim
Did you happen to buy this disk in a retail kit? I bought two kits (ST3500641AS-RK) that, despite having an ID
that indicated a known reliable 7200.9 drive, actually contained ST3500320AS 7200.11 drives. The drives
had a different part number from that on the box, and also said OEM on them! Despite this, the serial #s
on the boxes matched the serial#s on the drives. Perhaps the database used by Seagate is not properly
distinguishing the model# of the drive from the model# used on the box that contained the drive.
There have been several reports by people who bought boxed retail kits that contained
drives whose model# differed from the retail kit ID number, some wondering if this was an
attempt to unload known problematic 7200.11 drives.
I believe Seagate will claim that the retail kit # does not necessarily imply the model # contained in the kit.
This is annoying to say the least - how do you know what you are buying in a sealed retail boxed kit?
I bought these kits thinking I was getting drives with a known good reputation I'm still holding off on
using the ST3500320AS drives since they were intended to replace a RAID1 boot arrray and the
7200.11 drives have for some time been reported to have drop-out problems, especially in RAID arrays.
Despite current posts, it isn't realy clear that the latest update of of SD1A firmware (reportedly the 2/9/09 version)
can work well in RAID1 arrays for any period of time. There have been some posts saying they
seem to work, and some saying they definitely haven't after being upgraded to SD1A. Reports of
multiple failures of drives (different drives?) in RAID arrays suggest we should be cautious
Part of the uncertainty here is exactly WHICH version of SD1A is being used, and other potential factors
like is the "slowdown" jumper in use or not (these drives often ship with the SATAII disabling jumper in place),
did the drive seem to be having serious bad-sector problems previously, are there potential other
HW problems, etc.
Keep in mind that the "bricking" problem was due to a broken release firmware, which was withdrawn
and replaced by another in the 1/22/09 timeframe, and then the firmware was silently updated again
(appearing about 2/9/09, but with an ISO build time of 1/29/2009 embedded into the ISO).
What is really fixed, and what isn't fixed is NOT clear yet. Rare events will eventually occur (like the log-file
being at 320 when a system is shut down, leading to the "bricking") - so even if somebody updates their
firmware and says it seems to be working, we won't know for a while if the drives are reasonably reliable.
Perhaps there are boundary conditions related to timing, error management, etc. that will eventually trigger
I/O timeouts, drives dropping out, etc. that still need to be fixed. How are we to have confidence without
better information?
It would help if Seagate honestly told customers fully what was/is going on. What problems did they find,
and what are they confident they fixed? In which releases of firmware? What are outstanding issues?
Can we expect another firmware upgrade in the near timeframe to address any other know issues?
When?
The silence is deafening. It doesn't help for forum users to suggest that Seagate is doing
the best they can, or to suggest we should be nice to moderators. I've had a lot of experience in HW/SW
and there is no excuse for treating customers this way. Information is the best antidote to confusion.
SIlence and spin only adds to distrust and anger - it looks like a policy to hide problems rather than
to help customers. In the long run, this cannot be good for Seagate.
Others have asked why OEM ST3500320AS drives were packaged in ST3500641AS-RK kits,
and why these drives had "OEM" stamped on them despite being in retail kits, with no publilc
response.
02-20-2009 03:29 PM
Bloodknight41 wrote:@anxxous :
The last test I could think of is to try to HDD in another computer.If the other computer is also seeing as 0mb, fill a RMA, it's the drive that's screw upSorry about thatThe only revelant info I found was : this oneWhich go a bit overboard and you must do a quick format anyway. :\
02-20-2009 03:57 PM - edited 02-20-2009 04:00 PM
Alright, I ignored this for a week or two hoping it would sort out but it's still not very clear. I've read the whole thread and information is all over the place, so I want to be clear about my circumstances and my questions:
I have a number of affected ST31000340AS drives NOT in a RAID Array with SD15 that have shown NO signs of non-firmware related premature failure. In other words, they are performing perfectly. If I go download SD1A, MooseDT-SD1A-3D4D-16-32MB.ISO, RIGHT NOW February 20th 2009, will I have any problems assuming a successful flash? Has anyone been running stable with the LATEST SD1A for ST31000340AS drives?
Before I do this I'm going to buy another 1TB drive and backup my other 1TB drives one by one. Since I'm a glutton for punishment and I still trust the reliability of Seagate drives under normal circumstances, I was planning to buy an ST31000333AS. If I flash the ST31000333AS to SD1B, Brinks-3D6H-SD1B.ISO, RIGHT NOW February 20th 2009, will I have any problems assuming a successful flash? Has anyone been running stable with the LATEST SD1B for ST31000333AS drives?
My system has been up for 2 months at this point, and while that's not a problem I would like to be able to reboot and apply some operating system and driver updates at some point and this issue is interfering with this. I don't want to have a heart attack every time my system powers down. Anti was the only person giving any real post-flash feedback, so please if you've been running stable after applying the latest of either firmware update let us know.
02-20-2009 04:51 PM
ohnomydata wrote:
...
Before I do this I'm going to buy another 1TB drive and backup my other 1TB drives one by one. Since I'm a glutton for punishment and I still trust the reliability of Seagate drives under normal circumstances, I was planning to buy an ST31000333AS. If I flash the ST31000333AS to SD1B, Brinks-3D6H-SD1B.ISO, RIGHT NOW February 20th 2009, will I have any problems assuming a successful flash? Has anyone been running stable with the LATEST SD1B for ST31000333AS drives?
...
If you go buy an ST31000333AS right now, February 20th 2009, there is a chance that it will come with firmware SD35. In that case you CANNOT FLASH IT WITH ANY PUBLICLY AVAILABLE UPDATED FIRMWARE. There is no firmware update for those of us with this drive/firmware combo, even though some are reported as "affected" by the serial number checker.
That said, if you trust the serial number checker you can check the serial number before you buy. However, I must reiterate that according to Seagate's own field service bulletin, just because a drive is listed as not affected doesn't mean it does not have the firmware bug. It simply means that it was not tested with the offending test equipment during manufacturing, in which case the self bricking feature does not manifest. Unless, of course, the bits at the end of the event log area on disk should happen to flip. But that could never happen.
©2012 Seagate Technology LLC