Win 7 crashes with no BSD when backing up

User discussion and information resource forum for Image products.
Post Reply
nachor
Posts: 1
Joined: Mon Dec 05, 2011 4:50 pm

Win 7 crashes with no BSD when backing up

Post by nachor »

I have recently freshly installed a valid Windows 7 pro and am trying to use Image for Windows to make back ups of drives. When I installed windows from XP, I added a raid card and set it to mirror two 1 TB drives in order to be redundantly secure. The resulting "drive" can be seen and written to fine. It has had over 500 gigs of information copied to it to test the transfer speed and its performance under stress. However, if I attempt to use Image for Windows to back up a drive to the Raid array, the 2 TB drive or the 150 gb system drive the entire system restarts itself about 50% of the way through the backup with no BSD. This is the second RAID card I have installed to see if it the card causing the issue. Are there any known conflicts with RAID 1? Or does anyone know a possible solution short of abandoning the RAID?
TeraByte Support
Posts: 3598
Joined: Thu May 05, 2011 10:37 pm

Re: Win 7 crashes with no BSD when backing up

Post by TeraByte Support »

You'd want to disable automatic restart for Windows, update the storage
drivers, check thermal temperature during backup.

"nachor" wrote in message news:835@public.image...

I have recently freshly installed a valid Windows 7 pro and am trying to use
Image for Windows to make back ups of drives. When I installed windows from
XP, I added a raid card and set it to mirror two 1 TB drives in order to be
redundantly secure. The resulting "drive" can be seen and written
to fine. It has had over 500 gigs of information copied to it to test the
transfer speed and its performance under stress. However, if I attempt to
use Image for Windows to back up a drive to the Raid array, the 2 TB drive
or the 150 gb system drive the entire system restarts itself about 50% of
the way through the backup with no BSD. This is the second RAID card I have
installed to see if it the card causing the issue. Are there any known
conflicts with RAID 1? Or does anyone know a possible solution short of
abandoning the RAID?

Post Reply