If you have Seagate Barracuda 7200.11 disks from 2008 or 2009 you should be very concerned. These disks have a faulty firmware and also the disk surface is problematic. Sector errors are developed very quickly and the firmware will fall on its face.
The symptoms is a 7200.11 disk that either isn't detected by the BIOS anymore (BSY busy error) or reports itself as 0GB in size (0 LBA zero error). Sometimes the disk shows up again and can be accessed for a few moments and a couple of megabytes and goes away again with media error or BSY busy.
The failure rates of 7200.11 are reported to be as high 40-50%. And even if it ran for weeks or months doesn't mean it wont have the problem. Quite to the contrary. It most likely develop the one of the errors soon. Claudio lost a number of disks in his raid array and I just lost the one from my desktop computer.
Anyway, here are my recommendations:
1) Check whether you have any Seagate Barracuda 7200.11 with 500/750/1000/1500GB in your servers or desktops
2) If you have any, then backup the data *right now* to some safe disk or media
3) Replace the 7200.11 as soon as you can with some other brand and model, even if the Seagate tool/website says you disk is not affected
If you already have lost a 7200.11 and still have the disk or if it happens from now there is a way to recover your data. Do *not* do the firmware update that is recommended by Seagate. The recovery process is complicated and involves accessing the disk controller through a debug port and get the firmware into debug mode. All the nasty details in [1] and [2]. You have to cautious with the procedure though. There are some commands shown in the thread that should *not* be executed or further data loss may happen. Read up to page 35 of the forum and only then start your own attempts. "avico" is the guy to look for his posts.
I've done the recovery on two disks successfully, including one that had many fatal sector errors. So if you've got a bricked 7200.11 I've got a working setup and may be able to help you quickly to recover your data.
[1] http://www.msfn.org/board/solution-seagate-7200-11-hdds-t128807.html [2] http://sites.google.com/site/seagatefix/
Clarification: The Barracuda ES.2 is affected as well. Same firmware but slightly better hardware component selection. You may have it in your servers and RAID arrays. Be careful and do backup often!
On 12.01.2010 14:30, Andre Oppermann wrote:
If you have Seagate Barracuda 7200.11 disks from 2008 or 2009 you should be very concerned. These disks have a faulty firmware and also the disk surface is problematic. Sector errors are developed very quickly and the firmware will fall on its face.
The symptoms is a 7200.11 disk that either isn't detected by the BIOS anymore (BSY busy error) or reports itself as 0GB in size (0 LBA zero error). Sometimes the disk shows up again and can be accessed for a few moments and a couple of megabytes and goes away again with media error or BSY busy.
The failure rates of 7200.11 are reported to be as high 40-50%. And even if it ran for weeks or months doesn't mean it wont have the problem. Quite to the contrary. It most likely develop the one of the errors soon. Claudio lost a number of disks in his raid array and I just lost the one from my desktop computer.
Anyway, here are my recommendations:
- Check whether you have any Seagate Barracuda 7200.11 with
500/750/1000/1500GB in your servers or desktops
- If you have any, then backup the data *right now* to some safe disk
or media
- Replace the 7200.11 as soon as you can with some other brand and model,
even if the Seagate tool/website says you disk is not affected
If you already have lost a 7200.11 and still have the disk or if it happens from now there is a way to recover your data. Do *not* do the firmware update that is recommended by Seagate. The recovery process is complicated and involves accessing the disk controller through a debug port and get the firmware into debug mode. All the nasty details in [1] and [2]. You have to cautious with the procedure though. There are some commands shown in the thread that should *not* be executed or further data loss may happen. Read up to page 35 of the forum and only then start your own attempts. "avico" is the guy to look for his posts.
I've done the recovery on two disks successfully, including one that had many fatal sector errors. So if you've got a bricked 7200.11 I've got a working setup and may be able to help you quickly to recover your data.
[1] http://www.msfn.org/board/solution-seagate-7200-11-hdds-t128807.html [2] http://sites.google.com/site/seagatefix/
Hi,
thanks for this helpful information.... we do have ES.2 in our filers.
Thomas
-----Ursprüngliche Nachricht----- Von: swinog-bounces@lists.swinog.ch [mailto:swinog-bounces@lists.swinog.ch] Im Auftrag von Andre Oppermann Gesendet: Dienstag, 12. Januar 2010 16:23 An: swinog@lists.swinog.ch Betreff: [swinog] Barracuda ES.2 is affected too! Seagate Barracuda 7200.11defective, replace immediately
Clarification: The Barracuda ES.2 is affected as well. Same firmware but slightly better hardware component selection. You may have it in your servers and RAID arrays. Be careful and do backup often!
On 12.01.2010 14:30, Andre Oppermann wrote:
If you have Seagate Barracuda 7200.11 disks from 2008 or 2009 you should be very concerned. These disks have a faulty firmware and also the disk surface is problematic. Sector errors are developed very quickly and the firmware will fall on its face.
The symptoms is a 7200.11 disk that either isn't detected by the BIOS anymore (BSY busy error) or reports itself as 0GB in size (0 LBA zero error). Sometimes the disk shows up again and can be accessed for a few moments and a couple of megabytes and goes away again with media error or BSY busy.
The failure rates of 7200.11 are reported to be as high 40-50%. And even if it ran for weeks or months doesn't mean it wont have the problem. Quite to the contrary. It most likely develop the one of the errors soon. Claudio lost a number of disks in his raid array and I just lost the one from my desktop computer.
Anyway, here are my recommendations:
- Check whether you have any Seagate Barracuda 7200.11 with
500/750/1000/1500GB in your servers or desktops
- If you have any, then backup the data *right now* to some safe disk
or media
- Replace the 7200.11 as soon as you can with some other brand and model,
even if the Seagate tool/website says you disk is not affected
If you already have lost a 7200.11 and still have the disk or if it happens from now there is a way to recover your data. Do *not* do the firmware update that is recommended by Seagate. The recovery process is complicated and involves accessing the disk controller through a debug port and get the firmware into debug mode. All the nasty details in [1] and [2]. You have to cautious with the procedure though. There are some commands shown in the thread that should *not* be executed or further data loss may happen. Read up to page 35 of the forum and only then start your own attempts. "avico" is the guy to look for his posts.
I've done the recovery on two disks successfully, including one that had many fatal sector errors. So if you've got a bricked 7200.11 I've got a working setup and may be able to help you quickly to recover your data.
[1] http://www.msfn.org/board/solution-seagate-7200-11-hdds-t128807.html [2] http://sites.google.com/site/seagatefix/
_______________________________________________ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
On 12.01.2010 19:44, Thomas Weible wrote:
Hi,
thanks for this helpful information.... we do have ES.2 in our filers.
If you got the ES.2 from NetApp I would assume that either a different firmware was used (NetApp certifies the firmware for the disks they are selling) or that they've already fixed it on maintenance. Though I certainly wouldn't bet my data on it and check with NetApp directly to get a reliable answer from them. If you just got the empty shelf from them and plugged the disks yourself then you may be in big trouble already. In the MSFN thread there are many people who lost their ES.2 the same way the 7200.11 dies (the unbrick recovery procedure is exactly same for both).
If you got the ES.2 from NetApp I would assume that either a different firmware was used (NetApp certifies the firmware for the disks they are selling) or that they've already fixed it on maintenance. Though I certainly wouldn't bet my data on it and check with NetApp directly to get a reliable answer from them. If you
-> no, we just do have the ES.2 disks and do make use of the openfiler-project.
just got the empty shelf from them and plugged the disks yourself then you may be in big trouble already. In the MSFN thread there are many people who lost their ES.2 the same way the 7200.11 dies (the unbrick recovery procedure is exactly same for both).
-> lucky us, we still have some WD drives around the place and put them into operation. Currently the RAID is syncing.
Btw, do you know if you can ship the ES.2 to Seagate through the regular RMA procedure to get them fixed (I assume a firmware-upgrade should help)? Is there anything I should reference to. I mean the drives are still working at the moment... Thanks for your advices.
Thomas
-----Ursprüngliche Nachricht----- Von: swinog-bounces@lists.swinog.ch [mailto:swinog-bounces@lists.swinog.ch] Im Auftrag von Andre Oppermann Gesendet: Dienstag, 12. Januar 2010 16:23 An: swinog@lists.swinog.ch Betreff: [swinog] Barracuda ES.2 is affected too! Seagate Barracuda 7200.11defective, replace immediately
Clarification: The Barracuda ES.2 is affected as well. Same firmware but slightly better hardware component selection. You may have it in your servers and RAID arrays. Be careful and do backup often!
On 12.01.2010 14:30, Andre Oppermann wrote:
If you have Seagate Barracuda 7200.11 disks from 2008 or 2009 you should be very concerned. These disks have a faulty firmware and also the disk surface is problematic. Sector errors are developed very quickly and the firmware will fall on its face.
The symptoms is a 7200.11 disk that either isn't detected by the BIOS anymore (BSY busy error) or reports itself as 0GB in size (0 LBA zero error). Sometimes the disk shows up again and can be accessed for a few moments and a couple of megabytes and goes away again with media error or BSY busy.
The failure rates of 7200.11 are reported to be as high 40-50%. And even if it ran for weeks or months doesn't mean it wont have the problem. Quite to the contrary. It most likely develop the one of the errors soon. Claudio lost a number of disks in his raid array and I just lost the one from my desktop computer.
Anyway, here are my recommendations:
- Check whether you have any Seagate Barracuda 7200.11 with
500/750/1000/1500GB in your servers or desktops
- If you have any, then backup the data *right now* to some safe disk
or media
- Replace the 7200.11 as soon as you can with some other brand and model,
even if the Seagate tool/website says you disk is not affected
If you already have lost a 7200.11 and still have the disk or if it happens from now there is a way to recover your data. Do *not* do the firmware update that is recommended by Seagate. The recovery process is complicated and involves accessing the disk controller through a debug port and get the firmware into debug mode. All the nasty details in [1] and [2]. You have to cautious with the procedure though. There are some commands shown in the thread that should *not* be executed or further data loss may happen. Read up to page 35 of the forum and only then start your own attempts. "avico" is the guy to look for his posts.
I've done the recovery on two disks successfully, including one that had many fatal sector errors. So if you've got a bricked 7200.11 I've got a working setup and may be able to help you quickly to recover your data.
[1] http://www.msfn.org/board/solution-seagate-7200-11-hdds-t128807.html [2] http://sites.google.com/site/seagatefix/
swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
_______________________________________________ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
On 13.01.2010 08:17, Thomas Weible wrote:
If you got the ES.2 from NetApp I would assume that either a different firmware was used (NetApp certifies the firmware for the disks they are selling) or that they've already fixed it on maintenance. Though I certainly wouldn't bet my data on it and check with NetApp directly to get a reliable answer from them. If you
-> no, we just do have the ES.2 disks and do make use of the openfiler-project.
I see.
just got the empty shelf from them and plugged the disks yourself then you may be in big trouble already. In the MSFN thread there are many people who lost their ES.2 the same way the 7200.11 dies (the unbrick recovery procedure is exactly same for both).
-> lucky us, we still have some WD drives around the place and put them into operation. Currently the RAID is syncing.
Btw, do you know if you can ship the ES.2 to Seagate through the regular RMA procedure to get them fixed (I assume a firmware-upgrade should help)? Is there anything I should reference to. I mean the drives are still working at the moment... Thanks for your advices.
From what I've read only bricked drives can be sent in to Seagate. But you should check with your supplier. The firmware update you can do yourself. Though there are still some reports where even updated disk become bricks again. And also the serial number checker on Seagates website doesn't list all affected disks. There are again many reports of bricked disks with serial numbers other than the officially affected. On top of that at least the 7200.11 has a high probability of developing bad sectors. Maybe the ES.2 has better materials. I personally do not trust the 7200.11 and ES.2 at all anymore. I'm replacing another 7200.11 in a backup server even though Seagate says this serial number is not affected. I do not trust it anymore. And the price of new disks is low enough to justify that. Just imagine the work involved of restoring all your data when the Seagate disks fail anyway. I'm not willing to take that risk. It cost me at least two days to research on the Intenret and obtain all materials to get into the firmware. And then another day to recover the data. Even I have backups they were about a week old and I didn't want to lose all the work I had done in that week.
On 1/13/10 9:14 AM, Andre Oppermann wrote:
On 13.01.2010 08:17, Thomas Weible wrote:
If you got the ES.2 from NetApp I would assume that either a different firmware was used (NetApp certifies the firmware for the disks they are selling) or that they've already fixed it on maintenance. Though I certainly wouldn't bet my data on it and check with NetApp directly to get a reliable answer from them. If you
-> no, we just do have the ES.2 disks and do make use of the openfiler-project.
I see.
just got the empty shelf from them and plugged the disks yourself then you may be in big trouble already. In the MSFN thread there are many people who lost their ES.2 the same way the 7200.11 dies (the unbrick recovery procedure is exactly same for both).
-> lucky us, we still have some WD drives around the place and put them into operation. Currently the RAID is syncing.
Btw, do you know if you can ship the ES.2 to Seagate through the regular RMA procedure to get them fixed (I assume a firmware-upgrade should help)? Is there anything I should reference to. I mean the drives are still working at the moment... Thanks for your advices.
From what I've read only bricked drives can be sent in to Seagate. But you should check with your supplier. The firmware update you can do yourself. Though there are still some reports where even updated disk become bricks again. And also the serial number checker on Seagates website doesn't list all affected disks. There are again many reports of bricked disks with serial numbers other than the officially affected. On top of that at least the 7200.11 has a high probability of developing bad sectors. Maybe the ES.2 has better materials. I personally do not trust the 7200.11 and ES.2 at all anymore. I'm replacing another 7200.11 in a backup server even though Seagate says this serial number is not affected. I do not trust it anymore. And the price of new disks is low enough to justify that. Just imagine the work involved of restoring all your data when the Seagate disks fail anyway. I'm not willing to take that risk. It cost me at least two days to research on the Intenret and obtain all materials to get into the firmware. And then another day to recover the data. Even I have backups they were about a week old and I didn't want to lose all the work I had done in that week.
Andre, all,
I was hit by this on drives I purchased in Jan 2009. Only one of the 4 drives I put into the NAS was affected by the bug (I watched the error counters climb at light speed). I swapped out the drives before they crashed and was able to RMA those that were affected (not all the drives were, even with the firmware/rev details). But RMA did take 6-8 weeks.
YMMV, Thomas
-
Andre Oppermann -
Thomas Kernen -
Thomas Weible