Re: Strange behavior with F40 server iso and VM

[Paolo Galtieri <pgaltieri@xxxxxxxxx>]

    I did a little more investigating by running
      fdisk -l and here is what I found on my server install:
      
      Disk /dev/nvme0n1: 400 GiB, 429496729600 bytes, 838860800 sectors
      Disk model: VMware Virtual NVMe Disk
      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: gpt
      Disk identifier: FB141BA7-BCC9-4953-85BA-9AE731D845C4
      
      Device           Start       End   Sectors  Size Type
      /dev/nvme0n1p1    2048      4095      2048    1M BIOS boot
      /dev/nvme0n1p2    4096   2101247   2097152    1G Linux extended
      boot
      /dev/nvme0n1p3 2101248 838858751 836757504  399G Linux LVM
      
      
      Disk /dev/mapper/fedora-root: 15 GiB, 16106127360 bytes, 31457280
      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
      
      It does create a 400GB partition it's just not accessible after
      boot.
      
      On the desktop install fdisk -l shows:
      
      Disk /dev/nvme0n1: 200 GiB, 214748364800 bytes, 419430400 sectors
      Disk model: VMware Virtual NVMe Disk
      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: gpt
      Disk identifier: 1ADF4978-4138-465D-A6B0-871EEAF4E90F
      
      Device           Start       End   Sectors  Size Type
      /dev/nvme0n1p1    2048      4095      2048    1M BIOS boot
      /dev/nvme0n1p2    4096   2101247   2097152    1G Linux extended
      boot
      /dev/nvme0n1p3 2101248 419428351 417327104  199G Linux filesystem
      
      So how do I access that 400 GB partition after I boot my server? 
      
      
      Paolo

On 10/12/24 18:22, Jonathan Billings wrote:

On Oct 12, 2024, at 20:17, Paolo Galtieri <pgaltieri@xxxxxxxxx> wrote:

Folks,
 this is an issue that has me frustrated.  I created a VM under VMware and VirtualBox and allocated 400GB as the disk size.  I installed the F40 server iso on the VM, and it showed the disk size as 400GB, and the install went fine.  However, when I booted the VM and looked at the disk size it was 15GB.  This happened on both VMware and VirtualBox.  I created another VM and installed MATE-F40 iso and when I check the disk size there it was in fact 400GB.  So for shits and grins I tried running VMware on Windows 11 and created a F40-server VM there and it too showed the disk size as 15GB.  Why is there this limit?  Is there anyway to make it the size I want?

If you used the Server install ISO I believe it creates a 15 GB root (/) filesystem by default, as described in the documentation:

https://docs.fedoraproject.org/en-US/fedora-server/installation/#_storage_organization

This is not a bug and not something related to your virtualization software.

-- 

Jonathan Billings

-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue