From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rudy Zijlstra Subject: Re: Kernel 2.6.32-5-amd64 fails to boot. Date: Tue, 01 Feb 2011 22:02:10 +0100 Message-ID: <4D4874D2.601@grumpydevil.homelinux.org> References: <1D.26.13137.882784D4@cdptpa-omtalb.mail.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1D.26.13137.882784D4@cdptpa-omtalb.mail.rr.com> Sender: linux-raid-owner@vger.kernel.org To: lrhorer@satx.rr.com Cc: 'Linux RAID' List-Id: linux-raid.ids On 02/01/2011 09:52 PM, Leslie Rhorer wrote: >> On 02/01/2011 09:23 PM, Leslie Rhorer wrote: >> >> >>> doesn't boot, either. It gives a bit more detail in the output, but >>> >> nothing >> >>> illuminating. The old kernel (2.6.32-3-amd64) boots just fine. >>> >>> >> Can you enable serial console and catch the console output that way? >> > Well, not easily. I don't have a serial terminal. I suppose I > could set something up. You're suggesting I poke around to see what md is > reporting? Also, I'm not sure why - if the keyboard console is failing - > the serial console would work better. > > > Serial console can be captured to a file and then the output analysed. So you can read afterwards the messages that are flying past. What i do in such case, is that i take serial connector from a laptop, and run a terminal emulater like minicom. And capture it to a file so i can analyse what has been happening.