Re: [swinog] Barracuda ES.2 is affected too! SeagateBarracuda 7200.11defective, replace immediately
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-boun...@lists.swinog.ch [mailto:swinog-boun...@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: >> >> 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/ >> > > > > ___ > 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 ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Barracuda ES.2 is affected too! Seagate Barracuda 7200.11defective, replace immediately
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). -- Andre Thomas -Ursprüngliche Nachricht- Von: swinog-boun...@lists.swinog.ch [mailto:swinog-boun...@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: 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/ ___ 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
Re: [swinog] Barracuda ES.2 is affected too! Seagate Barracuda 7200.11defective, replace immediately
Hi, thanks for this helpful information we do have ES.2 in our filers. Thomas -Ursprüngliche Nachricht- Von: swinog-boun...@lists.swinog.ch [mailto:swinog-boun...@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: > > 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/ > ___ 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
Re: [swinog] Networkers Barcelona
Yes, me. See you there Steven :) Cheers, Jerome > -Original Message- > From: swinog-boun...@lists.swinog.ch > [mailto:swinog-boun...@lists.swinog.ch] On Behalf Of Steven Glogger > Sent: 12 January 2010 14:45 > To: swi...@swinog.ch > Subject: [swinog] Networkers Barcelona > > hi everyone > > someone joining cisco networkers in barcelona? > > -steven > > > ___ > 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] Barracuda ES.2 is affected too! Seagate Barracuda 7200.11 defective, 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: 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/ ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
[swinog] Networkers Barcelona
hi everyone someone joining cisco networkers in barcelona? -steven ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
[swinog] Seagate Barracuda 7200.11 defective, replace immediately
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/ -- Andre ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
