TeraByte Product Release Thread

Hello,

TeraByte Drive Image Backup and Restore Suite version 3.45 has been released.
Webpage - Downloads - TeraByte Unlimited User Community Forums

Image for Windows 3.45 - Downloads - Upgrade History

Image for DOS version 3.45 - Downloads - Upgrade History

Image for Linux version 3.45 - Downloads - Upgrade History

OSD Tool Suite version 2.04 - Downloads - Upgrade History

Note: At the time of this posting, the "Upgrade History" pages had not yet been updated. I will edit this post with that information once it becomes available.
Edited to add "Upgrade History".

 

Hello,

A new version of the TeraByte BootIt Collection (versions 1.72/1.24) has been released:

BootIt Bare Metal version 1.72 - Downloads - Upgrade History

BootIt UEFI version 1.24 - Downloads - Upgrade History

Note: At the time of this posting, the "Upgrade History" pages had not yet been updated. I will edit this post with that information once it becomes available.
Edited to add "Upgrade History".

 

Hello,

TeraByte Drive Image Backup and Restore Suite version 3.46 has been released.
Webpage - Downloads - TeraByte Unlimited User Community Forums

Image for Windows 3.46 - Downloads - Upgrade History

Image for DOS version 3.46 - Downloads - Upgrade History

Image for Linux version 3.46 - Downloads - Upgrade History

OSD Tool Suite version 2.04 - Downloads - Upgrade History
No new version released. Current Version is 2.04 released on June 18, 2021.

 

Hello,

A new version of the TeraByte BootIt Collection (versions 1.73/1.25) has been released:

BootIt Bare Metal version 1.73 - Downloads - Upgrade History

BootIt UEFI version 1.25 - Downloads - Upgrade History

 

Hello,

TeraByte Drive Image Backup and Restore Suite version 3.47 has been released.
Webpage - Downloads - TeraByte Unlimited User Community Forums

Image for Windows 3.47 - Downloads - Upgrade History

Image for DOS version 3.47 - Downloads - Upgrade History

Image for Linux version 3.47 - Downloads - Upgrade History

OSD Tool Suite version 2.05 - Downloads - Upgrade History

 

A new version of the TeraByte BootIt Collection (versions BIBM 1.74 - BIU 1.26) has been released:

BootIt Bare Metal version 1.74 - Downloads - Upgrade History

BootIt UEFI version 1.26 - Downloads - Upgrade History

 

A new version of the TeraByte BootIt Collection (versions BIBM 1.75 - BIU 1.27) has been released:

BootIt Bare Metal version 1.75 - Downloads - Upgrade History

BootIt UEFI version 1.27 - Downloads - Upgrade History

 

Hello,

TeraByte OSD Tool Suite version 2.06 has been released.
OSD Tool Suite version 2.06 - Downloads - Upgrade History

 

Hello,

A new version of the TeraByte BootIt Collection (versions BIBM 1.76 - BIU 1.28) has been released:

BootIt Bare Metal version 1.76 - Downloads - Upgrade History

BootIt UEFI version 1.28 - Downloads - Upgrade History

 

Hello,

TeraByte Drive Image Backup and Restore Suite version 3.48 has been released.
Webpage - Downloads - TeraByte Unlimited User Community Forums

Image for Windows 3.48 - Downloads - Upgrade History

Image for DOS version 3.48 - Downloads - Upgrade History

Image for Linux version 3.48 - Downloads - Upgrade History

OSD Tool Suite version 2.07 - Downloads - Upgrade History

 

I recommended Terabyte to a friend and he recently bought the license and today installed it on his new computer. He tells me that installation went fine, license applied, image done and he then created a UFD rescue stick. He wants to use the software to put the image of his new pc on a larger SSD disk as his new computer / SSD disk is too small. He booted up with the rescue stick, could see the image to use from the external drive but apparently when asked what the destination should be, the new larger SSD disk was not detected. Is there a step that he is missing regarding formatting / initialising the new drive so that it can be detected by the rescue stick? I am not sure if he used simple/automatic or normal restore but can ask him later, not that I can see in my own pc that this would make a difference. I am getting this question in both flavours.

 

beethoven,

Initialisation of the SSD isn't required. Which boot disk is he using? Can he see the new SSD in the BIOS and in Windows Disk Management?

 

Hi Brian, thank you. Please see attached three screenshots he forwarded to me showing the partitions from within the recovery environment (Rec1), the Live Environment (Live 1) and Disk Manager. As you can see in the recovery environment only the Stick and the external drive with the image are shown.

 

The SSD isn't seen? Check the cable and use a different SATA port on the MB.

Can the SSD be seen in the BIOS? Is it enabled?

 

Sorry, Brian - my friend was impatient and decided to reinstall Windows. As it was a fresh pc anyway with only windows, that's ok though of course now he has to wait for the updates to go through. He suspected that it was some kind of driver issue
but I guess it's moot now. I would think that if the rescue disk is done on the same pc than the recovery, drivers should not be an issue. Not sure about the cable and port option - he is normally very familiar with hardware issues (much more so than I am) and told me he had gone through the boot up in recovery mode more than once, each time with the same outcome.

 

Could you see his SSD on the above screenshots?

 

If I am not mistaken then Disk 1/ E in the live and disk manager screenshots indicate the new drive. Disk 2 / F is the backup drive holding the image. The Rec1 shot from the Rescue Environment only showed the Rescue Stick and the backup drive.

 

Ahh, I was looking for a blank disk. His mistake was the creation of a MBR partition. He should have left the disk blank. And done an entire drive backup/restore.

 

Sorry, I can't follow you - I don't think he created anything. He started with a blank disk and wanted to put the image onto it from a new pc (purely for the reason that the source disk is too small). I was not there when he did either the imaging or restore process but I think he did not use any special options when going through the process to choose the destination. The destination disk just was not available.

 

I don't follow it either. Disk Management and IFW shows a 465.76 MB MBR partition. Labelled "New Volume". He would have created this partition as the disk should be blank when bought. Unless someone else had the SSD before him.

It's a pity he installed Windows on this disk before we were able to ask a few questions.

 

you are correct and the fact that I am not an expert but have to relay the info probably does not help either
I just asked him about the partition and he told me he initialized this via windows disk manager adjusting it to max size after the first attempts to "see" the partition in the recovery mode failed. So you are correct that he already worked on this.
He also stressed again that the pc is a high performance HP model with a storage controller providing for raid. While he is not using raid, he suspects that for that a driver is required which is not included in the recovery environment. Apparently he also
used the copy function via a live session and while this finished successful , the bootup after swapping the drives did not work afterwards (BSOD) same as when he tried a restore from an image. When he gave up and decided to reinstall a fresh windows, Windows also had an initial hickup advising of a missing driver but asked him does he want to include this and after doing so, it continued. So maybe this is the problem. I suspect with more patience we , ie you could have worked out a proper way to do this. He says he might bring the pc (ie an identical) over to my place over the weekend and we can still do some simulation/testing.

 

Check his BIOS settings. Is the SATA controller in RAID or AHCI mode. Some Dell computers boot in RAID mode (but aren't using RAID) and can't see NVMe drives in IFL. You have to change the controller mode temporarily to AHCI to see the drives. From memory, these computers don't have issues with TBWinRE.
Mysterious. Neither of his internal drives were seen in his TBWinRE. Is he using standard SSDs or NVMe?

So, check the BIOS. In TBWinRE, try a backup. Can you see the internal drives?
In IFL, try a backup. Can you see the internal drives? You can abort the backup if the internal drives are visible.

Try IFU as well.

Edit... Was the TBWinRE UFD built in that computer?

 

Brian, we went back to the start, using an identical pc , creating a rescue stick and again cannot see the empty disk that should be destination of the source.
I checked the disk management of the live system and note that the attached screenshot does ask for initialization of the disk. I am not sure what was done on the earlier pc but this time I am waiting for your suggestion, especially as you indicated he should not have made an mbr partition. So should I initialise with GPT or do something completely different?
Checking on the other questions now.

 

Mystery solved - it was indeed a missing driver issue - using tools in the recovery mode I added a driver and once I had done that the internal drives showed up. Since we don't need to install the image anymore, we stopped there. Still for my understanding why is HD3 (the actual drive in the computer) is GPT and the blank disk for restoring the image MBR?

 

Nice work. Which driver was missing? Was it NVMe?

The new SSD is blank and even though it has no MBR sector data it still is called a MBR disk. The Windows OS is installed in UEFI mode on a GPT disk. HD0 in Disk Manager shows 3 partitions but there are really 4 partitions. The MSR doesn't appear in Disk Management.

So the sequence for image/ restore....
Create an entire drive image of Disk 0 (the smaller SSD)
Remove Disk 0 and install the new SSD
Boot Media
Do an entire drive restore to the empty SSD and use the Scale to Fit option. This will expand the OS partition but not the 3 small partitions.

The new SSD will now be a GPT disk as it is a clone of the smaller SSD.