public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Mark Knecht <markknecht@gmail.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Drives missing at boot
Date: Sat, 03 Jul 2010 18:01:15 +0200	[thread overview]
Message-ID: <4C2F5ECB.1040505@kernel.org> (raw)
In-Reply-To: <AANLkTimVkG9TFgyOTTnrztBjqT4JoOzFaP268vWLAAm9@mail.gmail.com>

(cc'ing linux-ide)

On 07/02/2010 07:56 PM, Mark Knecht wrote:
> Hi,
>    I have a newish machine - maybe 3 months old - which unreliably
> finds its disk drives at each boot. Probably 40% of the time booting 1
> or more drives will be missing.
> 
>    So far I've been unable to determine what might be wrong. Sometimes
> it finds all 5 drives, sometimes only 4 or 3 drives. It's not always
> the same drives that are missing. Shown below are two successive warm
> boots. The machien had been running with all 5 drives working. The
> first time through it missed both /dev/sdd and /dev/sde while the very
> next time it found all 5 drives. Each of the 5 drives has been missing
> one or more times at different boots. (I.e. - it's not always drive
> sdd for instance.)
> 
>    Every time I boot the AMI BIOS screen says all 5 drives are there.
> I have found that if I drop into BIOS before going to grub that
> selecting each drive one at a time and reading through it's setup
> seems to make the boot more reliable, but not 100%. Probably 80%
> reliable.
> 
>    I don't know what info is required to look at this. I'm running the
> newest Gentoo kernel but it's been happening with all kernels I've
> tried since I built the machine. I'm attaching the kernel config as
> well as dmesg from the last boot which had all the drives. The only
> difference in dmesg when the drives don't show up (that I've spotted)
> is that the missing drive just isn't in dmesg. (I.e. no error messages
> that I could spot.)
> 
>    Let me know what I might try or what other info you might want. The
> motherboard is an Asus Rampage II Extreme with an i7-980x 6 core/12
> thread processor. sda, sdb & sdc are part of a RAID1, sdd & sde are
> part of a RAID0.

Can you please *attach* full logs of a successful boot and several
failing boots?

Thanks.

-- 
tejun

  parent reply	other threads:[~2010-07-03 16:01 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02 17:56 Drives missing at boot Mark Knecht
2010-07-03 15:20 ` Mark Knecht
2010-07-03 16:01 ` Tejun Heo [this message]
2010-07-03 16:06   ` Mark Knecht
2010-07-03 16:13     ` Tejun Heo
2010-07-03 16:42       ` Mark Knecht
2010-07-05  6:30         ` Tejun Heo
2010-07-05 16:56           ` Mark Knecht
2010-07-06  6:33             ` Tejun Heo
2010-07-06 18:13               ` Mark Knecht
2010-07-07  5:50                 ` Tejun Heo
2010-07-07 15:34                   ` Mark Knecht
2010-07-07 15:48                     ` Tejun Heo
2010-07-07 16:15                       ` Mark Knecht
2010-07-07 16:19                         ` Tejun Heo
2010-07-07 16:27                           ` Mark Knecht
2010-07-07 17:06                       ` Mark Knecht
2010-07-07 17:26                         ` Tejun Heo
2010-07-07 17:32                           ` Mark Knecht
2010-07-19 19:31                           ` Mark Knecht
2010-07-19 21:01                             ` Tejun Heo
2010-07-20  3:14                               ` Paul Check
2010-07-20 14:14                                 ` Tejun Heo
2010-07-20 14:53                                   ` Mark Knecht
2010-07-20 16:16                                     ` Mark Knecht
2010-07-21 20:54                                   ` Mark Knecht
2010-07-21 21:22                                     ` Paul Check
2010-07-22 12:39                                     ` Tejun Heo
2010-08-02 22:07                                       ` Mark Knecht
2010-08-03 18:41                                         ` Randy Dunlap
2010-08-03 18:47                                           ` Mark Knecht
2010-08-03 18:55                                             ` Randy Dunlap
2010-08-04 16:16                                               ` Mark Knecht
2010-08-03 18:49                                           ` Jim Paris
2010-08-03 18:53                                             ` Mark Knecht
2010-07-20 20:52                                 ` Mark Knecht
2010-07-20 21:19                                   ` Paul Check
2010-07-20 21:26                                     ` Mark Knecht
2010-07-20 23:05                                       ` Paul Check
2010-07-03 18:56     ` Stan Hoeppner
2010-07-03 19:21       ` Mark Knecht
2010-07-03 19:42         ` Stan Hoeppner
2010-07-03 19:57           ` Mark Knecht
2010-07-03 22:31             ` Mark Knecht
2010-07-04  1:25               ` Thomas Fjellstrom
2010-07-05  6:19               ` Tejun Heo
2010-07-05 16:48                 ` Mark Knecht
2010-07-05 23:59                   ` Robert Hancock
2010-07-06  4:16                     ` Mark Knecht
2010-07-06  6:13                       ` Stan Hoeppner
2010-07-06 11:26                       ` Sander
2010-07-06  6:32                   ` Tejun Heo

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=4C2F5ECB.1040505@kernel.org \
    --to=tj@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markknecht@gmail.com \
    /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