Partition Size Error w/ Raw Download
-
I’m getting an error downloading a Linux Raw image using FOG 1.1.1 on Ubuntu 13.10 with an image of Mint 17. The error says, “Target partition size (40000 MB) is smaller than source (80000 MB). Use option -C to disable size checking (Dangerous).” I have successfully imaged various HD’s using Multiple Partition Image - All Disks, but I would like to be able to use just one image for different HD sizes.
Is the Raw image type the best choice, and if so, how do I disable size checking?
[ATTACH=full]1093[/ATTACH]
[url=“/_imported_xf_attachments/1/1093_OptionC.jpg?:”]OptionC.jpg[/url]
-
if you want to be able to use one image for different hard drive sizes, then the image MUST be of a drive smaller then the smallest drive you want to put it on.
-
This post is deleted! -
[quote=“Junkhacker, post: 31869, member: 21583”]if you want to be able to use one image for different hard drive sizes, then the image MUST be of a drive smaller then the smallest drive you want to put it on.[/quote]
Thanks for the info… I created a new Raw image on a 40GB HD and deployed the image to a 80GB HD. It created a 40GB partition for the OS and an additional 40GB of “Free Space.” How do I automatically take advantage of all of the HD space, i.e., one 80GB partition?
-
[quote=“Bill G., post: 31996, member: 24757”]Thanks for the info… I created a new Raw image on a 40GB HD and deployed the image to a 80GB HD. It created a 40GB partition for the OS and an additional 40GB of “Free Space.” How do I automatically take advantage of all of the HD space, i.e., one 80GB partition?[/quote]
My recommendation is gParted. In windows it’s as simple as editing the partition and telling it to expand the space. There are ways to do it with commands, but gParted is a GUI and a Live CD.
-
[quote=“Jaymes Driver, post: 31999, member: 3582”]My recommendation is gParted. In windows it’s as simple as editing the partition and telling it to expand the space. There are ways to do it with commands, but gParted is a GUI and a Live CD.[/quote]
We image hundreds of computers during a year and I’m looking for a way to automate the expansion during imaging. I’ve used gParted before, but I want students – who will be imaging these computers – to have as few steps as possible. Thanks for your reply.
-
[quote=“Bill G., post: 32037, member: 24757”]We image hundreds of computers during a year and I’m looking for a way to automate the expansion during imaging. I’ve used gParted before, but I want students – who will be imaging these computers – to have as few steps as possible. Thanks for your reply.[/quote]
I understand that! There are deffinately commands out there to complete the task, however I have never ventured into this territory, it might be wise to look in some linux imaging forums for a command that would complete the task for you
-
[quote=“Jaymes Driver, post: 32040, member: 3582”]I understand that! There are deffinately commands out there to complete the task, however I have never ventured into this territory, it might be wise to look in some linux imaging forums for a command that would complete the task for you :)[/quote]
Will do… thanks!
-
[quote=“Bill G., post: 32041, member: 24757”]Will do… thanks![/quote]
and of course whatever you learn come back and share with the class!
-
[quote=“Bill G., post: 31860, member: 24757”]I’m getting an error downloading a Linux Raw image using FOG 1.1.1 on Ubuntu 13.10 with an image of Mint 17. The error says, “Target partition size (40000 MB) is smaller than source (80000 MB). Use option -C to disable size checking (Dangerous).” I have successfully imaged various HD’s using Multiple Partition Image - All Disks, but I would like to be able to use just one image for different HD sizes.
Is the Raw image type the best choice, and if so, how do I disable size checking?
[ATTACH=full]1093[/ATTACH][/quote]
If this is a Windows 7 image, then why not use the Single Disk (Resizable)? It shrinks the volume to the smallest possible +5% that the disk can be shrunk. This option is suitable for exactly what you’re trying to accomplish. Is there a reason you’re using RAW for the image type?
-
[quote=“Bill G., post: 31996, member: 24757”]Thanks for the info… I created a new Raw image on a 40GB HD and deployed the image to a 80GB HD. It created a 40GB partition for the OS and an additional 40GB of “Free Space.” How do I automatically take advantage of all of the HD space, i.e., one 80GB partition?[/quote]
It will depend on the filesystems that you have chosen, but with ext4 as an example, you could write a script to update the partition table with parted and then resize the filesystem with e2fsprogs. You could set this script to run at the next reboot in your image (most distributions have a facility for this already). The complexity of the script would grow quickly depending on your partition layout but if you just have a single root partition it shouldn’t be too difficult.
I would start by booting one of your images and trying to do it manually on the command line. Once you have a sequence that works, make a script and start testing/debugging.
I’ve wondered about doing this as a special type of deploy in fog, but there are so many variations (different filesystems etc.) that it would probably be hard.
-
Out of interest I gave this a shot, this worked for me
[CODE]
$ parted /dev/sda
(parted) resizepart
Partition number? 1
Warning: Partition /dev/sda1 is being used. Are you sure you want to continue?
Yes/No? yes
End? [51.2GB]? 100%
(parted) quit$ resize2fs /dev/sda1
[/CODE]
I wouldn’t suggest this as a good idea on a working system, but since you already have your deploy image in fog, don’t worry about messing up the partition table/filesystem. If you make a mistake, you can just redeploy!A google search for “ubutnu first boot script” or something similar should give instructions on how to do this on the first reboot.
EDIT I chose to do this with “resizepart” rather than “resize” because “resize” will cause parted to try to resize the filesystem itself, I think this is better left to native tools like resize2fs!
-
resize2fs is a native part of the init as well. I just haven’t had any time to add resizing components for linux installs. If anybody has a patch system that may work for this, please let me know. I’d love to include, but do not have enough time to implement and test all by myself.
-
I’m interested in seeing this, and Tom’s right, the best place for this would probably be in the init before root filesystem is mounted.
Something like a checkbox “Expand to fill disk” associated with the Host (or Image) might work, then if the partition table and filesystem support it run, the resize {ext?,xfs,ntfs} tools after the initial deploy. I’ll try to make a patch if I get time.
-
It’d be very simple if i new the syntax of the resize2fs command. I could man/info/google for it but I’m being lazy for today
-
Also,
I think this would be done in a two part rather than per need basis.
I mean, following a similar process to Windows resizable imaging, the only issue I forsee is backing up the MBR for this, but I imagine the simplest method would be, resize, grab mbr of resized disk, upload image resize back to full size (or original).
After that, for download, all you’d theoretically need is push MBR back to disk. Download image, resize to full size of disk.
-
I’ve never actually played with the windows resizing - I’ve always just done it manually. I’ll take a look at it before I wander off down the wrong path
-
I’m currently testing an upload of my storage node, so it’s not perfectly accurate, but even with all the images on it, it’s gone from 50.5GB to 37.3GB. Have to wait to see if it re-expands.
Then I’ll test deployment to the same system and see if it at least re-expands properly. I’m lucky in that I have a default Ubuntu install which puts all space, that I’m aware of, on /, but I don’t know how it will work for setup’s where /, /home, /usr are on different partitions.
-
Starting with SVN 2002, I have added resize2fs and tested both download and upload. It isn’t a very thorough test. It’s a default Ubuntu 12.04 layout for 50GB disk. It shrunk the main ext partition (the only one) from 50gb to 3.4gb. I downloaded and had it expand only ext partitions and it all works if you’re willing to test it out.
-
I can’t test it today but I’ll give it a go over the weekend. Thanks!