# Mount essential system folders also to the respective subfolders of /mnt To accomplish that, mount the main partition of the bricked installation to the /mnt directory of the live CD system and use chroot to make pacman think /mnt is / (insert your bricked system's main partition for sdXXX) mount /dev/sdXXX /mnt I also used the package manager of my bricked on-disk installation (called pacman) from the live CD to reinstall all the packages of the base group (maybe only the kernel, so package linux would have been enough, I don't know) Now that I have internet again, I also found this thread So I recreated the symlink and reinstalled the base system from a live CD. So that meant all libraries and kernel modules, which are expected to be in /lib were missing :-)
#Wineskin error tried to run command debug update
The Problem was: An update replaced the symlink /lib -> /usr/lib with a directory. Sh: can't access tty: job control turned off You are being dropped to a recovery shell Skipping fsck.ĮRROR: Unable to find root device 'UUID=.'. Problem on reboot: Warning: /lib/modules/4.11.3-1-ARCH/vname not found - ignoringĮRROR: device 'UUID=.' not found. It is a mystery for me how the system managed to stay operative for so long, while I was trying to implement the countless suggestions by you (thank you a lot!!) On reboot it became apparent that it was so screwed up that even the fall-back console of initrd didn't recognize my keyboard anymore. OK, I was busy for the last eight hours to get my system up and running again after CPU overheating shut-down. What is the problem or what can I do to find out which file or directory is missing?
Write(2, "strace: exec: No such file or di"., 40strace: exec: No such file or directoryĮdited to add suggestion by The problem appears to happen before dynamically linked libraries are requested, because no ld debug messages are generated: $ LD_DEBUG=all wineĮven when only printing the possible values of LD_DEBUG, the error occurs instead $ LD_DEBUG=help wineĮdited to add suggestion of Sailopal: The problem seems to lie within the executable, as copying the contents of /usr/bin/wine to another already created file produces the same error root:bin # cp cat testcmdĩ712 bytes (9.7 kB, 9.5 KiB) copied, 0.000404061 s, 24.0 MB/sīash: /usr/bin/testcmd: No such file or directory
Strace shows: execve("/usr/bin/wine",, 0x7fff20dc8730 /* 66 vars */) = -1 ENOENT (No such file or directory)įstat(2, ) = 0 usr/bin/ldd: line 117: /usr/bin/wine: No such file or directory However, I cannot list the shared object dependencies using ldd: $ ldd /usr/bin/wine I can get the dynamic section of the executable: $ readelf -d /usr/bin/wineĭynamic section at offset 0x1efc contains 27 entries:Ġx00000001 (NEEDED) Shared library: Ġx0000001d (RUNPATH) Library runpath: The executable definitely is there and no dead symlink: $ stat /usr/bin/wine I want to launch the wine executable (Version 2.12), but I get the following error ( $=shell prompt): $ wineīash: /usr/bin/wine: No such file or directory
0 kommentar(er)
