BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] raid controller drivers
- Subject: [Discuss] raid controller drivers
- From: richard.pieri at gmail.com (Richard Pieri)
- Date: Wed, 24 Sep 2014 15:03:48 -0400
- In-reply-to: <CAJFsZ=oKtAu6X144VeEvbASuhNNqyjpJN++UGToS+GDFOo=Muw@mail.gmail.com>
- References: <1411579410.4278.37.camel@micphys04.nci.nih.gov> <5423053D.10400@gmail.com> <1411581461.4278.39.camel@micphys04.nci.nih.gov> <05c001cfd824$75cac900$61605b00$@Polcari.com> <54230D85.8060406@gmail.com> <CAJFsZ=oKtAu6X144VeEvbASuhNNqyjpJN++UGToS+GDFOo=Muw@mail.gmail.com>
On 9/24/2014 2:37 PM, Bill Bogstad wrote: > Or you could just specify your root filesystem with a label or UUID > and it wouldn't matter in what order the kernel enumerated disks. (Or > at least that is the recommended solution to the problem that you > apparently had.) The recommended solutions are at best inconsistent in my experience. I'm sure that it's possible to get one or more of them working consistently, even with LVM volumes on multiport SAS or SATA RAID controllers. I never did. I stopped trying because it's too much work for not nearly enough reward. -- Rich P.
- References:
- [Discuss] raid controller drivers
- From: adler at stephenadler.com (Stephen Adler)
- [Discuss] raid controller drivers
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] raid controller drivers
- From: adler at stephenadler.com (Stephen Adler)
- [Discuss] raid controller drivers
- From: Joe at Polcari.com (Joe Polcari)
- [Discuss] raid controller drivers
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] raid controller drivers
- From: bogstad at pobox.com (Bill Bogstad)
- [Discuss] raid controller drivers
- Prev by Date: [Discuss] raid controller drivers
- Next by Date: [Discuss] Home security & automation
- Previous by thread: [Discuss] raid controller drivers
- Next by thread: [Discuss] raid controller drivers
- Index(es):
