ATi says: Bad sectors seen during partition analysis???

Discussion in 'Acronis True Image Product Line' started by jeffcrowder, Jul 17, 2004.

Thread Status:
Not open for further replies.
  1. jeffcrowder

    jeffcrowder Registered Member

    Joined:
    Jul 14, 2004
    Posts:
    5
    Hello,

    Need some guidance on bad sector error. My system is as in sig and I am using Trial version of ATi (build 613). When Ati first loads after launch it "analyzes partitions" and gives the following error for one of my 80GB maxtor PATA drives:

    SEE END OF POST

    I have never had a prob with this HD in past but, naturally, I reformatted without probs and then went to CMD mode and did a chkdisk /R. No bad sectors were found. I rebooted and launched ATi again but same thing. It finds 6 sectors in all (same ones each time).

    After "ignoring" all these from the error dialog box, ATi loads and when I examine the drives using the 'create image' function this is what it says....

    plz see next post as I can only put one image per post.....
     

    Attached Files:

    Last edited: Jul 17, 2004
  2. jeffcrowder

    jeffcrowder Registered Member

    Joined:
    Jul 14, 2004
    Posts:
    5
    The report is below. The raid and the other maxtor PATA drive 'NEW DRIVE #2' are ok, but you can see what it thinks of the other PATA drive. So, is my drive bad eventhough scandisk and chkdsk say it's fine? Is it ATi causing the probs? Any ideas??
     

    Attached Files:

    Last edited: Jul 17, 2004
  3. TheQuest

    TheQuest Registered Member

    Joined:
    Jun 9, 2003
    Posts:
    2,301
    Location:
    Kent. UK by the sea
    Hi, jeffcrowder

    Welcome to Wilders and Acronis TrueImage Forums.

    Ti Build 613 will not work with your Raid0 Array.

    As you have read in When Raid0? thread, you will need the beta.

    But I am sure you will have to purchase Ti first to get the Link from Anton Acronis Support.

    Take Care,
    TheQuest :cool:

    EDIT:- SORRY Build 613 WILL work with jeffcrowder Abit IC7-MAX3 MotherBoard and Intel 875P Chipset
     
    Last edited: Jul 18, 2004
  4. TheQuest

    TheQuest Registered Member

    Joined:
    Jun 9, 2003
    Posts:
    2,301
    Location:
    Kent. UK by the sea
    Hi, jeffcrowder

    Could it be that you installed your RAID0 setup is using the Intel native SATA ports and your other PATA drive is hooked to the Silicon Image controller.

    Take Care,
    TheQuest :cool:
     
  5. jeffcrowder

    jeffcrowder Registered Member

    Joined:
    Jul 14, 2004
    Posts:
    5
    No, here is what I have...

    2 SATA WD 34Gb Raptors on Intel "onchip" RAID (uses ICH5R southbridge controller and not SI controller)

    IDE1/Slave=Maxtor 80 gb ATA133 IDE (PATA)
    IDE1/Master=Maxtor 80 GB ATA 133 IDE (PATA)

    These are just two of the same drives but NOT in raid config and NOT on SI controller. In fact none of the SI SATA ports are used and in BIOS I have 'onboard SATA' disabled. ATI sees the Raptor RAID drive and one of the Master Maxtor just fine, it's the slave Maxtor on IDE that is giving me the probs. I will just remove it, leaving the other Maxtor in and try an image of RAID to it.

    Thanks for your thoughts...keep em coming. I'll let you know how it goes. Anton did say that build 613 supports ICH5R RAID already....


    Jeff
     
  6. wdormann

    wdormann Registered Member

    Joined:
    Jun 27, 2004
    Posts:
    480
    Jeff:

    Extract SmartMonTools on your system somewhere.

    Run: smartctl -a /dev/hda
    to test your first disk, and then try hdb, hdc, hdd until you get results for your second drive. (The letter that you use will depend on your topology)

    Paste the results here.
     
  7. jeffcrowder

    jeffcrowder Registered Member

    Joined:
    Jul 14, 2004
    Posts:
    5
    Here is the info for the PATA Maxtor drive that Acronis TI is having probs with. BTW, TheQuest, I saw your edit and just to let you know, the IC7-MAX3 does not have a Via chipset. It is Intel 875P.

    Anyway, if it will help, here are all the sectors that came up bad on Acronis TI.

    218,129,509
    218,129,637
    218,129,525
    218,129,511
    218,129,512
    729,050,305

    These are reproducible each time ATI is launched and Windows Explorer is able to read/write to drive. Same bad sectors came up after running chkdsk and then reformatting.

    Ok, the smartmon dump is below:


    *****************************************
    C:\Documents and Settings\Jeff\My Documents\My Received Files\smartmontools-5.32
    -1.win32\bin>smartctl -a /dev/hda
    smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
    Home page is http://smartmontools.sourceforge.net/

    === START OF INFORMATION SECTION ===
    Device Model: MAXTOR 6L040J2
    Serial Number: 662131636664
    Firmware Version: A93.0500
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: 5
    ATA Standard is: ATA/ATAPI-5 T13 1321D revision 1
    Local Time is: Sun Jul 18 18:45:27 2004 Central Daylight Time
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled

    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED

    General SMART Values:
    Offline data collection status: (0x00) Offline data collection activity
    was never started.
    Auto Offline Data Collection: Disabled.
    Self-test execution status: ( 0) The previous self-test routine completed

    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 35) seconds.
    Offline data collection
    capabilities: (0x1b) SMART execute Offline immediate.
    Auto Offline data collection on/off supp
    ort.
    Suspend Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    No Conveyance Self-test supported.
    No Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    No General Purpose Logging support.
    Short self-test routine
    recommended polling time: ( 2) minutes.
    Extended self-test routine
    recommended polling time: ( 20) minutes.

    SMART Attributes Data Structure revision number: 11
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_
    FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x0029 100 253 020 Pre-fail Offline -
    0
    3 Spin_Up_Time 0x0027 080 080 020 Pre-fail Always -
    2518
    4 Start_Stop_Count 0x0032 099 099 008 Old_age Always -
    781
    5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail Always -
    0
    7 Seek_Error_Rate 0x000b 100 100 023 Pre-fail Always -
    0
    9 Power_On_Hours 0x0012 097 097 001 Old_age Always -
    2328
    10 Spin_Retry_Count 0x0026 100 100 000 Old_age Always -
    0
    11 Calibration_Retry_Count 0x0013 100 100 020 Pre-fail Always -
    0
    12 Power_Cycle_Count 0x0032 099 099 008 Old_age Always -
    777
    13 Read_Soft_Error_Rate 0x000b 093 093 023 Pre-fail Always -
    1
    194 Temperature_Celsius 0x0022 087 080 042 Old_age Always -
    35
    195 Hardware_ECC_Recovered 0x001a 100 021 000 Old_age Always -
    2818558
    196 Reallocated_Event_Count 0x0010 100 100 020 Old_age Offline -
    0
    197 Current_Pending_Sector 0x0032 100 100 020 Old_age Always -
    0
    198 Offline_Uncorrectable 0x0010 100 253 000 Old_age Offline -
    0
    199 UDMA_CRC_Error_Count 0x001a 194 194 000 Old_age Always -
    6

    SMART Error Log Version: 1
    ATA Error Count: 8 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.

    Error 8 occurred at disk power-on lifetime: 461 hours (19 days + 5 hours)
    When the command that caused the error occurred, the device was in an unknown
    state.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    40 59 0b 14 28 17 e0 Error: UNC at LBA = 0x00172814 = 1517588

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    -- -- -- -- -- -- -- -- ---------------- --------------------
    c9 00 15 0a 28 17 e0 17 00:05:36.215 READ DMA [OBS-5]
    c9 00 17 ca a3 81 e0 81 00:05:36.200 READ DMA [OBS-5]
    cb 00 18 99 80 2f e0 2f 00:05:36.199 WRITE DMA [OBS-5]
    cb 00 40 4a 71 25 e0 25 00:05:36.197 WRITE DMA [OBS-5]
    cb 00 08 c1 6f 25 e0 25 00:05:36.197 WRITE DMA [OBS-5]

    Error 7 occurred at disk power-on lifetime: 461 hours (19 days + 5 hours)
    When the command that caused the error occurred, the device was in an unknown
    state.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    40 59 0b 14 28 17 e0 Error: UNC at LBA = 0x00172814 = 1517588

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    -- -- -- -- -- -- -- -- ---------------- --------------------
    c9 00 15 0a 28 17 e0 17 00:05:22.321 READ DMA [OBS-5]
    c9 00 31 99 fd 81 e0 81 00:05:22.305 READ DMA [OBS-5]
    cb 00 08 91 80 2f e0 2f 00:05:22.305 WRITE DMA [OBS-5]
    cb 00 08 41 73 25 e0 25 00:05:22.305 WRITE DMA [OBS-5]
    cb 00 38 09 73 25 e0 25 00:05:22.303 WRITE DMA [OBS-5]

    Error 6 occurred at disk power-on lifetime: 461 hours (19 days + 5 hours)
    When the command that caused the error occurred, the device was in an unknown
    state.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    40 59 0b 14 28 17 e0 Error: UNC at LBA = 0x00172814 = 1517588

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    -- -- -- -- -- -- -- -- ---------------- --------------------
    c9 00 15 0a 28 17 e0 17 00:05:08.411 READ DMA [OBS-5]
    cb 00 08 ea f2 ce e0 ce 00:05:08.410 WRITE DMA [OBS-5]
    cb 00 08 11 09 47 e0 47 00:05:08.410 WRITE DMA [OBS-5]
    cb 00 40 ca 70 25 e0 25 00:05:08.408 WRITE DMA [OBS-5]
    cb 00 08 41 6f 25 e0 25 00:05:08.408 WRITE DMA [OBS-5]

    Error 5 occurred at disk power-on lifetime: 461 hours (19 days + 5 hours)
    When the command that caused the error occurred, the device was in an unknown
    state.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    40 59 0b 14 28 17 e0 Error: UNC at LBA = 0x00172814 = 1517588

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    -- -- -- -- -- -- -- -- ---------------- --------------------
    c9 00 15 0a 28 17 e0 17 00:04:54.511 READ DMA [OBS-5]
    cb 00 08 01 51 00 e0 00 00:04:54.511 WRITE DMA [OBS-5]
    cb 00 38 c9 50 00 e0 00 00:04:54.509 WRITE DMA [OBS-5]
    cb 00 08 fa f2 ce e0 ce 00:04:54.509 WRITE DMA [OBS-5]
    cb 00 06 d1 15 86 e0 86 00:04:54.508 WRITE DMA [OBS-5]

    Error 4 occurred at disk power-on lifetime: 461 hours (19 days + 5 hours)
    When the command that caused the error occurred, the device was in an unknown
    state.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    40 59 0b 14 28 17 e0 Error: UNC at LBA = 0x00172814 = 1517588

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    -- -- -- -- -- -- -- -- ---------------- --------------------
    c9 00 15 0a 28 17 e0 17 00:04:40.610 READ DMA [OBS-5]
    cb 00 08 11 c1 49 e0 49 00:04:40.610 WRITE DMA [OBS-5]
    cb 00 08 01 6e 25 e0 25 00:04:40.609 WRITE DMA [OBS-5]
    cb 00 38 c9 6d 25 e0 25 00:04:40.607 WRITE DMA [OBS-5]
    ef 00 46 01 00 00 a0 4d 00:04:36.947 SET FEATURES [Reserved subcommand]

    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA
    _of_first_error
    # 1 Short offline Completed without error 00% 2326 -

    Device does not support Selective Self Tests/Logging

    **********************************************
     
  8. wdormann

    wdormann Registered Member

    Joined:
    Jun 27, 2004
    Posts:
    480
    As chkdsk, Acronis, and the drive's SMART data all indicate, the drive has bad sectors. The "UNC" in the smartmontools output means "Uncorrectable error"

    In my experience, once a drive develops bad sectors like this, more are sure to come. If it's the drive that you're imaging *to*, then it's not all that urgent of a problem. Run PowerMax on the drive and you might be able to extend its life by doing a "factory recertification" or by zeroing the drive out.

    If PowerMax happens to give you an error code (good luck!) and the drive is under warranty, you should get it replaced ASAP.
     
  9. TheQuest

    TheQuest Registered Member

    Joined:
    Jun 9, 2003
    Posts:
    2,301
    Location:
    Kent. UK by the sea
    Hi, wdormann

    Beat me to it with PowerMax :D, it will wipe and fix most errors on a Maxtor.

    Been using it for years a long with MaxBlast.

    Take Care,
    TheQuest :cool:
     
Thread Status:
Not open for further replies.