Top
Best
New

Posted by stereo-highway 9 hours ago

Diskless Linux boot using ZFS, iSCSI and PXE(aniket.foo)
106 points | 54 commentspage 2
protoman3000 6 hours ago|
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.
theandrewbailey 2 hours ago|
> You could also boot into an ephemeral minimal initrd

Wouldn't that need a local disk?

wallst07 1 hour ago||
No. PXE boots routinely load the kernel and initramfs directly into RAM with no local disk involved. The initramfs then mounts the real root FS over the network.

Then anaconda or whatover os installer picks up and installs the OS in a PXE install sequence when there is a local disk.

guenthert 4 hours ago||
"I didn’t want to get into the hassle of repartitioning everything that the boot loader works with both Linux & Windows."

Hmmh? I haven't done so in years, but configuring multi-boot used to be considerably easier than disk-less operation.

snailmailman 3 hours ago||
It is relatively easy to configure. Just install Linux after windows, and Linux will generally automatically setup a boot-selection screen for you. The installer should detect windows and even shrink the partitions for you.

You can install a prettier looking boot selection menu like rEFInd, but the default works just as well, and I think the mainstream distros all setup secure boot too. On my pc it was very easy, on my (8yr old) laptop I had to add some secure boot keys and the bios was very confusing, using terms that didn’t seem to match what they should have been.

My setup has worked almost entirely flawlessly and survived updates from both OSes. Only issue being “larger” windows feature updates putting windows back as the first OS in the list, but that happens maybe once or twice a year? And it’s a quick bios change to fix the order.

jeroenhd 3 hours ago|||
The Debian installer is less than optimal for repartitioning.

The Linux NTFS resizing code also has a tendency to trigger data corruption. Not really Linux' fault, but it's a good reason to do partitioning from inside of Windows, which can be a pain already.

Another issue I've run into is Windows creating a very small (~300MiB) EFI partition that barely fits the Windows bootloader, let alone a Linux bootloader and kernel. You can resize and recreate the partition of course, but reconfiguring Windows to use a different boot partition is a special kind of hell I try to avoid.

charcircuit 2 hours ago||
>Not really Linux' fault

If Linux corrupts someone files, it is 100% Linux's fault and is absolutely unacceptable.

pbhjpbhj 4 hours ago||
SecureBoot is a PITA.
jeroenhd 4 hours ago||
For Debian and most other distros, secure boot isn't a problem. Installers are all using a signed, trusted-by-default bootloader.

There are some exceptions (some hardware from Microsoft doesn't trust the third party certificate used, for instance, and Red Hat Enterprise has their own root of trust if you opt into that), but they're very rarely ever an issue.

ahepp 6 hours ago||
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...

verytrivial 4 hours ago||
I know it was just a convenient pretext for a learning journey, but do not come away from this thinking llama.cpp needs to be compiled on Windows before use. The GitHib project has a cornucopia of pre-built artifacts to use.

https://github.com/ggml-org/llama.cpp/releases

nicman23 5 hours ago||
what i want to play with is rdma and having a bcache block device with the remote as a backing and a small local nvme as a write-through cache
iberator 3 hours ago||
Does zfs support error correcting instead of just finding (already) broken files?

I have been waiting for such a feature for like 15 years now. Without it, zfs is just a fad and useless filesystem (all that complexity for NOTHING).

ext2 for the win! still

tecleandor 3 hours ago||
I don't know if I'm understanding your question, but ZFS actively corrects data on disk when it finds a checksum error [0]. Those checksum errors can be found when accessing that data, or doing a 'scrub' action that scans the whole volume to check integrity.

--

  0: https://klarasystems.com/articles/troubleshooting-zfs-common-issues-how-to-fix-them/
olavgg 1 hour ago||
ZFS supports self healing, you do not have scrub, it will be corrected during a bad read as long you have a copy. Metadata has 2 copies by default for additional safety for a single disk.
shevy-java 3 hours ago||
I have to admit, I misread "Diskless Linux" initially ...
louwrentius 6 hours ago||
I would probably recommend to look into NVMe over TCP over iSCSI, especially for fast NVMe drives.
qzgrid37 1 hour ago|
[dead]