From: Simon McNair <simonmcnair@gmail.com>
To: paul@vandervlis.nl
Cc: 'Brad Campbell' <brad@wasp.net.au>,
linux-raid@vger.kernel.org, lrhorer@satx.rr.com
Subject: Re: Software raid, booting and bios
Date: Sun, 22 May 2011 07:31:48 +0100 [thread overview]
Message-ID: <4DD8ADD4.1050601@gmail.com> (raw)
In-Reply-To: <9A.9E.03893.C8577DD4@cdptpa-omtalb.mail.rr.com>
I think you might want to investigate a SATA DOM (Disk on module). My
Thecus 5200 uses on and it seems a neat solution.
eg
http://www.innodisk.com/flashstorage-list.jsp?items_name=satadom
Simon
On 21/05/2011 09:19, Leslie Rhorer wrote:
>> -----Original Message-----
>> From: linux-raid-owner@vger.kernel.org [mailto:linux-raid-
>> owner@vger.kernel.org] On Behalf Of Brad Campbell
>> Sent: Friday, May 20, 2011 4:52 PM
>> To: linux-raid@vger.kernel.org
>> Subject: Re: Software raid, booting and bios
>>
>> On 21/05/11 03:32, Phil Turmel wrote:
>>
>>> the big deal is the lack of moving parts: No spindle bearing, no head
>> positioner gear train.
>>
>> Sorry, this just tickled me. "gear train" ? Which decade are we talking
>> about? The last drive I saw
>> that had any form of mechanical power transfer mechanism for head
>> positioning was a 60MB RLL Seagate
>> clunker.
> Yeah, the number of moving parts in a hard drive is minimal. OTOH,
> it's not zero.
>
>> Now, to add some form of use to the thread I've been using commodity CF
>> cards in home-brew CF to ATA
>> adaptors in embedded systems for 10 years. Flash is _the_ way to go for
>> high reliability systems
>> that don't have lots of write cycles.
>>
>> My TV box that has no on-board PXE has been booting from a 10MB USB stick
>> using loadlinux since
>> 2003. Dead reliable after ~69,000 hours power on time. I've not had a hard
>> disk last that long since
>> my old 200MB WD IDE drive (which is still running with over 100,000 hours
>> on it).
> Oh, we have quite a number of embedded controllers with SCSI hard
> drives that have been spinning continuously since 1992.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-22 6:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 7:19 Software raid, booting and bios Simon Mcnair
2011-05-20 8:33 ` Paul van der Vlis
2011-05-20 8:56 ` Roman Mamedov
2011-05-20 9:33 ` Paul van der Vlis
2011-05-20 10:00 ` Simon McNair
2011-05-21 16:43 ` Paul van der Vlis
2011-05-20 12:11 ` Phil Turmel
2011-05-20 13:22 ` Gordon Henderson
2011-05-20 15:53 ` Paul van der Vlis
2011-05-20 19:32 ` Phil Turmel
2011-05-20 21:27 ` Roberto Spadim
2011-05-20 21:52 ` Brad Campbell
2011-05-21 8:19 ` Leslie Rhorer
2011-05-22 6:31 ` Simon McNair [this message]
2011-05-20 10:04 ` CoolCold
2011-05-20 19:13 ` Ed W
2011-05-21 16:58 ` Paul van der Vlis
2011-05-21 19:57 ` Ed W
-- strict thread matches above, loose matches on Subject: below --
2011-05-20 6:54 Paul van der Vlis
2011-05-20 7:03 ` Simon Mcnair
2011-05-20 7:14 ` Paul van der Vlis
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=4DD8ADD4.1050601@gmail.com \
--to=simonmcnair@gmail.com \
--cc=brad@wasp.net.au \
--cc=linux-raid@vger.kernel.org \
--cc=lrhorer@satx.rr.com \
--cc=paul@vandervlis.nl \
/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).