@ceciline02 in a recovery mode what is the error when you try to mount the file system?
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
in recovery mode as root I executed:
mount -o remount,rw /
mount --all
then cd'ed to /media/home, ls'ed and got no results.
I also don't know if changes to make the system writable are made on the go or if I have to reboot. I rebooted and the system is still in read only mode.
ETA: another command that might be relevant:
dpkg --configure -a
returns
error processing package install-info (--configure), installed install-info package post installation script subprocess returned error exit status 127
@ceciline02 when you execute those commands — not even sure if this would help — does dmesg say anything? Even before you go to mount them on boot maybe dmesg might say something about the disks? Or any log in var log?
dmesg prints a large log that I cannot copy, the only red lines I read regard bluetooth, but the log is huge and I can only see a fraction of it.
I can cd to /var/log and ls it, what file do I have to open? or what do I do now?
@ceciline02 you can pipe dmesg into less I think. Dmesg | less and then use the forward slash to search but also you can use the up and down arrows to go up and down.
mount --all
only does something if the mount point is in /etc/fstab
Sooo, I guess a couple of things.
What error do you get when you try to boot it not in rescue mode?
Was your /home directory a separate partition?
I don't think networking neccesarily starts in rescue mode, so you getting a response that 127.0.0.1:8118 is unreachable probably makes sense (your tor proxy will rely on the network service afterall)
wifi app was configured not to start automatically
With nmtui
(or nmcli) you can activate WiFi connection.
I can cd to media and to my home directory, but this last directory appears as empty.
Does mount /home
improve that ?
Does mount /home improve that ?
no
Im reading about nmtui
feel free to suggest other approaches
How about booting from Linux live medium (For example Ubuntu installation iso on pen drive, and choose Try without installing) and from there see if you can get to your home files.