Frank Steinmetzger wrote:
> 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 do have a monitor hooked up.  Keep saying I'm going to put the monitor
on the shelf before I bump it and knock it over or something and break
it.  Those screens are touchy.  Nothing like the old CRT days for sure. 

I first tried to login over ssh from my main rig.  Didn't work.  When I
tried to login with the keyboard connected to the machine itself, I
could type in root, hit return and it would sit for a bit, then return
to a login prompt.  It never asked for a password.  I had to use the alt
sysrq key trick to shut it down as graceful as I could without being
able to login. 


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

I meant to leave the one where I tried to ssh in on my screen.  Thing
is, when I complete a task, I tend to clear the screen.  I forgot and
cleared it out of habit and the error was gone.  I don't recall any @
stuff.  To be honest tho, when it failed, I just grabbed the keyboard
and tried it.  I didn't really read it.  It wasn't the usual key don't
match thingy tho.


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

I wouldn't have minded fixing it but it was taking way longer than just
reinstalling from scratch.  I did have backups but just copied what I
needed, nfs, make.conf and such from the old drive.  I didn't need to
copy much over really.  Mostly just settings like make.conf and my
exports file.  Oh, /root as well.  Got my little so called scripts in
there.

Anyway, the install is done now.  It worked last time I booted anyway. 
Could break next time I boot tho, I guess.  :/ 

Dale

:-)  :-) 

Reply via email to