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

    • KDE's KClock is getting Wayland Picture-In-Picture support by David Uzondu The KClock app for KDE Plasma over the years has received a number of updates, like better integration with KRunner and a dedicated background service (kclockd) for managing alarms. Now, it looks like KDE devs want to add something cool: pop-out timers using the new Picture-in-Picture protocol for Wayland. Image: Kai Uwe Broulik This all started from a simple observation. Kai Uwe Broulik, a KDE developer, saw someone using a small timer window during a presentation and thought it was a good idea. The problem is that achieving this kind of "always on top" behavior is handled differently between the old X11 display server and the newer Wayland. With X11, an application could pretty much do whatever it wanted. If a program wanted to draw a drop-down menu, it would just create a borderless window, place it in a specific spot, and grab all user input. Wayland operates on a different philosophy. As Broulik notes, under Wayland, the application describes what it wants, and the compositor gets to decide how to handle it. A drop-down menu is an XDG Popup. The application tells the compositor which button spawned it, and the compositor handles the placement and behavior. This is much more secure and consistent. It also means an application cannot just decide to keep its window on top of everything else. This restriction prevents a web browser from implementing an overlay video player under Wayland. To get around this in a standardized way, a proper Wayland support model for Picture-in-Picture, or PiP, was needed. Enter the xx-pip-v1 protocol. It is a new protocol designed specifically for creating floating PiP windows, and KWin, Plasma's compositor, recently gained support for it. Because it is an experimental protocol, its use is gated behind an environment variable, KWIN_WAYLAND_SUPPORT_XX_PIP_V1. A new protocol is fine for demos, but it needs a real application to find its weaknesses. So Broulik implemented it in KClock. This work allows KClock to offer pop-out timers and even a pop-out stopwatch in a small PiP window. The user could get system-wide options to control where the PiP window appears, or if it appears at all, and have that setting apply to every single application that uses the protocol. You can check out the merge request on GitLab for more technical details about this feature.
    • Nothing of course; it is just a classic syndrome of MAGA pathology.
    • They use it to assessment's in the UK already. Have a friend who said they basically feed response's and prompt during assessment's for many mental health conditions now (essentially tick boxes these days enough ticks and you got it) the AI can prompt questions to ask if its unsure how to score something. It's really good at recognising fractures and broken bones also.
    • Look it more of another tool in your toolbox. The good doctors will use tools like this to aid in proper diagnostics and help their patients. There will be some doctors out there that will rely on it and never actually learn how to be a doctor. My wife deals with chronic illness, seizures, and MS. If this would help her doctors to get her on a better path to recovery, I'm all for it. She does take about 4-5 different medications daily and no one wants to play Russian roulette to figure out which meds she really needs.
    • I'm currently wearing Hoka Clifton 8.  It's a good shoe.
  • Recent Achievements

    • One Month Later
      CHUNWEI earned a badge
      One Month Later
    • Week One Done
      TIGOSS earned a badge
      Week One Done
    • First Post
      henryj earned a badge
      First Post
    • First Post
      CarolynHelen earned a badge
      First Post
    • Reacting Well
      henryj earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      +FloatingFatMan
      196
    3. 3
      ATLien_0
      163
    4. 4
      Xenon
      81
    5. 5
      Som
      77
  • Tell a friend

    Love Neowin? Tell a friend!