Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Recovery after update
Recovery after update
Hey everyone,
I updated my debian home server and it won't boot anymore.
The error is "Failed to start Gnome Display Manager".
I don't normaly have it hooked up to a monitor and I use putty and root to login. I just now found out you can't use root to login from tty.
I know i have another user account, but whatever login I use, i get "Login incorrect" in tty.
As you can see, I have no way to fix the system. Can you suggest any course of action?
Thanks.
I updated my debian home server and it won't boot anymore.
The error is "Failed to start Gnome Display Manager".
I don't normaly have it hooked up to a monitor and I use putty and root to login. I just now found out you can't use root to login from tty.
I know i have another user account, but whatever login I use, i get "Login incorrect" in tty.
As you can see, I have no way to fix the system. Can you suggest any course of action?
Thanks.
Re: Recovery after update
hi,
The error is irrelevant because neither a desktop environment nor the Gnome Display Manager should be installed on a server anyway.
You can't login using ssh due to this:
I suggest you reset the root and user passwords.
Rather than rewrite the steps here, please see, for example reset-forgotten-root-password-in-debian
The error is irrelevant because neither a desktop environment nor the Gnome Display Manager should be installed on a server anyway.
You can't login using ssh due to this:
Code: Select all
[FAILED] failed to start OpenBSD Shell server.
See 'systemctl status ssh.service' for details.
Rather than rewrite the steps here, please see, for example reset-forgotten-root-password-in-debian
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
Re: Recovery after update
thanks for the reply!
i tried your suggestion.. unfortunately no improvement.
i googled the "authentication token manipulation error" and followed multiple solutions but nothing works i also tried booting into recovery which also fails.. any other ideas?
i tried your suggestion.. unfortunately no improvement.
i googled the "authentication token manipulation error" and followed multiple solutions but nothing works i also tried booting into recovery which also fails.. any other ideas?
Re: Recovery after update
Yes, try rescue mode: 8.6. Recovering a Broken System.
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
Re: Recovery after update
so first of all, good news: i got it to boot again following the steps described here https://www.mail-archive.com/debian-bug ... 18037.html
basically, booted from usb, got into recovery and ran these commands:
this got the system to boot, but i'm still unable to 'apt --fix-broken install' succesfully and have no ssh probably due to dependencies still being broken.
can i still salvage this or just backup data and go for a new install? right now i'm in a loop of dependecies being broken and fix unable to run because of dependecies being broken..
thanks for all your help so far!
basically, booted from usb, got into recovery and ran these commands:
Code: Select all
$ cd /tmp
$ apt -y download libcrypt1
$ dpkg-deb -x libcrypt1_1%3a4.4.25-2_amd64.deb .
$ cp -av lib/x86_64-linux-gnu/* /lib/x86_64-linux-gnu/
$ apt -y --fix-broken install
can i still salvage this or just backup data and go for a new install? right now i'm in a loop of dependecies being broken and fix unable to run because of dependecies being broken..
thanks for all your help so far!
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 12 times
- Been thanked: 66 times
Re: Recovery after update
What exactly do you mean by this?
What sources are you using?
Code: Select all
cat /etc/apt/sources.list{,.d/*}
AdrianTM wrote:There's no hacker in my grandma...
Re: Recovery after update
Using the -y flag isn't a good idea because it results in an automatic yes to all prompts and it's better to know what's going on when troubleshooting,gedorin wrote:Code: Select all
$ apt -y --fix-broken install
I think it's a good idea to try and try and fix it rather than going for a new install.gedorin wrote: Can I still salvage this or just backup data and go for a new install? Right now I'm in a loop of dependencies being broken and fix unable to run because of dependencies being broken.
If you have somehow created a "Frankendebian" by adding unofficial sources to your sources.list, then it may not be fixable at all, which is why dilberts_l_n has asked you to post the file. On the other hand, if your original file has been left unedited, then it's unlikely you won't be able to fix it.
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
Re: Recovery after update
If you can't login, then a screenshot is the only way to show what's happened, unless one copies a big chunk of tty text manually. After login has been achieved using the recovery option, then, without an internet connection, one must first cat the the output to a text file, copy it to a usb stick, transfer that to the desktop computer or laptop and then cut and paste the contents of the file here.dilberts_left_nut wrote: ↑2022-01-16 18:54What exactly do you mean by this?
What sources are you using?Also, please post text, not screenshots.Code: Select all
cat /etc/apt/sources.list{,.d/*}
The first step is very easy, for example:
Code: Select all
# cat /etc/apt/sources.list{,.d/*} > sources.list.txt
But now, when you insert the usb memory stick in the computer, things may not be quite so easy and some rigmarole is involved: You'll have to mount it first to be able to copy the file there. To know how to do this, see for example linuxhint.com/mount_usb_drive_debian, before you can copy the file, unmount the memory stick (e.g., in my case doing # umount /dev/sdc) and insert it in the desktop computer to be able to access it there in the GUI to be able to cut and paste a bunch of output.
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
Re: Recovery after update
this is the output for the cat you requested:
i'll try to explain the timeline:
- the original problem's root cause was my attempt to upgrade to bookworm from buster using the now commented source:
- after running into the "authentication token manipulation error" i added the now commented source (which didn't work anyway):
- after running recovery from a usb stick, i changed the buster sources to bullseye to try and fix the current issue (which also didn't work)
what should i try next?
Code: Select all
dro@home:~$ cat /etc/apt/sources.list{,.d/*}
#
# deb cdrom:[Debian GNU/Linux 10.4.0 _Buster_ - Official amd64 NETINST 20200509-10:25]/ buster main
# deb cdrom:[Debian GNU/Linux 10.4.0 _Buster_ - Official amd64 NETINST 20200509-10:25]/ buster main
deb http://deb.debian.org/debian/ bullseye main contrib non-free
deb-src http://deb.debian.org/debian/ bullseye main
deb http://security.debian.org/debian-security bullseye-security main
deb-src http://security.debian.org/debian-security bullseye-security main
# buster-updates, previously known as 'volatile'
deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
deb-src http://deb.debian.org/debian/ bullseye-updates main contrib non-free
# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
deb [arch=amd64] https://download.docker.com/linux/debian bullseye stable
# deb-src [arch=amd64] https://download.docker.com/linux/debian buster stable
# see the sources.list(5) manual.
#deb http://http.us.debian.org/debian/ testing non-free contrib main
#deb http://security.ubuntu.com/ubuntu bionic-security main
deb http://ftp.debian.org/debian bullseye-backports main contrib non-free
cat: '/etc/apt/sources.list.d/*': No such file or directory
- the original problem's root cause was my attempt to upgrade to bookworm from buster using the now commented source:
Code: Select all
#deb http://http.us.debian.org/debian/ testing non-free contrib main
Code: Select all
#deb http://security.ubuntu.com/ubuntu bionic-security main
what should i try next?
Re: Recovery after update
Please read DontBreakDebian.
Copy any files you need to a USB memory stick and reinstall stable and don't muck it up.
Copy any files you need to a USB memory stick and reinstall stable and don't muck it up.
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 12 times
- Been thanked: 66 times
Re: Recovery after update
Yeah, I wouldn't bother spending any time trying to fix that.
AdrianTM wrote:There's no hacker in my grandma...
Re: Recovery after update
Don't mix sources. Nothing from Ubuntu or similar. Everything from Debian.
It's not possible to upgrade to bookworm from buster without first upgrading to current stable.
Testing is a terrible choice for a server. Stable must be used.
Don't install a desktop on a server.
What do you want the server to do?
If I were you I would choose freedombox if you wish to run, for example, wordpress without any hassle.
It's not possible to upgrade to bookworm from buster without first upgrading to current stable.
Testing is a terrible choice for a server. Stable must be used.
Don't install a desktop on a server.
What do you want the server to do?
If I were you I would choose freedombox if you wish to run, for example, wordpress without any hassle.
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
Re: Recovery after update
It's just my home server.. it's not for hosting.
I have a few docker containers running homeassistant, influx, mqtt & grafana for sensors logging/visualization among other things.
It also works as a media server for my kodi client.
It's not really that big a deal to reinstall and i've been wanting to vitrualize for a while now and this gives me the opportunity.
I went for proxmox and i'm experimenting now.
Thanks for the support, guys. I managed to save all the important data.
I have a few docker containers running homeassistant, influx, mqtt & grafana for sensors logging/visualization among other things.
It also works as a media server for my kodi client.
It's not really that big a deal to reinstall and i've been wanting to vitrualize for a while now and this gives me the opportunity.
I went for proxmox and i'm experimenting now.
Thanks for the support, guys. I managed to save all the important data.
Re: Recovery after update
If it is Debian, you can install any package available in the repos. That's an other discussion, should there be GUI in the server.