On Thu, Sep 02, 2021 at 03:51:05PM +0200, Ignatios Souvatzis wrote:
> I read it as such. Remember, our bootloader doesn't really understand
> raidframe; we're cheating. It only knows an additional offset, which
> happens (well, we did it un porpose) to be where a raid0 root partition
> is inside
Hi,
On Thu, Sep 02, 2021 at 03:56:09PM +0200, Edgar Fuß wrote:
> I do know that, but the warning seems to be new.
> It didn't appear before, but I had -A root (which now is force) before.
Thats from x86's findroot() in x86_autoconf.c 1.1 (at least, I
haven't looked into 86_64 and i386), which
I do know that, but the warning seems to be new.
It didn't appear before, but I had -A root (which now is force) before.
Hi,
On Thu, Sep 02, 2021 at 02:43:00PM +0100, Patrick Welche wrote:
> On Thu, Sep 02, 2021 at 03:36:50PM +0200, Edgar Fu? wrote:
> > > > WARNING: findroot: double match for boot device (sd4, sd5)
> > > > (where sd4a/5a are raid2's components) before
> > > > boot device: raid2
> >
On Thu, Sep 02, 2021 at 03:36:50PM +0200, Edgar Fu? wrote:
> > > Additinally, I got
> > > WARNING: findroot: double match for boot device (sd4, sd5)
> > > (where sd4a/5a are raid2's components) before
> > > boot device: raid2
> > > root on raid2a dumps on raid2b
> > > What does that mean?
>
> > Additinally, I got
> > WARNING: findroot: double match for boot device (sd4, sd5)
> > (where sd4a/5a are raid2's components) before
> > boot device: raid2
> > root on raid2a dumps on raid2b
> > What does that mean?
>
> Is this with -current newer than
>
>
On Thu, Sep 02, 2021 at 01:45:29PM +0200, Edgar Fu? wrote:
> Additinally, I got
> WARNING: findroot: double match for boot device (sd4, sd5)
> (where sd4a/5a are raid2's components) before
> boot device: raid2
> root on raid2a dumps on raid2b
> What does that mean?
Is this with
On Thu, Sep 02, 2021 at 01:45:29PM +0200, Edgar Fuß wrote:
> If I have a number of autoconfigured RAIDframe sets on one machine, is there
> any guarantee which raid* number a set gets assigned? Is that numbering
> stable even if I remove one set (in the sense of physically un-plugging the
>
If I have a number of autoconfigured RAIDframe sets on one machine, is there
any guarantee which raid* number a set gets assigned? Is that numbering
stable even if I remove one set (in the sense of physically un-plugging the
drives) so the components will get different sd* numbers?
I had raid0
