Why is the TI2010 latest bootable image so much smaller?
The latest iso image is 36 MB compared to the previous build which was 57 MB.
Why?
Does the latest build lack any features?
Shouldn't they document this clearly and make the older version available as well as the new version?
Are the users with such RAID controllers SOL if they deleted the 5055 build?
Hello Aloke and Don,
Let me clarify this situation for you.
The latest ISO is smaller than the previous one because we modified some software modules in the latest one. Do not worry, it contains the same features as previous version.
The latest ISO contains build 6053 which does not provide support for many (if any) hardware RAID drivers.
Build 5055 had built-in support for RAID hardware drivers (at least ICH7r SATA RAID, NVIDIA, Dell SAS5iR, and Dell PERC6i).
We haven't changed RAID support in the latest builds. The same controllers are supported in 6053 build. Anyway, if your RAID controller is not detected, I'd recommend you to download the version which is based on another loader (the version has some extended list of drivers and startup parameters). We have implemented the possibility to download the appropriate ISO file after logging into your account (the serial number should be registered). This option is available for the current and (n-1) versions. Please log in to your account, go to the Registered products and downloads section -> Bootable media. Download the file.
To get access to the ISO you should first register Acronis software.
You can find more information on how to burn an ISO image to a CD here.
If this ISO still does not detect your RAID, please let us investigate the issue and collect the following information:
Please boot from the Acronis Bootable Rescue Media from ISO file and press Alt+Ctrl+F2 key combination when user's interface will be loaded, then please enter the following commands:
# cat /proc/partitions
This will give you the list of partitions/drives available in your system.
For example:
8 0 127744 scsi/host0/bus0/target0/lun0/disc
3 0 80417183 ide/host0/bus0/target0/lun0/disc
3 1 10241406 ide/host0/bus0/target0/lun0/part1
3 2 20482875 ide/host0/bus0/target0/lun0/part2
3 3 1020127 ide/host0/bus0/target0/lun0/part3
Flash drive is visible as 'scsi'. If there are some scsi devices in your system you may find your flash by partition/drive size. If the flash is partitioned it will bring the list of partitions as well.
Then you need to create a mount point for your flash and mount it.
# mkdir /mnt/tmp
# mount -t auto /devfs/scsi/host0/bus0/target0/lun0/disc /mnt/tmp
There can be some warning messages but it is safe to ignore them. If mount fails you may try to use 'vfat' (if the flash is formatted to FAT file system) or 'ext3fs' or 'ext2fs' (if its formatted to ext3 or ext2) parameter instead of 'auto' .
Make a directory on your flash drive to save files to it:
# mkdir /mnt/tmp/sysinfo
Check whether the drive is mounted correctly for writing access:
#ls /mnt/tmp
This will give a list of files/folders located on the drive.
Save 'sysinfo' and unmount the flash drive:
# sysinfo > /mnt/tmp/sysinfo/sysinfo.txt
# umount /mnt/tmp
Please, save the created sysinfo.txt file from the flash drive. Then 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 issue appears and the link to this thread. Then please provide me with the case number you receive from our system, so I can pick it up and speed up the process. We will do our best to investigate the problem and provide you with a solution.
Additionally to this, you are welcome to ask me any other questions concerning Acronis, and I will assist you further.
Regards,