• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
DerSnoezie

Seagate 7200.11 fail & fine dataset

272 posts in this topic

Purely for 7200.11 failing issue that will probably suffice.

I can see where you are going. If one could compose a database containing the basic computer setup of a large number of users, one would have a solid basis for diagnosing/researching other (perhaps similar) problems. However, this would also require the maintenance and active participation of quite a large user group. Say, for example, if a new problem would arise with a specific product, you would first need to mobilize your user group, check if they also have bought the product and ask - if the awnser is yes - if they will monitor the functioning of the product and provide feedback. In the meantime new entries will also be added to the dataset, etc., etc. But for now I'm more or less running a "one man show" in this sub-thread and I simply can't guarantee the safety of such a publically available dataset, regarding abuse of all various kinds.

Edited by DerSnoezie
0

Share this post


Link to post
Share on other sites

Yeah, something like this :) I tend to globalize things.. It's not practical sometimes but hdd failure database could be a great.

There is a nice program, called hdd sentinel. And they are running beta of something simmilar:

http://www.hdsentinel.com/storageinfo.php?lang=en

Let's see what seagate has to say. The had built a very good reputation over the years and i don't want to have 5 equally s***ty manufacturers when it concerns data storage.

0

Share this post


Link to post
Share on other sites
Yeah, something like this :) I tend to globalize things.. It's not practical sometimes but hdd failure database could be a great.

There is a nice program, called hdd sentinel. And they are running beta of something simmilar:

http://www.hdsentinel.com/storageinfo.php?lang=en

Let's see what seagate has to say. The had built a very good reputation over the years and i don't want to have 5 equally s***ty manufacturers when it concerns data storage.

Quite a nice link :D I believe there certainly is an opportunity for such systems.

According to a German article, which was posted this evening on the main thread, seagate is currenlty working on an official statement (see the concluding paragraph):

http://www.computerbase.de/news/hardware/l...rracuda_720011/

Edited by DerSnoezie
0

Share this post


Link to post
Share on other sites
According to a German article, which was posted this evening on the main thread, seagate is currenlty working on an official statement (see the concluding paragraph):

http://www.computerbase.de/news/hardware/l...rracuda_720011/

Someone just posted a knowledge base article to the seagate forums thread about the issue, and within 5 minutes the KB article was GONE. :(

I think until they have a press release tomorrow (seems fairly likely now, this sort of confirms the German article), that KB article will remain offline.

0

Share this post


Link to post
Share on other sites
Someone just posted a knowledge base article to the seagate forums thread about the issue, and within 5 minutes the KB article was GONE. :(

I think until they have a press release tomorrow (seems fairly likely now, this sort of confirms the German article), that KB article will remain offline.

Yeah, those STASI-moderators at the seagate forum are pretty efficient..

Edited by DerSnoezie
0

Share this post


Link to post
Share on other sites

I'll chuck my drives and config into the list:

5QM2S***:ST3500320AS:9BX154-303:SD15:unknown:unknown:SUZHSG:JAN09:N\A:OEM:seannyc:United Kingdom:running_fine - removed after 1 day due to this thread\Antec EarthWatts 500

5QM2N***:ST3500320AS:9BX154-303:SD15:unknown:unknown:SUZHSG:JAN09:N\A:OEM:seannyc:United Kingdom:running_fine - removed after 1 day due to this thread\Antec EarthWatts 500

5QM2T***:ST3500320AS:9BX154-303:SD15:unknown:unknown:SUZHSG:JAN09:N\A:OEM:seannyc:United Kingdom:running_fine - removed after 1 day due to this thread\Antec EarthWatts 500

5QM2T***:ST3500320AS:9BX154-303:SD15:unknown:unknown:SUZHSG:JAN09:N\A:OEM:seannyc:United Kingdom:running_fine - removed after 1 day due to this thread\Antec EarthWatts 500

Now these drives are slightly different to the rest having been manufactured in SUZHSG and being 5QM. They were running fine - they only ran for 1 day in a RAID 10 before I took them out though. They're shelved.

I'm not sure if these drives may fair any better but I certainly wasn't about to find out in a server... I may set them up on an Ubuntu box copying large amounts of data and rebooting to see what they do.

Also, thanks to this thread, I've realised why a FreeNAS I built keeps falling over - it has some retail 9QM ST3500320AS drives installed in a mirrored RAID. It's been stumping me for ages but this *must* be the cause since people have reported instabilities with RAID and these drives.

I'll try and get the unknown data for the 5QM drives, the 9QMs might not be so easy because they're running at a remote site.

Edited by seannyc
0

Share this post


Link to post
Share on other sites
I may set them up on an Ubuntu box copying large amounts of data and rebooting to see what they do.

Well, since they have only been online for one day their use is fairly limited to the dataset, but if you proceed with the idea above some interesting results may surface ;)

Edited by DerSnoezie
0

Share this post


Link to post
Share on other sites

Here are the details of my new brick. Couple of months old with no BIOS detection:

9QM281K9:ST3500320AS:9BX154-303:SD15:08381:KRATSG:(unsure):(01-12-09):DeadST3500320AS:SWE:(No detect in BIOS)

0

Share this post


Link to post
Share on other sites
Here are the details of my new brick. Couple of months old with no BIOS detection:

9QM281K9:ST3500320AS:9BX154-303:SD15:08381:KRATSG:(unsure):(01-12-09):DeadST3500320AS:SWE:(No detect in BIOS)

Thanks! Is this an OEM drive and what kind of OS and power supply are you using? If you can't remember the exact purchase date, the correct month and year will also do.

BTW is this entry also yours?:

62:9QM7****:ST3500320AS:9BX154-303:SD15:09116 (18-09-08):KRATSG:(25-11-08):(13-01-09):DeadST3500320AS:USA:(No detect in BIOS)

Because you appear to have the same username..

Edit ow, I see now, you're AlexLilic :P

so: **9QM281K9:ST3500320AS:9BX154-303:SD15:08381:KRATSG:(unsure):(01-12-09):AlexLilic:SWE:(No detect in BIOS)** it is.

Well I'm off for some sleep now. Tomorrow's going to be an exciting day - with a possible official statement from seagate -, but I won't be back until late. Work Work Work..

Edited by puntoMX
0

Share this post


Link to post
Share on other sites

@DerSnoezie: The night shift has been hard at work...

I've cleaned up the raw data from your first post, in the following ways:

- removed complete serial numbers; just first four characters remain

- removed extra spaces

- fixed some typos from users

- regularized the fine/(reason) text

- changed all dates to YYYY-MM-DD (ISO 8601)

- converted dates of the form "Month 200x" to YYYY-MM-01

- made sure all ':' are in place, so columns line up

My version of the data imports perfectly into Excel, so you can do some sorting/filtering/data mining.

Enjoy!

=====

Number:Serial N°:Model:Part N°:Firmware:DateCode:MfgDate:SiteCode:PurchaseDate:FailedDate:OEM/RETAIL:UserName:Country of User:fail reason/fine:OS

1:9QM7****:ST3500320AS:9BX154-303:SD15:09146:2008-10-09:KRATSG:2008-10-01:2008-12-24:N/A:poolcarpet:Malaysia::

2:9QM6****:ST3500320AS:9BX154-303:SD15:09115:2008-09-17:KRATSG:2008-10-01:2008-12-28:N/A:DaftMule:UK::

3:9QM6****:ST3500320AS:9BX154-303:SD15:N/A:N/A:KRATSG:2008-12-05:2008-12-19:N/A:DerSnoezie:Netherlands:(no detect in bios):

4:9QM4****:ST3500320AS:9BX154-303:SD15:08503:2008-06-16:KRATSG:2008-08-01:2008-11-01:N/A:dskbrk:::

5:9QM3****:ST3500320AS:9BX154-568:SD81:08464:2008-05-20:KRATSG:2008-08-01:2008-12-23:N/A:ToKuRo:Chile:(no detect in bios):

6:9QM7****:ST3500320AS:9BX154-501:SD15:09134:2008-09-30:KRATSG:2008-10-28:2009-01-07:N/A:jeroen__online:Netherlands::

7:9QM2****:ST3500320AS:9BX154-303:SD15:08406:2008-04-10:KRATSG:2008-04-12:2008-12-23:N/A:quattro150:Malaysia::

8:9QJ0****:ST31000340AS:9BX158-303:SD15:08496:2008-06-12:KRATSG:2008-09-01:2009-01-08:N/A:Nichev:::

9:9QM7****:ST3500320AS:9BX154-303:SD15:09114:2008-09-16:KRATSG:2008-10-13:2008-12-14:N/A:PrOdiGy1:UK::

10:9QJ1****:ST31000340AS:9BX158-303:SD15:09063:2008-08-11:KRATSG:2008-11-01:2008-12-27:N/A:AVINNC:USA::

11:9QJ1****:ST31000340AS:9BX158-303:SD15:08515:2008-07-02:KRATSG:2008-08-01:2009-01-04:N/A:Ruddrage:UK::

12:9QM6****:ST3500820AS:9BX134-505:SD25:09084:2008-08-26:KRATSG:2008-07-01:2008-12-20:N/A:rainshower:Germany::

13:9QM3****:STM3500320AS:9GT154-325:MX15:08396:2008-04-03:KRTASG:2008-09-01:2008-12-30:N/A:fabio.cillo:Italy::

14:9QM*****:ST3500320AS:9BX154-303:SD15:08367:2008-03-14:KRATSG:2007-12-01:2008-12-01:N/A:Death_Angel:Malaysia::

15:9QK*****:ST3750630AS:9BX146-621:HP24:08511:2008-06-21:TK:2008-10-01:2009-01-07:N/A:Taiketo:::

16:5QJ*****:ST31000340AS:9BX158-303:SD15:09121:2008-09-20:WUXISG:2008-10-01:2008-12-28:N/A:Styleman:::

17:9QM8****:ST3500320AS:9BX154-303:SD15:N/A:2008-10-13:KRATSG:2008-12-06:2008-12-24:N/A:roadstarter:Philippines::

18:9QM6****:ST3500320AS:9BX154-303:SD15:09076:2008-08-21:KRATSG:2008-10-15:2008-12-29:N/A:labraticmp3:USA::

19:9QM6****:ST3500320AS:9BX154-303:SD15:N/A:N/A:N/A:2008-10-01:2009-01-02:N/A:eli2k:::

20:9QM5****:ST3500320AS:9BX154-303:SD15:09063:2008-08-11:KRATSG:2008-11-06:2008-11-27:N/A:poim76:::

21:9QM2****:ST3500320AS:9BX154-303:SD15:08382:2008-03-23:KRATSG:2008-08-01:2008-11-30:N/A:caba212:Spain::

22:9QJ1****:ST31000340AS:9BX158-303:SD15:08496:2008-06-05:KRATSG:2008-07-01:2008-12-26:N/A:GrayGhost:USA::

23:9QM2****:ST3500320AS:9BX154-303:SD15:08381:2008-03-22:KRATSG:2008-08-12:2009-01-09:N/A:timha:::

24:9QJ0****:ST31000340AS:9BX158-303:SD15:08495:2008-06-11:KRATSG:2008-10-01:2009-01-02:N/A:viniciusferrao:Brazil::

25:9QM6****:ST3500320AS:9BX154-303:SD15:09076:2008-08-21:KRATSG:2008-10-31:2008-12-01:N/A:RiderZen:Australia:(BSY):

26:9QJ0****:ST31000340AS:9BX158-335:SD15:08457:2008-05-16:KRATSG:2008-07-01:2008-12-20:N/A:Macprk:USA::

27:9QM5****:ST3500320AS:9BX154-303:SD15:09071:2008-08-16:KRATSG:2008-11-04:2009-01-09:N/A:BigSilverHotdog:USA::

28:9QM2****:ST3500320AS:9BX154-303:SD15:08382:2008-03-23:KRATSG:2008-08-01:2009-01-01:N/A:Keddar:USA::

29:5QM1****:ST3500320AS:9BX154-303:SD15:08383:2008-03-24:WUXISG:2008-07-01:2009-01-02:N/A:waly2k1:Argentina:(no detect in bios):

30:9QM5****:ST3500320AS:9BX154-303:SD15:09063:2008-08-11:KRATSG:2008-07-01:2008-12-25:N/A:criverock:Italy:(no detect in bios):

31:9QM*****:ST3500320AS:9BX154-303:SD15:09076:2008-08-21:KRATSG:2008-10-01:2008-12-20:N/A:sarahcoco:France::

32:9QJ*****:ST31000340AS:9BX158-303:SD15:09104:2008-09-09:KRATSG:2008-10-10:2009-01-03:N/A:artpav:Canada::

33:9QM*****:ST3500320AS:9BX154-303:SD15:08371:2008-03-15:KRATSG:2008-05-07:2008-12-29:N/A:KillerB:Korea:(no detect in bios):

34:5QJ0****:ST31000340AS:9BX158-303:SD15:09045:2008-07-30:WUXISG:2008-08-01:2008-12-24:N/A:Fuzzy_3D:Canada::

35:9QJ0****:ST31000340AS:9BX158-303:SD15:08356:2008-03-06:KRATSG:2008-03-01:2008-06-01:N/A:TheName:Croatia:(maxtor!):

36:9QM2****:ST3500320AS:9BX154-303:SD15:08381:2008-03-22:KRATSG:2008-07-01:2009-01-05:OEM:BARAKASPEED:Thailand::

37:9QM1****:ST3500320AS:9BX154-303:SD15:08364:2008-03-11:KRATSG:2008-05-01:2008-12-12:OEM:taa:Russia:(no detect in bios):

38:9QM6****:ST3500320AS:9BX154-303:SD15:09096:2008-08-12:KRATSG:2008-09-01:2009-01-07:OEM:kiave:Poland:(no detect in bios):

39:9QM0****:ST3500320AS:9BX154-303:SD15:08315:2008-02-06:KRATSG:2008-03-31:2009-01-11:N/A:laz:Canada:(no detect in bios):

40:9QM6****:ST3500320AS:9BX154-303:SD15:09082:2008-08-24:KRATSG:2008-12-01:2009-01-11:OEM:SeaGAYBarracuTARD:Canada:(no detect in bios):

41:9QM0****:ST3500320AS:9BX154-303:SD15:08243:2008-12-17:KRATSG:2008-01-01:N/A:N/A:dragtop:Canada:fine:

42:9QM8****:ST3500320AS:9BX154-303:SD15:09174:2008-10-28:KRATSG:2008-11-14:2008-01-11:OEM:harwin:Singapore:(no detect in bios):

43:9QM*****:ST3500320AS:9BX154-335:SD15:09054:2008-08-05:KRATSG:2008-09-26:2008-12-19:RETAIL:matildasmith:USA:(BSY):

44:9QM*****:ST3500320AS:9BX154-335:SD15:09085:2008-08-27:KRATSG:2008-12-30:N/A:RETAIL:matildasmith:USA:fine:

45:9QM*****:ST3500320AS:9BX154-335:SD15:09085:2008-08-27:KRATSG:2008-12-30:N/A:RETAIL:matildasmith:USA:fine:

46:9QM1****:ST3500320AS:9BX154-303:SD15:08337:2008-02-22:KRATSG:not sure(at least 1 year old):N/A:OEM:harwin:Singapore:fine:

47:9QM6****:ST3500320AS:9BX154-303:SD15:09085:2008-08-27:KRATSG:2008-09-30:2009-01-11:N/A:bp2411:UK:(no detect in bios):

48:9QJ2****:ST31000340AS:9BX158-303:SD15:09086:2008-08-28:KRATSG:2008-09-22:2008-12-26:OEM:Lippy:UK:(BSY):

49:9QM5****:ST3500320AS:9BX154-303:SD15:09062:2008-08-10:KRATSG:2008-04-09:2008-12-01:OEM:prim:Spain:(no detect in bios):

50:5QJ0****:ST31000340AS:9BX158-303:SD15:08516:2008-06-26:WUXISG:2008-11-13:2009-01-14:RETAIL:Karlston:Australia:(no detect in bios):

51:5QJ0****:ST31000340AS:9BX158-302:SD04:08185:2007-11-07:WUXISG:2008-04-06:2008-06-21:RETAIL:hallwal:USA:(0GB reported):

52:9QM8****:ST3500320AS:9BX154-303:SD15:09167:2008-10-24:KRATSG:2008-12-01:2009-01-11:OEM:s1lencer:Malaysia:(no detect in bios):

53:9QJ0****:ST31000340AS:9BX158-303:SD15:09012:2008-07-06:KRATSG:N/A:N/A:OEM:rimask:Singapore:(no detect in bios):

54:9QK0****:ST3750330AS:9BX156-303:SD15:09024:2008-07-15:KRATSG:2008-11-28:2008-12-30:OEM:valdas:Lithuania:(no detect in bios):

55:9QJ1****:ST31000340AS:9BX158-303:SD15:08526:2008-07-03:KRATSG:2008-08-01:N/A:OEM:me0w:Sweden:fine:

56:9QJ1****:ST31000340AS:9BX158-303:SD15:08526:2008-07-03:KRATSG:2008-08-01:N/A:OEM:me0w:Sweden:fine:

57:5QJ0****:ST31000340AS:9BX158-303:SD15:08524:2008-07-01:WUXISG:2008-08-01:N/A:OEM:me0w:Sweden:fine:

58:9QM4****:ST3500320AS:9BX154-303:SD15:08525:2008-07-02:KRATSG:2008-08-01:N/A:OEM:me0w:Sweden:fine:

59:9QM1****:ST3500320AS:9BX154-303:SD15:08345:2008-02-27:KRATSG:2008-03-30:N/A:OEM:me0w:Sweden:fine:

60:5QJ0****:ST31000340AS:9BX158-303:SD15:09133:2008-09-29:WUXISG:2009-01-01:N/A:OEM:jkc120:USA:fine:FreeBSD 7.1

61:5QJ0****:ST31000340AS:9BX158-303:SD15:09133:2008-09-29:WUXISG:2009-01-01:N/A:OEM:jkc120:USA:fine:FReeBSD 7.1

61:5QJ0****:ST31000340AS:9BX158-303:SD15:09133:2008-09-29:WUXISG:2009-01-01:N/A:OEM:jkc120:USA:fine:FReeBSD 7.1

62:9QM7****:ST3500320AS:9BX154-303:SD15:09116:2008-09-18:KRATSG:2008-11-25:2009-01-13:N/A:DeadST3500320AS:USA:(no detect in bios):

63:9QJ1****:ST31000340AS:9BX158-303:SD15:09107:2008-09-12:KRATSG:2008-11-01:2009-02-01:OEM:SSKEV:Greece:(no detect in bios):

64:9QM5****:ST3500320AS:9BX154-303:SD15:09077:2008-08-22:KRATSG:2008-08-30:2009-01-10:N/A:D3m3nt0r:Germany:(no detect in bios):

65:5QM0****:ST3500320AS:9BX154-303:SD15:08225:2007-12-05:WUXISG:2008-01-21:N/A:N/A:Jack_Steel:Austria:fine:WinXP_32bit

66:9QM*****:ST3500320AS:9BX154-303:SD15:09075:2008-08-20:KRATSG:2008-09-01:N/A:OEM:CheshireCat:Israel:fine:xp32pro_vista32ult_now

67:9SZ*****:ST3320613AS:9FZ-162-300:SD11:08391:2008-03-29:TK:2008-08-01:2008-12-22:OEM:kadolf:Germany:(0GB reported):WinServer 2k8 x64

68:9QM2****:ST3500320AS:9BX154-303:SD15:08381:2008-03-22:KRATSG:(unsure):2009-12-01:N/A:AlexLilic:Sweden:(no detect in bios):N/A

0

Share this post


Link to post
Share on other sites

Here are my drives. They're to be installed as a RAID-1 pair in a Sun X2100 server this weekend, so they've only been run through the SeaTools application, with no problems experienced in the six hours or so that they've been run. I want to get them into the mix because it's like pulling teeth trying to find any info regarding the susceptibility to the BSY issue of the NS drives with this particular firmware rev, so I'll be sure to report any issues I come across with them.

SeaTools reports the model number as GB1000EAFJL, which is also printed on the drive in addition to the ST31000340NS identifier. I suspect my drives are a Hewlett-Packard-tweaked version of the standard NS drive for their DL-series servers, with an HP-specific version of the firmware. I have no idea whether there's any correlation between the HPG6 and SD15 firmware, or any common issues between the two.

69:9QJ28WEA:ST31000340NS:9CA158-784:HPG6:09131:2008-09-27:KRATSG:2009-01-09:N/A:OEM:CGremlin:US:fine:Solaris

70:9QJ283EF:ST31000340NS:9CA158-784:HPG6:09131:2008-09-27:KRATSG:2009-01-09:N/A:OEM:CGremlin:US:fine:Solaris

Edited by CGremlin
0

Share this post


Link to post
Share on other sites
@DerSnoezie: The night shift has been hard at work...

I've cleaned up the raw data from your first post, in the following ways:

- removed complete serial numbers; just first four characters remain

- removed extra spaces

- fixed some typos from users

- regularized the fine/(reason) text

- changed all dates to YYYY-MM-DD (ISO 8601)

- converted dates of the form "Month 200x" to YYYY-MM-01

- made sure all ':' are in place, so columns line up

My version of the data imports perfectly into Excel, so you can do some sorting/filtering/data mining.

Enjoy!

Wow, you sure cleaned up the dataset :P Great job, thanks! BTW If you want to maintain a copy of the list at blist, be my guest.

I want to get them into the mix because it's like pulling teeth trying to find any info regarding the susceptibility to the BSY issue of the NS drives with this particular firmware rev, so I'll be sure to report any issues I come across with them.

Okidoki :thumbup

0

Share this post


Link to post
Share on other sites

71:9TE04W4X:ST31000333AS:9FZ136-300:SD15:09101:TK::N/A:RETAIL:toudoku:Japan:fine:w2k:

It showed up once with 0GB-size but with the Seatools4Dos (Advanced Features -> Set Capacity To MAX Native) I was able to get it back to normal. At that time I was not yet aware of the SD15-related problem. I am also not sure whether these two problems are really related (beside the fact that both relate to the drive's firmware), since with the firmware problem the harddisk is no longer detected at all. Also the "0GB-Bug" is known for a much longer time and did not seem to be limited to a certain firmware, modell or site code, sometimes the blame was even put on the motherboard maker. It would help to isolate the current SD15-problem by confirming if users with a drive reporting only 0GB have tried to reset the size as described above.

I have also a 1500GB drive (S/N:9VS0DA9X:Rev:CC1H:PN:9JU138-302), but I am not sure whether it is affected.

0

Share this post


Link to post
Share on other sites

72:9QM1****:ST3500320AS:9BX154-303:SD15:08366:KRATSG:Spring08:Dec08:RETAIL:idshark:Germany:(no detect in bios):Linux:BeQuiet750W

jeez and I had thought I just caught a bad apple this time until I read the news @ heise.de today and their forum pointed here. Well here is another 500GB that died in December.

0

Share this post


Link to post
Share on other sites

Hi all from Spain!

My disk just crashed yesterday, with a ton of photos in it... :no:

I can't check whether the disk is detected in the BIOS, but my SO reports it has 2100GB (approximate, i can't tell you right now)

The purchase date is approximate.

My data:

9QM4****:ST3500320AS:9BX154-303:SD15:08481:2008-05-31:KRATSG:2008-06-27:2009-01-15:N/A:sunne2k:Spain:(2100GB report in linux):linux kernel 2.6.24-21

Has you seen this page? http://www.salvationdata.com/data-recovery...ny/news0811.htm

Do they actually fix our drives??

0

Share this post


Link to post
Share on other sites

Hello & thanks @ toudoku, idshark and sunne2k for your input.

Yes salvation data provides a recovery kit, containing hard and software, which can unlock your drive so your data can be recovered. However, there is the cost to consider (500 dollar) and your drive can and will most likely will fail again later on, so it is not a fix. You will need a firmware update from seagate, which is not yet available, to prevent the drive from failing again. This firmware update - if it's ever going to be released that is - will be specific for your drive model and associated firmware version and can only be performed on drives which are still operating normally. Please do not download the SD1A firmware update, since it was issued to adress other problems in drives with SD04 and SD14 firmware and most likely will cause harm to your drive.

BTW please take your time to read the main thread, all info above can also be found over there:

http://www.msfn.org/board/index.php?showtopic=128092

Edited by DerSnoezie
0

Share this post


Link to post
Share on other sites

9QM62***:STM3500320AS:9BX154-303:SD15:09083:KRATSG:121108:160109:OEM:Schoolisoutfan:Germany:NO DETECT IN BIOS

0

Share this post


Link to post
Share on other sites
9QM62***:STM3500320AS:9BX154-303:SD15:09083:KRATSG:121108:160109:OEM:Schoolisoutfan:Germany:NO DETECT IN BIOS

Hi, thanks! Could you also add some info on your OS and power supply please?

0

Share this post


Link to post
Share on other sites

5QM1DARX:ST3500320AS:9BX154-303:SD15:08386:WUXISG:150708:160109:Roonster:Germany:STILL WORKS FINE

5QJ0N65D:ST31000340AS:98X158-335:SD15:09036:WUXISG:041108:160109:Roonster:Germany:STILL WORKS FINE

Both drives are working in my MacPro (Model 2008) under Mac OS X 10.5.6 and Windows Vista 64. They are used for Data Backup (har har) and storage (45000 RAW-Pictures, HD Video Material, Music etc.) . Since today, I'm a little bit scared about the situation with those drives. Tomorrow, I will try to buy 2 drives from Western Digital, to backup my Data additionally. Any suggestions for a good and fast drive, bigger than 1 TB?

Greets from Germany,

Roonster

Edited by Roonster
0

Share this post


Link to post
Share on other sites
Hey guys,

These folks have a fix for it, but they quickly took down the video for fear that people would find out their fix (they are data recovery professionals).

http://forum.hddguru.com/solution-for-7200...isk-t10714.html

Apparently it uses PC3000 data recovery tools.

DRP

Yeah, you should check the main thread for more info on that subject. BTW the PC3000 recovery kit costs several 1000's of dollars.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.