From: Robert Hancock <hancockrwd@gmail.com>
To: DanVolkman <danvolkman@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.32-22-generic sata problems
Date: Sun, 06 Jun 2010 01:49:27 -0600 [thread overview]
Message-ID: <4C0B5307.1020206@gmail.com> (raw)
In-Reply-To: <4C0A6326.1090100@gmail.com>
On 06/05/2010 08:45 AM, DanVolkman wrote:
> SYNOPSES
> ==========
> Kernel fails to boot when multiple SATA drives are connected. After a
> day of working on the problem (changing cables, sata positions,
> motherboards, CPUs, power supplies, etc.) I discovered that with only
> the boot drive connected everything worked fine.
>
> BACKGROUND
> =============
> I had a career in UNIX so it is common for me to use cpio(1), tar(1),
> dump(1), and dd(1) to replicate disks but have not been able to do so
> with two SATA disks connected using older kernels but with this new
> kernel I could not even have the second disk connected.
>
> PROBLEM APPEARED WHEN
> ======================
> An Ubuntu kernel update stopped my computer from booting. I have no
> backup computer so my description is sketchy because I was not willing
> to use a pencil and write the lengthy terse information. Boot error
> message was something like:
>
> Gave up waiting for root device. Common problems:0f106d71e58
> ...
> ALERT! /dev/disk/by-uuid/..... does not exist. Dropping to a shell!
Can you get any of the libata messages showing up on the console? You
might need to change grub options to boot with more debug displayed
(don't know how to do that offhand on Ubuntu).
next prev parent reply other threads:[~2010-06-06 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 14:45 Kernel 2.6.32-22-generic sata problems DanVolkman
2010-06-06 7:49 ` Robert Hancock [this message]
2010-06-06 10:42 ` Alejandro Riveira Fernández
2010-06-07 18:34 ` DanVolkman
2010-06-07 23:35 ` Robert Hancock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C0B5307.1020206@gmail.com \
--to=hancockrwd@gmail.com \
--cc=danvolkman@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox