Forum archive
System Size (w Webmin Screenshots!)
OK, got Samba hobbled together enough to use VMware vCenter Converter to create a disk image from an XP machine to be used in Virtualbox on TKL Core appliance. Now when I started the 85GB convertion, I ran in to a wall on my TKL install. At first I thought it was a directory quota or a Samba limit, but it turns out to be the TKL partition limit.
I set up my TKL Core as a bare metal install on a brand new 500GB drive, which I had used GParted to format into two partitions -- 400GB ext4 and 100GB NTFS (this is my "just in case" partition). I used a LiveUSB drive to install TKL Core to the hard drive, and accepted the defaults for partitions, setting the size to "max" when asked about how much of the ext4 partition I wanted to use.
So I'm thinking I have this installed on a 400GB partition... right? Wrong. It created a 2.34GB partition and installed the TKL Core.

Check out Partition 1 details (NOTE: Status = Not in use):

...and Partition 5 details, where the TKL Core is installed:

So I go poking around in System > Disk and Network Filesystems to see if I can change the size of Partition 5 or somehow get TKL Core moved over to Partition 1:

Clicking on / (Root filesystem) above, gives me a chance to edit the mount:

Can I just change the Partition with ID to (SATA device A partition 1)? Or will this just destroy the entire Filesystem?
I also looked at the documentation, and found switch_root:
Manual page for switch_root(8)
SWITCH_ROOT(8) SWITCH_ROOT(8)
NAME
switch_root - switch to another filesystem as the root of the mount
tree.
SYNOPSIS
switch_root [-hV]
switch_root newroot init [arg...]
DESCRIPTION
switch_root moves already mounted /proc, /dev and /sys to newroot and
makes newroot the new root filesystem and starts init process.
WARNING: switch_root removes recursively all files and directories on
the current root filesystem.
Does this make any sense to use in my scenario?
Thanks,
Drew
switch root sounds interesting, can't say I've ever even heard of it! And assuming you haven't done too much work, why not give it a go. Worst case scenario you can start again right!? I know you've probably done a bit by now but I bet you've learned heaps and you'd be able to redo it all pretty quick. Also you will probably need to update grub (the bootloader) once you've moved it
If on the other hand, you don't want to risk starting again, you could just add partition 1 to the TKL LVM. You'll need to leave a small ext4 partition right at the start of the drive though (because Linux needs a 'real' FS to boot from. There's a blog post Liraz did on LVM and it's really easy from the commandline. AFAIK there is a Webmin LVM module too, but it's probably worth reading the blog post first anyway, so you've got a bit of an idea how it all works.
Or just start again... I haven't ever install TKL to real hardware (only ever VMs) so I haven't ever touched the partitioning, but perhaps it's easier to just start with a clean HDD and create a TKL partition as big as you want, straight off the bat, then partition the rest of the blank space later? TBH I don't know.