true image and bad sector

Discussion in 'Acronis True Image Product Line' started by chris_j11, Mar 22, 2005.

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

    chris_j11 Registered Member

    Joined:
    Mar 22, 2005
    Posts:
    1
    i just recently started using true image
    while creating disk image, it found a bad sector in my hd (error = 500(0x101F4), i clicked ignore and continue creating the image.
    will this error prevent me from restoring my xp if a corruption occur
    how do i fix this bad sector?

    2nd q: i just schedule to create a image every xtime, the image (image.tib) i created initially was 2.7GB size, the first schedule created an incremental image of image2.tib and only 300MB
    when i restore my image which one do i click on,

    3rd q: is it better to just create a new image n the schedule or incremental?
     
  2. Acronis Support

    Acronis Support Acronis Support Staff

    Joined:
    Apr 28, 2004
    Posts:
    25,885
    Hello chris_j11,

    Thank you for choosing Acronis True Image (http://www.acronis.com/homecomputing/products/trueimage/).

    The bad sector error will not prevent you from restoring the image but it is bad signal for you since there may data loss occur when you use the hard drive. Please try to open "Start" -> "Run" and input the following command:

    chkdsk <drive letter>: /r

    for all drive letters you have. This may fix the problem.

    When you restore the incremental image you may choose any of the whole set (full and all correpsonding incrementals). After that you will be given a choice from what point you wish to restore the image. Acronis True Image will find the necessary image files itself providing all these files are in the same folder.

    The incremental image is much less than the full one. However, if the full image or one of previous incrementals gets corrupted you will not be able to restore all the subsequent incrementals. So it is up to you to decide which way is more convinient for you.

    Thank you.
    --
    Ilya Toytman
     
Thread Status:
Not open for further replies.