Capture Ubuntu 20.04 just free diskspace


  • Hello,

    I capture a physical Ubuntu 20.04 Server.
    There is a 1 TB HDD, which are in different Partition´s.

    Now I capture the PC and set the compression very high, to save diskspace on the FOG server.

    But he show me for /dev/sda3 while capturing:
    Device size 566GB
    Space in use: 566GB
    Free space: 0 Byte

    And it takes hours to capture it.

    Is it sure, that he just capture just the used space? Because in this partition are just around 10GB used.

    This is the logical group and logical volume from Ubuntu 20.04

    Filesystem                         Size  Used Avail Use% Mounted on
    udev                               3.8G     0  3.8G   0% /dev
    tmpfs                              779M  1.4M  778M   1% /run
    /dev/mapper/ubuntu--vg-ubuntu--lv  520G  6.9G  492G   2% /
    tmpfs                              3.9G     0  3.9G   0% /dev/shm
    tmpfs                              5.0M  4.0K  5.0M   1% /run/lock
    tmpfs                              3.9G     0  3.9G   0% /sys/fs/cgroup
    /dev/sda2                          398G  201M  378G   1% /boot
    /dev/loop0                          56M   56M     0 100% /snap/core18/1944
    /dev/loop3                          70M   70M     0 100% /snap/lxd/19032
    /dev/loop5                          32M   32M     0 100% /snap/snapd/10707
    /dev/loop1                          56M   56M     0 100% /snap/core18/1932
    /dev/loop4                          32M   32M     0 100% /snap/snapd/10492
    /dev/loop2                          68M   68M     0 100% /snap/lxd/18150
    tmpfs                              3.9G  5.6M  3.8G   1% /opt/omd/sites/monitoring/tmp
    tmpfs                              779M     0  779M   0% /run/user/1000
    
    

    Thank you!


  • @sebastian-roth Hi Sebastian,

    thank you!

    Well, the 3 partitions are because of the Ubuntu software Raid.

    I need the Raid to prevent system halt, because the server is not local monitoring. so no one will check if the HDD goes failed.

    I finish my setup and try to capture … as long he copy 1:1 the HDD for the backup its fine

  • Senior Developer

    @seppim said in Capture Ubuntu 20.04 just free diskspace:

    The Raid I need when a disk get failure (not so unusual)

    If the disk dies you hopefully have a backup of the data as well as the FOG image to deploy that to a fresh disk in a few minutes.

    Not saying that RAID is useless. Not at all. There are setups where RAID is great. But with FOG it’s not as simple if you want to use such things.

    The setup as you have it now seems to be spread across three MD/RAID containers. I have no idea how to handle that in FOG. Simply setting host primary disk will probably not work.

    I have not played with RAID setups yet and so this is just from the top of my head. Maybe there are other users with more insight into that topic. But I just want to give you hints trying to make this easier for you.


  • @sebastian-roth said in Capture Ubuntu 20.04 just free diskspace:

    @seppim said in Capture Ubuntu 20.04 just free diskspace:

    Host Primary Disk: /dev/md126

    This might be specific to Intel (software) RAID, but I am not sure. Why do you need to use a complex setup with LVM or RAID?

    Well, the LVM I dont need and already deleted.
    The Raid I need when a disk get failure (not so unusual)

    I finish setuping the Ubuntu Server and try then again to capture.

  • Senior Developer

    @seppim said in Capture Ubuntu 20.04 just free diskspace:

    Host Primary Disk: /dev/md126

    This might be specific to Intel (software) RAID, but I am not sure. Why do you need to use a complex setup with LVM or RAID?


  • @sebastian-roth Hi Sebastian,

    I made a data backup and install Ubuntu 20.04 new. This time with Ubuntu Software Raid 1 and no LVM.

    When I start capture he throws the error: no resizeable disks where found.
    I added this to my host:

    Host Kernel Arguments: mdraid=true
    Host Primary Disk: /dev/md126
    

    This is my system:

    cat /proc/mdstat
    Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
    md0 : active raid1 sdb2[1] sda2[0]
          1046528 blocks super 1.2 [2/2] [UU]
    
    md2 : active raid1 sdb4[1] sda4[0]
          967189504 blocks super 1.2 [2/2] [UU]
          [=====>...............]  resync = 29.8% (288817088/967189504) finish=83.6min speed=135156K/sec
          bitmap: 7/8 pages [28KB], 65536KB chunk
    
    md1 : active raid1 sda3[0] sdb3[1]
          8379392 blocks super 1.2 [2/2] [UU]
    
    unused devices: <none>
    

    Are this not resizeable or did I need to change the host settings?


  • @sebastian-roth Hi Sebastian,

    Or did you just blindly skip through the partition setup when installing Ubuntu.
    Yes 🙂

    Well, at the end he finished the capture … but seems the image on the fog server ist not really huge. I set compression to 20!
    Size 4.5GB on FOG Server

    Yes, the boot Partition is much to big. This happen, because:

    • installed Ubuntu Server 20.04 in Virtual Box (HDD 10GB)
    • deploy later to physical maschine (HDD 1000GB)
    • he resize the first? partition to maximum (boot)
    • LVM keep size (9GB)

    I change the size of the LVM… but I do this again … Boot Partition I need just 1GB and the rest I added to the LVM.

    I deploy now back the image (before 1HDD, now 2HDD in Raid1) and seems the LVM disadvantage ist “just” the time while capture/deploy

  • Senior Developer

    @seppim Your Ubuntu install was setup with LVM but FOG does not support capturing the filesystem within the LVM yet. So FOG will capture as RAW - takes very long and image files in FOG server is huge.

    Do you need the LVM setup? Or did you just blindly skip through the partition setup when installing Ubuntu.

    The other question arising is, why would /boot have to be 398 GB? That doesn’t make sense at all.

345
Online

8.3k
Users

15.1k
Topics

142.0k
Posts