From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Grub fails. I missed something.
Date: Sun, 23 Mar 2025 23:28:57 +0100 [thread overview]
Message-ID: <Z-CLKUxL-83mp-ni@q> (raw)
In-Reply-To: <3e9d408c-2dca-8742-ec3e-1789d725cf26@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2005 bytes --]
Am Sun, Mar 23, 2025 at 12:41:31AM -0500 schrieb Dale:
> Dale wrote:
> >
> > Sorry it took me a bit to do anything with this. We still working on
> > that tree. We getting close to being done. Anyway, I mounted the new
> > SSD OS on the old OS and copied over /etc and /root again. I really
> > don't need /home much since I only use root on that thing. Oh, for
> > fstab, I used the same labels on each. After doing that, I shutdown,
> > unplugged the old drive and booted the SSD OS up. I was able to login
> > over ssh even. I'm sure something in /etc was messed up somehow. I
> > think it worked a couple times before failing. So, this time, I did
> > several reboots and shutdowns just to be as sure as I could be. It
> > worked each time.
>
> Well, it took a little longer than I expected. I booted the NAS box to
> update my backups. It booted just fine, couldn't login tho.
How do you know it booted fine? Did you have a monitor attached?
Could you log in locally with a keyboard?
> I usually
> use ssh and meant to save the error but already cleared the Konsole.
> Force of habit. My plan, reinstall the OS on the SSD and be done with
> it.
Would be really helpful to know the error message. For instance whether it
came from ssh, the network, PAM or whatever else is involved in the login
process. Perhaps it’s got something to do with ssh host keys, because after
moving the SSD, the system has a different IP, but your machine still knows
the host key from a different IP.
Did the error message start with @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@?
> It likely has a simple fix but it's either reinstall or target practice.
Due to the nature of Gentoo, I’d always prefer fixing over reinstall. It’s
just faster and better for the environment.
--
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.
The best thing of Sundays is Saturday evening.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-03-23 22:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-15 7:29 [gentoo-user] Grub fails. I missed something Dale
2025-03-15 9:18 ` Michael
2025-03-15 20:42 ` Dale
2025-03-15 21:43 ` eric
2025-03-16 2:15 ` William Kenworthy
2025-03-16 5:04 ` Dale
2025-03-16 5:34 ` William Kenworthy
2025-03-16 7:30 ` Dale
2025-03-16 9:58 ` Dale
2025-03-16 11:40 ` Michael
2025-03-16 14:05 ` Michael
2025-03-16 19:14 ` Dale
2025-03-17 1:01 ` [gentoo-user] " Grant Edwards
2025-03-17 2:34 ` Dale
2025-03-17 8:21 ` Michael
2025-03-17 13:28 ` Grant Edwards
2025-03-17 3:50 ` [gentoo-user] " Dale
2025-03-17 8:10 ` Michael
2025-03-20 2:25 ` Dale
2025-03-23 5:41 ` Dale
2025-03-23 22:28 ` Frank Steinmetzger [this message]
2025-03-24 0:38 ` Dale
2025-03-18 22:35 ` Frank Steinmetzger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z-CLKUxL-83mp-ni@q \
--to=warp_7@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox