Welcome to the community forums for Theopenem. All responses are provided by other users that wish to help out. Theopenem will not respond to these posts. If you require more assistance than what the community can provide, we offer various paid support options.

Getting "Unknown error while determining volume size" error while uploading image

Support
Log in to reply
  • A

    Hi,
    I'm getting an "Unknown error while determining volume size" error while uploading the image to the Theopenem server.
    20221205_142633.jpg

    0
  • A

    Imaging LOG

    Setting webPath to http://IPAddress:8888/clientimaging/

    System Model: 20U1S06A00

    ** Looking For Active Task For 38:f3:ab:2a:d6:f3.PF2P3GA4.7885b2cc-2d47-11b2-a85c-de0c069be4ed **

    {"computerId":"false","task":"ond","taskId":null,"computerName":null}

    ...... This Computer Was Not Found

    ** Looking For Model Match Task For 20U1S06A00 **

    {"imageProfileId":null,"imageName":null,"imageProfileName":null}

    System Model: 20U1S06A00

    ** Looking For Active Task For 38:f3:ab:2a:d6:f3 **

    {"computerId":"false","task":"ond","taskId":null,"computerName":null}

    ...... This Computer Was Not Found

    ** Looking For Model Match Task For 20U1S06A00 **

    {"imageProfileId":null,"imageName":null,"imageProfileName":null}

    This Computer Is Not Registered. No Active Web Tasks Were Found For This Computer. Starting Registration.

    ** Displaying Boot Arguments **

    BOOT_IMAGE=/theopenem/5.17.3x64 ramdisk_size=156000 root=/dev/ram0 rw web=http://172.16.2.253:8888/clientimaging/ USER_TOKEN=66B96F47900D4FD9BD2E518E99520765 consoleblank=0 MAC: 38:f3:ab:2a:d6:f3
    Linux client_console 5.17.3 #1 SMP PREEMPT Thu Apr 14 12:41:19 EDT 2022 x86_64 GNU/Linux

    Boot Image Version: 1.0.1

    ** Using On Demand Mode **

    ** Creating Active Task **

    image_name=W10-test profile_id=6 pre_scripts="" before_file_scripts="" after_file_scripts="" file_copy=False sysprep_tags="" web_cancel=true task_completed_action="Reboot" image_type=Block compression_algorithm=lz4 compression_level=-1 image_server="http://172.16.2.253:8888/clientimaging/" upload_server="172.16.2.253" computer_id=-166993

    ...... Success

    ** Checking Current Queue **

    ...... Complete

    ** Verifying Image Server **

    ...... Success

    ** Looking For Hard Drive(s) **

    ...... Displaying Available Devices
    RO RA SSZ BSZ StartSec Size Device
    rw 256 512 512 0 159744000 /dev/ram0
    rw 256 512 512 0 512110190592 /dev/nvme0n1
    rw 256 512 512 2048 536870912 /dev/nvme0n1p1
    rw 256 512 512 1050624 16777216 /dev/nvme0n1p2
    rw 256 512 512 1083392 511555141632 /dev/nvme0n1p3
    rw 256 512 512 0 31331450880 /dev/sda
    rw 256 512 512 2048 31330402304 /dev/sda1
    Disk /dev/ram0: 152.35 MiB, 159744000 bytes, 312000 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

    Disk /dev/nvme0n1: 476.96 GiB, 512110190592 bytes, 1000215216 sectors
    Disk model: Micron MTFDHBA512TDV
    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: 49A1AA4F-C9EA-4E10-9EDD-41B57726FCDE

    Device Start End Sectors Size Type
    /dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
    /dev/nvme0n1p2 1050624 1083391 32768 16M Microsoft reserved
    /dev/nvme0n1p3 1083392 1000214527 999131136 476.4G Microsoft basic data

    Disk /dev/sda: 29.18 GiB, 31331450880 bytes, 61194240 sectors
    Disk model: Cruzer Blade
    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: 0x00277ce3

    Device Boot Start End Sectors Size Id Type
    /dev/sda1 * 2048 61194239 61192192 29.2G c W95 FAT32 (LBA)

    all_hard_drives: /dev/sda
    /dev/nvme0n1

    disk_label: dos /dev/sda

    disk_label: gpt /dev/nvme0n1

    partitions: /dev/nvme0n1p1
    /dev/nvme0n1p2
    /dev/nvme0n1p3

    ...... Found Drive(s)

    ...... Drive(s): /dev/nvme0n1

    ** Removing All Files For Existing Image: W10-test **

    ** Creating Image Schema **

    Current NVRAM Entries
    BootCurrent: 001F
    Timeout: 0 seconds
    BootOrder: 001F,0000,0001,0019,001A,001B,001C,001D,001E,0020,0021,0022,0023
    Boot0000* Windows Boot Manager HD(1,GPT,6f31ad6a-9dbd-4c70-bc3c-92169d3a9a36,0x800,0x100000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...d................
    Boot0001* ubuntu HD(1,GPT,6f31ad6a-9dbd-4c70-bc3c-92169d3a9a36,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
    Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
    Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
    Boot0012 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
    Boot0013 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
    Boot0014 Regulatory Information FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)
    Boot0015 ThinkShield secure wipe FvFile(3593a0d5-bd52-43a0-808e-cbff5ece2477)
    Boot0016 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
    Boot0017 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
    Boot0018 MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
    Boot0019* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
    Boot001A* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
    Boot001B* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
    Boot001C* NVMe1 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a401)
    Boot001D* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
    Boot001E* ATA HDD1 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
    Boot001F* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
    Boot0020* PXE BOOT VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
    Boot0021* LENOVO CLOUD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri(https://download.lenovo.com/pccbbs/cdeploy/efi/boot.efi)
    Boot0022 Other CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35406)
    Boot0023 Other HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f606)
    Boot0024* USBR BOOT CDROM PciRoot(0x0)/Pci(0x14,0x0)/USB(11,1)
    Boot0025* USBR BOOT Floppy PciRoot(0x0)/Pci(0x14,0x0)/USB(11,0)
    Boot0026* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
    Boot0027* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)

    Calculating volume size for /dev/nvme0n1p1
    Partclone v0.2.90 http://partclone.org
    Starting to clone device (/dev/nvme0n1p1) to image (/dev/null)
    Reading Super Block
    we need memory: 135748 bytes
    image head 4160, bitmap 131072, crc 516 bytes
    Calculating bitmap... Please wait...
    used_size:34
    volume_size:542

    Partition Volume Size
    volume_size:542

    Partition Used Size
    used_size:34
    e2fsck 1.45.5 (07-Jan-2020)
    ext2fs_check_desc: Corrupt group descriptor: bad block for block bitmap
    e2fsck: Group descriptors look bad... trying backup blocks...
    e2fsck: Invalid argument while using the backup blockse2fsck: going back to original superblock
    Error reading block 62423039 (Invalid argument). Ignore error? yes

    Force rewrite? yes

    Superblock has an invalid journal (inode 8).
    Clear? yes

    *** journal has been deleted ***

    The filesystem size (according to the superblock) is 76473440 blocks
    The physical size of the device is 4096 blocks
    Either the superblock or the partition table is likely to be corrupt!
    Abort? yes

    Error writing block 62423039 (Invalid argument). Ignore error? yes

    /dev/nvme0n1p2: ***** FILE SYSTEM WAS MODIFIED *****

    Calculating volume size for /dev/nvme0n1p2
    Partclone v0.2.90 http://partclone.org
    Starting to clone device (/dev/nvme0n1p2) to image (/dev/null)
    Reading Super Block
    we need memory: 9567440 bytes
    image head 4160, bitmap 9559180, crc 4100 bytes
    Calculating bitmap... Please wait... extfsclone.c: Couldn't find valid filesystem bitmap.

    Partition Volume Size

    Partition Used Size

    ** An Error Has Occurred **

    ...... Unkown error while determining volume size

    0
  • T

    Something bizarre going on. It seems that partclone can't determine the filesystem that is in use on the partitions. Is there anything installed on the computer that could be doing something with the partitions?

    0
  • A

    can this be an issue? Im getting "pending confirmation" status in the client computer even after approving the request
    Capture.PNG

    0
  • A

    and this is another error I got.

    ed107cda-fde1-4467-967b-421a23708bf7-image.png

    0
  • A

    @theopenem_admin any sugetions

    0
  • T

    What does your Toec client service log say?

    0