Windows 10 - Image upload - sectorsize error



  • This is the best pic I could get, but here are some errors it’s spitting out.

    0_1453488623324_image1.PNG

    *EDITSVN 4696 => I just updated to SVN4699 and it did the same thing
    ubuntu 13.10
    Single-Disk Resizable image
    UEFI non secure boot
    windows 10 education edition (64bit)



  • @Tom-Elliott
    Yep no worries! Sorry… You fixed the initial problem. It did upload.


  • Senior Developer

    @GFm Don’t be worried about the back to back posts. You’re trying to help us figure out where a problem is.
    I would like, if you’d be so kind, for you to start a new thread as what you’re seeing now is NOTHING related to sectorsize and weird sed inaccuracies.



  • @Tom-Elliott

    Here it is after the quick-image… sorry so many posts.
    0_1453731802204_IMG_5463.JPG



  • @Tom-Elliott
    I booted back to my win10 flash drive and saw this…
    0_1453731527993_IMG_5462.JPG

    So it must have deleted everything? I then went and quick-imaged it with the image I just uploaded and it went back through, but when it started to boot it said…

    “The Boot Configuration Data for your PC is missing or contains errors.”



  • @Tom-Elliott
    I just updated and it seemed to upload fine. Upon reboot, it says no bootable devices now. Any ideas?

    Thanks!


  • Senior Developer

    @Quazz No clue. Maybe a picture of the first and second go arounds can help?


  • Moderator

    @Tom-Elliott Then I’m not sure what happened. How come the first time it stops the process entirely when it fails to resize the fat32 partition (claiming the mbr partition is too large and needs to be resized), but then when I reboot and try again it works fine?

    It’s no big deal since it works the second time around, just want to know what’s going on. ;)


  • Senior Developer

    @Quazz I don’t think that’s the case at all.

    fat32 has no support for resizing in the init’s.

    The way we perform resizing is per partition, so what you see as fail on one, and success on another is only from the next partition. If you had 4 fat32 partitions on the disk, you’d likely see the failure on all four partitions.


  • Moderator

    I had this same issue and after updating it seems to work for me. I was busy switching all my images to single disk resizable, so this is great timing for me ;)

    Although I do have to try it twice, it fails on resizing the first partition (fat32 UEFI partition), but then on second try it always works. I’m guessing it DOES succeed on resizing the partition, but doesn’t realize it for some reason!



  • @Tom-Elliott
    I will update and try on Monday. Thanks for the info!


  • Senior Developer

    @GFm I finally got my own system to test this. (VM with GPT layout) and i can say, with reasonable certainty, this should now operate too.

    Apparently, upload resize of GPT structures was broken. This same methodology (only reversed) was also used for download. The escaping wasn’t pretty either, but that appears to be good now too. I don’t know how viable this will be for non-resizable images, but with any luck this doesn’t require as much “thought” to go in.

    When you have free time, please test again and let me know.

    Thank you very much for at least reporting and getting us to look at the source. It was a fun time.


  • Moderator

    @Developers This output looks strikingly similar to errors I have here using UEFI, resizable disks:

    https://forums.fogproject.org/topic/6482/acer-aspire-e-11-es1-111m-p2yu/21?page=1

    I think these two threads have a common problem.


  • Moderator

    @GFm One thing I see missing from your post is what hardware are you trying to upload from? Make and model, please.


  • Senior Developer

    I have not encountered these issues before :(

    However, I do know where they’re coming from.

    Our issue is apparently the checks for sgdisk need a TON more refinement, which I hope you don’t mind me working on getting from you, maybe next week?

    I hope so…


Log in to reply
 

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