Jump to content

Debian Buster -- Cannot ssh after apt update/upgrade


ASword
 Share

Go to solution Solved by Igor,

Recommended Posts

I have an N2+ that I'm flashing Debian Buster onto an emm card.  Have tried numerous times in several variations -- flash emm, boot system, log in via ssh, set up personal account, "apt update", "apt upgrade", reboot.  After that I cannot log in via ssh anymore.  I am using the system in headless mode and don't currently have a working serial connection (SiLabs hasn't updated their drivers to Big Sur yet) so I can't tell if the system is booting but ssh isn't working.  Anyone know why "apt upgrade" would cause it to not boot or not present an ssh server properly?

 

Link to comment
Share on other sites

Donate and support the project!

Just now, ASword said:

And is this an "always" problem with Armbian, or just after an update?  Bit of a non-starter for me if its an always.


Two types of problem could explain your symptoms - one is elimited, second is this https://github.com/armbian/build/issues/2106 ... neither is manifesting with my N2+ To diagnose your problem, you have to tell exact steps - we need to reproduce this problem since you didn't provide nothing, no logs to debug. Which image? URL or a exact filename.

Link to comment
Share on other sites

I've noticed that after powering it on there is a period when ssh waits until it says operation timed out, and after a while there is a period when it immediately says the host is down, then it goes back to waiting for it to time out.  Seems to be repeating that at some cadence, so... trying to boot, failing and starting again?

 

Link to comment
Share on other sites

Heh, no, no, not at all.  :)

 

Unfortunately, after I installed a few more things I need (daemons, compilers, etc) it has stopped booting again.  It all seems innocuous and not the kind of things that ought to stop the OS from booting!  I’ll have to start over and reboot after every item to narrow down the cause.

 

Link to comment
Share on other sites

2 hours ago, ASword said:

it has stopped booting again.


Now, this is intriguing and if you want our assistance - you need to tell us everything. All steps which lead you to here. 

 

This should not happen. Only occasional hang at boot loader is present, but that is (always) workarounded with a power cycle.

Link to comment
Share on other sites

Yes, I'm building up a setup script so rebuilding my OS config isn't such a big deal.  Just starting to go systematically through the steps again to see where the boot fails again.  Should have more details soon.

 

Okay, so to be clear:  there is a known hang at boot that requires a manual power cycle?  Good to know while diagnosing my setup script, plus that's a show stopper for me since my application requires automatic and dependable restart after a reboot.  I presume this is being debugged and we can expect an eventual solution?

 

Unfortunately I don't seem to be able to get my N2 to boot at all anymore, using either eMMC nor an SDCard, all with fresh flashes of the latest Armbian build.  A bit mystified by how that can be.

 

Link to comment
Share on other sites

3 hours ago, ASword said:

Okay, so to be clear:  there is a known hang at boot that requires a manual power cycle?  Good to know while diagnosing my setup script, plus that's a show stopper for me since my application requires automatic and dependable restart after a reboot.  I presume this is being debugged and we can expect an eventual solution?

 

Yes, and is random and doesn't manifest for all. Probably it will be fixed soon, perhaps already is. I assume you don't have serial console to debug better - that is handy in such cases.

 

 

Link to comment
Share on other sites

unfortunately SiLabs haven’t updated their OS X drivers to make them BigSur friendly yet, and I needed BigSur for another project.

 

 

Well this is curious (and probably not usefully reproducible).  My N2+ was refusing to boot and re-flashing the eMMC wasn't helping, so I flashed an SDCard and tried that (with eMMC removed).  Didn't work.  In frustration I flipped the MMC/SPI switch to SPI and back, and powered it back on (with both the eMMC and SDCard installed).  Lo'and'behold it booted!  So I went through the initial set-password-and-create-user-account process, then rebooted again... after which I had to do the initial setup process _again_.  Now it boots as expected -- so for some reason the first time it booted from the SDcard, and the second time it booted from the eMMC (with both flash devices inserted).  The docs seem to say it ought to prefer the eMMC if it is present, but apparently it didn't.

 

Anyhow, haven't gotten any further yet.

 

 

 

I think my residual problem arose because I installed too much while backports was in the apt sources list.  By only having it active while I installed clang/llvm 8, and nothing else, I seem to end up in a good state.  So far.

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...