From: Barry Scott <barry.scott@onelan.co.uk>
To: linux-ide@vger.kernel.org
Subject: 2.6.16.20 fails to boot on SATA system but works on IDE
Date: Fri, 16 Jun 2006 17:36:15 +0100 [thread overview]
Message-ID: <4492DDFF.6010303@onelan.co.uk> (raw)
I originally post to linux kernel dev list. But guess that this is a
more appropriate list to ask for help on.
After failing to get 2.6.17-rc6 working on a HP dc7600U I went back
to 2.6.16.20. It also fails to find any volume group during boot.
I think this might be problem with SATA as I can boot the same build on
two other systems that have IDE disks.
I get success on VIA Epia M10000 and a P4 Shuttle systems that use
IDE disks but fail on the HP dc7600U that uses a SATA disk. All three
systems use LVM2.
The Fedora build of 2.6.16 works on all three systems.
I'm going to see if there are debug messages I can turn on it libata
and md that might give more information.
Any suggestions as to what I can do to track down this problem?
Barry
next reply other threads:[~2006-06-16 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 16:36 Barry Scott [this message]
2006-06-20 13:44 ` 2.6.16.20 fails to boot on SATA system but works on IDE Barry Scott
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=4492DDFF.6010303@onelan.co.uk \
--to=barry.scott@onelan.co.uk \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).