[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: cannot access machine after apt-get dist-upgrade



Robert Cates a écrit :



From: Daniel Burrows <dburrows@debian.org>
To: Robert Cates <cates58@hotmail.com>
CC: debian-user@lists.debian.org
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 <debian-user@lists.debian.org>; 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 debian-user@lists.debian.org; Mon, 04 Jun 2007 08:29:21 -0500 (CDT) X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlK+ZzoV09lDsZmbz8QigGIQtU5Yvr3lK0P 
Old-Return-Path: <dburrows@debian.org>
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: debian-user@lists.debian.org
References: <[🔎] 20070601233305.GB10295@alpaca><[🔎] BAY115-F22DF8F781818189A3CE2CA2220@phx.gbl> 
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: <IEG3xC.A.iHD.tOBZGB@murphy>
Resent-From: debian-user@lists.debian.org
X-Mailing-List: <debian-user@lists.debian.org> archive/latest/487457
X-Loop: debian-user@lists.debian.org
List-Id: <debian-user.lists.debian.org>
List-Post: <mailto:debian-user@lists.debian.org>
List-Help: <mailto:debian-user-request@lists.debian.org?subject=help>
List-Subscribe: <mailto:debian-user-request@lists.debian.org?subject=subscribe> List-Unsubscribe: <mailto:debian-user-request@lists.debian.org?subject=unsubscribe> 
Precedence: list
Resent-Sender: debian-user-request@lists.debian.org
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 <cates58@hotmail.com> 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


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Um, how do I set the boot option init=/bin/sh if I can't access the machine?
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 guess I'll probably have to use a Live CD, I was hoping though that maybe somebody on the list already knows right where the problem is. 

Robert
The "init=/bin/sh" could be modified during the OS choice (grub ou lilo) if you have one. With grub, edit the boot option with "e" and modify the launch line with "e" too, add at the end of line "init=/bin/sh" and valid by enter then boot with "b". With lilo, just select the boot option and add at the end of line "init=/bin/sh". This solution is available if you have a boot menu and if your keyboard is detected... Be careful that nothing is mounted except the root partition which is in read-only mode. /proc filesystem isn't mounted too !!!
I can suggest you to boot with a liveCD and paste here log files as /var/log/syslog for example.
If you have a initrd, you should use it. You can create a shell script (with liveCD) and launch it at boot time with "init=/path/to/shell/script". This script can be use to load modules, make "pause" to see the errors, and try to store datas somewhere (usb disk ?). Don't forget to chmod u+x the script shell or you will need a new liveCD boot (believe my experience).... 

Hope this can help you

Christophe

_________________________________________________________________
Don’t miss your chance to WIN $10,000 and other great prizes from Microsoft Office Live http://clk.atdmt.com/MRT/go/aub0540003042mrt/direct/01/
Reply to: