Can't restore from network share with Rescue CD w/2337

TrueImage 9.0, build 2337
Dell Inspiron 8200, BIOS A11, NIC Netgear GA511
Network server Linksys NSLU2 NAS, firmware 2.3r29

When trying to restore from a network share TrueImage won't accept a filename that is below the root.

The image is named \\winback\noteback\nomad3.housenet.jrv\TrueImage\Manual\2006-0002-20.tib

When I type this name in the Restore Filename area the Next button is not highlighted – there is no way to proceed.

In the Explorer-like pane on the left if I click on the name of the toplevel directory (nomad3.housenet.jrv) to expand its contents it shows “nomad3.housenet.jrv” again – which is wrong as there is no such subdirectory – and does not show subdirectory “TrueImage”.

Working from memory I'd pretty sure build 2302 did not have the problem of showing the incorrect subdirectory above.

From other Windows and unix systems I can check and see that the complete path I show above is correct.

Note: this notebook has no floppy disk. Perhaps you can post/update the instructions for sending sysinfo.txt to use a USB key instead?

 

Hello jamesv,

Thank you for choosing Acronis Disk Backup Software.

First of all, please boot your laptop from Bootable Rescue CD created using build (2302) of Acronis True Image 9.0 and see if the problem persists. If there is no problem restoring this particular image using Bootable Rescue CD created using build (2302) of Acronis True Image 9.0 then please do the following for both build 2302 Bootable Rescue CD and build 2337 Bootable Rescue CD (rename the files created to sysinfo_2303.txt, net_2302.txt and sysinfo_2337.txt, net_2337.txt accordingly). Otherwise (the problem persists with both CDs), please perform the actions described below for build 2337 Bootable Rescue CD only.

- Boot the computer from Acronis True Image 9.0 Bootable Rescue CD and press F11 key when the selection screen advising you to select either "Full", "Safe" or "Boot into Windows" option 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;

- Issue the following commands:

asamba dhcp -n
asamba masters

- Write down the output after each of the commands or use a digital camera to make a shots of the output screens;

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

cd tmp
mkdir mntdir
mount /devfs/floppy/0 mntdir
cat /proc/net/dev > mntdir/net.txt
sysinfo > mntdir/sysinfo.txt
umount mntdir

- If you do not have a floppy drive then please take a look at this previous post of mine explaining how to save the sysinfo.txt file to USB flash drive (the same applies to net.txt);

- Boot into Windows and collect the net.txt and sysinfo.txt files from the diskette or USB Flash Drive.

Please note that sometimes the sysinfo.txt file is not readable from under Windows. In this case please try entering the file name using capital letters (SYSINFO.TXT) or follow the instructions provided in this previous post of mine.

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 investigate the problem and try to provide you with the solution.

Thank you.
--
Alexey Popov

 

I cannot enter the bug report.

The bug report submission page requires "choose one of your registered products" but no choices are listed. When I try to register TI9 again that page says " Serial Number is already registered".

Build 2302 works fine. 2337 fails. I have both SYSINFO files.

 

Hello jamesv,

Please accept our apologies for the delay with the response.

Please submit a request for technical support using Ask a question before you purchase Acronis software link (does not require to have any products registered) or send a letter directly to support@acronis.com. Attach all the collected files and information to your request\letter along with your serial number and the link to this thread. We will investigate the problem and try to provide you with the solution as soon as possible.

Thank you.
--
Alexey Popov