#547 - [GH-ISSUE #1626] Clonezilla: Waiting for ethernet cards up - since menus 2.0.87 - starred/netboot.xyz

kerem commented

2026-02-27 14:52:10 +03:00

Owner

Originally created by @LenryNmQ on GitHub (May 24, 2025).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1626

[X]: This bug persists when memory is increased beyond 8GB.

Describe the bug
Clonezilla boot stuck at "Waiting for ethernet cards up... If this fails...". It worked before, now it stuck on every machine I tried, even on ones that worked before.

To Reproduce
Steps to reproduce the behavior:

Download the latest clonezilla debian or ubuntu stable and try to boot it

Expected behavior
It should boot

Screenshots

This is a Lenovo T480. It could boot Clonezilla before.

Additional context

Originally created by @LenryNmQ on GitHub (May 24, 2025). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1626 [X]: This bug persists when memory is increased beyond 8GB.  **Describe the bug** Clonezilla boot stuck at "Waiting for ethernet cards up... If this fails...". It worked before, now it stuck on every machine I tried, even on ones that worked before. **To Reproduce** Steps to reproduce the behavior: 1. Download the latest clonezilla debian or ubuntu stable and try to boot it **Expected behavior** It should boot **Screenshots** ![Image](https://github.com/user-attachments/assets/2a014e94-f665-466d-8cda-0128dc21d21e) This is a Lenovo T480. It could boot Clonezilla before. **Additional context**

kerem

2026-02-27 14:52:10 +03:00

closed this issue
added the
bug

confirmed
labels

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@gesa60 commented on GitHub (Jun 10, 2025):

I have the same problem. Other OSs (at least those I've tried) boot from netboot.xyz normally as before.
Please give a feedback on this strange behaviour. Tx

@gesa60 commented on GitHub (Jun 10, 2025): I have the same problem. Other OSs (at least those I've tried) boot from netboot.xyz normally as before. Please give a feedback on this strange behaviour. Tx

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@Gilibenzio commented on GitHub (Jun 14, 2025):

Yeah, having the same issue here...

@Gilibenzio commented on GitHub (Jun 14, 2025): Yeah, having the same issue here...

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@antonym commented on GitHub (Jun 14, 2025):

Confirmed on Debian and Ubuntu image seems to fail out as well.

@antonym commented on GitHub (Jun 14, 2025): Confirmed on Debian and Ubuntu image seems to fail out as well.

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@gesnaud commented on GitHub (Jun 19, 2025):

Hi there!

I confirm also! I tried the version embedded with netboot and also latest Clonezilla version... strange 🤔

@gesnaud commented on GitHub (Jun 19, 2025): Hi there! I confirm also! I tried the version embedded with netboot and also latest Clonezilla version... strange 🤔

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@zezretro commented on GitHub (Jun 29, 2025):

I have the same issue

@zezretro commented on GitHub (Jun 29, 2025): I have the same issue

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@zezretro commented on GitHub (Jun 29, 2025):

I got around this by rolling back to menu 2.0.86, now Clonezilla boots again

@zezretro commented on GitHub (Jun 29, 2025): I got around this by rolling back to menu 2.0.86, now Clonezilla boots again

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@LenryNmQ commented on GitHub (Jun 29, 2025):

How do I roll back?

@LenryNmQ commented on GitHub (Jun 29, 2025): How do I roll back?

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@zezretro commented on GitHub (Jun 29, 2025):

I am using the docker compose image: ghcr.io/netbootxyz/netbootxyz which give 2.0.86 by default

I just blew away my config and rebuilt it. Admittedly not an option for everyone

@zezretro commented on GitHub (Jun 29, 2025): I am using the docker compose image: ghcr.io/netbootxyz/netbootxyz which give 2.0.86 by default I just blew away my config and rebuilt it. Admittedly not an option for everyone

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@antonym commented on GitHub (Jun 29, 2025):

I'd also suggest trying the Clonezilla releases directly and see if you experience the same behaviors.

@antonym commented on GitHub (Jun 29, 2025): I'd also suggest trying the Clonezilla releases directly and see if you experience the same behaviors.

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@gesa60 commented on GitHub (Jul 5, 2025):

I confirm that same Clonezilla release (and others), directly booted, doesn't have same buggy behaviour.

@gesa60 commented on GitHub (Jul 5, 2025): I confirm that same Clonezilla release (and others), directly booted, doesn't have same buggy behaviour.

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@ffidelis commented on GitHub (Aug 1, 2025):

Hi team, I've checked both menus package and got the differences between the released versions 2.0.87 from 2.0.86.
Basically, the clonezilla.ipxe in the 2.0.86 has a different previous debian-squash release, which worked like a charm for me in my laptop or PC successfully booting the clonezilla at /debian-squash/releases/download/3.2.0-5-5641363c/

The left is 2.0.86 and the right is the 2.0.87:

After downloaded the following previous menus file, I just extracted the clonezilla.ipxe file and rebooted my machine again.

- https://github.com/netbootxyz/netboot.xyz/releases/download/2.0.86/menus.tar.gz

My netbootxyz is still running with the 2.0.87 but with previous clonezilla.ipxe version:

Hopefully this helps and in the next menus version release everything comes fixed.
Cheers!

@ffidelis commented on GitHub (Aug 1, 2025): Hi team, I've checked both _menus_ package and got the differences between the released versions 2.0.87 from 2.0.86. Basically, the `clonezilla.ipxe` in the 2.0.86 has a different previous `debian-squash` release, which worked like a charm for me in my laptop or PC successfully booting the clonezilla at `/debian-squash/releases/download/3.2.0-5-5641363c/` The left is 2.0.86 and the right is the 2.0.87: <img width="1920" height="1048" alt="Image" src="https://github.com/user-attachments/assets/56b3a0b4-1631-4e85-b559-4701a3f31155" /> After downloaded the following previous _menus_ file, I just extracted the `clonezilla.ipxe` file and rebooted my machine again. `- https://github.com/netbootxyz/netboot.xyz/releases/download/2.0.86/menus.tar.gz` My netbootxyz is still running with the 2.0.87 but with previous `clonezilla.ipxe` version: <img width="1931" height="951" alt="Image" src="https://github.com/user-attachments/assets/180a2ea1-1bc0-4663-9594-4521105202c4" /> Hopefully this helps and in the next menus version release everything comes fixed. Cheers!

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@ffidelis commented on GitHub (Aug 11, 2025):

Just an update, the new release 2.0.86 looks fine. The menus.tar.gz is updated and the stable entries for CloneZilla are the ones that are working (3.2.0-5-5641363c):

https://github.com/netbootxyz/netboot.xyz/releases/download/2.0.86/menus.tar.gz

┌─ 🐧fidelis@sbrubles:/tmp
└─■ cat clonezilla.ipxe
#!ipxe

goto ${menu} ||

:live_menu
set os_arch ${arch}
iseq ${os_arch} x86_64 && set os_arch amd64 ||
iseq ${os_arch} i386 && set os_arch i686 ||
set os Clonezilla
menu ${os}
item --gap ${os} Versions
item debian ${space} ${os} Debian Based
iseq ${os_arch} amd64 && item ubuntu ${space} ${os} Ubuntu Based ||
choose live_version || goto live_exit
menu ${os} ${live_version} - ${os_arch}
item --gap ${os} Flavors
goto ${live_version}

:debian
iseq ${os_arch} i686 && item /debian-squash/releases/download/3.2.0-5-ef1ff756/ ${space} Clonezilla 3.2.0-5 Stable ||
iseq ${os_arch} amd64 && item /debian-squash/releases/download/3.2.0-5-5641363c/ ${space} Clonezilla 3.2.0-5 Stable ||
iseq ${os_arch} amd64 && item /debian-squash/releases/download/3.2.1-9-9e73bfe5/ ${space} Clonezilla 3.2.1-9 Testing ||
iseq ${os_arch} i686 && item /debian-squash/releases/download/3.2.0-3-d1702a7a/ ${space} Clonezilla 3.2.0-3 Testing ||
choose path || goto live_menu
goto clonezilla-boot

:ubuntu
iseq ${os_arch} amd64 && item /ubuntu-squash/releases/download/20250303-oracular-48403403/ ${space} Clonezilla 20250303-Oracular Stable ||
iseq ${os_arch} amd64 && item /ubuntu-squash/releases/download/20250303-plucky-c67d897c/ ${space} Clonezilla 20250303-Plucky Testing ||
choose path || goto live_menu
goto clonezilla-boot

:clonezilla-boot
imgfree
set url ${live_endpoint}${path}
kernel ${url}vmlinuz boot=live username=user union=overlay config components noswap edd=on nomodeset ocs_live_run="ocs-live-general" ocs_live_batch=no net.ifnames=0 nosplash noprompt fetch=${url}filesystem.squashfs initrd=initrd.magic ${cmdline}
initrd ${url}initrd
boot

:live_exit
clear menu
exit 0

@ffidelis commented on GitHub (Aug 11, 2025): Just an update, the new release 2.0.86 looks fine. The menus.tar.gz is updated and the stable entries for CloneZilla are the ones that are working (3.2.0-5-5641363c): https://github.com/netbootxyz/netboot.xyz/releases/download/2.0.86/menus.tar.gz ``` ┌─ 🐧fidelis@sbrubles:/tmp └─■ cat clonezilla.ipxe #!ipxe goto ${menu} || :live_menu set os_arch ${arch} iseq ${os_arch} x86_64 && set os_arch amd64 || iseq ${os_arch} i386 && set os_arch i686 || set os Clonezilla menu ${os} item --gap ${os} Versions item debian ${space} ${os} Debian Based iseq ${os_arch} amd64 && item ubuntu ${space} ${os} Ubuntu Based || choose live_version || goto live_exit menu ${os} ${live_version} - ${os_arch} item --gap ${os} Flavors goto ${live_version} :debian iseq ${os_arch} i686 && item /debian-squash/releases/download/3.2.0-5-ef1ff756/ ${space} Clonezilla 3.2.0-5 Stable || iseq ${os_arch} amd64 && item /debian-squash/releases/download/3.2.0-5-5641363c/ ${space} Clonezilla 3.2.0-5 Stable || iseq ${os_arch} amd64 && item /debian-squash/releases/download/3.2.1-9-9e73bfe5/ ${space} Clonezilla 3.2.1-9 Testing || iseq ${os_arch} i686 && item /debian-squash/releases/download/3.2.0-3-d1702a7a/ ${space} Clonezilla 3.2.0-3 Testing || choose path || goto live_menu goto clonezilla-boot :ubuntu iseq ${os_arch} amd64 && item /ubuntu-squash/releases/download/20250303-oracular-48403403/ ${space} Clonezilla 20250303-Oracular Stable || iseq ${os_arch} amd64 && item /ubuntu-squash/releases/download/20250303-plucky-c67d897c/ ${space} Clonezilla 20250303-Plucky Testing || choose path || goto live_menu goto clonezilla-boot :clonezilla-boot imgfree set url ${live_endpoint}${path} kernel ${url}vmlinuz boot=live username=user union=overlay config components noswap edd=on nomodeset ocs_live_run="ocs-live-general" ocs_live_batch=no net.ifnames=0 nosplash noprompt fetch=${url}filesystem.squashfs initrd=initrd.magic ${cmdline} initrd ${url}initrd boot :live_exit clear menu exit 0 ```

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@LenryNmQ commented on GitHub (Aug 12, 2025):

It still doesn't work for me

@LenryNmQ commented on GitHub (Aug 12, 2025): It still doesn't work for me

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@gesa60 commented on GitHub (Aug 13, 2025):

Bug still in 2.0.88 version :-(

@gesa60 commented on GitHub (Aug 13, 2025): Bug still in 2.0.88 version :-(

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@drunkly commented on GitHub (Sep 23, 2025):

I start using this tool today and confirm last version is not working.
I also confirm version 2.0.86 is working

@drunkly commented on GitHub (Sep 23, 2025): I start using this tool today and confirm last version is not working. I also confirm version 2.0.86 is working

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@SpazShark commented on GitHub (Oct 31, 2025):

I just installed netboot.xyz today and I'm having the exact same issue. As with others, going back to 2.0.86 fixed it.

@SpazShark commented on GitHub (Oct 31, 2025): I just installed netboot.xyz today and I'm having the exact same issue. As with others, going back to 2.0.86 fixed it.

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@henkez73 commented on GitHub (Nov 7, 2025):

The initrd file for e.g. clonezilla/gparted does not have the drivers. I've replaced the initrd file with the one from the respective downloads (size was ~150k, downloaded one has size ~450k). Now the netboot works again as it has the drivers available again...

@henkez73 commented on GitHub (Nov 7, 2025): The initrd file for e.g. clonezilla/gparted does not have the drivers. I've replaced the initrd file with the one from the respective downloads (size was ~150k, downloaded one has size ~450k). Now the netboot works again as it has the drivers available again...

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@antonym commented on GitHub (Nov 8, 2025):

The initrd file for e.g. clonezilla/gparted does not have the drivers. I've replaced the initrd file with the one from the respective downloads (size was ~150k, downloaded one has size ~450k). Now the netboot works again as it has the drivers available again...

This was helpful, thanks. I found that the iso processing logic was not handling the initrd layers on the newer structures. Fix is here and latest rebuilds of Clonezilla (Ubuntu) and Gparted are loading correctly in Dev.

github.com/netbootxyz/docker-iso-processor@7262fb896f

I'll work on getting this all released this weekend.

@antonym commented on GitHub (Nov 8, 2025): > The initrd file for e.g. clonezilla/gparted does not have the drivers. I've replaced the initrd file with the one from the respective downloads (size was ~150k, downloaded one has size ~450k). Now the netboot works again as it has the drivers available again... This was helpful, thanks. I found that the iso processing logic was not handling the initrd layers on the newer structures. Fix is here and latest rebuilds of Clonezilla (Ubuntu) and Gparted are loading correctly in Dev. https://github.com/netbootxyz/docker-iso-processor/commit/7262fb896fe93aef95e62632d8cf8d9de6b5d199 I'll work on getting this all released this weekend.

kerem commented

2026-02-27 14:52:11 +03:00

Author

Owner

@antonym commented on GitHub (Nov 8, 2025):

Should be fixed in release 2.0.89 going out today.

@antonym commented on GitHub (Nov 8, 2025): Should be fixed in release 2.0.89 going out today.

kerem referenced this issue

2026-02-27 14:53:53 +03:00

[PR #547] [MERGED] 2.0.6-RC1 Bug Fix #965

kerem referenced this issue

2026-03-01 18:40:20 +03:00