Unable to locate image store.

[ManofValor]

@Sebastian-Roth

[root@localhost bin]# cat /opt/fog/images/MCWP82/d1.partitions
label: dos
label-id: 0x0007ef66
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=  1953523120, type=7
[root@localhost bin]# cat /etc/exports
/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

[george1421]

Since we moved things around you probably should issue this command cat /images/MCWP82/d1.partitions Just so the screen shots are consistent. It better give you the same exact answer.

But looking at the files, and screen shots. It appears your reference computer’s disk image didn’t make it to the fog server completely (mostly didn’t make it).

[ManofValor]

@george1421 It did give the same answer. So now what. BTW, my boss told me to start looking into other imaging options. I would hate for all this work to go to waste but he’s getting antsy for an imaging solution.

[Wayne Workman]

@ManofValor said:

BTW, my boss told me to start looking into other imaging options. I would hate for all this work to go to waste but he’s getting antsy for an imaging solution.

Don’t let us hold you back. And if you think that’s going to get you more attention, I do apologize but it won’t - it will push people away if anything. I feel both developers and moderators have given generous time and thought to you because your new, but it’s not nice to say your leaving while your still here (in our house, so-to-speak).

Your image didn’t upload completely, we need to figure out why, and then try again.

Please run this and give the output:
df -h

After that, re-upload this image. We need to know everything and anything that happens out of the ordinary while the upload is going. If you need to, take a video while it gets going so you catch everything.

After upload, please issue this command and give us the output, and then we will go from there.

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

[ManofValor]

@Wayne-Workman @Tom-Elliott @george1421 @Jbob @Sebastian-Roth Man, I apologize, your absolutely right. I did not mean it to get attention or try to get you guys to work harder. You guys have been more than awesome. I meant it as, “Crap these guys have spent so much time on this with me that I don’t want to move on and have their time have been for nothing”. But I see what you mean about saying that “In your house”, I was going to continue this anyway on my own time but he told me to keep going on it if I think I’m making progress. I am really really grateful to you guys for your time and effort. Please accept my apology.

[Tom Elliott]

@ManofValor I have no hard feelings though It did initially hurt.

Apparently my wife’s endless cycling of Harry Potter is hitting home here: “Help will always be given to those who ask for it.”

[ManofValor]

@Wayne-Workman

[root@localhost bin]# df -h
Filesystem                      Size  Used Avail Use% Mounted on
/dev/mapper/centos00-root00      20G  5.1G   14G  27% /
devtmpfs                        1.9G     0  1.9G   0% /dev
tmpfs                           1.9G  152K  1.9G   1% /dev/shm
tmpfs                           1.9G   88M  1.8G   5% /run
tmpfs                           1.9G     0  1.9G   0% /sys/fs/cgroup
/dev/sda5                       969M  187M  716M  21% /boot
/dev/mapper/fog-opt_fog_images  395G  327M  374G   1% /opt
tmpfs                           379M   24K  379M   1% /run/user/1000

[ManofValor]

@Tom-Elliott Sorry for that. Hate being human sometimes…ok a lot of times…lol.

[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.