0xc00000e



  • Hello i come back again with a new partionning problem

    I made a capture of a dell computer, at the end of the capture i’ve got this error message :

    " 0xc00000e boot selection failed because a required device is inaccessible".

    Then i try to deploy the image to see if it solve the problem and the the computer stuck on “booting…”

    I think it’s a partitionning problem as i had before.
    [https://forums.fogproject.org/topic/6620/fog-restore-only-one-partition/](link url)
    Here is informations about partitions

    ls -al /home/images/GEII101/
    total 19882180
    drwxrwxrwx  2 root root        4096 avril  6 08:58 .
    drwxrwxrwx 10 root root        4096 avril  6 08:58 ..
    -rwxrwxrwx  1 root root           2 avril  6 08:19 d1.fixed_size_partitions
    -rwxrwxrwx  1 root root       32256 avril  6 08:22 d1.mbr
    -rwxrwxrwx  1 root root         365 avril  6 08:22 d1.minimum.partitions
    -rwxrwxrwx  1 root root          62 avril  6 08:22 d1.original.fstypes
    -rwxrwxrwx  1 root root           0 avril  6 08:19 d1.original.swapuuids
    -rwxrwxrwx  1 root root       78748 avril  6 08:22 d1p1.img
    -rwxrwxrwx  1 root root  6140950340 avril  6 08:32 d1p2.img
    -rwxrwxrwx  1 root root 14217811629 avril  6 08:58 d1p3.img
    -rwxrwxrwx  1 root root         512 avril  6 08:58 d1p4.ebr
    -rwxrwxrwx  1 root root         512 avril  6 08:22 d1p5.ebr
    -rwxrwxrwx  1 root root      428296 avril  6 08:58 d1p5.img
    -rwxrwxrwx  1 root root         365 avril  6 08:19 d1.partitions
    
    cat /home/images/GEII101/d1.minimum.partitions
    label: dos
    label-id: 0x73ee0dbc
    device: /dev/sda
    unit: sectors
    
    /dev/sda1 : start=          63, size=       80262, type=de
    /dev/sda2 : start=       81920, size=    16748252, type=7, bootable
    /dev/sda3 : start=    18395136, size=    75761314, type=7
    /dev/sda4 : start=   526211072, size=   450562048, type=f
    /dev/sda5 : start=   526213120, size=   450560000, type=7
    
    cat /home/images/GEII101/d1.original.fstypes
    /dev/sda2 ntfs
    /dev/sda3 ntfs
    /dev/sda4 imager
    /dev/sda5 ntfs
    
    
    cat /home/images/GEII101/d1.partitions
    label: dos
    label-id: 0x97be5b6a
    device: /dev/sda
    unit: sectors
    
    /dev/sda1 : start=          63, size=       80262, type=de
    /dev/sda2 : start=       81920, size=    18313216, type=7, bootable
    /dev/sda3 : start=    18395136, size=   507815936, type=7
    /dev/sda4 : start=   526211072, size=   450562048, type=f
    /dev/sda5 : start=   526213120, size=   450560000, type=7
    

  • Developer

    @plegrand Any news on this?


  • Developer

    @plegrand Can you please try the known methods of fixing bootup errors by booting the windows recovery DVD. Get to the command prompt and run chkdsk /f /x /r C:. Then reboot and see if you have any changes. If that does not work then please boot the recovery DVD and run bootrec /fixmbr - again reboot to check if this fixed the error. If not try bootrec /fixboot, reboot, check. Then try bootrec /rebuildbcd. Please make sure you reboot in between trying those commands to see which of those did/didn’t work. We might get an idea of what is wrong this way.



  • Could you please do another debug deploy (Multiple partition - single disk) and keep your eyes open for Clearing part /dev/sdaX messages

    Actually i use this kind of image :
    default: Windows 7
    Multiple Partition Image - Single Disk (Not Resizable)
    Everything

    7104 version
    then i made a deploy task debug mode. I didnt see any Clearing part /dev/sdaX messages
    and again the 0xc00000e error

    i upgraded to 7196 version, i made the deploy task debug mode again
    Same problem (0xc00000e error)



  • @plegrand said in 0xc00000e:

    @Sebastian-Roth said in 0xc00000e:

    Nevertheless you can always try non-resizable. Just create a new image definition and upload from that client again. The non-resizable upload does less magic and should not cause any error on the machine. Then try deploy and see if it works.

    what i have to choose between
    Multiple Partition Image - Single Disk (Not Resizable) - (2)
    and
    Multiple Partition Image - All Disks (Not Resizable) - (3)
    ?

    Then i choose " Multiple Partition Image - Single Disk (Not Resizable) - (2)"
    Capture works fine
    Deploy fail with 0xc00000e



  • @Sebastian-Roth said in 0xc00000e:

    Nevertheless you can always try non-resizable. Just create a new image definition and upload from that client again. The non-resizable upload does less magic and should not cause any error on the machine. Then try deploy and see if it works.

    what i have to choose between
    Multiple Partition Image - Single Disk (Not Resizable) - (2)
    and
    Multiple Partition Image - All Disks (Not Resizable) - (3)
    ?




  • Developer

    @plegrand I did play with the partition stuff you gave me once again and I cannot reproduce the issue. Well I don’t have all the data you have on your partitions and that might be the difference. From what I can see and test the partition tables are not being screwed on upload but I don’t know what you have in those partitions…

    Possibly you can give me some more information about what is stored on the partitions?

    • sda1 (type dell utility, size 40MB, used ~1MB): possibly recovery tools??
    • sda2 (type ntfs, size 8.8GB, used ~7-8GB): maybe recovery data??
    • sda3 (type ntfs, size 242GB, used ~15-20GB): windows?
    • sda5 (type ntfs, size 215GB, used ~1MB): intended for user data?

    Please open disk management in windows to see if you can match my guesses and tell me if I stand correct.

    Nevertheless you can always try non-resizable. Just create a new image definition and upload from that client again. The non-resizable upload does less magic and should not cause any error on the machine. Then try deploy and see if it works.



  • @Sebastian-Roth

    I launch sfdisk command before capture but for the moment i cant do the capture itself because i need this computer
    Then i’m going to install what i need on this computer, make a ghost image to be sure and then after test capture and deploy with fog.
    ok ?

    sfdisk -d /dev/sda
    label: dos
    label-id: 0x97be5b6a
    device: /dev/sda
    unit: sectors
    
    /dev/sda1 : start=          63, size=       80262, type=de
    /dev/sda2 : start=       81920, size=    18313216, type=7, bootable
    /dev/sda3 : start=    18395136, size=   507815936, type=7
    /dev/sda4 : start=   526211072, size=   450562048, type=f
    /dev/sda5 : start=   526213120, size=   450560000, type=7
    


  • @Sebastian-Roth i’ll do that tomorrow morning with picture or copy paste from ssh session
    thanks again for your help


  • Developer

    @plegrand You have the most interesting partition layouts in the universe. Recovery and extended partition. Let’s see if we can still handle this. I did some tests with the information you gave and upload is working for me without corrupting the partition table on the source system (your’s was corrupted if I understood correctly). So what I need you to do is to get the machine in the original state (you have done this already as I know from the chat!), then schedule a debug upload task and run sfdisk -d /dev/sda. Please take a picture of the screen because I need the exact numbers! If those numbers are different from what you posted as d1.partitions then you can just stop here and wait till I have figured it out. But if the numbers you see (again - please take a picture so we can check as well!) are exactly the same as in d1.partitions then you need to run capture (command fog) and check output of sfdisk -d /dev/sda right after capture has finished to see if it is corrupted again and possibly why (take a picture and post here!).




Log in to reply
 

452
Online

39.3k
Users

11.0k
Topics

104.6k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.