My digione/ropieee unit stuck on “your device is busy updating for more than 12 hours.
Feedbacka338ae9de7154012
Thx
Bruce
My digione/ropieee unit stuck on “your device is busy updating for more than 12 hours.
Feedbacka338ae9de7154012
Thx
Bruce
Ok, that unit missed a few updates
2 options: reflash or, if you’re familiair and comfortable with SSH, some manual instructions.
It was unplugged for a while. Moved it to other system
I will try the ssh route first.
ssh root@ropieee (password: ropieee)
pacman -Syu
show me the output here
Cannot get in
Trying above command - could not resolve hostname
Tred to replace ropieee with ip- asks for password, but does not accept ropieee. Permission denied
I persisted with root password
Here is response to pacman command line
[root@ropieee ~]# pacman -Syu
:: Synchronizing package databases…
error: failed to update ropieee-stable (unable to lock database)
error: failed to update core (unable to lock database)
error: failed to update extra (unable to lock database)
error: failed to update community (unable to lock database)
error: failed to update alarm (unable to lock database)
error: failed to synchronize all databases
first reboot.
3 hours and 39 minutes later.
You should have re-flashed the freaking thing.
Yeah, I know. Minding my own business, now.
done.
repeated steps. Same result
error: failed to update ropieee-stable (unable to lock database)
error: failed to update core (unable to lock database)
error: failed to update extra (unable to lock database)
error: failed to update community (unable to lock database)
error: failed to update alarm (unable to lock database)
error: failed to synchronize all databases
Refreshing would likely have been easier , but logistically not possible, given I am working remotely, and don’t have an sd adapter to accomplish this at the moment
This got me out of a similar hole. Be warned, I’m a Debian Linux user and know little about the Pacman tool. This could end in tears but it worked here, YMMV. That said:
SSH onto the Ropieee box as root and
rm /var/lib/pacman/db.lck
then try
pacman -Syu
If you see loads of errors like this
qt5-base-ropieee: /usr/share/licenses/qt5-base/LICENSE.GPL2 exists in filesystem
qt5-base-ropieee: /usr/share/licenses/qt5-base/LICENSE.GPL3 exists in filesystem
qt5-base-ropieee: /usr/share/licenses/qt5-base/LICENSE.GPL3-EXCEPT exists in filesystem
qt5-base-ropieee: /usr/share/licenses/qt5-base/LICENSE.LGPL3 exists in filesystem
qt5-base-ropieee: /usr/share/licenses/qt5-base/LICENSE.LGPLv3 exists in filesystem
Errors occurred, no packages were upgraded.
then
pacman -Qqen > pkglist.txt
pacman --force -S $(< pkglist.txt)
pacman -Syu
Should sort it.