I have my elemental derivative booting into live c...
# elemental
w
I have my elemental derivative booting into live cd mode and now it is automatically starting the
elemental-register --install
process, however now it seems that I am hitting a
no space left on device
error. This error I believe is coming from the loop device when elemental creates a snapshot. Does anyone have an idea of how to debug this? I can try to provide more logs if needed.
b
It might be related to after an upgrade?
I can't get 6.1 to install with the loopback enabled. I have to use btrfs.
w
Ok thanks for the info. Do you know if it works with loopdevice snapshotter for 6.0?
b
It did for me previously, but I have no idea why/when it broke.
the btrfs has been great though.
w
hmm ok so I am using my own derivative image I made from rocky linux. Rocky linux does not support brtfs by default, so it seems I have to use the loopdevices snapshotter. I tried downgrading my elemental toolkit version to 2.1.1 which is packaged with SLE Micro 6.0. I'm now seeing the vm just constantly reboot or something. I just see it go from the login screen and then it goes to a black screen, back and forth. Trying to debug more. Going to remove the elemental-register-install service so I can login and try to run manually to get more logs.
So just for some additional info @bland-article-62755 I found this issue in the elemental-toolkit repo https://github.com/rancher/elemental-toolkit/issues/2324 Also I was able to expand the loop device the snapshotter creates by specifying a config.yaml that looks like this
Copy code
snapshotter:
    type: loopdevice
    config:
      size: 4000
      fs: ext2
I placed that config file in /etc/elemental/config.yaml on the machine before running
elemental install
. I think the portion of this that is broken is where elemental-toolkit attempts to calculate the size the loop device should be in the case that you do not supply a size in the config. This happens here https://github.com/rancher/elemental-toolkit/blob/a19b720892d8b999076177ec391d119a6fde241b/pkg/elemental/elemental.go#L312
now I am hitting your issue I think though. I am seeing it just constantly trying to rsync and it never finishes. Just constantly syncs files.
b
From what I saw, it rsyncs, unmounts, remounts, and rsyncs again,
Time to use btrfs!
You can switch to alma instead of Rocky, 😉
w
haha yeah I could, really wanted to get this to work on rhel/rocky though
b
Alma is pretty close to RHEL
They actually submit packages to CentOS.