<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
ZFS sounds really good. What is the problem with it? I don't know
that it covers every conceivable setup but looks really good on
paper. Anyone with long term experience with it and Linux?<br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 06/16/15 11:52, david wrote:<br>
</div>
<blockquote cite="mid:5580545B.8090503@knology.net" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
All of them will fail on boot if there is no other disk/partition
with a boot flag and an OS to load.<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 06/16/15 10:49, WebDawg wrote:<br>
</div>
<blockquote
cite="mid:CAKdd5H8sh9PNfPYDxG2RYPObY1QZ6hniWMEYOX=k=gtssdtu_g@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="h5">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra"><br>
</div>
</div>
</blockquote>
</div>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>I would highly recommend not using any
FakeRAID with Linux. I've done it before (in
order to dual-boot a workstation) and it was a
real pain. If you're going hardware RAID, fine.
But if you're going to do it all in software,
you might as well just use the mdadm in the
normal manner (it's really not that hard) and it
will be more resilient if you need to move it to
a new machine. The few bits in the ROM that the
FakeRAID gives you really do nothing helpful.</div>
</div>
</div>
</div>
<br>
<br>
</blockquote>
<div><br>
</div>
<div>My primary concern is how the bios or Grub would
handle a corrupt/failed boot loader?<br>
<br>
</div>
<div>I have had systems with mdadm/dual bootloaders and
such and I have seen bios's try and boot a failed drive
and just sit there.<br>
<br>
</div>
<div>I have seen bios boot a corrupt boot partition and
really screw things up too. At least I think that was
the problem at the point.<br>
<br>
</div>
<div>Sure once the system is booted mdadm can handle a bad
disk or what not.<br>
<br>
</div>
<div>But what exists to handle a bad /boot or bad
bootloader, etc. The stuff that is not protected by
mdadm.<br>
<br>
</div>
</div>
It always seemed like the FaikeRAID bios at least handled
bad disks on boot.<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
General mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:General@lists.makerslocal.org">General@lists.makerslocal.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.makerslocal.org/mailman/listinfo/general">http://lists.makerslocal.org/mailman/listinfo/general</a></pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
General mailing list
<a class="moz-txt-link-abbreviated" href="mailto:General@lists.makerslocal.org">General@lists.makerslocal.org</a>
<a class="moz-txt-link-freetext" href="http://lists.makerslocal.org/mailman/listinfo/general">http://lists.makerslocal.org/mailman/listinfo/general</a></pre>
</blockquote>
<br>
</body>
</html>