That will be nice
Me too, but thats because I’ve been engrossing myself in Arch on my Dedibox XC. Switching back to Ubuntu is confusing
Does anyone succeed to start a server with Arch Linux ?
Yeh, my server is running Arch Linux ARM right now…
Can you list the modifications needed ?
I just created a extra volume, formatted it ext4.
Then I downloaded http://os.archlinuxarm.org/os/ArchLinuxARM-armv7-latest.tar.gz and extracted it to that volume, created snapshot and new server, and it worked…
I then added /dev/nbd0 to fstab, so it get mounted rw.
Are you using systemd ?
Did you port some scripts from upstart to systemd ?
Yes I’m using systemd.
I haven’t ported any script… At the moment, I’m trying to see if there a better way todo what nbd-disconnect-root do…
Ok, and what about the ssh key syncing ? are you using an hardcoded password ? did you manually added your authorized_key file ?
That tar archive I downloaded and extracted default login is, root and root
Ok, so we know Arch Linux runs on our servers : \o/
Now, we need to port the upstart scripts to we can create an official image that people can boot with their volumes and ssh keys
Can you try adding “–systemd-mark” to your initramfs? That should solve kernel panic because nbd root get unmounted. Wouter Verhelst is working on a systemd service which unmount nbd not-root mount correctly. https://twitter.com/wouter_verhelst/status/523073956040163329 http://lists.freedesktop.org/archives/systemd-devel/2014-March/018053.html
Ok, we will release a new initrd with --systemd-mark, I will need your server-id to manually configure it to boot with the new initrd
You can restart your server, it should add the option, tell me if it works.
It won’t start.
transferring data (Cannot start server. (last state: kernel-started))
What version of nbd, did you include in the initramfs? “–systemd-mark” was added in 3.8
our version of nbd-client is too old, We will build a new initrd with an up-to-date nbd-client