Topics created by bartont126

@bartont126 Well unfortunately we need to see what the partclone error is. Partclone doesn’t give a good quality error message back to fog, other than the copy failed. FOG ties to make a good guess to why the copy didn’t happen but misses some times. If you setup a debug capture then single step through the deployment you can capture what is on the partclone screen.

I know this is an old topic, just wanted to reiterate that this fixed my problem. The weird thing is that this wasn’t a problem until today. Been using Fog with the same laptops, same basic install of Windows 10 for around 1.5 years now, and today was the first time I saw this error. Went and turned off fast boot and it works great. Yay for forum search functions. 😉

Philip

@bartont126 On Linux systems you can easily mount drives anywhere in the filesystem. So you can just hock up the huge drive to your machine, check the name it came up with, mount that, move your images and remount it in /images location.

Hint: Please be very careful with those commands and make sure you understand every step before proceeding! There is a chance that you wipe all your data from the server if you don’t know what you do and things go wrong! I am not liable for any actions done blindly following the steps posted here.

That said, shutdown the server, connect the new drive and boot it up again.

sudo -i fdisk -l

That should print out all the disks, where quite often /dev/sda is your system disk and the new one might be /dev/sdb. See if it is partitioned properly yet. If not, go ahead:

aptitude install parted parted /dev/sdb mklabel gpt mkpart primary ext4 1MiB 100% mkfs.ext4 /dev/sdb1 mkdir /newdisk mount /dev/sdb1 /newdisk service nfs-kernel-server stop mv /images/* /newdisk mv /images/.mntcheck /newdisk umount /newdisk rmdir /newdisk mount /dev/sdb1 /images service nfs-kernel-server start

You should see the new bigger disk space in the FOG web UI now. But to make this change persistent you need to add an entry to /etc/fstab so the big disk will be mounted automatically on boot. Add the following line.

/dev/sdb1 /images ext4 defaults 0 0

Now reboot you FOG server and see if everything is up to your needs.

@bartont126 I’m glad you have it all worked out. I checked in on the other threads and it looks like you found out about the dirty bits and shutting windows down properly and how to add additional storage to your fog server. well done.