Unable to locate image store.

[Wayne Workman]

@ManofValor Ok so you didn’t run out of space… can you try to re-upload and really pay attention to what’s outputted to the screen, and note exactly where the failure occurs? A video of the entire process would be of immense help.

[ManofValor]

@Wayne-Workman So I went to re-image, without changing anything, and it’s working. The first time it got to the image screen, blue screen with red status bars, and it went really quick. This time it’s actually going through the process. I’ve got 7 1/2 min left.Fingers crossed.

[george1421]

Great once you get it working, lets try to break it again…

Actually I’d like you to upgrade to the latest trunk version. There has been some advancements in some of the init scripts that may help you too. But first get it to image capture then deploy. Once that is successful try to upgrade.

[ManofValor]

@george1421 I’m afraid to break it…lol.

[Quazz]

@ManofValor said:

@Wayne-Workman So I went to re-image, without changing anything, and it’s working. The first time it got to the image screen, blue screen with red status bars, and it went really quick. This time it’s actually going through the process. I’ve got 7 1/2 min left.Fingers crossed.

That’s because it does progress partition by partition, so the really quick one is the boot partition in front of your main one

[ManofValor]

@Wayne-Workman

[root@localhost bin]# cd /images/MCWP82;ls -lahRt;cat d1.fixed_size_partitions;cat d1.partitions;cat d1.original.swapuuids;cat d1.original.fstypes;cat d1.minimum.partitions
.:
total 24G
drwxrwxrwx. 5 root root 4.0K Mar  8 10:09 ..
drwxrwxrwx  2 root root 4.0K Mar  8 10:09 .
-rwxrwxrwx  1 root root  24G Mar  8 10:09 d1p1.img
-rwxrwxrwx  1 root root  132 Mar  8 09:32 d1.minimum.partitions
-rwxrwxrwx  1 root root 1.0M Mar  8 09:32 d1.mbr
-rwxrwxrwx  1 root root   15 Mar  8 09:28 d1.original.fstypes
-rwxrwxrwx  1 root root    0 Mar  8 09:28 d1.original.swapuuids
-rwxrwxrwx  1 root root  132 Mar  8 09:28 d1.partitions
-rwxrwxrwx  1 root root    1 Mar  8 09:28 d1.fixed_size_partitions

label: dos
label-id: 0x0007ef66
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=  1953521664, type=7, bootable
/dev/sda1 ntfs
label: dos
label-id: 0x0007ef66
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=   111430488, type=7, bootable

[ManofValor]

Ok, so successful image and now for the deployment. It is going right now, no issues. 27 min left +/-.

[george1421]

@ManofValor 27 min left. How fast are you deploying (GB/Min). Your only have a 24GB disk image. On the surface I would say less than 1GB/min, which is kind of slow.

[Edit] If I did the math correct that’s about 16MB/s, which is close to the top speed for 100Mhz network link [/Edit]

[ManofValor]

@george1421 Roughly 1.8.

[george1421]

@ManofValor said:

@george1421 Roughly 1.8.

Understand I’m not poking holes in something that is working. But if your server is somewhat new and your desktops are somewhat new I might expect better. For reference I was using a dual core celeron intel nuc as my demo fog server which had a 128GB ssd drive. For the demo, I was deploying to a Dell e6410 (circa 2008). With that setup I was getting about 4-5GB/min transfer rate. In my production environment I can get between 5 and 8GB/min. But understand I have an insanely fast vm host server. In my production environment I can deploy a 7GB windows thin image in about 1.5 minutes with a 10 minute bare metal to deploy state. A 20GB fat image will go from bare metal to fully deployed in about 16 minutes.

But for now baby steps. Just get it working then you can think about optimizing the process.

[ManofValor]

@george1421 Sounds good.

[Wayne Workman]

@ManofValor Now try to deploy that image to another machine of the same model.

[ManofValor]

Successful deployment. Woot woot!

[george1421]

@ManofValor said:

Successful deployment. Woot woot!

This is great, so for the 64 million dollar question. Why did it start working. I looked back through this thread and didn’t find a key fix (this thread did wander a bit).

[Tom Elliott]

@george1421 Just guessing, but maybe I finally coded something right?

[ManofValor]

@george1421 said:

This is great, so for the 64 million dollar question. Why did it start working. I looked back through this thread and didn’t find a key fix (this thread did wander a bit).

That’s what I want to know.

[Wayne Workman]

Happy fogging.

[ManofValor]

Now I want to make another FOG server so I can take an image of this FOG server incase something happens…lol

[Wayne Workman]

@ManofValor Bad idea… use Clonezilla for that.

[ManofValor]

@Wayne-Workman Yeah I was joking but maybe thats not such a bad idea. Thanks.