NAS not recognised by rescue CD/DVD
I bought and installed a Synology NAS (DS220j) some time ago. The NAS (which is the only network drive) is connected (by Ethernet) to a router (RT-N66U) which forms the heart of a small wired home network consisting of two DELL desktop PCs (Windows 11) and a Brother laser printer.
Trueimage 2020 is set up on the two PCs to make weekly incremental backups to the NAS. Everything appears to work fine for backups, but I have recently discovered that the NAS is not recognised by TI rescue CD/DVD media, which makes the whole exercise of backing up pointless if one of the PCs no longer boots.
I have tried creating bootable CDs and DVDs, both WinPE and Linux. They boot into rescue TI just fine and recognise all non-network drives, but not the NAS. I have tried this on both PCs on the LAN, with the same results. Windows and TI when run inside Windows recognise the NAS as a network drive.
Apart from the non-recognition of the NAS, the only anomaly I have seen is that the CMD window in WinPE does not accept commands: it blocks on the line below the launch of the TI .exe without a prompt for a new command. So I can't use ipconfig or ping to check network connectivity as suggested by some posts. However, the "Network options" window suggests that the network itself is seen, since it gives the correct IPs for both the PC and the router.
I don't know if it is relevant, but there are two sub-networks, the one referred to above, which has IPs 128.168.2.xxx, and a second, consisting solely of an internet box, 192.168.1.1. I set this up years ago to increase isolation between the PC LAN and the outside world.
Any suggestions?
Apart from the non-recognition of the NAS, the only anomaly I have seen is that the CMD window in WinPE does not accept commands: it blocks on the line below the launch of the TI .exe without a prompt for a new command. So I can't use ipconfig or ping to check network connectivity as suggested by some posts. However, the "Network options" window suggests that the network itself is seen, since it gives the correct IPs for both the PC and the router.
The above is correct operation and you need to close the launched Acronis application window if you want to use the CMD window, then copy and re-execute the launch command afterwards.
The rescue media environment has no DNS server so you need to address your NAS using the IP address instead.
See the following data captured from my own system booted from the ATI 2021 Simple rescue media with an encrypted drive connected.
X:\windows\system32>wpeinit
X:\windows\system32>"X:\Program Files\Acronis\TrueImageHome\trueimage_starter.exe"
Terminate batch job (Y/N)? nX:\windows\system32>manage-bde -status
BitLocker Drive Encryption: Configuration Tool version 10.0.19041
Copyright (C) 2013 Microsoft Corporation. All rights reserved.....
X:\windows\system32>"X:\Program Files\Acronis\TrueImageHome\trueimage_starter.exe"
X:\windows\system32>
The alternative approach is to create custom WinPE rescue media using the MVP Assistant Version 2.6.3 is available. tool which has a desktop type environment from which you can launch a variety of tools including a new command prompt and file explorer window etc.
I discovered that I could access the NAS using the file name \\ds220j\. I haven't actually tried launching a recovery, but all the steps up to that point seem to work, so all is okay.
Thanks for your replies.
Julian Scott wrote:I discovered that I could access the NAS using the file name \\ds220j\. I haven't actually tried launching a recovery, but all the steps up to that point seem to work, so all is okay.
Thanks for your replies.
Hello Julian.
Thanks for updating the thread.
I am glad the issue is resolved and you managed to access the NAS.
I wish you a nice day in advance!