New DD 10 Bootable Media ISO build 2239 problems
I've noticed two new problems with the build 2239 ISO of the Product Native Bootable Media for Disk Director 10. Both of these problems occur when booted to the recovery media:
1. The Disk Editor does not work. If you launch it, DD 10 locks up and the PC reboots a few seconds later. This occurs no matter how the editor is launched; either by right-clicking on a disk or partition and choosing "Edit", or by choosing a link in the Advanced navigation pane. The previous ISO for build 2160 that was posted a couple of months ago works fine.
2. The mount point for my Linux home partition is incorrect. I have a separate /home partition, and if I choose "Explore" for this partition I do not see the files in /home. Instead, I see the file structure of the RAMDISK (/bin, /dev, /devfs, /etc, /lib, /mnt, /proc, /sbin, /tmp, and /var). My home partition can be found in the above file structure by navigating to /mnt/volume_7r5cD9.
If you have Build 2160 installed in Windows and you use Bootable Media Builder to create an ISO, and you boot from it, the /home partition is mounted correctly. In other words, if I click on the /home partition and choose "Explore", the explorer dialog opens up directly to /home.
This problem was also present in the prior ISO based on Isolinux for build 2160, but I never reported it.
Problem #1 is fairly serious; it rules out use of the Disk Editor in the boot environment. I have not installed the Windows build 2239 to see if the same problem exists there.
Sort of hijacking your thread, I've raised a ticket on the non installation problem on W7.
What is interesting is a new service has been installed that I don't recall before and it isn't deleted when DD10 is uninstalled. Namely Acronis OSS Reinstall Service.
Even though it isn't started it won't allow itself to be deleted even via an Admin Command window
sc delete oss_reinstall_svc.exe does nothing.
The OSS Reinstall Service has been around for a long time. As far as I know, it gets installed when DD is installed even if you're not using OSS.
...Acronis OSS Reinstall Service. Even though it isn't started it won't allow itself to be deleted even via an Admin Command window sc delete oss_reinstall_svc.exe does nothing.
Colin:
Funny, that's how I've deleted the service in all previous installations of DD 10, after first stopping the service and after removing its startup command from the registry. Check HKLM\Software\Microsoft\Windows\Current Version\Run or, if x64, check the similar path in HKLM\Software\Wow6432Node.
I only run DD now from the boot environment, so I'm not positive of the name of the service. So before issuing your command, open the Services console and look for the service, open its property page, and check the exact name. You should be able to kill it.
Mark,
I haven't run any extensive tests, but some quick tests in VPC 2007 SP1 using the downloaded ISO confirm the reboot problem with the Disk Editor. I also get a reboot if I select a partition, select Properties and then click on Statistic (all partitions were NTFS).
Paul:
Thanks for confirming. If VPC 2007 won't open the editor, chances are that nobody's physical harware will either.
I checksum (batch MD5 program) my archived files and recently noticed that on my Acronis registered products page that the Disk Director ISO from the new bootable media tabs (on that webpage) are of the same build!
Both V2160 and V2239 are one of the same if you Download the ISO seperately. I'm assuming that the only changes between V2160 & V2239 are between the windows version and not the bootable ISO's.
If you check the bootable Versions Build in program you'll notice it still says V2160. I haven't though tried creating Rescue/bootable media from the DD10 windows side of things, just incase it's different.
Then again if there is a different DD10 ISO ie a true V2239 then Acronis may not of updated their website accordingly.
I'll try another download of the V2239 ISO bootable and see if Acronis have uploaded another version and infact there was a mistake.
But in the meantime it would be good if you could check the DD10 Bootable Versions Build number within the program and see if it as I've found says Build 2160.
MD5 for DD10 ISO (versions 2160 & 2239), BOTH = b6be70b623ed05a13e9189c3a51d6548
EDIT: Looks like a NEW file has been uploaded as I'm now getting a new MD5 but as yet haven't created a new boot/rescue disc and checked the build version within the program. Be interesting to see if you are infact using the older version rather than the new.
Vorlon:
I just downloaded and tested the ISO for DD10 build 2239 again. The Help/About menu displays the build number as 2239. However, the problem with the editor remains. Starting the Disk Editor locks up the program and the PC reboots a few seconds later.
Kolo,
I've burnt that new DD10 ISO and it is indeed version 2239. The only problem with the ISO downloads is that the version number isn't indicated in the file name as the main program is. So there may be others out there that haven't looked at the version info within the DD10 rescue disk and are in fact using version 2160, as it does appear acronis initially uploaded the old version on the new release.
Are you in AHCI and/or Raid mode?
I'm assuming as it seems this version has a different bootloader that it runs in FULL mode and maybe you need to run DD in safe mode as per the earlier builds.
Is this happening with versions 2160 & 2239? or does it happen with previous versions too?
Vorlon:
The problem with the PC rebooting after starting the Disk Editor only happens with build 2239. The previous builds work correctly.
I have tested build 2239 ISO on a PC using AHCI, on one running in standard IDE mode, and on a virtual machine. All exhibit the reboot problem when opening the Disk Editor module in DD.
Just for the sake of clarity, the program loads and opens correctly to the graphical user interface. Most of the features work correctly, but if you start the hex Disk Editor module the program crashes and the PC reboots.
Do you see this issue also?
Hi Kolo,
Yes! I've just tried the ISO version of DD10 build 2239 on my laptop and as soon as I actually click on the "Edit" button/link for the selected drive, Disk director 10 will immediately reboot the laptop.
It is not as though it reboots into another mode, or another utility/screen etc, It just simply reboots the laptop and if the DD10 disk is still in the drive, it just starts DD10 up in the normal way.
So yes, it seems there are problems with the EDIT function on this build and so far testing with my Laptop Indicates that the EDIT function is NOT usable.
My basic laptop specs are:
Intel T2080 CPU
2GB DDR667 Ram
Intel ICH7
Sata HD
Bios in standard native mode ie Not ahci/raid.
Hello all,
Thank you for using Acronis Disk Director Suite 10.0
I have submitted a request to our QA Team. We will try to reproduce the issue.
Thank you.
I have not been able to get to the problems reported in this thread. My experience with the latest ISO bootable image is that it boots, but the display remains blank. This makes the product unusable for me.
This is on a Thinkpad W500 with high resolution video -- up to 1920x1200. In contrast, the ISO bootabe image for the Backup and Recovery 10 product handles the display correctly and functions correctly on the same hardware.
Hello Robert,
We can check the screen resolution issue in the following way:
Please create Acronis Bootable Rescue Media by means of Acronis Media Builder. This CD is based on Acronis Loader, it can set the proper video resolution automatically. If you want to use ISOLINUX CD, please see this article on how to set the desired resolution manually.
Use this code for screen resolution: 0x31A
Also please try this code: 0x322
These codes will allow to set the nearest to 1920x1200 value.
Please let us know the results.
Thank you.
Regarding this service:-
"C:\Program Files\Acronis\DiskDirector\OSS\reinstall_svc.exe"
I have just upgraded DD to 2011 on XP SP3 .
This service runs automatically, and is described in Win Services as "Required for Acronis OS Selector reactivation".
I don't plan to use the OSS Selector on this machine, but may on another if I install Ubuntu with Win 7.
Can I therefore:-
- stop the service without penalty?
- set it to manual or Disabled instead of Automatic?
I ask because it is quite an overhead on this machine.
Peter
Peter:
Yes, you can disable the OS Selector reinstall service. You can also delete it if you would like. Stop the service then go to a command prompt and type:
sc delete "OS Selector"