Deploy Image ERROR

Support
Log in to reply
  • S

    @theopenem_admin Ubuntu was preinstalled by Dell. Good approach. Many Thanks!

    0
  • T

    If you update your schema to this, it should work.

    {"harddrives": [ {"name":"/dev/nvme0n1","size":"500118192","table":"gpt","boot":"","lbs":"512","pbs":"512","guid":"B38686FA-414F-4EA0-914B-BB040B4761F6","active":"true","partitions": [ {"number":"1","start":"2048","end":"206847","size":"204800","volumesize":"101","type":"","usedmb":"31","fsType":"vfat","fsid":"EF00","uuid":"4200-94A7","guid":"18D02F59-F2AD-4643-BFDA-877F8331EF4A","active":"true","customsize":"","customsizeunit":"","forcefixedsize":"false","prefix":"p","efibootloader":"Windows Boot Manager#\\EFI\\Microsoft\\Boot\\bootmgfw.efi","volumegroup": { } },{"number":"2","start":"206848","end":"239615","size":"32768","volumesize":"16","type":"","usedmb":"16","fsType":"","fsid":"0C01","uuid":"","guid":"1ACC9C3A-932F-48DB-AC8D-390BA8CA4483","active":"true","customsize":"","customsizeunit":"","forcefixedsize":"false","prefix":"p","efibootloader":"","volumegroup": { } },{"number":"3","start":"239616","end":"499060436","size":"498820821","volumesize":"27670","type":"","usedmb":"26864","fsType":"ntfs","fsid":"0700","uuid":"A6A401E7A401BAB7","guid":"C8F26185-9F11-40CF-A7C9-04EC581155A0","active":"true","customsize":"","customsizeunit":"","forcefixedsize":"false","prefix":"p","efibootloader":"","volumegroup": { } },{"number":"4","start":"499060736","end":"500115455","size":"1054720","volumesize":"515","type":"","usedmb":"439","fsType":"ntfs","fsid":"2700","uuid":"A2D6BC09D6BBDC2B","guid":"CE58390B-CF72-4E2F-9391-3311E39E21D2","active":"true","customsize":"","customsizeunit":"","forcefixedsize":"false","prefix":"p","efibootloader":"","volumegroup": { } }] }] }

    I've manually removed the ubuntu info from the schema. Find your image location in your filesystem, find the schema file, delete everything in it and replace with above.

    0
  • S

    @theopenem_admin The image was recreated today. The download still does not work. The error message is identical. The log file for upload is attached.

    N001_02-19-2021_12_08-onddeploy.txt

    S 1 Reply 0
  • S

    @sesam Thats the Upload-Log!

    DESKTOP-87D3BNC-upload.txt

    Ok, just discovered that Ubuntu is still showing up. Will be checked again.

    S 1 Reply 0
  • S

    @sesam Sorry, that was the old upload log. Here is a new upload log without Ubuntu with the same Error.

    DESKTOP-87D3BNC-upload (2).txt

    0
  • T

    You still have 2 boot loaders listed even though Ubuntu is gone. I can make some changes so that only the first one is used if multiple are found, but that will need to wait until the next release. If you use the schema I provided it will work fine.

    0
  • T

    This should be fixed now with this commit.
    https://github.com/theopenem/Toems-MSI/commit/6bdc61fbba345519e55cfe206fc9380d4702af49

    If you want to download that file and ovewrite the existing, it should fix your issue, otherwise it will be in the next release.

    0
  • S

    @theopenem_admin The accumulation of boot loaders is inexplicable. We therefore set up a brand new notebook: After deleting all partitions, installed Win10. Uploaded the image and successfully installed it on a new client. An update of the image that had already been carried out also worked without any problems and could be distributed. The upload log is attached.

    Thank you for your support. In the next step, we test the distribution of the images via PXE.

    DESKTOP-TSO39GK-upload.txt

    0
  • T

    I've added another commit for this issue.

    https://github.com/theopenem/Toems-MSI/commit/0111e90040ed8ce1ce92a2c2494375b4f27cbb0a

    Again, this will be in the next release.

    S 1 Reply 0
  • S

    @theopenem_admin Thanks for the new release. In the meantime, we were able to successfully download the image of 20 Dell Latitude 3150s via PXE.

    It was noticed here that the image is very large (240 GB). However, this jump did not show up until a rollback software was installed: Reboot RX. Could it be related? Tomorrow I will upload the upload log file here.

    S 1 Reply 0
  • S

    @sesamAs already mentioned, the image is very large and covers the entire size of the hard disk. Could this be related to the installed rollback solution "Remote RX". Here is the upload log file.

    DESKTOP-TSO39GK-ondupload.txt

    0
  • T

    From the log you can see the partition is uploaded as raw instead of ntfs, that why it's so large. This is almost certainly because of the rollback software. It's preventing the filesystem from being read as ntfs.

    S 1 Reply 0
  • S

    @theopenem_admin Thanks for the fast respond. Currently only 5 devices can download the image at the same time. Can this limit be controlled?

    0
  • T

    It is set in your com server imaging settings. Max client connections.

    S 1 Reply 0
  • S

    @theopenem_admin Perfect!

    Is there a way to tell the devices to shut down after the image download.

    0
  • T

    That's under the image, then image profiles, task options, task completed action

    S 1 Reply 0
  • S

    @theopenem_admin Great. Is there a donation box somewhere where we can deposit something?

    0
  • T

    https://theopenem.com/donate/

    0
  • T

    Much appreciated!

    0
  • G

    I am having this same issue on a Dell Latitude 5520 Laptop. How can I see the NVRAM Entries and Edit them to remove the Dual boot entries. I have reloaded the OS from a standard Windows ISO and cleared everything I can get to but I am still not getting a valid upload the files all come over but no Schema. The lag is showing more Partitions than I can see in Windows.

    Thanks

    Disk /dev/nvme0n1: 476.96 GiB, 512110190592 bytes, 1000215216 sectors
    Disk model: PM991a NVMe Samsung 512GB
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 16384 bytes / 131072 bytes
    Disklabel type: gpt
    Disk identifier: C3D77BEF-617D-4E5D-886E-EFBDF0C46A6E

    Device Start End Sectors Size Type
    /dev/nvme0n1p1 2048 206847 204800 100M EFI System
    /dev/nvme0n1p2 206848 239615 32768 16M Microsoft reserved
    /dev/nvme0n1p3 239616 999189207 998949592 476.3G Microsoft basic data
    /dev/nvme0n1p4 999190528 1000212479 1021952 499M Windows recovery environment

    Current NVRAM Entries
    BootCurrent: 0001
    Timeout: 5 seconds
    BootOrder: 0005,0001,0002,0000
    Boot0000* UEFI PM991a NVMe Samsung 512GB S65ZNE1NC08267 1 HD(1,GPT,b3752689-2d60-44ff-86c5-564c2fa70b84,0x800,0x32000)/File(\EFI\Boot\BootX64.efi)N.....YM....R,Y.
    Boot0001* ONBOARD NIC (IPV4) PciRoot(0x0)/Pci(0x1f,0x6)/MAC(34735ab08a7a,0)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.
    Boot0002 ONBOARD NIC (IPV6) PciRoot(0x0)/Pci(0x1f,0x6)/MAC(34735ab08a7a,0)/IPv6([::]:<->[::]:,0,0)N.....YM....R,Y.
    Boot0005* Windows Boot Manager HD(1,GPT,b3752689-2d60-44ff-86c5-564c2fa70b84,0x800,0x32000)/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.}...a................
    The protective MBR's 0xEE partition is oversized! Auto-repairing.

    0