On 04.10.2021 03:41, Joe Pfeiffer wrote:
That's not it then... googling "md127" I found a *bunch* of possible
causes.
I tried already updating the name attribute, setting the homehost to
none and a few others. Unfortunately none helped.
Reiner Buehl writes:
> On 02.10.2021 01:32, Joe Pfeiffer wrote:
>> Is it possible you need to update your init ramdisk? Maybe your changes
>> to your mdadm.conf aren't being seen?
>
> I do run update-initramfs -u after each change. Shouldn't that be
> enough to to update the mdadm.conf in the ini
On Fri, 1 Oct 2021, Joe Pfeiffer wrote:
Tim Woodall writes:
On Fri, 1 Oct 2021, Reiner Buehl wrote:
On 01.10.2021 16:11, Felix Miata wrote:
Mine (old) is like so:
# head -n3 /etc/mdadm.conf
HOMEHOST
DEVICE containers partitions
ARRAY /dev/md0 metadata=1.0 name=msi85:0tmp UUID=...
I tried
On 02.10.2021 01:32, Joe Pfeiffer wrote:
Is it possible you need to update your init ramdisk? Maybe your changes
to your mdadm.conf aren't being seen?
I do run update-initramfs -u after each change. Shouldn't that be enough
to to update the mdadm.conf in the init ramdisk?
Tim Woodall writes:
> On Fri, 1 Oct 2021, Reiner Buehl wrote:
>
>> On 01.10.2021 16:11, Felix Miata wrote:
>>> Mine (old) is like so:
>>> # head -n3 /etc/mdadm.conf
>>> HOMEHOST
>>> DEVICE containers partitions
>>> ARRAY /dev/md0 metadata=1.0 name=msi85:0tmp UUID=...
>> I tried changing the HOME
On Fri, 1 Oct 2021, Reiner Buehl wrote:
On 01.10.2021 16:11, Felix Miata wrote:
Mine (old) is like so:
# head -n3 /etc/mdadm.conf
HOMEHOST
DEVICE containers partitions
ARRAY /dev/md0 metadata=1.0 name=msi85:0tmp UUID=...
I tried changing the HOMEHOST from to but that did not
help.
I've
On 01.10.2021 16:11, Felix Miata wrote:
Mine (old) is like so:
# head -n3 /etc/mdadm.conf
HOMEHOST
DEVICE containers partitions
ARRAY /dev/md0 metadata=1.0 name=msi85:0tmp UUID=...
I tried changing the HOMEHOST from to but that did not
help.
On 01.10.2021 15:50, Linux-Fan wrote:
I have observed this in the past, too and do not know how to "fix" it.
Why is it necessary for the volume to appear under /dev/md3? Might it
be possible to use its UUID instead, i.e. check the output of
ls -l /dev/disk/by-uuid
to find out if your m
Reiner Buehl composed on 2021-10-01 11:11 (UTC+0200):
> I created a new mdadm RAID 1 as /dev/md3. But after each reboot, it gets
> activated as md127. How can I fix this - preferably without haveing to
> delete the whole array again...
> The array is defined like this in /etc/mdadm:
> ARRAY /dev/
Reiner Buehl writes:
I created a new mdadm RAID 1 as /dev/md3. But after each reboot, it gets
activated as md127. How can I fix this - preferably without haveing to delete
the whole array again...
The array is defined like this in /etc/mdadm:
ARRAY /dev/md3 metadata=1.2 level=raid1 num-dev
I created a new mdadm RAID 1 as /dev/md3. But after each reboot, it gets
activated as md127. How can I fix this - preferably without haveing to
delete the whole array again...
The array is defined like this in /etc/mdadm:
ARRAY /dev/md3 metadata=1.2 level=raid1 num-devices=1
UUID=41e0a87f:22a2205
11 matches
Mail list logo
