Jackie78

Member
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jackie78

  1. Hello, I have a brand new ST31500341AS1.5TB drive, firmware CC1H so obviously not affected by the currently discussed BIOS bug, but another thing is worrying me: my Smart value 05 (Reallocated Sector Count) is increasingat the moment, currently at 3, every few days one more. Is this a thing to worry? Is it a reason to RMA the drive, or is it normal for a new Seagate device? I have many harddisks, different manufacturers, some are more than 3 years old, and none of them has Reallocated Sectors :smileysad: Here is my SMART data, please help. Thanks alot. HD Tune: ST31500341AS Health ID Current Worst ThresholdData Status (01) Raw Read Error Rate 119 99 6 224165191 Ok (03) Spin Up Time 100 100 0 0 Ok (04) Start/Stop Count 100 100 20 7 Ok (05) Reallocated Sector Count 100 100 36 3 Ok (07) Seek Error Rate 60 60 30 1076924 Ok (09) Power On Hours Count 100 100 0 113 Ok (0A) Spin Retry Count 100 100 97 0 Ok (0C) Power Cycle Count 100 100 20 7 Ok (B8) (unknown attribute) 100 100 99 0 Ok (BB) (unknown attribute) 100 100 0 0 Ok (BC) (unknown attribute) 100 100 0 0 Ok (BD) (unknown attribute) 99 99 0 1 Ok (BE) Airflow Temperature 60 59 45 672399400 Ok (C2) Temperature 40 41 0 40 Ok (C3) Hardware ECC Recovered 55 41 0 224165191 Ok (C5) Current Pending Sector 100 100 0 0 Ok (C6) Offline Uncorrectable 100 100 0 0 Ok (C7) Ultra DMA CRC Error Count 200 200 0 0 Ok (F0) Head Flying Hours 100 253 0 113 Ok (F1) (unknown attribute) 100 253 0 -12241740 Ok (F2) (unknown attribute) 100 253 0 -121623263 Ok Power On Time : 113 Health Status : Ok
  2. Hello, I have noticed that my SMART value 05 - Reallocated Sector Count is increasing, although my drive is brand new, firmware CC1H, is it a reason to worry? Heres what it looks like: HD Tune: ST31500341AS Health ID Current Worst ThresholdData Status (01) Raw Read Error Rate 118 99 6 171292852 Ok (03) Spin Up Time 100 100 0 0 Ok (04) Start/Stop Count 100 100 20 7 Ok (05) Reallocated Sector Count 100 100 36 3 Ok (07) Seek Error Rate 60 60 30 1076572 Ok (09) Power On Hours Count 100 100 0 112 Ok (0A) Spin Retry Count 100 100 97 0 Ok (0C) Power Cycle Count 100 100 20 7 Ok (B8) (unknown attribute) 100 100 99 0 Ok (BB) (unknown attribute) 100 100 0 0 Ok (BC) (unknown attribute) 100 100 0 0 Ok (BD) (unknown attribute) 99 99 0 1 Ok (BE) Airflow Temperature 60 59 45 672399400 Ok (C2) Temperature 40 41 0 40 Ok (C3) Hardware ECC Recovered 55 41 0 171292852 Ok (C5) Current Pending Sector 100 100 0 0 Ok (C6) Offline Uncorrectable 100 100 0 0 Ok (C7) Ultra DMA CRC Error Count 200 200 0 0 Ok (F0) Head Flying Hours 100 253 0 112 Ok (F1) (unknown attribute) 100 253 0 -12255735 Ok (F2) (unknown attribute) 100 253 0 -174337236 Ok Power On Time : 112 Health Status : Ok
  3. Hi, is there an update for drives with CC1H firmware already? Seagate writes on their update page: I hope they are right
  4. Affected drives were being reported as NOT affected because people were not putting in all capital letters. Seagate probably took the tool offline to rewrite it so it would not matter if the letters were capital or not. I'll bet it will be back up before too long. It was just a careless programming error I'd bet. This is definitely not true. I have entered several serial numbers from the failed-drives Thread in Caps into the Seagate tool, most of them were reported as being not affected. So the tool was definitely not covering all drives. Besides, there was no plausibility check, if you entered any string that the tool could not identify, it always reportet "Not affected" too, which lead to even more confusion. I really hope that Seagate have indeed found out what is causing all the trouble, and provide a solution soon. Their information policy up to now really is a catastrophy I think
  5. This seems not true, many users have reported that their drive is reported as affected. So maybe the database is incomplete, but I think it is simply faulty, which frightens me, since this could mean Seagate themself don't know which drives actually might be affected.
  6. Hi Ciobi, please check my post on the previous page: http://www.msfn.org/board/index.php?showto...st&p=828094 I have already checked some serials from another thread here of drives that have already failed, and the seagate tool reports they are not affected
  7. Is it me, or is that serial checking tool crap? Or are the users telling crap? If I look at this thread: http://www.msfn.org/board/index.php?showto...mp And enter some of the fully readable serial numbers of people whose drives have already failed to the seagate online checking tool, it keeps telling me that these drives are NOT affected. What now?
  8. Strange thing is: when I enter your serial number in seagates online checker, they say your drivbe is not affected. Wo how much can you trust that tool? http://support.seagate.com/sncheck.html Let's share our results here: http://www.msfn.org/board/index.php?showtopic=128793
  9. Hello, I have read the threads about the Seagate BIOS detection bug, and it seems that there is an online check available now in order to check if your specific drive is affected. You have to enter a serial number and the onlie check tells you if your drive is affected or nor. http://support.seagate.com/sncheck.html In this thread, I'd like to collect information which drives are affected, and which are not, since it is not yet clear if it is a firmware issue ir something else. Note: the Date-Code can be found on top of your drive. I will start with my ST31500341AS: Model: ST31500341AS Firmware version: CC1H Date Code: 09254 Serial Number: 6VS03*** Seagate-Tool says: NOT affected Jackie
  10. seagate support says not yet affected, whatever that means Thanks alot, so we will wait and see what ahppens, has anybody got an answer to their support email yet? Btw, what's the difference between CC1H and SD1A? As far as I know, they are not interchangeable, so what's the difference between the hardware? Since there is an online serial checking tool available from Seagate, I have started a new thread in order to compare which drives may be affected: http://www.msfn.org/board/index.php?showtopic=128793
  11. Hi, just another question: can anybody please tell me what is technically different between drives with CC1H firmware and SD1A? I know you cannot change them between drives, but what is different in hardware (different number of platters?)
  12. Hi, I have found the list of drives affected on the seagat website, but no information which firmware versions are affected. Is it me or did Seagate forget to put that on their site? I have an ST31500341AS, Firmware CC1H, is it affected or not?
  13. I have just another question: In order to send a support email to seagate, you need to register as a new customer on this site: https://partnerreg.seagate.com/pppm/csoregi...source=casemgmt Is it normal, that if you have entered all of your data in the support form, and then select another language than English in the "Choose your Language"-dropdown box, all the user input is deleted? Very strange, or is this a problem with my firefox broswer?
  14. Hi, has anybody ever seen an 1.5TB drive fail (ST31500341AS)? At least there is none in this thread so far, isn't it strange that this model is obviously not affected?
  15. I'd be very surprised if this problem was related to the OS in use, but I don't think it is very probable. It is obviously rather related to the firmware of the drive itself.