Support for the Adaptec 2020SA Controller

Discussion in 'Acronis True Image Product Line' started by GregMooreSRG, May 4, 2005.

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

    GregMooreSRG Registered Member

    Joined:
    May 4, 2005
    Posts:
    2
    I have a Supermicro server with an Adaptec 2020SA SATA RAID 0/1/5 Controller that the rescue media does not recognize, thus I am unable to backup my server's RAID array.

    I am using True Image Server (latest build).

    When can I expect support for this controller?

    Thanks!

    Greg
     
  2. Acronis Support

    Acronis Support Acronis Support Staff

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

    Thank you for choosing Acronis Server Disk Backup Software.

    Our Development Team is constantly improving Acronis software and the range of supported hardware is broadening fast. We expect your controller to be supported quite soon. Unfortunately, we cannot tell the exact date but each new build of Acronis True Image contains new drivers for particular devices.

    Thank you.
    --
    Ilya Toytman
     
  3. Doug Rhea

    Doug Rhea Guest

    I was trying to test teh Acronis.. and the best test would be.. I have to redo a server this weekend and it has an Adaptec 2020sa controller.

    I have backedup the RAID5 array ie: C & D partitions and now want to restore... but the Acronis boot image recovery CD deos not recognize the controller and thus sees no drives and I can't restore the C: drive...

    very very bad.... what use is Acronis, get 2 thumbs down from me

    and of course now hours and hours of work to redo the server.... since I didn't bother making a tape backup from Veritas of which I would have been able to recover from ...
     
  4. Acronis Support

    Acronis Support Acronis Support Staff

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

    First of all, please make sure that you use the latest build of the respective Acronis True Image version which is available at: http://www.acronis.com/enterprise/support/updates/

    To get access to updates you should create an account at:
    http://www.acronis.com/enterprise/my/
    then log in and use your serial number to register your software.

    Please create new Bootable Rescue CD after installing the update, boot your server from this CD and see if the problem still persists.

    If the problem still persists with Bootable Rescue CD created using the latest build of the respective Acronis True Image version then please try booting with "acpi=off noapic" parameter as it is described in Acronis Help Post.

    If that does not help then please do the following:

    - Boot the server from Bootable Rescue CD created using the latest build of the respective Acronis True Image version and press F11 key when the "Staring Acronis Loader..." message appears;

    - After you get the "Linux Kernel Settings" prompt, please remove the "quiet" word, click on the OK button, choose "Full Version" and wait for # prompt to appear;

    - Insert a diskette in a floppy disk drive and issue the following commands;

    cd tmp
    mkdir mntdir
    mount /devfs/floppy/0 mntdir
    sysinfo > mntdir/sysinfo.txt
    lspci > mntdir/lspci.txt
    umount mntdir

    - Collect the sysinfo.txt and lspci.txt files from the diskette.

    Please also create Acronis Report in the way described below:

    - Download and run Acronis Report Utility;
    - Select the "Create Bootable Floppy" option;
    - Insert a blank floppy disk in the A: drive and proceed with creation of the bootable floppy;
    - Boot the computer from this diskette and wait for report creation process to finish;
    - Collect the report file from the floppy.

    Please submit a request for technical support. Attach all the collected files and information to your request along with the step-by-step description of the actions taken before the problem appears and the link to this thread. We will certainly try to provide you with the solution as soon as possible.

    Thank you.
    --
    Alexey Popov
     
Thread Status:
Not open for further replies.