I've probably made a meal of this but here goes.
We have a HP ML350 G6 server running SBS 2008.
Storage was a RAID 1 array(2 x 146GB hard drives) partitioned into two Logical drives.
Replaced 146GB drives with 2 x 300GB drives which populated nicely.
Drives C: with OS on it & D: a large volume which I now suspect was a swapfile?
Installed IFW 2.97E, seemingly without any problem.
Created DOS boot disk onto CD which when tested worked fine.
Opened HP Array Config Tool, deleted array & created new array to reflect the increased size.
Via DOS boot CD did a restore of the Backup previously created by IFW.
All went swimmingly until reboot after restore finalised.
Server goes through startup routine (which takes forever!) & says it has successfully restored backup.
Reboot: the server goes through its startup motions, shows the Microsoft logo for a bit & makes sounds like it's actually booting up until it gets to a point where the screen says "going into sleep mode" & then it just reboots & goes through the cycle over & over.
I've delved into DOS & can see drives C & D do exist.
Responses welcomed
IFW 2.97E Restore Issues
-
- Posts: 3623
- Joined: Thu May 05, 2011 10:37 pm
Re: IFW 2.97E Restore Issues
disable automatic restart via F8 menu then you can see what the BSOD is.
Also, run chkdsk /f on your drive (should have ran it prior to the backup
and did validate byte-for-byte when creating the backup).
Also if the new drives are higher speed, consider changing out the cables.
Also could try restore using Linux instead of DOS environment. And validate
byte-for-byte.
"RodSchober" wrote in message news:10343@public.image...
I've probably made a meal of this but here goes.
We have a HP ML350 G6 server running SBS 2008.
Storage was a RAID 1 array(2 x 146GB hard drives) partitioned into two
Logical drives.
Replaced 146GB drives with 2 x 300GB drives which populated nicely.
Drives C: with OS on it & D: a large volume which I now suspect was a
swapfile?
Installed IFW 2.97E, seemingly without any problem.
Created DOS boot disk onto CD which when tested worked fine.
Opened HP Array Config Tool, deleted array & created new array to reflect
the increased size.
Via DOS boot CD did a restore of the Backup previously created by IFW.
All went swimmingly until reboot after restore finalised.
Server goes through startup routine (which takes forever!) & says it has
successfully restored backup.
Reboot: the server goes through its startup motions, shows the Microsoft
logo for a bit & makes sounds like it's actually booting up until it gets to
a point where the screen says "going into sleep mode" & then it just reboots
& goes through the cycle over & over.
I've delved into DOS & can see drives C & D do exist.
Responses welcomed
Also, run chkdsk /f on your drive (should have ran it prior to the backup
and did validate byte-for-byte when creating the backup).
Also if the new drives are higher speed, consider changing out the cables.
Also could try restore using Linux instead of DOS environment. And validate
byte-for-byte.
"RodSchober" wrote in message news:10343@public.image...
I've probably made a meal of this but here goes.
We have a HP ML350 G6 server running SBS 2008.
Storage was a RAID 1 array(2 x 146GB hard drives) partitioned into two
Logical drives.
Replaced 146GB drives with 2 x 300GB drives which populated nicely.
Drives C: with OS on it & D: a large volume which I now suspect was a
swapfile?
Installed IFW 2.97E, seemingly without any problem.
Created DOS boot disk onto CD which when tested worked fine.
Opened HP Array Config Tool, deleted array & created new array to reflect
the increased size.
Via DOS boot CD did a restore of the Backup previously created by IFW.
All went swimmingly until reboot after restore finalised.
Server goes through startup routine (which takes forever!) & says it has
successfully restored backup.
Reboot: the server goes through its startup motions, shows the Microsoft
logo for a bit & makes sounds like it's actually booting up until it gets to
a point where the screen says "going into sleep mode" & then it just reboots
& goes through the cycle over & over.
I've delved into DOS & can see drives C & D do exist.
Responses welcomed