That's a file-system/kernel issue.
Possibly caused by a currently-running opkg process from within enigma2 already holding the lock.
At the command line run:
to shut down enigma2, then wait a few seconds (or minutes...the "other" opkg may need to timeout...) and runCode:init 4
againCode:opkg update
The run
to get the enigma2 GUI back up.Code:init 3