Results 1 to 7 of 7

Thread: Samsung F1 failed.... Or maybe not ?

  1. #1
    Member
    Join Date
    May 2008
    Posts
    135
    Thanks
    4
    Thanked
    11 times in 4 posts
    • nick_h's system
      • Motherboard:
      • Gigabyte P67A-UD4 Intel P67
      • CPU:
      • Intel Core i5 2500K "Unlocked"
      • Memory:
      • 8GB (2x4GB) Corsair Vengeance DDR3 PC3-12800
      • Storage:
      • 60GB Corsair Force F60 + 6TB HD
      • Graphics card(s):
      • 1280MB EVGA GTX 570 SC
      • PSU:
      • Corsair 850W HX Modular
      • Case:
      • Coolermaster Cosmos S
      • Operating System:
      • Windows 7 Home Premium 64bit
      • Monitor(s):
      • Asus VG236H 23" + Benq 19" LCD
      • Internet:
      • Virgin 50mbit

    Samsung F1 failed.... Or maybe not ?

    This is odd. Vista reported a Bad Block on my system drive last Thursday.

    I whipped all the data off, dropped the Samsung's Diagnostic program onto a DVD and ran it.

    All passes until it started the Surface Scan which reported a Bad Block at around 2%. Stopped the scan and restarted and this time it only got as far as the random read which failed reporting Sector Errors.

    Fine I thinks. I generate an RMA with Samsung and run the Samsungs Low Level Format utility on the disk to wipe it.

    Decided this morning to give the diagnostic program one last run before it the disk goes and so far it's got to 57% with no errors !

    Whats gives ? In my experience if a disk has a Bad Block then it has a Bad Block !

  2. #2
    Senior Member
    Join Date
    Aug 2007
    Posts
    1,094
    Thanks
    11
    Thanked
    77 times in 75 posts
    • LuckyNV's system
      • Motherboard:
      • MSI GD65
      • CPU:
      • i5 750 w/ Thermalright Ultra120X
      • Memory:
      • 2x2GB DDR3-1600 Cas7
      • Storage:
      • 640GB.AAKS, 2xSamsung F1 1TB, 2xSamsung 64GB SLC SSD
      • Graphics card(s):
      • Sapphire HD6870 1GB
      • PSU:
      • Corsair HX620W
      • Case:
      • Coolermaster HAF-932
      • Operating System:
      • Windows 7 Pro 64bit
      • Monitor(s):
      • LG W2286L
      • Internet:
      • Be* Unlimited@21Mbps w/ Draytek 2710n

    Re: Samsung F1 failed.... Or maybe not ?

    Generally diagnostic tools have the ability to examine the surface, if any bad sectors are found, it will mark them as bad and then the HDD will ignore and never write to that sector.

    I had issues with my WD Raptor, I only did a quick format because I'm such a lazy sod, anyway, installed Windows and every start up Windows kept running the disk check, after 3-4 times I decided that something was definitely wrong, ran the WD diagnostic tool, said it found errors and corrected them, bang, no more issues (drive is about 2yo now, near 24/7 use)

  3. #3
    HEXUS.social member Agent's Avatar
    Join Date
    Jul 2003
    Location
    Internet
    Posts
    19,185
    Thanks
    739
    Thanked
    1,614 times in 1,050 posts

    Re: Samsung F1 failed.... Or maybe not ?

    Something that people often forget is that bad sectors are *normal* on drives. No manufacturing process is perfect.
    The issue is when bad sectors start rising. A hard disk has so many sectors 'spare' so that data can be stored there and not in the bad area, without altering the size of the drive.

    Bad sectors after manufacture are normally marked as such, thus the user never sees them. Sometimes they can slip through though.

    In short: Run a full scan (a few times if you like) and see what it reports. If the errors 'vanish' it's just the drive allocating the spare sectors to the bad ones. If they rise, RMA the drive.

    Having said that if you hear anything abnormal or you just don't trust the drive, RMA it
    Quote Originally Posted by Saracen View Post
    And by trying to force me to like small pants, they've alienated me.

  4. #4
    Member
    Join Date
    May 2008
    Posts
    135
    Thanks
    4
    Thanked
    11 times in 4 posts
    • nick_h's system
      • Motherboard:
      • Gigabyte P67A-UD4 Intel P67
      • CPU:
      • Intel Core i5 2500K "Unlocked"
      • Memory:
      • 8GB (2x4GB) Corsair Vengeance DDR3 PC3-12800
      • Storage:
      • 60GB Corsair Force F60 + 6TB HD
      • Graphics card(s):
      • 1280MB EVGA GTX 570 SC
      • PSU:
      • Corsair 850W HX Modular
      • Case:
      • Coolermaster Cosmos S
      • Operating System:
      • Windows 7 Home Premium 64bit
      • Monitor(s):
      • Asus VG236H 23" + Benq 19" LCD
      • Internet:
      • Virgin 50mbit

    Re: Samsung F1 failed.... Or maybe not ?

    Thanks guys. In my experience when a drive starts to get bad blocks it's usually the start of the end. Acording to my Vista logs it was only one bad block .....

    I've now run the full Samsung Diagnostics again including the surface scan and it say the drive has no errors.

    I hope I'm not in a Catch 22 situation now ....

    I've already raised the RMA on the results of the first run of Samsungs diagnostic prog. I dont want to send the drive back to them for them to do the same check and say the drive is fine.

    On the otherhand I dont want them to say I cant raise another RMA later if the drive shows more symptoms of failing.

    According to KillDisk the drive has only had a total of 3 months of use in the last 18 or so.

  5. #5
    HEXUS.social member Agent's Avatar
    Join Date
    Jul 2003
    Location
    Internet
    Posts
    19,185
    Thanks
    739
    Thanked
    1,614 times in 1,050 posts

    Re: Samsung F1 failed.... Or maybe not ?

    GRab something like Speedfan and view the SMART status of the drive. That'll contain all sorts of useful info
    Quote Originally Posted by Saracen View Post
    And by trying to force me to like small pants, they've alienated me.

  6. #6
    Senior Member
    Join Date
    Aug 2003
    Posts
    655
    Thanks
    0
    Thanked
    22 times in 22 posts

    Re: Samsung F1 failed.... Or maybe not ?

    Did you do the full surface scan after using the low level format tool? If that's the case then the drive is fine and the bad block was probably caused by an interrupted write due to a crash etc.

  7. #7
    Senior Member
    Join Date
    Aug 2005
    Posts
    334
    Thanks
    10
    Thanked
    12 times in 12 posts

    Re: Samsung F1 failed.... Or maybe not ?

    try soak testing it whilst it has no valuable data on it.

    I use an old utility that keeps looping disk tests (unfortunately no longer produced).
    But various security companies (try Steganos) also have utilities for secure over-writes that will overwrite the entire disk (rather than files) with sequences of all 0 and then all 1s - pick a high value of repeats... leave it running for a while and then retest - if the number of bad blocks rises - as Agent says, then it needs RMAing...

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Samsung USB Modem driver
    By Goost in forum Help! Quick Relief From Tech Headaches
    Replies: 2
    Last Post: 24-11-2010, 09:30 AM
  2. Give muggers a shock with a cellphone stun-gun
    By Bob Crabtree in forum HEXUS News
    Replies: 13
    Last Post: 05-07-2006, 11:02 PM
  3. TomTom 5 on PDA?
    By Mike Fishcake in forum Smartphones and Tablets
    Replies: 25
    Last Post: 05-07-2006, 11:37 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •