Antsle Forum

Welcome to our Antsle community! This forum is to connect all Antsle users to post experiences, make user-generated content available for the entire community and more. 

Please note: This forum is about discussing one specific issue at a time. No generalizations. No judgments. Please check the Forum Rules before posting. If you have specific questions about your Antsle and expect a response from our team directly, please continue to use the appropriate channels (email: [email protected]) so every inquiry is tracked. 

Please or Register to create posts and topics.

Cannot start Antlet

I am trying to start an antlet and when I do I get the following error :

internal error: guest failed to start: Failure in libvirt_lxc startup: cannot find init path '/sbin/init' relative to container root: No such file or directory

 

This is on a raspberry pi.  I have a external drive connected via the usb that has a zpool on it, which has this antlet on it.  I am waiting for my official nano to arrive next week.  I've mostly had good results with my setup on a pi 4 4GB that I had laying around.  This is the first issue i've had where i could not figure it out on my own.

Hey @tcoursen3!

It sounds to me like the zfs filesystem of your antlet might not be properly mounted... Could you please check `zpool status` and `zfs list`?

I'm guessing the zpool has been properly imported and is mounted?

Cheers,

Marc

 

So, initially, I just deleted the antlet that was giving me trouble and recreated it from scratch.  it was only running plex, so no big deal to recreate.  It was working fine for a few days, and just now crapped out with the same error.  However, now NONE of my antlets will start on this device.   I did receive my official nano today, and I did plug that in and register that, so I now do have two pi's running antsle, in case that matters.

zpool status returns :

zpool status
pool: antlets
state: ONLINE
scan: none requested
config:

NAME STATE READ WRITE CKSUM
antlets ONLINE 0 0 0
mmcblk0p4 ONLINE 0 0 0

errors: No known data errors

pool: usbPool
state: ONLINE
scan: none requested
config:

NAME STATE READ WRITE CKSUM
usbPool ONLINE 0 0 0
sda ONLINE 0 0 0

errors: No known data errors

 

zfs list does not show any errors :

zfs list
NAME USED AVAIL REFER MOUNTPOINT
antlets 6.94G 1.78G 28K /antlets
antlets/_backups 24K 1.78G 24K /antlets/_backups
antlets/_docker 1.86G 1.78G 5.92M /var/lib/docker
antlets/_docker/0868aeb1e8ecd0494a8eeca541e9d457f7f812d38a6d6ca93bafd719be949311 1.24M 1.78G 866M legacy
antlets/_docker/08e1814d0cebeea71bfcdb3fed9521d2b9c31461a497b7a44416e22e12b363eb 58.5K 1.78G 903M legacy
antlets/_docker/25d12b98d8b5d953e6e335b8f7a8d437e7b4b448a0c7c2edf845a991108f974d 25.1M 1.78G 135M legacy
antlets/_docker/374c68ff2f6b1544dc027809f24e97697b2a7ff14a21d20ba3cd2ed767dd3367 149M 1.78G 289M legacy
antlets/_docker/4864d4aa45f8cd04909f7a6841283bc1be8b7ef0a6b5c8dd41bd7bca430af8cf 8.54M 1.78G 135M legacy
antlets/_docker/591d19973e6f0a54cc2fda0b1fdfbdd08e77530b6d898932394855214cb6450c 596K 1.78G 805M legacy
antlets/_docker/6a910346bf0b6800f5d6fe3af8e7ab8dedaa0f2b36581e51c17f8f2f7f02d645 56.5K 1.78G 953M legacy
antlets/_docker/6eb458ec20b370a0fdad2fead340bfde2e6526058402991bd0da9dc2cc244326 4.51M 1.78G 915M legacy
antlets/_docker/723b6e74b9b30099d0543b19758b32ef674be911f7362104efdf85d8e4fb676e 54.8M 1.78G 911M legacy
antlets/_docker/783b9b04f3d02a8ba762f71817b97fe03418b91d9845c37c7750e52c65a63ded 190K 1.78G 805M legacy
antlets/_docker/7e0fe1247f7f3e28785cdace853d0d75f0c3ff538c1b8abdaeda40c3711e8ac8 107M 1.78G 107M legacy
antlets/_docker/87f91b39926d9f29f08e2a3c97d63ce270d356d707bc423e8196c15b0cdf229c 22.8M 1.78G 128M legacy
antlets/_docker/8c602efe216d4d5a2fc7070d088395e251227c0b8417ed8b2329263376cfdff9 37.2M 1.78G 953M legacy
antlets/_docker/ab754acab0a3b48a41dbb8daa712a779a03e3f3368bcb4b348b3d61e59953665 532M 1.78G 805M legacy
antlets/_docker/abd6c83a5c233e3573eb0841986a8ed583466e108bfebebe1371ab3509f66c84 42K 1.78G 903M legacy
antlets/_docker/abd6c83a5c233e3573eb0841986a8ed583466e108bfebebe1371ab3509f66c84-init 69K 1.78G 903M legacy
antlets/_docker/ba168725a142e12db06b257856724e7caa12d3eba4a388db8cb7805403cdd9a0 188K 1.78G 856M legacy
antlets/_docker/be9c1680cb9c3cedcc4ceada9443535685e7b19f836b0152a8415522ae2cb344 598K 1.78G 856M legacy
antlets/_docker/c97ec8217148c6473049b023b385666ed299135d0976c855612ff32332f64790 4.51M 1.78G 865M legacy
antlets/_docker/cabd5babc31c34726412e35d9afa9d26ea41bdb795c7824411734dea8e23ff83 21.4M 1.78G 936M legacy
antlets/_docker/d2c96e5e0a9fdc10f5231ddd04cc64c28b9ca7641d5b1b7a3823c948cdac705d 55.2M 1.78G 860M legacy
antlets/_docker/d333e034edfb1bd24175bbb5fd3975ceb8cbca326412f66d87b16da520ed3e4b 570M 1.78G 855M legacy
antlets/_docker/d4ac5ac5786ec24847db0f29f0c6aa99e09ca718f6632fc3e497f07929153015 112M 1.78G 112M legacy
antlets/_docker/e5e5e58884618f708d5aee73430928e6151cd3a871ce6a1f8d65a88560c0a541 8.91M 1.78G 142M legacy
antlets/_docker/f564f4a3918e6c70c5a81310144be07efc0840b587e8265d0f4f9379d5256a09 37.1M 1.78G 903M legacy
antlets/_docker/fca265079bdbcf912d4baa407373c5b9e2fad012132074d32c57ff2715a72862 144M 1.78G 276M legacy
antlets/_templates 2.52G 1.78G 24K /antlets/_templates
antlets/_templates/centos7.lxc 1.28G 1.78G 1.28G /antlets/_templates/centos7.lxc
antlets/_templates/raspbian.lxc 1.24G 1.78G 1.24G /antlets/_templates/raspbian.lxc
antlets/_tmp 24K 1.78G 24K /antlets/_tmp
antlets/antlet06 570M 1.78G 1.83G /antlets/antlet06
antlets/appServer01 669M 1.78G 1.93G /antlets/appServer01
antlets/jira02 1.34G 1.78G 2.61G /antlets/jira02
usbPool 12.7G 886G 104K /usbPool
usbPool/gitBucket01 1.33G 886G 1.33G /usbPool/gitBucket01
usbPool/plex01 4.64G 886G 4.64G /usbPool/plex01
usbPool/teamCity01 6.69G 886G 6.69G /usbPool/teamCity01

 

I have an external usb zpool also, and I've found that if I have an antlet that "lives" on a zpool other than "antlets", I have to at least create a 1 GB virtual drive on the antlets zpool to get it to work.

Although this is with edgeLinux 0.12.1 (non-nano).

 

Getting very frustrated.  Killed the antlet and started over yet again.   This time once I had the new antlet set up the way I wanted, I created a snapshot.

So once again, it crapped out on me with the same error.   I tried to rollback the snapshot, and that did not work either.  Is taking a snapshot worthless?  Seems so.

I really have concerns about putting any real data on this setup.

This same thing happened to me today after a long power outage (the UPS batteries ran out and my antlse shut off).

After it came back up, my antlets wouldn't load (getting the missing file error in this thread).

I had to fix it by:

unmount all zfs filesystems:

zfs unmount -a

Check that antlets is empty:

ls -l /antlets

If it is not empty, rename antlets and re-create directory:

mv /antlets /antlets-bad

mkdir /antlets

re-mount zfs filesystems:

zfs mount -a

 

Hi all,

I've been enjoying my Nano since I got one last year! But I'm now getting the same error whenever I'm restarting, power cycling the nano... "

internal error: guest failed to start: Failure in libvirt_lxc startup: cannot find init path '/sbin/init' relative to container root: No such file or directory"

I go and check the /antlets/ folder and *some* of the antlets' contents just go missing. Meaning, the folders only contain "dev, proc, sys" folders, and nothing else — other (still healthy) antlets have a bunch of other folders. No wonder I can't start the antlet!

Antlets that go down like this include both running and stopped Antlets. Basically, I have to delete and re-setup the Antlet from scratch every time because ZFS or the nano just decides to *delete all the contents randomly*

Does this mean my SD card or the nano is damaged? Is this a feature? I can't really tell...

 

Hi yawnxyz:

Yes, it's possible that the SD Card is damaged which can cause errors in zpools.

You can check the status of your zpool by typing this command:

zpool status

You can also downloading the edgeLinux 2.0 ISO for aarch64 here:

http://anthill.antsle.com/#/downloads

Then you can burn image by following instructions here:

https://docs.antsle.com/get-started/getting-started-with-edgelinux-software-only-version#install-iso

Quote from daniel.luck on June 21, 2021, 2:30 pm

Hi yawnxyz:

Yes, it's possible that the SD Card is damaged which can cause errors in zpools.

You can check the status of your zpool by typing this command:

zpool status

You can also downloading the edgeLinux 2.0 ISO for aarch64 here:

http://anthill.antsle.com/#/downloads

Then you can burn image by following instructions here:

https://docs.antsle.com/get-started/getting-started-with-edgelinux-software-only-version#install-iso

why can't I download edgeLinux 2.0 ISO?

shell shockers

Hi @lorde

You can download the latest ISO's for edgeLinux and antMan here:

http://anthill.antsle.com/#/downloads

Thank you,
antsle Support