[ML-General] hardware RAID

[david]

Y'all are correct - RAID 1 is mirroring, not RAID 5.  '1' is what the 
disks are.  <another heavy sigh>  I still blame the '60's.

David



On 06/11/15 17:11, david wrote:
> I'm thinking about putting all the computers on the network disk 
> array, including the SOC's: beaglebone blacks, arduino mega256, and 
> the RPi2.  I would not mind doing the compiles (and maybe even the 
> booting!) on the hard drives instead of the limited-life SD cards and 
> 'flash' that are on the SOC's.  Any of you guys done that?  Everything 
> in the house is 1Gb Ethernet.  If only I could get that to the outside 
> world <heavy sigh.> :-)
>  Already have the BBB's booting of the SD card, which you have to do 
> with the rev B's and their 2 Gb size..
>
> David
>
>
>
>
> On 06/11/15 17:01, david wrote:
>> 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.
>>
>> David
>>
>>
>> On 06/11/15 16:56, Brian Oborn wrote:
>>>
>>>
>>> On Thu, Jun 11, 2015 at 4:49 PM, WebDawg <webdawg at gmail.com 
>>> <mailto:webdawg at gmail.com>> wrote:
>>>
>>>
>>>
>>>     On Thu, Jun 11, 2015 at 2:41 PM, david <ainut at knology.net
>>>     <mailto:ainut at knology.net>> wrote:
>>>
>>>         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.
>>>
>>>         Thanks,
>>>         David
>>>
>>>
>>>     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.
>>>
>>>
>>>     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?
>>>
>>>     This was a big failing with software raid. I am sure it could be
>>>     hacked around by placing the bootloader somewhere else...or
>>>     something.
>>>
>>> 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.
>>>
>>>
>>> _______________________________________________
>>> General mailing list
>>> General at lists.makerslocal.org
>>> http://lists.makerslocal.org/mailman/listinfo/general
>>
>>
>>
>> _______________________________________________
>> General mailing list
>> General at lists.makerslocal.org
>> http://lists.makerslocal.org/mailman/listinfo/general
>
>
>
> _______________________________________________
> General mailing list
> General at lists.makerslocal.org
> http://lists.makerslocal.org/mailman/listinfo/general

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.makerslocal.org/pipermail/general/attachments/20150611/6ffbb068/attachment.html>