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.
I tried that, but I did
Tobx wrote:
> RAID assembling at boot only works when no journal device is involved.
>
I can't help much here, nothing to compare. I forgot to mention that md
driver is compiled in the kernel in my case.
> VERBOSE=false
perhaps set to true and see what it says.
>
> Options in /etc/mdadm/mdad
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:
>
Tobx wrote:
> What am I missing?
I don't know if it is related and I don't use raid5, but rather raid1, and
in the past year or so I had experienced similar with our server. Now I run
4.12.10 and noticed in the changelog/release notes that there are a lot of
fixes in the md stack. The issues are
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
5 matches
Mail list logo
