Re: A few remaining questions about installing to RAID-10

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri Oct 02, 2009 at 07:54:04AM -0700, Ben DJ wrote:

> Hi everybody,
> 
> 2009/10/2 Keld Jørn Simonsen <keld@xxxxxxxx>: 
> > You can boot from a raid-10,n2 with the superblock last, standard
> > raid10,n2 will do. But the normal thing is to boot from raid-1
> >
> > There is a description of a setup at
> > http://linux-raid.osdl.org/index.php/Preventing_against_a_failing_disk
>
> Thanks for the URL.  Is there a reason that raid-1 is the "normal
> thing"? Just popularity or something technical?

The main reason is that RAID-1 works across any number of disks (as
they're all identical) whereas RAID-10,nX working is an artifact of how
that layout works for X drives (they end up being identical to RAID-1).

> On Fri, Oct 2, 2009 at 12:54 AM, Robin Hill <robin@xxxxxxxxxxxxxxx> wrote:
> > With OpenSUSE you can just switch to the second console at that point of
> 
> I didn't know about the console switching option, thanks.  I'll look
> for docs on how to switch; I guess a F-key does the trick.  As far as
> you know, even though the graphical installers don't offer RAID-10
> config as an option, are they RAID-10 aware enough to correctly
> recognize/identify the array as RAID-10 after manual setup then
> rescan?
> 
> SystemRescueCD approach still seems straightforward too, and can be
> doc'd as doable across any OS install.
> 
Yes, Alt-F2 will get you to the second console, Alt-F3 for the third (or
Ctrl-Alt-F2 from within X).  The installer uses some of the consoles for
progress/debugging output, but at least one of them is just a basic
shell so you can run any normal commands from there.

The installer is sufficiently RAID-10 aware to pick up the arrays (if
not, the SystemRescueCD approach wouldn't work either).

> On Fri, Oct 2, 2009 at 5:30 AM, adfas asd <chimera_god@xxxxxxxxx> wrote:
> > I am booting just fine from a RAID10-o2 array, although I'm told I'm
> > not supposed to.
> 
> Why "not supposed to"?  Is it the RAID 10? or the 'o2' that's the problem?
> 
It's the combination - RAID10,o2 for 2 drives results in one drive
having all data in normal order (so bootable) and the other having every
pair of chunks flipped.  I'm surprised that the bootloader even
recognises the filesystem, let alone manages to boot from it.

Cheers,
    Robin

P.S. The Wikipedia entry for Non-standard RAID levels has diagrams for a
number of the Linux RAID-10 layouts which may help to understand why
some layouts boot and others don't.
-- 
     ___        
    ( ' }     |       Robin Hill        <robin@xxxxxxxxxxxxxxx> |
   / / )      | Little Jim says ....                            |
  // !!       |      "He fallen in de water !!"                 |

Attachment: pgps62NEVwQjJ.pgp
Description: PGP signature


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux