• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. glucas
    3. Topics
    G
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 6
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by glucas

    • G

      "Resizing extfs volume…done" but system partition not expanded to disk size

      FOG Problems
      • • • glucas
      4
      0
      Votes
      4
      Posts
      491
      Views

      G

      New tests:

      I deploy myImageV1 on my test workstation with FOG 1.5.9 + init.xz from 2020 (see my previous post) Boot my test workstation on a Ubuntu LiveUSB to change logical partition (sda2) into primary one with fixparts + resize partition with gparted + fsck + grub-install Modify what I want on the system (do system updates, modify the content of a configuration file) Capture from my test workstation to myImageV2 (with FOG 1.5.9 + init.xz from 2020) Deploy my new myImageV2 to my test workstation (with FOG 1.5.9 + init.xz from 2020) The partition is properly expanded

      .
      AMO, the logical partition (sda2) confuses / puzzles partclone (or an another piece of software).

      My new myImageV2structure:

      $ ls -lh /images/myImageV2 total 53G -rwxrwxrwx 1 root root 2 Apr 7 12:58 d1.fixed_size_partitions -rwxrwxrwx 1 root root 0 Apr 7 12:59 d1.has_grub -rwxrwxrwx 1 root root 1.0M Apr 7 12:59 d1.mbr -rwxrwxrwx 1 root root 208 Apr 7 12:59 d1.minimum.partitions -rwxrwxrwx 1 root root 16 Apr 7 12:58 d1.original.fstypes -rwxrwxrwx 1 root root 0 Apr 7 12:58 d1.original.swapuuids -rwxrwxrwx 1 root root 1.7K Apr 7 12:59 d1p1.img -rwxrwxrwx 1 root root 53G Apr 7 13:31 d1p2.img -rwxrwxrwx 1 root root 208 Apr 7 12:58 d1.partitions $ cat /images/myImageV2/d1.fixed_size_partitions 1 $ cat /images/myImageV2/d1.minimum.partitions label: dos label-id: 0x78c7d5cb device: /dev/sda unit: sectors sector-size: 512 /dev/sda1 : start= 2048, size= 1048576, type=b, bootable /dev/sda2 : start= 1050624, size= 278817898, type=83 $ cat /images/myImageV2/d1.original.fstypes /dev/sda2 extfs $ cat /images/myImageV2/d1.partitions label: dos label-id: 0x78c7d5cb device: /dev/sda unit: sectors sector-size: 512 /dev/sda1 : start= 2048, size= 1048576, type=b, bootable /dev/sda2 : start= 1050624, size= 499067392, type=83

      After the deployment of my new myImageV2 (all is fine):

      root@testwks:~# fdisk -lu /dev/sda Disk /dev/sda: 238,49 GiB, 256060514304 bytes, 500118192 sectors Disk model: SK hynix SC311 S Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x78c7d5cb Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 1050623 1048576 512M b W95 FAT32 /dev/sda2 1050624 500118015 499067392 238G 83 Linux root@testwks:~$ parted /dev/sda print Model: ATA SK hynix SC311 S (scsi) Disk /dev/sda: 256GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 538MB 537MB primary fat32 boot 2 538MB 256GB 256GB primary ext4 root@testwks:~# df -h / Filesystem Size Used Avail Use% Mounted on /dev/sda2 234G 123G 100G 56%
    • G

      Solved Fog 1.5.4: "wake" feature doesn't send Magic Packet when "deploy" feature does

      FOG Problems
      • • • glucas
      4
      0
      Votes
      4
      Posts
      591
      Views

      I

      Just for notice,
      I’m using Fog 1.5.4 normally with ubuntu 16.04 and this function is working fine. Both this option you mentioned and the option to go in the option “power management” work the same.

      Best regards, Igor.

    • 1 / 1