First of all, why not let the user specify the damn file system? Why must I fight with this system that apparently does not and cannot work properly on it's own?
I have a Debian 8.02 image with a single ext4 partition. Here is my fstab:
/etc/fstab: static file system information.#
Use 'blkid' to print the universally unique identifier for a device; this may be used with UUID= as a more robust way to name devices that works even if disks are added and removed. See fstab(5).#
/ was on /dev/vda1 during installation/dev/vda1 / ext4 errors=remount-ro 0 1 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/sr1 /media/cdrom1 udf,iso9660 user,noauto 0 0
I get the following output from fdisk:
fdisk -l
Disk /dev/vda: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x063db64f
Device Boot Start End Sectors Size Id Type /dev/vda1 * 2048 4192255 4190208 2G 83 Linux
I want to resize it, but I always get the message that cloudmin can't figure out the FS type. I have tried all kinds of tricks and stuff, but it just won't work. This feature is clearly horribly broken - if there were some proper documentation specifying exactly how to set up the partitions and everything it might work, but right now it's a mess and yes I am pretty upset about it. You need to do much better than this.
Comments
Submitted by yngens on Sun, 10/18/2015 - 11:26 Comment #1
If you can SSH into the system, try this http://akyl.net/easy-way-extending-linux-logical-volumes
Submitted by JamieCameron on Sun, 10/18/2015 - 22:40 Comment #2
Can you post the exact error message you are getting?
Also, does the host system that the VM is running on also support ext4 filesystems?
Submitted by quadrox on Thu, 10/22/2015 - 09:15 Pro Licensee Comment #3
The exact message I get is this:
Warning - this disk cannot be safely resized. Cloudmin does not know what type of filesystem this disk contains, and so cannot properly resize it. This is most likely because the disk is not mounted on the virtual system.
I have tried both storing the disk as .img file, and having it as logical volume.
Submitted by JamieCameron on Fri, 10/23/2015 - 21:04 Comment #4
Ok, try SSHing into your Cloudmin master system as root and running the command :
cloudmin list-disks --host your.vm.name --multilineand post the output here.
Submitted by quadrox on Sat, 10/24/2015 - 04:06 Pro Licensee Comment #5
Due to horrible formatting, I have attached the output as list-disks.txt
Submitted by quadrox on Sat, 10/24/2015 - 04:06 Pro Licensee Comment #6
Submitted by quadrox on Sat, 10/24/2015 - 04:45 Pro Licensee Comment #7
Ok, I have made some progress.
Somehow the fstab had reverted to using UUID, I fixed that and removed the cdrom drive. Now I get the output attached in list-disks-2.txt.
I no longer get a warning that it cannot recognize the file system, but when it tries to perform the resize it gives a different error:
Shutting down system .. .. done
Updating virtual disk on /dev/vg0/green_localhost_0_img .. .. update failed : No partitions were found on the disk image!
Starting up system .. .. done
After this, the disk is still not resized.
Submitted by JamieCameron on Sun, 10/25/2015 - 13:00 Comment #8
Ok, that seems like a different problem. If you SSH into the host system and run
fdisk -l /dev/vg0/green_localhost_0_img, what does it output?Submitted by quadrox on Tue, 10/27/2015 - 11:59 Pro Licensee Comment #9
I had moved the disk to a logical volume (to see if it makes a difference), so it is now placed differently. The output is attached in fdisk-l.txt
Submitted by JamieCameron on Wed, 10/28/2015 - 01:13 Comment #10
That fdisk output looks fine.
However, when you moved the disk, was this done using Cloudmin so that it is aware of the new location? If not, it certainly won't be able to resize the disk.
Submitted by quadrox on Wed, 10/28/2015 - 08:00 Pro Licensee Comment #11
Yes, it was moved with cloudmin.
I have run all diagnostic commands again to give you a consistent view of the current situation.
Submitted by quadrox on Wed, 03/28/2018 - 05:15 Pro Licensee Comment #12
Not sure what happened in the time since I created this issue, but it's working now.
Submitted by yngens on Wed, 03/28/2018 - 17:11 Comment #13
Guys, I am re-opening this not because of the reported issue itself, but because this one is listed among my issues on https://www.virtualmin.com/project/issues/user, which is really strange. Jamie, could you take a look why it's happening so?
Submitted by JamieCameron on Wed, 03/28/2018 - 23:11 Comment #14
Maybe because you commented on it? Joe, any ideas?
Submitted by yngens on Wed, 04/04/2018 - 05:50 Comment #15
Quite might be, but then commenting should not make this my issue, should it?