Last active 7 weeks ago
My fdisk skills are okay, but I can always learn if there's something I don't know. Thank you for the suggestion, I'll try that the next chance I get.
That's weird as well...the thing is, the very first image I ever created with CD was on a 500GB hard drive, have since switched to 160, but I've never used anything over 500GB...I uploaded the current image in On Demand mode, and was deploying also in on demand mode...this is just weird .-.
So really, I guess the question would become: How on earth is this bad partition table being generated? I created a new image before I went home for the day, and used a different computer to pull from, but the same results were yielded.
I tried it with the "Don't Expand Volumes" option, and it doesn't change anything. Here's that log.
It's in On Demand mode, but here's the most recent log from that UUID.
This may be a dumb question, but it looks like the hard drives of computers I am imaging get partitioned without being expanded. I'm deploying Ubuntu 16.04 in On Demand mode, originally on a 160GB hard drive, and most computers already have a 160GB hard drive.
The logs say nothing about expanding anything, which is what I think could indicate a issue of some kind. Ubuntu boots, but it tells me the hard drive is 6 gigabytes in capacity, but the 'Disks' application says the hard drive itself is 99% full and has 160GB capacity.
In Images>(imagename)>Profiles>Default>View>Deploy Options>Modify Schema, the one partition that is there says its' size is 142.28GB with a volume size of 5888MB, rounding and converting to 5.9GB, which Ubuntu says I have.
I have made sure that "Don't Expand Volumes" is unchecked.
Am I missing something?