Imaging SSD first timer

Support
Log in to reply
  • T

    Its not going to boot if Windows was installed with Raid and now it's set to AHCI. Windows needs to be installed while the hd is set to AHCI. There isn't anything else I can do for nic. It may be better to use the WIE for this model.

    dannyneunan S 2 Replies 0
  • dannyneunan

    @theopenem_admin my image was created from a vm. I don't believe a raid was involved. So I can't use TheOpenEm on any new Dell Optiplex machines I purchase for our school system?

    0
  • T

    Was your vm legacy or efi? In your image profile, change the partition type to standard.

    dannyneunan 1 Reply 0
  • dannyneunan

    @theopenem_admin I have changed it to standard now. I do see an additional option while using the new kernel. Which option should I select here?

    74bb567e-a2ca-4231-a51a-d63f408f2d67-image.png

    0
  • T

    It looks like you cloned the image profile. You need to select the one that you changed to standard.

    dannyneunan 1 Reply 0
  • dannyneunan

    @theopenem_admin Changing it to standard did not change anything. 😞 I did go in and delete the cloned image profile.

    T 1 Reply 0
  • T

    Please post the deploy log.

    dannyneunan 1 Reply 0
  • dannyneunan

    @theopenem_admin I hope this is what you are asking for.

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

    System Model: OptiPlex 3080

    ** Looking For Active Task For b0:7b:25:09:27:91.GK2V8B3.4c4c4544-004b-3210-8056-c7c04f384233 **

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

    ...... This Computer Was Not Found

    ** Looking For Active Task For 00:24:9b:49:5b:62.GK2V8B3.4c4c4544-004b-3210-8056-c7c04f384233 **

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

    ...... This Computer Was Not Found

    ** Looking For Model Match Task For OptiPlex 3080 **

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

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

    Image Id: 4

    {"Count":"1","FirstProfileId":"4","ImageProfiles":["4 Default_LIE_Block"]}

    ** Displaying Boot Arguments **

    BOOT_IMAGE=/theopenem/5.11.10x64 ramdisk_size=156000 root=/dev/ram0 rw web=http://10.1.80.86:8888/clientimaging/ USER_TOKEN=0A0B90C47C884461896889913CF2A6D5 consoleblank=0 MAC: 00:24:9b:49:5b:62
    Linux client_console 5.11.10 #1 SMP Mon Mar 29 10:58:44 EDT 2021 x86_64 GNU/Linux

    Boot Image Version: 1.0.0

    ** Using On Demand Mode **

    ** Creating Active Task **

    image_name=ImageMaster_Windows10_2009 profile_id=4 pre_scripts="" before_file_scripts="" after_file_scripts="" file_copy=False sysprep_tags="" web_cancel=true task_completed_action="Reboot" change_computer_name=true fix_bcd=true randomize_guids=true fix_bootloader=true partition_method=dynamic custom_deploy_schema=true custom_hard_drives="" image_server="http://10.1.80.86:8888/clientimaging/" computer_id=-144068

    ...... 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 256060514304 /dev/nvme0n1
    rw 256 512 512 2048 256059448832 /dev/nvme0n1p3
    rw 256 512 512 0 15472047104 /dev/sda
    rw 256 512 512 2048 15470981632 /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: 238.49 GiB, 256060514304 bytes, 500118192 sectors
    Disk model: BC511 NVMe SK hynix 256GB
    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: 5A609CA2-8216-4563-A4B4-4584AB7D5956

    Device Start End Sectors Size Type
    /dev/nvme0n1p3 2048 500118158 500116111 238.5G Microsoft basic data

    Disk /dev/sda: 14.42 GiB, 15472047104 bytes, 30218842 sectors
    Disk model: DataTraveler 3.0
    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: 22040440-B059-478F-9D4D-023B42464BA5

    Device Start End Sectors Size Type
    /dev/sda1 2048 30218808 30216761 14.4G Microsoft basic data

    ...... Found Drive(s)

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

    ** Processing /dev/nvme0n1 **

    Get hd_schema: profileId=4&clientHdNumber=0&newHdSize=256060514304&schemaHds=&clientLbs=512

    {"BootPartition":"","Guid":"4C1882E5-2FC2-4F66-A797-6C03B5365D44","IsValid":"true","Message":null,"PartitionType":"gpt","PhysicalPartitionCount":1,"PhysicalPartitions":[{"Compression":"lz4","EfiBootLoader":"","FileSystem":"ntfs","Guid":"34803F0F-E8DD-464D-AFE1-015D044D4C0F","ImageType":"Block","Number":"3","PartcloneFileSystem":"ntfs","Prefix":null,"Type":"","Uuid":"DE480EAE480E858D","VolumeGroup":null}],"SchemaHdNumber":0,"UsesLvm":"false"}

    ...... HD Meets The Minimum Sized Required

    ** Clearing MBR / GPT **
    GPT data structures destroyed! You may now partition the disk using fdisk or
    other utilities.
    2047+0 records in
    2047+0 records out
    1048064 bytes (1.0 MB, 1.0 MiB) copied, 0.00759484 s, 138 MB/s

    ** Restoring MBR / GPT On /dev/nvme0n1 **
    2047+0 records in
    2047+0 records out
    1048064 bytes (1.0 MB, 1.0 MiB) copied, 0.0491689 s, 21.3 MB/s
    GPT fdisk (gdisk) version 1.0.4

    Caution: invalid backup GPT header, but valid main header; regenerating
    backup header from main header.

    Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
    on the recovery & transformation menu to examine the two tables.

    Warning! One or more CRCs don't match. You should repair the disk!
    Main header: OK
    Backup header: ERROR
    Main partition table: OK
    Backup partition table: ERROR

    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: damaged

    ****************************************************************************
    Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
    verification and recovery are STRONGLY recommended.

    Disk /dev/nvme0n1: 500118192 sectors, 238.5 GiB
    Model: BC511 NVMe SK hynix 256GB
    Sector size (logical/physical): 512/512 bytes
    Disk identifier (GUID): 4C1882E5-2FC2-4F66-A797-6C03B5365D44
    Partition table holds up to 128 entries
    Main partition table begins at sector 2 and ends at sector 33
    First usable sector is 34, last usable sector is 83886046
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 6134 sectors (3.0 MiB)

    Number Start (sector) End (sector) Size Code Name
    1 2048 206847 100.0 MiB EF00 EFI system partition
    2 206848 239615 16.0 MiB 0C01 Microsoft reserved ...
    3 239616 82862022 39.4 GiB 0700 Basic data partition
    4 82862080 83881983 498.0 MiB 2700

    Repairing Damaged GPT Table
    Caution: invalid backup GPT header, but valid main header; regenerating
    backup header from main header.

    Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
    on the recovery & transformation menu to examine the two tables.

    Warning! One or more CRCs don't match. You should repair the disk!
    Main header: OK
    Backup header: ERROR
    Main partition table: OK
    Backup partition table: ERROR

    ...... Complete

    ** Creating Partition Table On /dev/nvme0n1 **

    ** Deleting Existing Partitions **
    gdisk /dev/nvme0n1 &>/dev/null <<GDISK
    d
    1
    d
    2
    d
    3
    d
    4
    w
    y
    y
    q
    GDISK

    ** Partition Creation Script **
    gdisk /dev/nvme0n1 &>>/tmp/clientlog.log <<GDISK
    n
    3
    2048

    0700
    w
    y
    GDISK
    GPT fdisk (gdisk) version 1.0.4

    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present

    Found valid GPT with protective MBR; using GPT.

    Command (? for help): Partition number (1-128, default 1): First sector (34-500118158, default = 2048) or {+-}size{KMGTP}: Last sector (2048-500118158, default = 500118158) or {+-}size{KMGTP}: Current type is 'Linux filesystem'
    Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Microsoft basic data'

    Command (? for help):
    Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
    PARTITIONS!!

    Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/nvme0n1.
    The operation has completed successfully.

    ...... Success

    ** New Partition Table Is **
    GPT fdisk (gdisk) version 1.0.4

    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present

    Found valid GPT with protective MBR; using GPT.
    Disk /dev/nvme0n1: 500118192 sectors, 238.5 GiB
    Model: BC511 NVMe SK hynix 256GB
    Sector size (logical/physical): 512/512 bytes
    Disk identifier (GUID): 4C1882E5-2FC2-4F66-A797-6C03B5365D44
    Partition table holds up to 128 entries
    Main partition table begins at sector 2 and ends at sector 33
    First usable sector is 34, last usable sector is 500118158
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 2014 sectors (1007.0 KiB)

    Number Start (sector) End (sector) Size Code Name
    3 2048 500118158 238.5 GiB 0700 Microsoft basic data

    ** Restoring GUID On /dev/nvme0n1 **
    The operation has completed successfully.

    4C1882E5-2FC2-4F66-A797-6C03B5365D44

    { "Compression": "lz4", "EfiBootLoader": "", "FileSystem": "ntfs", "Guid": "34803F0F-E8DD-464D-AFE1-015D044D4C0F", "ImageType": "Block", "Number": "3", "PartcloneFileSystem": "ntfs", "Prefix": null, "Type": "", "Uuid": "DE480EAE480E858D", "VolumeGroup": null }

    ** Starting Image Download For /dev/nvme0n1p3 **

    lie_reporter 123 partclone & curl -sSk -H Authorization:NEFCNTk0NjAyQTU0NDQ5QjgzMURGMkMyQzUxMENCRjkyOTg0NjI1RDdCQjM0RTg0QTk2RUIwN0E4RjRCQTIzQQ== --data 'profileId=4&hdNumber=0&fileName=part3.ntfs.lz4' http://10.1.80.86:8888/clientimaging/GetImagingFile --connect-timeout 10 --stderr - | lz4 -d | partclone.ntfs -B -r -o /dev/nvme0n1p3
    Partclone v0.2.90 http://partclone.org
    Starting to restore image (-) to device (/dev/nvme0n1p3)
    we need memory: 560904 bytes
    image head 4160, bitmap 552644, crc 4100 bytes
    Calculating bitmap... Please wait... get device size 256059448832 by ioctl BLKGETSIZE64,
    done!
    File system: NTFS
    Device size: 18.1 GB = 4421142 Blocks
    Space in use: 15.8 GB = 3849925 Blocks
    Free Space: 2.3 GB = 571217 Blocks
    Block size: 4096 Byte
    Syncing... OK!
    Partclone successfully restored the image (-) to the device (/dev/nvme0n1p3)
    Mounting volume... OK
    Processing of $MFT and $MFTMirr completed successfully.
    Checking the alternate boot sector... FIXED
    NTFS volume version is 3.1.
    Going to un-mark the bad clusters ($BadClus)... No bad clusters...OK
    NTFS partition /dev/nvme0n1p3 was processed successfully.

    volumeMargin: 237950450688

    ** Expanding NTFS Volume on /dev/nvme0n1p3 **

    Expanding NTFS Volume To: 256048963072
    ntfsresize v2020.4.13 (libntfs-3g)
    Device name : /dev/nvme0n1p3
    NTFS volume version: 3.1
    Cluster size : 4096 bytes
    Current volume size: 18108998144 bytes (18109 MB)
    Current device size: 256059448832 bytes (256060 MB)
    New volume size : 256048960000 bytes (256049 MB)
    Checking filesystem consistency ...
    Accounting clusters ...
    Space in use : 15770 MB (87.1%)
    Collecting resizing constraints ...
    Schedule chkdsk for NTFS consistency check at Windows boot time ...
    Resetting $LogFile ... (this might take a while)
    Updating $BadClust file ...
    Updating $Bitmap file ...
    Updating Boot record ...
    Syncing device ...
    Successfully resized NTFS on device '/dev/nvme0n1p3'.

    ...... Success
    Mounting volume... OK
    Processing of $MFT and $MFTMirr completed successfully.
    Checking the alternate boot sector... FIXED
    NTFS volume version is 3.1.
    Going to un-mark the bad clusters ($BadClus)... No bad clusters...OK
    NTFS partition /dev/nvme0n1p3 was processed successfully.

    ** Restoring GUID On /dev/nvme0n13 **

    ...... part gptGUID: 34803F0F-E8DD-464D-AFE1-015D044D4C0F
    The operation has completed successfully.

    ** Updating BCD **

    Efi Boot Layout Selected

    disk_guid: 328E0667-E62C-4451-A56D-EBD15DAF83AD

    recovery_guid:

    windows_guid: 8EBCC1E2-0434-4C31-B814-2BE4D40C4FAC

    Checking if NVRAM needs updated

    No EFI System Partition Found.
    GPT fdisk (gdisk) version 1.0.4

    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present

    Found valid GPT with protective MBR; using GPT.
    Disk /dev/nvme0n1: 500118192 sectors, 238.5 GiB
    Model: BC511 NVMe SK hynix 256GB
    Sector size (logical/physical): 512/512 bytes
    Disk identifier (GUID): 328E0667-E62C-4451-A56D-EBD15DAF83AD
    Partition table holds up to 128 entries
    Main partition table begins at sector 2 and ends at sector 33
    First usable sector is 34, last usable sector is 500118158
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 2014 sectors (1007.0 KiB)

    Number Start (sector) End (sector) Size Code Name
    3 2048 500118158 238.5 GiB 0700 Microsoft basic data

    ** Closing Active Task **

    0
  • T

    @dannyneunan said in Imaging SSD first timer:
    That's correct. Is this the newest log? Your partition_method says dynamic instead of standard.

    partition_method=dynamic

    dannyneunan 1 Reply 0
  • dannyneunan

    @theopenem_admin Let me try it one more time. I will post the newest log when it finishes.

    dannyneunan 1 Reply 0
  • dannyneunan

    @dannyneunan I ran it again and I see the same thing you do. Where exactly do I change the image profile you mentioned earlier? Is there more than one place to change it?

    dannyneunan 1 Reply 0
  • dannyneunan

    @dannyneunan I did not change it in this location last time. Is this what I am missing?

    72967225-3020-4ed1-90fe-f22edcfda93f-image.png

    0
  • T

    Yes, your picture is the correct location. Make sure you check the correct windows partition after you select standard.

    dannyneunan 1 Reply 0
  • dannyneunan

    @theopenem_admin Do you recommend one over another for these Dells?

    0
  • T

    Partition method?

    dannyneunan 1 Reply 0
  • dannyneunan

    @theopenem_admin Good news. It worked. I selected EFI partition. That is great.

    0
  • T

    It isn't a model issue. It's an efi / legacy issue. Your original image was legacy so when it's deployed, Theopenem configures the machine for legacy to match the original. But since it's an efi machine that's not going to work. Setting the partition method to standard tells Theopenem to ignore the original image and match the destination machine type. That's how a single image can be used for both efi / legacy, using the standard partition type.

    0
  • dannyneunan

    @theopenem_admin Have you had any luck creating a new kernel? Thanks

    0
  • S

    @theopenem_admin I also have a few different Dell machines that have this new realtek family of NICs. Will a new kernel be possible?

    0
  • dannyneunan

    I ended up building a WinPE bootable usb drive and using it for imaging. It is not ideal but it works.

    0