Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756026Ab0GCTmN (ORCPT ); Sat, 3 Jul 2010 15:42:13 -0400 Received: from mo-65-41-216-221.sta.embarqhsd.net ([65.41.216.221]:52478 "EHLO greer.hardwarefreak.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755776Ab0GCTmM (ORCPT ); Sat, 3 Jul 2010 15:42:12 -0400 Message-ID: <4C2F9292.708@hardwarefreak.com> Date: Sat, 03 Jul 2010 14:42:10 -0500 From: Stan Hoeppner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: Mark Knecht CC: Tejun Heo , Linux Kernel List , "linux-ide@vger.kernel.org" Subject: Re: Drives missing at boot References: <4C2F5ECB.1040505@kernel.org> <4C2F87C1.8000701@hardwarefreak.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1715 Lines: 43 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/