Clonezilla failing on new systems with 7th generation Intel processors


Recommended Posts

Hi guys, Clonezilla is failing to create an image of any laptop or desktop that has a new 7th generation Intel processor. Any ideas? It works on anything else I throw at it. It appears to be an issue with how the partitions are setup on these new systems. Thanks.

 

 

 

 

20170912_103847.jpg

Edited by sks447

Not sure what the processor has to do with the partitions....

 

Only thing I see is this and it's related to graphics card, so appears different that your issue.

https://sourceforge.net/p/clonezilla/discussion/Clonezilla_live/thread/05295651/?limit=25

 

Have you tried fresh format and reinstall using one format.  GPT or MBR.

 

  On 18/09/2017 at 01:17, farmeunit said:

Not sure what the processor has to do with the partitions....

 

Only thing I see is this and it's related to graphics card, so appears different that your issue.

https://sourceforge.net/p/clonezilla/discussion/Clonezilla_live/thread/05295651/?limit=25

 

Have you tried fresh format and reinstall using one format.  GPT or MBR.

 

Expand  

The part where I get the error is the very last step before it grabs the image. The user in the graphics thread wasn't even able to boot to clonezilla. The partition error just happens to only appear on systems with the newer processors. I have tried an newly formatted hard drive and the error is the same. Somehow Clonezilla reads MBR and GPT and it gets messed up. Very odd issue. Thanks for the reply.

We disable UEFI and use Legacy boot for all our imaging right now.  I want to start using UEFI, but haven't had time to work on it.  If you disable Secure Boot and UEFI, what happens?

  On 18/09/2017 at 21:06, farmeunit said:

We disable UEFI and use Legacy boot for all our imaging right now.  I want to start using UEFI, but haven't had time to work on it.  If you disable Secure Boot and UEFI, what happens?

Expand  

Same thing, you have to disable UEFI just to get into Clonezilla.

Hello,

You might want to try using the amd64 version, as those 7th generation Intel processors and chipsets may be doing something that the compiler used to make those i386/686 builds does not like, at a guess.

 

Regards,

 

Aryeh Goretsky

 

  On 20/09/2017 at 06:28, goretsky said:

Hello,

You might want to try using the amd64 version, as those 7th generation Intel processors and chipsets may be doing something that the compiler used to make those i386/686 builds does not like, at a guess.

 

Regards,

 

Aryeh Goretsky

 

Expand  

Great idea, i'll check it out. Thanks!

This topic is now closed to further replies.
  • Posts

    • Another reason to stick with Firefox
    • Yes, the Control Pannel issue has been fixed. As I ask when people claim it hasn't, can you name a single thing in Windows 11 that can only be done by opening Control Panel? Your comment about Error 0x80070643 is so asinine that I debated if you were worth a reply, but here I am. The article mentioned a VERY specific issue with the WinRE partition size being too small in Windows 10 and preventing updates from being installed unless you reinstalled or manually fixed it. That issue does not exist on Windows 11, period. To point to random issues with Windows updates on 11 that don't affect everyone and don't involve that issue is being dishonest. Had the article said "Issues with updates, such as..." then I'd agree with you, but it didn't, it simply mentioned that one specific issue, which despite your claim, does not exist on 11 or on newer builds of 10 (so the article is kind of wrong, it did get fixed, just not gracefully). As far as UX/UI comes more down to opinion, but again, you are saying it is "terrible" which has nothing to do with consistency. Windows 11 has a more consistent interface. You are welcome to say it is constantly bad, but I don't see how any objective person can say it isn't more constant than Windows 10's unholy merger of Windows 7 and Windows 8. To be fair, I really like Windows 10's interface, it worked great, but was it consistent, NO, it was one of the least consistent interfaces MS has ever made. I agree with the lack of competition. Linux continues to get better
    • Microsoft isn't happy you're using unsupported Exchange versions, announces final deadline by Usama Jawad Earlier this month, Microsoft announced Exchange Server Subscription Edition (SE), which is the official transition of the product to the Modern Lifecycle Policy, where software is continuously serviced without an end-of-life date, as long as you keep it updated. It also revealed surprising, but brief, Extended Security Updates (ESUs) for Exchange 2016 and 2019. As it winds down support for these products, the company has expressed some displeasure that some customers are using even older and, obviously, unsupported versions of Exchange. In a blog post, the company has noted that it currently offers migration tools that enable the migration of public folders from on-premise Exchange 2013 or older versions to Exchange Online. This is by design, but Microsoft is now changing its tune on the topic. Starting from October 1, 2025, customers leveraging Exchange 2010 or older versions of the software will not be allowed to use Microsoft's tools to migrate their public folders to Exchange Online. Microsoft believes that this deprecation will reduce reliance on legacy systems and enhance "long-term service reliability". Any migrations that are attempted after the aforementioned date will fail, so Microsoft has urged customers to complete their migrations as soon as possible. If customers want to move their data to Exchange Online after October 1, they will first have to upgrade to a newer Exchange version, which is Exchange 2013, but it is important to keep in mind that supported versions are 2016 and 2019. Microsoft has emphasized in a rather stern tone that it does not encourage using unsupported versions of Exchange Server at all, and it has just put out this advisory because it is aware that public folder migrations from legacy systems are currently active, even though they shouldn't be. Needless to say, customers should upgrade to Exchange Server 2016 or 2019 as quickly as possible, but ideally, they should consider moving to Exchange Server SE at this point, considering that the other two versions are running out of support soon, too.
    • A little bit, yeah, if you ask me. Granted, he has the right to be upset with this jerk user that attacked him, but why drop the entire project just because of ONE person? Seems a little exaggerated.
  • Recent Achievements

    • Week One Done
      NeoWeen earned a badge
      Week One Done
    • One Month Later
      BA the Curmudgeon earned a badge
      One Month Later
    • First Post
      Doreen768 earned a badge
      First Post
    • One Month Later
      James_kobe earned a badge
      One Month Later
    • Week One Done
      James_kobe earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      673
    2. 2
      ATLien_0
      256
    3. 3
      Xenon
      165
    4. 4
      neufuse
      145
    5. 5
      +FloatingFatMan
      115
  • Tell a friend

    Love Neowin? Tell a friend!