this post was submitted on 25 May 2024
25 points (96.3% liked)

Linux

48252 readers
640 users here now

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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
25
Partial upgrade to xubuntu 24.04 from 23.10, FS only accessible in recovery mode as root + wifi may be down. Help appreciated (lemmy.ml)
submitted 5 months ago by ceciline02@lemmy.ml to c/linux@lemmy.ml
10 comments fedilink hide all child comments
 

before the issue, wifi app was configured not to start automatically because I sometimes change the mac after logging in. I usually enable it afterwards with iftop and then systemctl start NetworkManager.service && sudo nm-applet

Back to the issue: I can log in to recovery mode, filesystem is read and write, unsure that ‘network’ enables the network.

I can also root it.

If I execute sudo apt update output reads: failed to fetch http…. Could not connect to 127.0.0.1:8118, connection refused. I don’t know how to fix this.

8118 should be tor.

If I execute sudo apt install -f or dpkg –configure -a I get the regular list of packages I should delete with autoremove and the broken package I believe caused this issue during upgrade:

libfreerdp2-2

and a dpkg error:

/usr/sbin/update-info-dir: 11 /etc/environment: debug: not found dpkg: error processing package install-info (-configure) errors were encountered while processing install-info sub process /usr/bin/dpkg returned an error code (1)

lsb_release -a shows distro is 23.10

secondary questions: is there any way to access my data as root? I can cd to media and to my home directory, but this last directory appears as empty.

How do I change the font’s color as root? Very dark blue, cannot read anything

thanks

you are viewing a single comment's thread
view the rest of the comments
[–] gigatexal@mastodon.social 3 points 5 months ago (1 children)

@ceciline02 in a recovery mode what is the error when you try to mount the file system?

[–] ceciline02@lemmy.ml 1 points 5 months ago* (last edited 5 months ago) (2 children)

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

[–] gigatexal@mastodon.social 1 points 5 months ago (1 children)

@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?

[–] ceciline02@lemmy.ml 1 points 5 months ago (1 children)

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?

[–] gigatexal@mastodon.social 1 points 5 months ago

@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.

[–] krolden@lemmy.ml 1 points 5 months ago

mount --all only does something if the mount point is in /etc/fstab