Norton Ghost 15 / Symantec System Recover 2013 SRD problem

KnauthR · December 5, 2013, 1:12am

Hi everybody,

until now I could not find a similar problem description ... therefore here is my issue:

My config:

Board: Asus P8P67 Deluxe with newest BIOS version: 3602

Bootdisk: 1x Vertex4 SSD (120GB)

Datadisks: 2x Seagate ST4000DM000 (4TB) as Raid1 on onboard intel P67 express chipset (SATA RAID-Mode)

OS: Windows 7 x64 Ultimate (german)

On my working machine I upgraded my Data-Raid1 with these two 4TB disks (Seagate ST4000DM000) initialized as GPT disk(s) and now it's not possible to acces the created partitions on the disk via SRD for backup or restore! In windows the disks are working perfectly.

But if I boot the SRD (CD or custom copy on HDD) the layout of the 4TB disks is not seen if I select backup a disk or try to restore to a partition on the 4TB disk. Even Microsofts diskpart shows me a capacity of only 1678GB and sees no partitions on it.

But if I boot in SRD I can use the included browser to browse/read/write in volumes on the 4TB disk - in this application everything is shown like in windows.

ONLY with backup/restore function the layout is not correct - if I allocate smaller partitions (lower the 2TB) on the 4 TB disk(s) then these partitions are accessable (but shown all over capacity is 1678GB too)!

What did I try?

- booting Norton Ghost 15 SRD: failure

- booting custom Norton 15 SRD (from HDD with Intel RST drivers v11.2.0.1006 included): failure

- booting custom Norton 15 SRD (from HDD with Intel RST drivers v12.8.6.1000 included): failure

- booting Symantec System Recover 2013 SRD (64bit): failure

- booting Symantec System Recover 2013 SRD (64bit with Intel RST x64 drivers v12.8.6.1000 loaded): failure

- booting in UEFI-Mode in Symantec System Recover 2013 SRD (64bit with Intel RST x64 drivers v12.8.6.1000 loaded): failure

- all above with 2 disks as Raid 1 or just one disk as non-RAID disk: failure

- GParted boot disk could access/read partitions without any problems

- Seagate DiscWizard (Acronis) could backup/restore without any problems (but it is working on a linux)

Where is the problem?

1. ASUS: too old firmware for intel controller on board?

2. SYMANTEC: incorrect SRDs for GPT support?

3. MICROSOFT: incorrect implementing of GPT in PXE boot image?

I added a screenshot from disk layout in Windows.

If use SMEDump in failure case it shows same errors for the layout of both 4TB disk(s) - I added the extract for these disks in attachment file:

(under windows this dump is without failures)

######################################

* 2013-12-01T15:06:45.4563674Z Main Thread(696) Context: SME : INFO
RegionFactory.cpp(90) Function: RegionFactory::Instantiate
Region for SME~Computer~Sg6F9B8B30~M6F9B8B30 is SME~Computer~Sg6F9B8B30~M6F9B8B30~M6F9B8B30Region-0

* 2013-12-01T15:06:45.4791275Z Main Thread(696)
Device constructor: unique id: Sg0001FDAF name: \\.\PhysicalDrive2

* 2013-12-01T15:06:45.4794037Z Main Thread(696) Context: DEVICE : INFO
WindowsDevice.cpp(1196) Function: WindowsDevice::CheckKernelDeviceName
The kernel device name for \\.\PhysicalDrive2 is \Device\Harddisk2\DR2.

* 2013-12-01T15:06:45.4791557Z Main Thread(696) Context: DEVICE : INFO
WindowsDevice.cpp(771) Function: WindowsDevice::GetDeviceCharacteristics

----------------------------- Entering GetDeviceCharacteristics(v1.5) ------------------------------
GetDriveGeometry succeeded for \\.\PhysicalDrive2. Cyls: 219051 Hds: 255 Scts: 63 BPS: 512.
Media Type: Fixed.
Bus Type: RAID.
Calling DeviceIoControl(IOCTL_DISK_GET_PARTITION_INFO).
IOCTL_DISK_GET_PARTITION_INFO returned 3519069872 sector(s).
maxSectorCount is now 3519069872 sector(s).
Calling DeviceIoControl (IOCTL_SCSI_GET_ADDRESS).
Found serial number from calling GetSmartDriveData&colon; W300EM3A.
Location: IDE Primary Slave.
Calling CanChangeDeviceAddressableSectors.
Model Name: ST4000DM000-1F2168 of device \\.\PhysicalDrive2.
The NT Drive Signature for \\.\PhysicalDrive2 is 130479.
Creating a media for \\.\PhysicalDrive2, with 130479 as the NT Drive Signature.
--------------------------------- Leaving GetDeviceCharacteristics ---------------------------------

* 2013-12-01T15:06:45.9815127Z Main Thread(696) Context: DEVICE : INFO
WindowsDevice.cpp(2980) Function: WindowsDevice::CheckGoBackEnabled
GoBack is not active on device \\.\PhysicalDrive2

* 2013-12-01T15:06:46.0132710Z Main Thread(696)     Context: SME : INFO
MbrRegion.cpp(3939)   Function: MbrRegion::GetDriveLayout
After Direct GetDriveLayout
Disk                 : 2
Sector               : 0
NT Signature         : 0001FDAF
# Type Boot SCyl SHead SSector ECyl EHead ESector Sector Before Sector Count
- ---- ---- ------------------ ------------------ ------------- ------------
0   EE   00     0     0       2 1023   255      63              1    4294967295
1   00   00     0     0       0     0     0       0              0             0
2   00   00     0     0       0     0     0       0              0             0
3   00   00     0     0       0     0     0       0              0             0

* 2013-12-01T15:06:46.0134283Z Main Thread(696)     Context: SME : INFO
WindowsDriveLayout.cpp(183)   Function: WindowsComputer::GetDriveLayout
After GetDriveLayout
DriveLayout for drive: A4D37FB6
PartitionStyle       : GPT
PartitionCount       : 10
DiskId               : a4d37fb6-5630-19e3-b245-806e6f6e6963
StartingUsableOffset : 4400
UsableLength         : 1A3817CDA00
MaxPartitionCount    : 80

Part StartingOffset    PartitionLength            PartitionTypeGuid                   UniquePartitionGuid             Attributes                Name
---- ----------------- ------------------ ------------------------------------ ------------------------------------ ---------------- ----------------------------
   1              4400            8000000 e3c9e316-0b5c-4db8-817d-f92df00215ae a4d37fb7-5630-19e3-b245-806e6f6e6963                0 Microsoft reserved partition
   2           8100000         2580100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fb8-5630-19e3-b245-806e6f6e6963                0 Basic data partition
   3        2588200000         7D00100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fb9-5630-19e3-b245-806e6f6e6963 8000000000000000 Basic data partition
   4        A288300000         1900100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fba-5630-19e3-b245-806e6f6e6963                0 Basic data partition
   5        BB88400000         7D00100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fbb-5630-19e3-b245-806e6f6e6963                0 Basic data partition
   6       13888500000          C80100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fbc-5630-19e3-b245-806e6f6e6963                0 Basic data partition
   7       14508600000         4B00100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fbd-5630-19e3-b245-806e6f6e6963                0 Basic data partition
   8       19008700000         3200100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fbe-5630-19e3-b245-806e6f6e6963 8000000000000000 Basic data partition
   9       1C208800000         4B00100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fbf-5630-19e3-b245-806e6f6e6963 8000000000000000 Basic data partition
10       20D08900000        19678A00000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fc0-5630-19e3-b245-806e6f6e6963 8000000000000000 Basic data partition

* 2013-12-01T15:06:46.0139542Z Main Thread(696) Context: RESULT_CLASS : RESULT
Argument.cpp(204) Function: Argument::Argument
Error SME_GPT_PARTITION_ENDS_BEFORE_START (E0BB004E): The GPT partition's ending value is less than its starting value.
(UMI:V-*-187-78)

* 2013-12-01T15:06:46.0159329Z Main Thread(696) Context: RESULT_CLASS : RESULT
GptRegion.cpp(714) Function: GptRegion::ValidatePartitions
e0bb004c
1: Error E0BB004E: The GPT partition's ending value is less than its starting value.
Error SME_GPT_PARTITION_INVALID (E0BB004C): The GPT partition is invalid.
Error SME_GPT_PARTITION_ENDS_BEFORE_START (E0BB004E): The GPT partition's ending value is less than its starting value.
(UMI:V-*-187-76)

* 2013-12-01T15:06:46.0171826Z Main Thread(696)     Context: SME : INFO
MbrRegion.cpp(3939)   Function: MbrRegion::GetDriveLayout
After Direct GetDriveLayout
Disk                 : 2
Sector               : 0
NT Signature         : 0001FDAF
# Type Boot SCyl SHead SSector ECyl EHead ESector Sector Before Sector Count
- ---- ---- ------------------ ------------------ ------------- ------------
0   EE   00     0     0       2 1023   255      63              1    4294967295
1   00   00     0     0       0     0     0       0              0             0
2   00   00     0     0       0     0     0       0              0             0
3   00   00     0     0       0     0     0       0              0             0

* 2013-12-01T15:06:46.0181216Z Main Thread(696) Context: RESULT_CLASS : RESULT
Argument.cpp(204) Function: Argument::Argument
Error SME_GPT_PARTITION_ENDS_BEFORE_START (E0BB004E): The GPT partition's ending value is less than its starting value.
(UMI:V-*-187-78)

* 2013-12-01T15:06:46.0191901Z Main Thread(696) Context: RESULT_CLASS : RESULT
GptRegion.cpp(714) Function: GptRegion::ValidatePartitions
e0bb004c
1: Error E0BB004E: The GPT partition's ending value is less than its starting value.
Error SME_GPT_PARTITION_INVALID (E0BB004C): The GPT partition is invalid.
Error SME_GPT_PARTITION_ENDS_BEFORE_START (E0BB004E): The GPT partition's ending value is less than its starting value.
(UMI:V-*-187-76)

* 2013-12-01T15:06:46.0204641Z Main Thread(696)     Context: SME : INFO
MbrRegion.cpp(3939)   Function: MbrRegion::GetDriveLayout
After Direct GetDriveLayout
Disk                 : 2
Sector               : 0
NT Signature         : 0001FDAF
# Type Boot SCyl SHead SSector ECyl EHead ESector Sector Before Sector Count
- ---- ---- ------------------ ------------------ ------------- ------------
0   EE   00     0     0       2 1023   255      63              1    4294967295
1   00   00     0     0       0     0     0       0              0             0
2   00   00     0     0       0     0     0       0              0             0
3   00   00     0     0       0     0     0       0              0             0

* 2013-12-01T15:06:46.0210124Z Main Thread(696)     Context: SME : INFO
WindowsDriveLayout.cpp(183)   Function: WindowsComputer::GetDriveLayout
After GetDriveLayout
DriveLayout for drive: A4D37FB6
PartitionStyle       : GPT
PartitionCount       : 10
DiskId               : a4d37fb6-5630-19e3-b245-806e6f6e6963
StartingUsableOffset : 4400
UsableLength         : 1A3817CDA00
MaxPartitionCount    : 80

Part StartingOffset    PartitionLength            PartitionTypeGuid                   UniquePartitionGuid             Attributes                Name
---- ----------------- ------------------ ------------------------------------ ------------------------------------ ---------------- ----------------------------
   1              4400            8000000 e3c9e316-0b5c-4db8-817d-f92df00215ae a4d37fb7-5630-19e3-b245-806e6f6e6963                0 Microsoft reserved partition
   2           8100000         2580100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fb8-5630-19e3-b245-806e6f6e6963                0 Basic data partition
   3        2588200000         7D00100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fb9-5630-19e3-b245-806e6f6e6963 8000000000000000 Basic data partition
   4        A288300000         1900100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fba-5630-19e3-b245-806e6f6e6963                0 Basic data partition
   5        BB88400000         7D00100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fbb-5630-19e3-b245-806e6f6e6963                0 Basic data partition
   6       13888500000          C80100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fbc-5630-19e3-b245-806e6f6e6963                0 Basic data partition
   7       14508600000         4B00100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fbd-5630-19e3-b245-806e6f6e6963                0 Basic data partition
   8       19008700000         3200100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fbe-5630-19e3-b245-806e6f6e6963 8000000000000000 Basic data partition
   9       1C208800000         4B00100000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fbf-5630-19e3-b245-806e6f6e6963 8000000000000000 Basic data partition
10       20D08900000        19678A00000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 a4d37fc0-5630-19e3-b245-806e6f6e6963 8000000000000000 Basic data partition

* 2013-12-01T15:06:46.0214672Z Main Thread(696) Context: RESULT_CLASS : RESULT
WindowsMbrRegion.cpp(269) Function: WindowsMbrRegion::GetDriveLayout
e0bb007f
1: 2
Error SME_ONDISK_LAYOUT_DOESNT_MATCH_OS (E0BB007F): The on-disk layout of disk 2 doesn't match the OS information.
(UMI:V-*-187-127)

* 2013-12-01T15:06:46.0224383Z Main Thread(696)     Context: SME : INFO
MbrRegion.cpp(3939)   Function: MbrRegion::GetDriveLayout
After Direct GetDriveLayout
Disk                 : 2
Sector               : 0
NT Signature         : 0001FDAF
# Type Boot SCyl SHead SSector ECyl EHead ESector Sector Before Sector Count
- ---- ---- ------------------ ------------------ ------------- ------------
0   EE   00     0     0       2 1023   255      63              1    4294967295
1   00   00     0     0       0     0     0       0              0             0
2   00   00     0     0       0     0     0       0              0             0
3   00   00     0     0       0     0     0       0              0             0

######################################

Maybe someone has an idea about this issue ... at the moment it is a bit tricky to backup/restore the data disk(s) (in worst case I need a working windows first) :(

Thanx Rene.

KnauthR · December 5, 2013, 7:41pm

Hi Brian,

like I wrote, I tested with added RST drivers:

booting custom Norton 15 SRD (from HDD with Intel RST drivers v11.2.0.1006 included): failure

booting custom Norton 15 SRD (from HDD with Intel RST drivers v12.8.6.1000 included): failure

booting Symantec System Recover 2013 SRD (64bit with Intel RST x64 drivers v12.8.6.1000 loaded): failure

booting in UEFI-Mode in Symantec System Recover 2013 SRD (64bit with Intel RST x64 drivers v12.8.6.1000 loaded): failure

I may test v10.5 too...

In custom SRD of NG 15 I integrated RST drivers in custom lightsout restore wizard and for SSR2013 SRD I integrated it on creation of custom SRD and after UEFI boot after starting the mSRD from menu point include drivers. All methods are showing same failure. In my windows installation I use RST v11.2.0.1006 (but this is x64). So I may try to create a SSR 2013 custom SSR with RST v11.2.0.1066 (x64) and your recommended v10.5 (x64) ...

I will tell you more results next ...

Thanx for the tip with RST - is this from intel website? I couldn't find any hint in this direction until now, but I was thinking about a controller (firmware/driver) issue too ...

Thank you until now,

Rene.

Brian_K · December 5, 2013, 7:56pm

Rene,

Apologies. I misread your section on the drivers. The issue certainly suggests the Intel RST drivers.

I saw that quote in this page....

http://www.terabyteunlimited.com/howto/tbwinre_tutorial.htm

DaveH · December 5, 2013, 9:17pm

I'm confused here.

Do you think all those partition problems are not real and are in that dump because the recovery disk may not have the right driver to view the disk properly?

Or do you think those errors really exist?

When you ran that dump and you said diskpart also shows the drive as the wrong size, was that from the recovery enviroment only or from within windows?

Dave

edit- I saw where you said "In windows the disks are working perfectly" but that does not necessarily mean the partition errors don't exist.

Does diskpart in windows give the correct size?

DaveH · December 5, 2013, 10:32pm

Just a thought, but when SSR 2013 was released it still had problems with GPT drives, expecially trying to recover windows installed as UEFI.

The problems were corrected in SP1 and a new recovery disk set was released.

I'm not sure if this will help but make sure you are using the recovery disk versions 2013_11.0.1.47662

The orginal version was 2013_11.0.0.46600, the 1 in the new version designates it as SP1.

Dave

KnauthR · December 6, 2013, 9:41pm

Hi Dave,

I'm confused of this effect at all too ...

Yes I think these are not really partition problems, because under the running (installed) windows everything is fine:

diskpart shows correct size and layout

disk management (MMC gui) shows correct size and layout

normal access/working with data on volumes is possible

All the effects are ONLY seen if any possible variant of booting SRD (original CD, custom CD, custom LightsOut Restore) is used AND ONLY if I try to access it with partition tools like diskpart or the backup/restore functionality from NG/SSR. And its unbelievable, but if I try to restore a partition I may search on all partitions of the 4TB disc (like I wrote in first message already) BUT AFTER selecting a backup file it is not possible to select an partition from this 4TB disk because its shown as 2TB disk without usable space ... really funny :(

OK, on weekend I will try to manipulate the used wim-Image from custom SRD directly with IRST driver, because using wizard to add it seems not to work and manually adding it manually after booting SRD even not.

Rene.

KnauthR · December 6, 2013, 9:42pm

Yes, I use the latest available SRD from SSR (v2013_11.0.1.47662).

DaveH · December 7, 2013, 7:01am

If you have SSR 2013 installed can you go into the programs utility folder and make another dump file from inside windows?

Click on "SeaST.exe" and then choose the bottom option "SME Dump Operations".

It will generate the same file you posted and attached above.

While you are in that folder also double click partinfo.exe

It will create a text file in that same folder called partinfo.txt

Attach both those text files and we can see if they are OK when run from windows.

Dave

edit- I'm sorry again, I missed the part you said "under windows the report has no errors"

I don't know whats wrong, I seem to be loosing my brain functions.

I sent a message to Andy to see if he knows anything about this discrepancy.

DaveH · December 10, 2013, 8:40pm

Rene,

Andy got back to me and he says that drives or partitions up to 16TB are supported so yours should be as well.

He did say that the 2013 SP1 recovery disk is required and has asked for more info.

The "snip" of the dump file you posted is not enough and they also want to see a partinfo.txt file to see what each operating system is reporting. (Your installed Windows 7 and the windows 8 PE version from the recovery disk)

Can you please attach the full dump file made from the SP1 recovery disk that shows all the errors?

Also post partinfo.txt files made from both inside of windows and from the SP1 recovery disk?

Thanks,

Dave

KnauthR · December 11, 2013, 1:13am

Hi Dave,

possibly I crashed my GPT disc structure now - because of testing (back and forth) with different configs of SRDs and so on.

First I thought I found a workaround, but it did the job not really good.

Because of Brians info about IRST version I tried to implement the v10.5 driver, but after booting SRD it's too late for adding it, because it will be needed during boot! So I tried to add this driver to boot.wim ... but NG15 uses a Vista RTM PXE image, so I needed the WAIK for Vista RTM and in this one there is just the old peimg for doing the job (adding drivers) normally ... but it was not working (each time error 0x800f0003). So I deciced to substitute the driver iastorV.sys (v6.2.0.1019) in boot.wim with the iastor.sys from IRST v10.5 - I renamed the newer driver to the old name. The same I did with the associated inf file.

So booting the SRD was fine and now diskpart was showing the correct capacity of the 4TB drive - check! :) But doing backup and restore was not working correctly. First I tried to backup a partition from 4TB disk and hey all partitions were shown. OK, fine so I stoped here and checked restore function, but after selecting and backup file (from a partition of $TB disk!) it was not possible to select and destination on the 4TB dic, because it was shown as 2TB and 1,68TB unspecific partition ... :(

So I did the partinfo, because I made some SMEDumps already last week and rebootet to windows.

Now something in windows was wrong too! :(

After first boot after doing SRD boot, NG15 show problems during dtecting disks and now I could NOT see the 4TB partitions inside NG15 restore/backup function (same like in SRD). I took a partinfo and a new SMEDump and rebootet again. Now NG15 could determine the disks correctly again, I took another partinfo ...

Hmm now are the GPT structure is bad on the disc - there are errors about bad backup LBA in a wrong GPT header ...

So at least I tried a reboot with GPartEd disc, but here I got error messages about bad header too and GPartEd couldn't open! :( Before weekend was running ...)

So I think the SRD smashed the structure ... that really **bleep**ty. Under windows all filesystems seems OK at the moment, but I have to repair it!!!

I attach some full SMEDumps here too. I think in actual situation it makes not really sense to do more dumps with SSR2013 SRD because of corrupted GPT structure.

How may fix the GPT problem? backup data and reinitialize?

At the end SSR2013 SRD is NOT OK for booting and testing, because here is iastor.sys v8.6.2.1019 included and therefore this was showing wrong partitioning of 4TB discs last week too ... :(

In NG15 utility folder I found a debug file (don't know what generates it), maybe this helps too ...

Rene.

KnauthR · December 11, 2013, 1:17am

... here some more SMEDump files from weekend and this debug file I found ...

DaveH · December 11, 2013, 2:21am

I'm not sure how to repair GPT partitions, I personally don't use them much except for the testing with SSR 2013 that lead to the problems being corrected in the SP 1.

Brian may know how, he uses BootitNG for his partition work and it's a very good tool for fixing partition problems.

I can confirm that the SSR 2013 SP1 recovery disk has the old driver.

The iaStorV.inf file says that it is 8.6.2.1022 but the iaStorV.sys file is as you mention, version 8.6.2.1019

I cant check the version from a Windows 8.1 64bit installation disk at the moment, I'm unable to open those wim files on the 32bit system I am using.

I loaned my good 84bit system to a friend with a broken computer and my 64bit test system is burried behind her system here that I took apart.

Although Ghost 15 claims to be able to support GPT data drives, I recall seeing some problems discussed here with drives larger than 2TB. I don't know if that was just because of the driver or if something else is causing it as well but I may not want to trust Ghost 15 on that drive until proven otherwise.

In all fairness, I'm not sure if there even were drives that large when Vista SP1 came out (thats what the recovery disk used).

@andreash_utah

Andy, if the SSR 2013 recovery disk boots up and loads the default intel driver on the disk, what happens if the user then manually loads a more recent version of the driver?

Does the more recent driver actually load and gets used by the system?

Or does nothing happen because the recovery disk can't replace the driver in use or maybe it thinks the one being used is "good enough" so it skips loading the new driver?

It seems like Rene has confirmed that the right driver is not being used since it worked after he changed the driver inside the boot.wim file of Ghost 15.

Dave

Brian_K · December 11, 2013, 2:41am

Rene,

Which tool created the partitions on the GPT disks?

Brian_K · December 11, 2013, 6:09am

The GPT partitions are a mess and I doubt they can be repaired. I think you will need to backup your data, delete the partitions, run a wipe for a minute or so to zero the start of the drive, then create a GPT disk and create partitions. I'd use BIBM for this.

KnauthR · December 11, 2013, 6:31am

I did this more than once on cmd with diskpart, with gparted and the last time with Windows GUI of disk management. I tried to patitioning first the first disc and then configure the Raid1 and I did first the raid1 and partitioned after this the disc ... last time I did first one disc and than put it together as raid1 (hardware raid from inside intel bios)

Rene.

andreash_utah · December 11, 2013, 6:52am

In the partinfo file, I am still seeing "WARNING: Above partition extends beyond end of disk." on DISK 1, which coincides with the errors being seen in SMEDump. This disk is also being reported as having 4k physical sectors. 4k sector drives may not show up correctly in SSR, while they do show up correctly in Windows Disk Management. I hate to admit that, but I can say that there are plans for 4k support in the next release.

KnauthR · December 11, 2013, 9:20am

Hi Andy,

"there are plans for 4k support in the next release" that exactly what I don't want to hear! :smileyfrustrated:

OK, that means there are two problems which are correlating: first the IRST driver version problem and second the 4k sector problem of the disc(s)?!

So, I interpret this as I should stop using these tools in "standalone/boot mode" (=SRD) for backup/restore of partitions on my system?! Because if the SRD boots it will do strange things with GPT headers, but If I use NG15/SSR2013 under windows only it will be OK?

For backup/restore of the 4TB disc this will be OK, but I need another tool/strategy for the emergency case if the boot disc gets corrupt or something like this and I have to restore it. hmm ...

Rene.

DaveH · December 11, 2013, 8:21pm

Would the "next version" be the SP2 expected in February or do you mean "next major version". (Will not be in SSR 2013).

andreash_utah · December 11, 2013, 9:30pm

SP2 is the next sevice pack. The are following the similar model of BacupExec and the next release is tentatively SSR 2013 R2, slated for release in late 2014.

KnauthR · December 5, 2013, 1:12am