Stupid Windows Server 2008 Installer
Friday 5th June, 2009 22:27 Comments: 0
I wanted to install Windows Server 2008 x64 onto a SATA hard disk. I've had it running on an IDE disk, but I wanted to move to a larger SATA disk. After replacing an old array of 1TB disks with a new array of 2TB disks, I decided to re-use one of the 1TB drives. It should be simple, boot off the DVD, delete any existing partitions on the disk, install Windows onto the unpartitioned space.
Attempt #1
I can only see the IDE hard disk. I try looking for ICH9R drivers on the Gigabyte driver CD, but I can't get it to display any drivers other than the Gigabyte SATA controller.
Attempt #2
I move the SATA drive onto the Gigabyte controller and use the Gigabyte CD to load the Gigabyte SATA drivers. I can only see the IDE hard disk.
Attempt #3
I load the drivers off the IDE drive for my 8 port Supermicro SATA controller (the 64 bit signed drivers I've been using are actually Adaptec drivers) that I'd been using earlier today to migrate data between the two arrays. I can only see the IDE hard disk.
Attempt #4
I try hooking up another 1TB hard disk, one to the Gigabyte controller and one to the Intel one, setting both to legacy IDE mode (rather than native AHCI). I load the Gigabyte driver off the Gigabyte CD. I can only see the IDE hard disk.
Attempt #5
I disconnect the 1TB drive on the Gigabyte controller and copy the Intel ICH9R drivers onto the IDE disk (under the IDE install of 2008) and try loading them during the installer (I thought it supported ICH9R natively, but I'm getting a bit desperate and will try anything). I can still only see the IDE drive.
Attempt #6
I decide to boot back into the IDE install of 2008 and go into Disk Management. I delete the volume and the disk reverts to a basic unformatted disk. I boot off the DVD and...
I can see the 1TB hard disk! I can finally see it! And I didn't have to load any drivers either, it was built into the installer already.
Yes, it was as simple as that. The installer was hiding the hard disk. I don't know if having the entire array hooked up would have worked (as they would appear as foreign disks that need to be imported), but it would appear that a single drive from an array will not show up until you've deleted the volume. This probably prevents a few stupid administrators from installing the OS over the top of a disk that's part of an existing array, but I suspect it fools just as many people when they try and re-use disks.
The moral of this story is that you should always delete your volumes after you've finished with them.
Attempt #1
I can only see the IDE hard disk. I try looking for ICH9R drivers on the Gigabyte driver CD, but I can't get it to display any drivers other than the Gigabyte SATA controller.
Attempt #2
I move the SATA drive onto the Gigabyte controller and use the Gigabyte CD to load the Gigabyte SATA drivers. I can only see the IDE hard disk.
Attempt #3
I load the drivers off the IDE drive for my 8 port Supermicro SATA controller (the 64 bit signed drivers I've been using are actually Adaptec drivers) that I'd been using earlier today to migrate data between the two arrays. I can only see the IDE hard disk.
Attempt #4
I try hooking up another 1TB hard disk, one to the Gigabyte controller and one to the Intel one, setting both to legacy IDE mode (rather than native AHCI). I load the Gigabyte driver off the Gigabyte CD. I can only see the IDE hard disk.
Attempt #5
I disconnect the 1TB drive on the Gigabyte controller and copy the Intel ICH9R drivers onto the IDE disk (under the IDE install of 2008) and try loading them during the installer (I thought it supported ICH9R natively, but I'm getting a bit desperate and will try anything). I can still only see the IDE drive.
Attempt #6
I decide to boot back into the IDE install of 2008 and go into Disk Management. I delete the volume and the disk reverts to a basic unformatted disk. I boot off the DVD and...
I can see the 1TB hard disk! I can finally see it! And I didn't have to load any drivers either, it was built into the installer already.
Yes, it was as simple as that. The installer was hiding the hard disk. I don't know if having the entire array hooked up would have worked (as they would appear as foreign disks that need to be imported), but it would appear that a single drive from an array will not show up until you've deleted the volume. This probably prevents a few stupid administrators from installing the OS over the top of a disk that's part of an existing array, but I suspect it fools just as many people when they try and re-use disks.
The moral of this story is that you should always delete your volumes after you've finished with them.