Server 2003 SCSI HDD upgrade resulted in extremely long boot times
Hello I'm running Server 2003 Standard SP1. This server acts as a DC,and runs with a split DNS scenario for a small organization. Hardware is a Dell Power Edge w\ a PERC 4e\Si Raid adapter card (Running RAID 1 with two HDD bay's).
We recently decided to upgrade the storage space on this server since it was running very low. Specifically upgrading the Hot Swap SCSI HDD's. From 73 to 146GB.
Scenario #1: Symantec LiveState Recovery. Created images of existing partitions (C and D), installed new drives. Configured array for two logical partitions on Raid Card at boot. Dumped images back to logical partitions. Using Livestate to expand the partitions.
PROBLEM: EXTREMELY LONG BOOT TIMES- 50 mins. System hangs on applying network connections, applying security, ect. Once log on screen appears, desktop comes up slow but not extremely long.
Scenario#2: Dell Support. Boot up OS, pull out one 73 GB drive insert new 146GB--system rebuilds 73GB of data on the 146. After rebuilt, pull the original drive and insert the 2nd new drive and let that one rebuild. Use 3rd party software to expand the partitions (had Acronis Disk Director in mind).
SIMILAR PROBLEM: EXTREMELY LONG BOOT TIMES- 50 mins. System hangs only on applying security only, applying Network Connect came up quick. Once log on screen appears and I login, it's taking 30mins so far...
Any suggestions would be much appreciated, as I'm still waiting for my desktop to come up, and will most likely roll back to the previous drives.
We recently decided to upgrade the storage space on this server since it was running very low. Specifically upgrading the Hot Swap SCSI HDD's. From 73 to 146GB.
Scenario #1: Symantec LiveState Recovery. Created images of existing partitions (C and D), installed new drives. Configured array for two logical partitions on Raid Card at boot. Dumped images back to logical partitions. Using Livestate to expand the partitions.
PROBLEM: EXTREMELY LONG BOOT TIMES- 50 mins. System hangs on applying network connections, applying security, ect. Once log on screen appears, desktop comes up slow but not extremely long.
Scenario#2: Dell Support. Boot up OS, pull out one 73 GB drive insert new 146GB--system rebuilds 73GB of data on the 146. After rebuilt, pull the original drive and insert the 2nd new drive and let that one rebuild. Use 3rd party software to expand the partitions (had Acronis Disk Director in mind).
SIMILAR PROBLEM: EXTREMELY LONG BOOT TIMES- 50 mins. System hangs only on applying security only, applying Network Connect came up quick. Once log on screen appears and I login, it's taking 30mins so far...
Any suggestions would be much appreciated, as I'm still waiting for my desktop to come up, and will most likely roll back to the previous drives.
I forgot to add - update the BIOS on the PERC if there is a newer one available.
ASKER
The original drivers were setup as one logical partition on the RAID controller. And we do have the latest and greatest bios revision. Question regarding Livestate recovery, when restoring the recovery points, we have opted out of using the the "restore MBR", "restore original disk signiture" switches. Is this corect? And I'm assuming it would be better to create the images from the Restore server disk than to create them while the server is up and running? I'm concerned about 1)Volume shadow copies and 2) active directory. And thoughts or input you have would be appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You may need to run a chkdsk /f to fix any issues with the partitions.
With the original drives installed, run a defrag.
Run chkdsk /f from the Run box, select Y at the prompt.
Shutdown, and do your image (Ghost would work as long as you can see the controller).
Remove old drives.
Configure the 2 drive in RAID 1 using the controller.
Configure 2 Logical Drives using the controller.
Slam the image back onto C extending it in the process.
Slam the image back onto D extending it in the process.
Reboot and chkdsk should run automatically.
Let us know if it works any better.