Diskless Linux boot using ZFS, iSCSI and PXE
stereo-highway
45 points
12 comments
May 07, 2026
Related Discussions
Found 5 related stories in 74.0ms across 8,303 title embeddings via pgvector HNSW
- Just Enough Chimera Linux speckx · 51 pts · April 13, 2026 · 52% similar
- Linux Page Faults, MMAP, and userfaultfd for fast sandbox boot times shayonj · 14 pts · March 12, 2026 · 48% similar
- Kioxia and Dell cram 10 PB into slim 2RU server rbanffy · 121 pts · May 16, 2026 · 48% similar
- curl > /dev/sda: How I made a Linux distro that runs wget | dd astralbijection · 140 pts · March 24, 2026 · 47% similar
- Sylve – Proxmox Alternative by FreeBSD imbobbytables · 34 pts · March 28, 2026 · 47% similar
Discussion Highlights (8 comments)
ggm
NFS diskless is the more common approach I've used but this is very cool.
protoman3000
Pretty cool! You could also boot into an ephemeral minimal initrd that displays a selection menu instead of doing it in iPXE. That would grab the new kernel and initrd from the network and kexecs it without reboot.
yjftsjthsd-h
Nice. I'm extra fond of ZFS backed network root filesystem, because it lets you put an OS on ZFS without needing to deal with ZFS support in that OS. (One of these days I want to try OpenBSD with its root on NFS on ZFS, either from Linux or FreeBSD.) Does anyone have an opinion on iSCSI vs NBD?
ahepp
You might find it worth upgrading to 10gbps if you continue to go down this road. The Mikrotik CRS-309 has served me well, and a couple Intel X520-DA2s. I believe those NICs can do iSCSI natively, and pass the session to the operating system with iBFT. SFP28 might be cheap enough now too, I'm not sure...
dhash
something worth mentioning here is that iSCSI is quite unhappy on congested networks or packet loss caused by incast traffic. to make this actually work well, consider modifying your switches QoS settings to carve out a priority VLAN for iSCSI traffic
tehlike
I used similar ipxe setup for robotic cluster - every robot booted from the same thing, then kubernetes managed the containe orchestration. it was fun.
anonymousiam
I've done a lot of headless/diskless stuff. I haven't done much for years, because my NAS only has gigabit Ethernet ports. I can cascade them and get four Gbps downstream, but it's still painful. I have recently upgraded my house to 10Gbps Ethernet, with only one room still stuck at gigabit, and unfortunately, it's my main office. I'm working on getting the drop there now (literally, just taking a break here). Even once I'm done, accessing an iSCSI drive over 10GbE will be 4-8 times slower than a local NVMe drive, but it will sure be a lot better than it was! Ideally, I could run VMs on the NAS and have great performance, but that's another hardware upgrade...
louwrentius
I would probably recommend to look into NVMe over TCP over iSCSI, especially for fast NVMe drives.