lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C2F9292.708@hardwarefreak.com>
Date:	Sat, 03 Jul 2010 14:42:10 -0500
From:	Stan Hoeppner <stan@...dwarefreak.com>
To:	Mark Knecht <markknecht@...il.com>
CC:	Tejun Heo <tj@...nel.org>,
	Linux Kernel List <linux-kernel@...r.kernel.org>,
	"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>
Subject: Re: Drives missing at boot

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ