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.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org