From: Stan Hoeppner <stan@hardwarefreak.com>
To: Mark Knecht <markknecht@gmail.com>
Cc: Tejun Heo <tj@kernel.org>,
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 14:42:10 -0500 [thread overview]
Message-ID: <4C2F9292.708@hardwarefreak.com> (raw)
In-Reply-To: <AANLkTimVJEO-yF3GZ2ghX6DNPuAu-A-MNNO9x8Q1EpRc@mail.gmail.com>
Mark Knecht put forth on 7/3/2010 2:21 PM:
> Note two things:
>
> 1) All the drives are always reported by BIOS at boot time. Now, that
> doesn't guarantee that the drives spin up. It may only mean they can
> be read by BIOS, but they are there as far as I can tell. They show up
> in the boot screens and in BIOS itself if I drop in to play with
> settings.
I missed that. I thought I read it was both. My bad.
> QUESTION: There are some settings in BIOS for delaying the drive. (Or
> something. I'm using the machine and not in BIOS) There were settings
> from 0 to 35 seconds if I remember correctly. Possibly I should try
> setting each drive to a different value to different value to stagger
> power up?
If that PSU meets published specs you shouldn't need delayed spin up with
those 5 drives.
> If you need more info or have other ideas please let me know.
Your answers here should have pretty much eliminated hardware issues as the
cause, unless that particular mobo has BIOS or other issues I'm unaware of.
I've found it's always best to ask about hardware with this kind of report
just to eliminate possibilities. All that gear is good quality stuff. If the
problem is due to hardware, it's because one of your components is defective,
but we don't see evidence of that at this point.
Also, TTBOMK, if a SATA drive motor doesn't spin up, the drive firmware won't
report the drive as ready upstream, thus the BIOS won't list the drive.
--
Stan
next prev parent reply other threads:[~2010-07-03 19:42 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
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 [this message]
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=4C2F9292.708@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=tj@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