my NAS is not detected when using bootable media
Hi,
I have a problem to access to my Nas*, when I try to use Bootable media/Acronis Startup Recovery Manager. It is a USB flash drive created from ATI 2014; my NAS is never detected.
Nas Connection section is empty, as in the Near Computers section: no way to restore a backup directly from my nas.
When I enter the address \192.168.168.1.20 (IP of my NAS), I don't have any more results (ok button is greyed out).
Clicking on Network Options button show properties of Network adapter; unfortunately IP start with 169.254 and not with 192.168.x.xxx :
EDIT 18h27 : In order to use WinPE-based media, I burned a CD as Bootable media/ ̶A̶c̶r̶o̶n̶i̶s̶ ̶S̶t̶a̶r̶t̶u̶p̶ ̶R̶e̶c̶o̶v̶e̶r̶y̶ ̶M̶a̶n̶a̶g̶e̶r̶ from ATI 2018
Result is not better; Nas Connection section & Near Computers section are empty and network card is not listed (empty) :
Then, if I switch to black command-line window behind Acronis True Image, I'm not able to type ipconfig /all because keyboard doesn't respond when typing anything. Ctrl +C cannot abort trueimage_starter.exe processes; nothing else than a blinking cursor on the screen
Of course, I don't have any problems under Windows to make a Backup of the complete system. The Nas is correctly detected. All folders are public shared (no credentials).
* my NAS is a Tandberg device, BizNAS D400 model
I hope you can help
Thanks


- Log in to post comments

Steve, thanks for answering.
I want to add this clarification first.
1) Under windows, my Nas does not appear in the Nas Connections section; I must use the Network section under which I see the PCs of my small local network as well as my NAS.
2) Tandberg Data's technical support suggests to me that the problem would be more on the side of Acronis; I quote them:
I think the issue is more likely Acronis Recovery Manager, either it doesn’t support NAS kernel version that is currently installed.
The link you mention is only troubleshooting Network issue but since you can access and backup to the NAS direct from a windows system we can rule out the network issue and maybe you might want to check with Acronis if there's anything needs to be done manually on the NAS. I never try such operation but I'll check if I can reproduce if the Acronis Recovery Manager is free.
I therefore confirm that I have a functional local area network fully equipped with ethernet cables (no wifi) that I use daily with my NAS under Windows. Backups Under Windows via Acronis are normally done through this network organized in a star-shaped network around a router.
Last thing: the 3 PCs on my local network are all unable to find my NAS from the Acronis rescue media on a USB key.
- Log in to post comments

Franck, if you are using the Acronis Startup Recovery Manager (ASRM), then this is typically based on a Linux kernel (or was in the versions when I used it!) and may not have support for your particular network adapter.
I have not used ASRM for some years for a variety of reasons! My own preference is to create the bootable Acronis Rescue Media on a USB stick and using WinPE as the boot OS. I use the MVP Custom ATIPE Builder tool to create the USB media and this works fine with my own network and NAS.
See the attached zip file which contains a short slideshow (.scr) file with images from my WinPE rescue media connecting to my NAS. Note: I am using ATI 2019 with the rescue media.
Attachment | Size |
---|---|
483361-161750.zip | 1.22 MB |
- Log in to post comments

Maybe I've been confused.*
Just like you, I only use bootable Acronis Rescue Media on a USB stick and not the ASRM system (F11)
Thank you for the slideshow detailing all the steps. I'm following exactly the same steps as you are.
Question: After entering the IP of my NAS \\192.168.1.20, what am I supposed to do? Type 'enter' or click OK (but the button remains greyed out)?
For me, one and the other fail. Nothing is happening.
Why? Probably because of the Ip address of the network adapter which starts with 169.254 instead of 192.168.x.xx
I'm trying to find a solution so that Tandberg NAS and Acronis can work together. Not easy job.
* my very first message has been edited
- Log in to post comments

Franck, if you are still getting an IP address starting 169.254 then you have no network connection as this is a fail address when there is no other allocated by DHCP.
You said in your first post: " It is a USB flash drive created from ATI 2014 " - but you are posting here in the ATI 2018 forum, so I would strongly recommend creating a new USB rescue media stick using ATI 2018 instead.
I do not believe there is an issue here with your NAS, but rather one with the USB media being used.
See KB 60820: Acronis True Image 2018: how to create bootable media - and KB 60091: Acronis True Image 2018: how Simple bootable media creation mode works
- Log in to post comments

Steve, you're right, I mentioned the usb stick created under ATI 2014.
But then I burned a bootable rescue media CD using ATI 2018 (see my first post EDIT : 18H27 in bold); that's why I posted here in the ATI 2018 forum. Of course a bootable CD rescue media is not exactly as reliable as an USB rescue media stick, but I got a message of success from burning the CD).
So to be perfectly clear, the result with a CD rescue media using ATI 2018 is worse than with an USB rescue media stick using ATI 2014 since my network adapter is not detected at all.
Tomorrow I will do the test again using this time not a bootable CD, but a USB stick created with ATI 2018.
I apologize for my poor english.
- Log in to post comments

Franck, I would recommend giving the MVP Custom ATIPE Builder tool a try for making your USB stick - this has the ability to inject device drivers from your computer into the WinPE media, along with many other features including a network manager tool. This is the tool I used for my earlier screen capture slideshow file.
Please do not apologise for your english! It is 100% better than my own attempts at any other language. I rely very much on using Google Translate or similar tools.
- Log in to post comments

Franck, I would recommend giving the MVP Custom ATIPE Builder tool a try for making your USB stick
Steve, I'm not sure where I can find it :(
Following this link https://kb.acronis.com/node/60820 I built this morning a new bootable key with ATI 2018 that I tested on my laptop and then on my desktop:
Method for building rescue media : I choosed the ADVANCED creation method for WinPE-based media to install 2 elements of the toolbox [Deployment Tools & Windows Preinstallation Environment (Windows PE)] in order to have a better chance to make work more efficiently the network adapter giving access to the wired local network.
Result is unfortunately the same: clicking on "Network options" shows an empty window
I haven't seen any differences between this new usb stick and the former CD bootable media; I also understood that I just had to close the acronis window (red cross) to kill the process that prevented me from having control on the command prompt.
So I have tested ipconfig /all and then 2 ping tests :
ipconfig /all: good news, network adapter is recognized, but bad news, 169.254 is back again
ping \\192.168.1.20 -w 10 [IP adress of BizNAS]
ping \\192.168.1.1 -w 10 [IP adress of my router]
Both test failed with 100% errors (screenshots)
I also tested with another ethernet cable without success.
Now I feel really stuck.
- Log in to post comments

Franck, there is a link to the MVP Custom ATIPE Builder tool in my signature - the advantage of this tool is that you can capture and inject device drivers from your computer which can include those needed for your network adapter.
See also forum topic: MVP Tool - CUSTOM ATI WINPE BUILDER
- Log in to post comments