Forum Home
Press F1
Thread ID: 143699	2017-03-21 02:31:00	Cloning Server RAID1 SATA drive to SATA SSD	Geek4414 (12000)	Press F1

Post ID	Timestamp	Content	User
1433099	2017-03-21 02:31:00	I'm experimenting with replacing the two HDDs in a RAID1 array on a Proliant ML110 G6 server, to give it some performance boost for large database applications. This is a stop gap measure till the system is shifted to the cloud. There are 2x 250GB SATA HDDs connected to the RAID controller as RAID1, I'm hoping to replace them with 2 x 250GB SSDs (or larger) Initially tried cloning the 1st drive using a cloning dock (disk to disk clone) but that didn't seem to work, the drive appears to be blank after the clone was done successfully. I guess that's because it's part of the RAID1 array and does not have normal partitions on the drive? Next tried CloneZilla with the SSD connected via SATA and the RAID1 array in place, that appears to have cloned the data successfully and it did it very fast, around 35 to 40 minutes with 160GB of data on the drive. However, it wouldn't boot off the SSD, initially it did a 'repair' and created a new entry in the boot menu for Windows Server 2008 R2 (recovered), selected that and it booted up but latterly I realised it actually booted off the RAID1 array, as the HDD is shown as C and the SSD shown as D after it booted. If I select the first entry from the Boot menu Windows Server 2008 R2, it crashed immediately (didn't copy down the message last night), if I choose the 2nd option of Windows Server 2008 R2 (recovered), it will proceed to boot and a mouse pointer will appear briefly and then it will just reboot. Tried that on one of my PC off site and the same, the message from booting from the 2nd entry is (see attached pix) Status: 0xc000000e Info: The boot selection failed because a required device is inaccessible 7953 I gather it is looking for some hardware (probably the RAID controller) that was in the ML110 and not on this PC I am testing it on. I thought it was something to do with the boot record and tried the bootrec /fixmbr and /rebuildbcd but then thinking about it, it actually booted into the boot manager and proceeded to boot, so it's more likely to do with hardware/driver configuration in the cloned drive? Tried Safe mode on both boot options and the PC just reboot part way through booting up. Any ideas of how to proceed from here or other cloning options?	Geek4414 (12000)
1433100	2017-03-21 03:44:00	Might be similar to this (support.microsoft.com)	Speedy Gonzales (78)
1433101	2017-03-21 04:52:00	Might be similar to this (support.microsoft.com) Speedy, thanks for that. I will try it out shortly. Just writing another copy of Windows Server 2008 R2 ISO to a bootable USB now. For some unknown reason, it wouldn't boot from the USB ISO any more, did work perfectly fine earlier today. >_< Will report back afterwards.	Geek4414 (12000)
1433102	2017-03-21 10:15:00	Speedy, thanks for that. I will try it out shortly. Just writing another copy of Windows Server 2008 R2 ISO to a bootable USB now. For some unknown reason, it wouldn't boot from the USB ISO any more, did work perfectly fine earlier today. >_< Will report back afterwards. Unfortunately, that didn't help. I booted off the USB with W2008R2 and tried the bcdedit, but it came up with error The boot configuration data store could not be opened. The volume for a file has been externally altered so that the opened file is no longer valid. So tried bootrec /scanos followed by /fixmbr and /fixboot and /rebuildbcd which all completed fine ... 7956 Then this time bcdedit came up ok 7957 And completed the steps from that page ... 7958 Rebooted PC and tried again, the same two entries came up in the boot manager with exactly same results as before. I might have to try a different cloning software like Active Disk Image and see I have better luck with that.	Geek4414 (12000)
1433103	2017-03-21 10:26:00	To clone a RAID array wouldn't you need to create a new one first and use it as a destination? not something I've tried personally just a guess. Is starting over not an option? because it seems like cloning is taking a lot of time and effort.	dugimodo (138)
1433104	2017-03-21 17:51:00	I'm no expert but I know that with my Raid 1 NAS I can just replace a drive with a new one then fire it up and it rebuilds the system. I can also make an image of a drive with Active @ and put it on a new one with no problems.	CliveM (6007)
1433105	2017-03-21 19:16:00	Several methods mentioned here. community.spiceworks.com One is similar to CliveMs suggestion, take out one HDD, replace with SSD, allow system to rebuild, then do the same with the other.	KarameaDave (15222)
1433106	2017-03-21 20:29:00	As KarameaDave said "take out one HDD, replace with SSD, allow system to rebuild, then do the same with the other." This the purpose of and what Raid is designed to do.	berryb (99)
1433107	2017-03-21 21:55:00	. . . Is starting over not an option? because it seems like cloning is taking a lot of time and effort . The DB server need to be activated with the new install and it can only be done during business hours, I can't do all this during business hours as they will have to shut up shop for half a day at least . Also the idea is do this with minimal cost and interruption . If we are to reinstall from scratch, then we may as well upgrade the whole server instead, which was also considered, although at a way higher cost . As KarameaDave said "take out one HDD, replace with SSD, allow system to rebuild, then do the same with the other . " This the purpose of and what Raid is designed to do . I've always thought you have to put in an identical drive, but apparently not, only need to be bigger drive . I am only experimenting at this stage, as HPE does not officially support SSD in this old server, although they acknowledged that it's technically possible . I don't want to order the SSD drives until I tested it first, hence going down the cloning route . I was hoping to clone to the SSD, then just boot off the SSD connected to SATA with the RAID1 array disconnected completely . If it works, then I will order the pair of SSDs, clone to the first drive, and let it rebuild the second drive . This way, I can leave the original pair of RAID1 HDD completely untouched in case anything goes wrong, I can simply plug them back in . My other concern with simply replacing the 2nd drive with SSD is that, I still can't tell if it would boot off the rebuilt drive and don't know how long the rebuild would take . I am not sure if playing around with the RAID setting to rebuild the array would mean I may not be able to plug the original pair of HDD back in without fiddling? Just trying to play safe here :)	Geek4414 (12000)
1433108	2017-03-21 22:25:00	make image (save image to USB HD), remove old drives install new drives, setup/initialise raid clone to new 'drive' from image . This assumes its not some sort of software raid , or semi-software raid	1101 (13337)
1 2 3