Questions about Image for Windows

Since the problem seems to be related to unreliability of the SSD cache, a solution would be to disable it permanently.

 

Hi MudCrab,

There is an issue that I need to make you aware of. The new HP disks I used to recover my system created one large C-partition (see my disk mgmt. screen below).



Before Windows crashed, my system partition was only 62GB and I had 4 additional logical partitions (I'd love to restore my last system image and my old partition structure)!

Cruise

 

Robin,

I can't accept that solution. I paid extra for that mSSD option based on the premise that it would speed-up startup and my frequently used apps. It seems to do just that. I need an imaging solution that is compatible with my configuration!

Cruise

 

Hi Cruise,

Why do you need BIBM? I don't know but somehow I have the feeling that your problems were due to using BIBM on a RAID setup. Maybe, both Brain and Mudcrab can chime on this.

BTW, I have BIBM but never have used it.

Best regards,

 

I understand, that´s your choice.

[ If I have understood it correctly, there are two different functions of a SSD cache. One is to accelerate the normal operation of the disk acting as a faster cache.

The other is to accelerate the start-up of the computer. To do this, a special "hibernation partition" is created in the SSD. I suppose that there are problems if it is damaged or corrupted. Perhaps one should image this SSD partition also? Is it possible to do this? ]

 

I realize the partition structure is different that what you had. What I'm interested in at this point is determining if all your "boot-up" programs can see all the partitions normally the same as Windows sees them. That would at least tell us if they can interface properly with the setup while it's in a working condition. I'm assuming that they will all see the partitions correctly, but there may be exceptions.

The fact that the system was working fine and then wasn't when it was turned on one time would seem to indicate a failure in the hardware setup and not a software program. Add to that that image restores were previously done successfully. There were quite a few bugs in the SSD drives/firmware for a while, including some bad ones, so it wouldn't surprise me a bit if there are bugs in this configuration too. The main things is to have a plan that allows restoring when/if that happens.

If all your imaging programs (DS, IFD, IFL, IFW, etc.) and your partitioning programs (BIBM, DD, etc.) can be booted and see the partitions correctly, then it would be good to create a new backup image (or images) and do some restores and see what happens. That's what I would do, anyway. For example, can you successfully restore your previous backup image of the drive from this state (assuming you have one of the entire drive)?

I'm not seeing anything helpful in the manuals. Will do some searching on it.

When the drives are in RAID you will only see one drive (unless the RAID isn't being detected properly). You would then only be able to image it as "one" drive.

 

aladdin, I used BIBM after the 'shxt hit the fan' (on Brian's recommendation). BIBM had nothing to do with the cause of the problem or the inability of my tib/sna restores to recover my system.

Cruise

 

I don't think it is possible because it doesn't show up as a drive/partition!

Cruise

 

Cruise,

Please follow MudCrab's recommendations. After you have checked the various partitioning apps, image the current Win7 partition and see if a restore is successful. I think it will be. Then restore your image taken last week prior to the crash. I think it will be successful too.

 

MudCrab, my son has my digicam so I have no way to take snaps when not in Windows. However, I can tell you categorically that BIBM, IFD, and DS see precisely what Windows Disk Manager shows!

I'm sorry if I created the wrong impression in this regard, but I never before tried restoring a backup image of my new laptop!

They all do see the partitions correctly, but nothing sees the mSSD! After this ordeal I'm very nervous about trying another restore without knowing that "it should work with my setup".

Most appreciated.

Cruise

 

Brian, since I would like to also restore the partition structure in-place before my system crash, do you see any problem in my also attempting to do that?

And in that regard, since my DS (sna) image is more recent than my tib image, do I restore the partition structure before or after restoring the system (using DS)?

Cruise

 

Cruise,

With DS, restore the partition structure before restoring the image. I think you only have an image of the Win7 partition so even though DS restores your logical volumes, they will be empty. But you have data backups of those volumes that you can restore to the empty volumes and be back to "normal".

 

Brian,

Thanks for that info on using DS - to be perfectly clear, should that be an MBR restore or a Partition Structure restore?

If I don't hear anything to the contrary from MudCrab by the end of the day I'll brave trying another restore tomorrow.

Cruise

 

Cruise,

You need a "Partition Structure restore". A MBR restore doesn't restore the partition table.

 

I have seen the partition shown in Windows Disk Manager (in another forum).

But I think this thread has become confusing and this topic could be discussed in another one. The open questions are:

- How to image a system when a SSD cache is used? Are there any special considerations?

- What about the hibernation partition in the SSD? Must it be imaged?

 

I'd open a new thread but how do I recreate all of the pertinent posts (history) within this thread?


Also fwiw, while the mSSD does not show up under Windows Disk Management or Windows Explorer, a search within my system found this...

 

Dear Cruise,

Good to hear the above. You have three partitions. One is SRP which is 200MB and it makes sense. The another one is C, which is system drive, which again makes sense. And, the third one is HP_Tools which is about 104MB, which doesn't make sense.

What is this HP_Tools, 104MB partition for?

Is this partition where the information for the RAID is kept, especially for the mSSD setup?

Did the above partition somehow got deleted earlier which caused your problems?

1. Did you make the image for system drive C?
2. Did you make the image for the 200MB SRP partition?
3. And, did you make the image for the 104MB HP_Tools partition?

Best regards,

 

aladdin,

I believe that the HP_Tools partition just contains HP's diagnostic tools.

When I first got the laptop I repartitioned it (much smaller C-partition plus other logical partitions for data, photos, etc.). At that time I also followed the TeraByte article on moving the contents of the SRP partition to the C-partition in order to not have to backup an SRP patition every time I backup C: The laptop worked great for the next couple of months until Windows crashed and my backup images didn't save the day! After recovering my system using the HP recovery disks I again have the SRP partition along with a very large C:

I never imaged the HP_Tools (FAT32) partition - can I even do that?

Cruise

 

If the BIOS correctly handles the RAID/cache setup then using the DOS-based programs should work. Linux-based recovery will need the correct Linux drivers for the RAID (SRT). For the Windows based (WinPE/RE) versions you probably will need the Intel SRT driver installed if it's not already included.

The reason I suggested creating a new image of the current drive and doing some test restores with it was because you haven't yet made any changes. If you have to reset back using the HP discs you haven't wasted time in customizing things.

I was under the impression that Brian previously helped you restore DS and IFD images on this laptop and that they were successful. I guess that was a different computer.

Just keep in mind that even if these restores go okay that doesn't mean future ones always will. If the cache/RAID gets screwed up again (out of sync, whatever), it will most likely need to be reset before a restore would work again. Is it possible to look in the BIOS and make notes of the options there and then post them? I know that's asking a lot, but without pictures it's hard to know what options are available (from what I've read, that BIOS is pretty sparse on options).

 

Hi Cruise,

It is a very small partition, about 104MB. I have the feeling that the information for cache/RAID is being kept on this partition outside the operating system partition.

I believe and I am not sure, if the cache/RAID gets screwed up again (out of sync, whatever), it will most likely need to be reset before a restore would work again, so therefore you need to keep this partition properly imaged for restoration (reset). Just a feeling, no hard facts.

Best regards,

 

Background information about Intel "Responsiveness Technologies", produced by Dell:

http://en.community.dell.com/dell-b...-responsiveness-technologies-setup-guide.aspx

 

As far as I know, the RAID settings are stored on the drive outside of existing partitions (usually in the last sectors). For example, you can take a set of normal Intel RAID drives out of one computer and put them into another one and they will retain their RAID setup (assuming a compatible controller and RAID is enabled on the system). I would think the Intel SRT would be along the same lines, but there's more going on since the SSD is only a cache instead of standard RAID drive.

Most of the time, those small "tool" partitions contain DOS-type programs, which tend to be very small.

 

Dear Mudcarb,

Many thanks for the above information.

Best regards,

 

I just realized that the last board I bought supports Intel SRT and Rapid Start. After I get it configured I can run some tests on it and see how it works with imaging (probably won't be until later this week at the earliest, though).

 

Robin, thanks for that interesting article.

Would those features be of benefit if your OS partition was on a SSD?