<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
There was an itsy-bitsy blurb about it on Debian's site but there
were no details given and, doing Yet Another Fresh Install
(copyright), I could not find it in any of the auto OR manual disk
setups. <sigh> This was less than a month ago.<br>
<br>
David<br>
<br>
<br>
<div class="moz-cite-prefix">On 06/11/15 16:56, Brian Oborn wrote:<br>
</div>
<blockquote
cite="mid:CAFtQAgR42KbZa+j-JQ-yFc+741_DAosPhkm9YM2HQsr5RnGkDA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Jun 11, 2015 at 4:49 PM,
WebDawg <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:webdawg@gmail.com" target="_blank">webdawg@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote"><span class="">On Thu, Jun
11, 2015 at 2:41 PM, david <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:ainut@knology.net"
target="_blank">ainut@knology.net</a>></span>
wrote:<br>
</span><span class="">
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> Software
Linux raid is fine with the striping but it
sucks at mirroring. The second (mirror) drive
is NOT identical in any shape form or
fashion. Even the partitions are different.
And it is not bootable!!! In mirroring, I
want immediate fail-over, or at most, one
shutdown, remove/replace drive, then back up
right where I was.<br>
<br>
Thanks,<br>
David<br>
</div>
</blockquote>
<div><br>
</div>
</span>
<div>I agree. I had to go through hell with a
Debian mdadm system to install the boot loader on
both drives. I know this is a problem with a few
software raid solutions.<br>
<br>
<br>
</div>
<div>Anyone know if this has been fixed in any OS +
Filesystem/Software Raid? One of the things that
killed me was if the bootloader was corrupted on
one disk, or the disk was partially corrupted or
something, in a software raid scenario, the bios
has to know to move to the next disk, but when
does that ever happen?<br>
<br>
</div>
<div>This was a big failing with software raid. I
am sure it could be hacked around by placing the
bootloader somewhere else...or something.<br>
<br>
</div>
</div>
</div>
</div>
</blockquote>
<div> </div>
</div>
Again, this isn't a problem with the software RAID, but just
how Linux works. mdadm doesn't know anything about the MBR
since it's not in a partition. Instead you configure the
bootloader to install itself on the MBR of both drives. IIRC
some installers (Debian maybe?) offered to do this for you.</div>
</div>
<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>