[quote=“TheGorgotron, post: 42852, member: 28622”]I will check that tomorrow and copy an image over to see if it works. I’m pretty sure I had both set as 775 last time I tried this, but I’ll make sure this time. Thanks for the suggestion.[/quote]
Still getting permission denied. I’ll have to check on this some more later. Right now the main drive has a little bit of room left.
[quote=“Wayne Workman, post: 42846, member: 28155”]Maybe double check the permissions on the linked (new) hard drive or directory?
I would suspect that those permissions need to be the same as the ones applied to the original /images directory.[/quote]
I will check that tomorrow and copy an image over to see if it works. I’m pretty sure I had both set as 775 last time I tried this, but I’ll make sure this time. Thanks for the suggestion.
[quote=“Wayne Workman, post: 42818, member: 28155”]This might help:
That looks to be for expanding a partition on the same drive that Debian is already installed on. I’m looking to add internal HDDs to add more room for my FOG images.
Sorry if this has been asked before, I did a search and didn’t find my answer.
I have FOG 1.2.0 setup on Debian 7. I have two internal drives (empty ext4 partitions) I would like to use for extra storage space for my images. I tried adding them when I fist did the install and linked them to the /images location. This allowed me to upload fine but the deploy would fail out every time (problems finding the right image location).
My question: what is the best way to add storage space to an existing FOG for images?
[quote=“Junkhacker, post: 42426, member: 21583”]what you are describing is how single disk resizable works. it shrinks the partitions to as small as can hold the data before images are uploaded, and when putting the partitions on a new drive it expands the partitions to fill the drive.[/quote]
OK great, I will try that out then and see how it goes. Thanks so much for all the replies, I really do appreciate everyone taking the time to help us new guys/gals out.
[quote=“Uncle Frank, post: 42420, member: 28116”]Hold on a second. I think you are mixing things up here. Let me explain. When you start deploying an image your client boots up via PXE and comes up with the FOG client. This small linux is made up of several shell scripts to do the magic and deploy an image from your server to that client. First it mounts the image directory from the FOG server via NFS into the local filesystem. So ‘/images’ on the client is essentially the same as ‘/images/<imagename>’ on the server. ‘/dev/sda’ is simply the first hard disk on the client and this is where the image will be restored to (aka destination disk).
From what I can see your ‘/images’ seams perfectly alright (we’d see other error messages if not!).
[B]BUT, are you sure that the disk you pulled the image from is NOT larger than the disk to be deployed to…[/B][/quote]
I am new to this but I understand that much. What I was saying is that my images are not on /images located on /dev/sda. They are on a seperate (sdb) internal drive and I have linked the location on there to the /images located on /dev/sda. I think you might be right about the problem though, I compared the two drives and didn’t realize that the drive I made the image on was bigger. Am I correct in thinking that if I were to shrink the partition on my master image before uploading then any drive I use that’s larger than that partition should work? Also, will FOG automatically expand the partition to take up the full space of the drive during deployment? Sorry if this is super basic stuff.
[quote=“Uncle Frank, post: 42403, member: 28116”]FOG is trying to restore the MBR using the following command when the error occours:
[CODE]sgdisk -gel /images/d1.mbr /dev/sda[/CODE]
Possibly failes because the destination disk is too small?? Or somehow different to the original source disk??[/quote]
Ok that’s good to know. I wonder if the /dev/sda might be causing the issue since my images are linked on a seperate drive and not stored on /images. Do you know where I would go to alter that sgdisk line? Thanks for the reply.
Also, I created another image the exact same way and it deploys just fine.
I was on Ubuntu before switching to Debian and had to run the “restart tftp-hpa” command on a regular basis.
Thanks for the responses. Here is a little more info and a screenshot:
Debian 7.8.0
FOG 1.2.0
This image is set as "single disc, multiple partitions (not resizable).
[IMG]https://lh4.googleusercontent.com/-BEwX-0Ru_cQ/VOTOOjByZkI/AAAAAAAACwg/5X47tLTuPho/w682-h527-no/Capture.PNG[/IMG]