On 8. Nov 2017, at 21:58, deloptes wrote:
>
> Tobx wrote:
>
>> VERBOSE=false
>
> perhaps set to true and see what it says.
The comment to this option states:
# if this variable is set to true, mdadm will be a little more verbose e.g.
# when creating the initramfs.
On 8. Nov 2017, at 22:40, deloptes wrote:
> How is this possible and how to solve it - I would simply add 3rd 500MB disk
> to the raid and remove one of the others, but still what is the impact of
> this (stupid) coincidence …
I would not call it coincidence, what are the odds? There must be a r
I was on 4.9.0-4 (Stretch), now tried with 4.13.0-0 but had no luck.
I also tried it again on a clean Ubuntu-Server 17.10 with Kernel 4.13.0-16 and
had exactly the same issue:
RAID assembling at boot only works when no journal device is involved.
> On 7. Nov 2017, at 20:04, deloptes wrote:
>
Hello,
I try to get a RAID 5 array to assemble at boot with mdadm:
# mdadm --create /dev/md/test --level=5 --raid-devices=3
--write-journal=/dev/sde1 /dev/sd[bcd]1
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md/test started.
# /usr/share/mdadm/mkconf > /etc/mdadm/mdadm.conf
# upd
4 matches
Mail list logo