Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
cannot access machine after apt-get dist-upgradeOn Thu, May 31, 2007 at 06:03:06PM +0000, Robert Cates wrote: can you ssh in? A Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
cannot access machine after apt-get dist-upgrade
On Thu, May 31, 2007 at 02:36:45PM -0700, Andrew Sackville-West wrote:
> On Thu, May 31, 2007 at 06:03:06PM +0000, Robert Cates wrote:
> > I've just decided to upgrade my Sarge server to Etch, which the process
> > itself seemed to go very smoothly, but now after rebooting it does not
> > bring up my eth0 and eth1, nor can I input any on the keyboard. In
> > other words, I'm now locked out.
> >
> > The last thing I did was installed kernel/linux image 2.6.18 (with SMP),
> > so I have both the original 2.6.8 as well as the new 2.6.18. Now,
> > regardless of which kernel I boot, I'm locked out. Is there a way I can
> > still access my machine? I'll like to avoid having to completely
> > re-install from fresh.
>
> can you ssh in?
Probably not with eth*.
Although you can't input to the keyboard, can you see the boot messages
scrolling by? Do they provide any clews? Can you boot up the install
CD in rescue mode and read /var/log/dmesg and /var/log/boot? What about
connecting a spare computer to the serial port and issuing a console=
line to the kernel at boot so you can log messages there? What about
booting in rescue, and adding a line to inittab to give you a getty on
the serial line and see if you can log in that way?
Doug.
--
cannot access machine after apt-get dist-upgrade
On Thu, May 31, 2007 at 08:43:35PM -0400, Douglas Allan Tutty wrote:
> On Thu, May 31, 2007 at 02:36:45PM -0700, Andrew Sackville-West wrote:
> > On Thu, May 31, 2007 at 06:03:06PM +0000, Robert Cates wrote:
> > > I've just decided to upgrade my Sarge server to Etch, which the process
> > > itself seemed to go very smoothly, but now after rebooting it does not
> > > bring up my eth0 and eth1, nor can I input any on the keyboard. In
--------------------^^^^^^^^^^^
> >
> > can you ssh in?
>
> Probably not with eth*.
D'oh! sometimes I amaze myself.
A
cannot access machine after apt-get dist-upgrade
On Mon, Jun 04, 2007 at 07:16:54PM +0000, Robert Cates was heard to say:
> >On Sun, Jun 03, 2007 at 11:58:55AM +0000, Robert Cates
> > was heard to say:
> >> this is going to be my new server, so there's no GUI, only text mode,
> >and
> >> it gets all the way to the login prompt, but the machine will not take
> >> keyboard (USB, which is what I always used) input. As I was saying, I
> >can
> >> see during the bootup that the network cards are not started, but I
> >can't
> >> tell why, so I'm therefore also unable to access the machine per remote
> >SSH.
> >
> > OK -- have you tried booting with init=/bin/sh? I'm betting you still
> >won't be able to type, but it might be worth a try. You could also try
> >booting a live CD and using it to examine the system logs for clues about
> >what's happening.
> >
> > Here's another thought: have you been loading the USB/network modules
> >from
> >/etc/modules or from udev/hotplug?
>
> Um, how do I set the boot option init=/bin/sh if I can't access the machine?
Oh, sorry -- you said you were booting different kernels, so I figured
you had access to the bootloader. Never mind then.
> Well, I can't tell from where the USB/network modules are loading from. Is
> this a difference between kernels 2.6.8 and 2.6.18?
I'm not sure, but I doubt it's the kernel upgrade that caused your
problems (since they persist in both kernels). I think the udev/hotplug
protocol did change a few times, but I couldn't tell you how -- however,
the code in udev did change (version 0.056-3 -> version 0.105-4), and
if udev broke *and* udev was loading your USB keyboard driver, that could
explain the problem.
My general hunch is that something in the userspace toolchain that loads
your modules is broken, but I don't know what (for all I know it's as
simple as that you need to run depmod -a).
Daniel
--
cannot access machine after apt-get dist-upgrade
On Thu, May 31, 2007 at 06:03:06PM +0000, Robert Cates was heard to say:
> I've just decided to upgrade my Sarge server to Etch, which the process
> itself seemed to go very smoothly, but now after rebooting it does not
> bring up my eth0 and eth1, nor can I input any on the keyboard. In
> other words, I'm now locked out.
>
> The last thing I did was installed kernel/linux image 2.6.18 (with SMP),
> so I have both the original 2.6.8 as well as the new 2.6.18. Now,
> regardless of which kernel I boot, I'm locked out. Is there a way I can
> still access my machine? I'll like to avoid having to completely
> re-install from fresh.
It sounds like you can access your bootloader. Have you tried booting
with init=/bin/sh and poking around that way?
When you say you can't input anything on the keyboard -- what is
displayed on the screen? Is it showing a graphical login, a text-mode
login, or something completely different?
Daniel
--
cannot access machine after apt-get dist-upgrade
Try booting up a Knoppix CD and poke around from there.
Check /etc/profiles for LD_ASSUME_KERNEL=2.4.## or such. This will murder
recent bash versions (including static). If you have anything like this
ANYWHERE, delete it.
(Old versions of jackd and, according to a poster here, Oracle!! wanted this.)
--
cannot access machine after apt-get dist-upgrade
On Sun, Jun 03, 2007 at 11:58:55AM +0000, Robert Cates was heard to say:
> this is going to be my new server, so there's no GUI, only text mode, and
> it gets all the way to the login prompt, but the machine will not take
> keyboard (USB, which is what I always used) input. As I was saying, I can
> see during the bootup that the network cards are not started, but I can't
> tell why, so I'm therefore also unable to access the machine per remote SSH.
OK -- have you tried booting with init=/bin/sh? I'm betting you still
won't be able to type, but it might be worth a try. You could also try
booting a live CD and using it to examine the system logs for clues about
what's happening.
Here's another thought: have you been loading the USB/network modules from
/etc/modules or from udev/hotplug?
Daniel
--
cannot access machine after apt-get dist-upgrade
Robert Cates a écrit :
>
>> From: Daniel Burrows
>> To: Robert Cates
>> CC:
>> Subject: Re: cannot access machine after apt-get dist-upgrade
>> Date: Mon, 04 Jun 2007 06:27:43 -0700
>> MIME-Version: 1.0
>> Received: from murphy.debian.org ([70.103.162.31]) by
>> bay0-mc6-f15.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668);
>> Mon, 4 Jun 2007 06:30:02 -0700
>> Received: from localhost (localhost [127.0.0.1])by murphy.debian.org
>> (Postfix) with QMQPid 9C1462E140; Mon, 4 Jun 2007 13:29:17 +0000 (UTC)
>> Received: from vms044pub.verizon.net (vms044pub.verizon.net
>> [206.46.252.44])by murphy.debian.org (Postfix) with ESMTP id
>> 320662E160for ; Mon, 4 Jun 2007
>> 13:29:10 +0000 (UTC)
>> Received: from emurlahn.burrows.local ([71.112.26.136]) by
>> vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01
>> (built Apr 3 2006)) with ESMTPA id
>> <0JJ400EAO5GWFZ22@vms044.mailsrvcs.net> for
>> ; Mon, 04 Jun 2007 08:29:21 -0500 (CDT)
>> X-Message-Info:
>> LsUYwwHHNt3660MmjhEvYg2f34OAemlK+ZzoV09lDsZmbz8QigGIQtU5Yvr3lK0P
>> Old-Return-Path:
>> X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-26) on
>> murphy.debian.org
>> X-Spam-Level: X-Spam-Status: No, score=-5.5 required=4.0
>> tests=AWL,BAYES_00,FORGED_RCVD_HELO,LDOSUBSCRIBER,MAILTO_TO_SPAM_ADDR
>> autolearn=no version=3.1.4
>> X-Original-To:
>> References:
>> <20070601233305.GB10295@alpaca>
>>
>> User-Agent: Mutt/1.5.13 (2006-08-11)
>> X-Rc-Virus: 2006-10-25_01
>> X-Rc-Spam: 2007-05-24_01
>> Resent-Message-ID:
>> Resent-From:
>> X-Mailing-List: archive/latest/487457
>> X-Loop:
>> List-Id:
>> List-Post:
>> List-Help:
>> List-Subscribe:
>>
>> List-Unsubscribe:
>>
>> Precedence: list
>> Resent-Sender:
>> Resent-Date: Mon, 4 Jun 2007 13:29:17 +0000 (UTC)
>> Return-Path: bounce-debian-user=cates58=hotmail.com@lists.debian.org
>> X-OriginalArrivalTime: 04 Jun 2007 13:30:03.0469 (UTC)
>> FILETIME=[753A4FD0:01C7A6AC]
>>
>> On Sun, Jun 03, 2007 at 11:58:55AM +0000, Robert Cates
>> was heard to say:
>> > this is going to be my new server, so there's no GUI, only text
>> mode, and
>> > it gets all the way to the login prompt, but the machine will not take
>> > keyboard (USB, which is what I always used) input. As I was saying,
>> I can
>> > see during the bootup that the network cards are not started, but I
>> can't
>> > tell why, so I'm therefore also unable to access the machine per
>> remote SSH.
>>
>> OK -- have you tried booting with init=/bin/sh? I'm betting you still
>> won't be able to type, but it might be worth a try. You could also try
>> booting a live CD and using it to examine the system logs for clues
>> about
>> what's happening.
>>
>> Here's another thought: have you been loading the USB/network modules
>> from
>> /etc/modules or from udev/hotplug?
>>
>> Daniel
>>
>>
>> --