-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PUMP not working? #10
Comments
Thanks for trying pimod and please excuse the troubles. Based on your first and the following logs, the problem lies with the execution of pimod's chroot part as an unprivileged user. However, it seems like a loop device was created, which is now causing problems. An easy fix would be: # check if there are any loop devices
losetup -a
# delete all orphaned loop devices (replace loop0 with your devices)
sudo losetup -d /dev/loop0
# just clean up
sudo dmsetup remove_all
# Check again and, if anything is present, try deleting them again.
# If everything fails, reboot your machine ¯\_(ツ)_/¯ Afterwards, running your Please consider, the |
So I just started a clean session (rebooted my system and started from scratch) and here is my whole output, not sure if this error is relevant
am I doing something wrong about it? |
Could you please try to execute pima.sh as root using sudo? As you see, problems start to occur, when you
|
Closed due to no further activity. Feel free to reopen! |
Hello. I'm trying to get to use pimod, but my first test already failed :)
Here is my Pifile
and here is the output I get, is this normal? I tried running as non-sudo user:
then with sudo
also docker
Just wondering if this is normal or to check if I'm doing something wrong
thank you
The text was updated successfully, but these errors were encountered: