Deploying FOG in a raw SSD disk



  • Hi, guys!

    I have several computers that had SSD issues, forcing assistance to change them by newer, raw disks.
    Each computer has two-disks (sda-SSD 100Gb, sdb-SATA 500Gb). Only SSD was changed.

    So I cannot deploy image on them due to it.

    That’s the classical error message:

    Image store corrupted, unable to locate MBR, no file found (MBRFileName)
    

    Other message I got (in other moment):

    Error trying to restore GPT partition tables (restorePartitionTablesAndBootLoaders)
    

    I saw some ancient issues opened here, but nothing of them conclusive.

    As workaround, I make a clear-Windows 10 formatting; after that, I can deploy successfully on them.
    Do we have any updated news about it?


  • Developer

    @Redbob Hmm, that’s interesting. Have your tried in non-debug mode again? Failure or does it run through as well? What changed in between? Non-debug and debug mode are not any different while the later one only waits for your confirmations and if variables are set will print more debug information.



  • @Sebastian-Roth, it’s funny. Fog deployed successfully all partitions, simply pressing ENTER after each breakpoint.


  • Developer

    @Redbob Sorry I wasn’t specific enough. Now on the last screen you posted we see the blue command shell waiting for you to enter a command. Type in fog and hit ENTER. That will start the task in debug mode and you need to confirm every step. Having set the mentioned Host Kernel Args we should see helpful information at the point where it hits the error. Take a picture of that error screen and post here.



  • @Sebastian-Roth That’s what I did.
    Follows Settings you suggested:
    0_1537215931585_Seleção_006.png
    After usual messages, these are what I get. Here are the images:
    0_1537215659192_IMG_20180917_160534805.jpg
    0_1537215678783_IMG_20180917_160539989_HDR.jpg
    0_1537215702615_IMG_20180917_160603030_HDR.jpg


  • Developer

    @Redbob I was asking you to add the Host Kernel Args and deploy again till it fails with one of the errors. Then take a picture or copy text output here.



  • @Sebastian-Roth Follows here:

    Below is a variable dump from FOG
    osid=9
    osname=Windows 10
    mbrfile=
    type=down
    storage=172.24.3.144:/images/
    img=PositivoD535Win10A8
    imgType=mpa
    imgFormat=0
    imgPartitionType=All
    disks=/dev/sda /dev/sdb
    hd=/dev/sda
     * Press [Enter] key to continue
    
    [Tue Sep 11 root@fogclient /]#
    

    Typing fdisk -l, we have:

    Disk /dev/sda:119.2 GiB, 128035676160 bytes, 250069680 sectors
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/physical): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x00000000
    
    Device     Boot Start       End   Sectors  Size Id Type
    /dev/sda1           1 500118191 500118191 238.5 ee GPT
    
    
    Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 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
    
    

  • Developer

    @Redbob FOG web UI -> Hosts -> select the host you want and scroll a little down till you find the field called “Host Kernel Args” -> put in isdebug=yes ismajordebug=1 and save.



  • @Sebastian-Roth said in Deploying FOG in a raw SSD disk:

    ismajordebug=1

    @Sebastian-Roth, where will I add these Host Kernel Args?


  • Developer

    @Redbob Please add the following to the Host Kernel Args: isdebug=yes ismajordebug=1 and then deploy to that machine again. Take pictures of the messages on screen and post here.


 

567
Online

5.4k
Users

12.6k
Topics

118.9k
Posts