Multi-Image H/D issue

[MikeDThePhoneGuy]

Has anyone experienced an issue when cloning the Multi-image hard drive, that the BCM50 R6 image will not enable when initializing it? I have made numerous copies for all versions of BCM450 and 50 where they all worked, but every time I try to initialize the BCM5 R6 version it bricks the h/d. I am using Acronis 2015 and making an 'AS IS' copy to an identical 250GB h/d. Any help would be greatly appreciated.

 

[curlycord]

I have not noticed as using straight images only lately but will try it when can.

These are non upgraded BCM50's correct? they are R6 out of the box?


________________________________________

Add me to LinkedIN

=----(((((((((()----=

http://www.curlycord.com

Toronto, CAN

 

[exsmogger]

I've never gotten a cloned multi-image HDD to load the BCM50 R6. The upgrade process aborts shortly after starting and renders the drive useless until I re-image it. It seems to work with every other version of BCM50 and BCM450. I used Acronis 2009 to make my image. Never have found a fix for this.

Brian Cox
Georgia Telephone

http://Georgia-Telephone.com

http://www.linkedin.com/in/briancox1952

 

[number1telecom]

I have a master that I clone and swap in every R6 BCM50 we get in (true R6 units, not upgraded) and have never had any issues.

http://www.number1telecom.com

 

[rrmass]

Did you clone the actual multi-image drive and create the R6 image on the BDM50 system in question or did you use a cloned image that was created on another BCM50 R6.

I have created virgin images of all BCM50 revisions from the multi-image drive. It then only takes a few minutes to create a new drive from the correct cloned revision instead of building a drive on the BCM50 that needs a new drive.

I have found that using a drive with an R6 image that was created on an original R6 works fine on an original R6 system but if you put that same drive in a system that was upgraded it displays the same symptoms that you are describing. I believe it's systems that were upgraded from R1 or R2 to R6 that have this problem.

I noticed this one time when I wanted to make a new drive for a R2 system that was upgraded to R6. On boot up of the multi-image drive it would only give me the choice of creating a drive for R1 or R2 even though the system was upgraded to R6. I imagine I would have had to create an R2 drive and then upgrade it to R6 to accomplish to create the drive. Instead I had another working system that was an R2 to R6 upgrade. I then cloned that drive and put it in the sick system, reset the programming, added the license file, reprogrammed and away she went.

It was a few years ago that I did this but at the time I did a little investigating and found that the boot partitions on an original R6 drive and an R6 that was upgraded had different names for the boot file. I suppose the boot loader on the upgraded system is trying to load the wrong file, can't find it and then craps out.

 

[exsmogger]

As curlycord mentioned I think the issue is with BCM50's that have been previously upgraded to R6 as opposed to units that are original R6. My R6 image works fine. It came from an R6 that I did a level 2 reset on so it was back to factory default. Then I added the most recent system and desktop patches, along with the factory image upgrade patch, and made my R6 image. Never had any issues with it. I just can't get the multi-image to load the R6 without errors.

Brian Cox
Georgia Telephone

http://Georgia-Telephone.com

http://www.linkedin.com/in/briancox1952

 

[MikeDThePhoneGuy]

Unfortunately in this case the BCM50 is a true R6, not an upgraded unit. I have never been able to get the R6 to fully initialize, I have always had to use a clone or the R6 drive itself. Thought it might have been what I was doing, but sounds like this is an issues for many of us.

 

[exsmogger]

Thanks for letting me know that. I was going to experiment on a true R6 the next time I got one. I'll just keep using clones from my R6 image.

Brian Cox
Georgia Telephone

http://Georgia-Telephone.com

http://www.linkedin.com/in/briancox1952