I tried a lot of things but finally saw in the rdsosreport.txt that the kernel
was seeing the array but refusing to use it. It was several months ago so
that's
about all I remember.
Bill
On 10/4/2015 5:01 PM, Alex wrote:
Hi,
I ran into this or something similar. My system would boot fine
Hi,
> I ran into this or something similar. My system would boot fine on
> an older kernel but fail on a new oue. Can't remember which one worked
> and which didn't. The solution I found was remove the bitmap, re-boot on
> the newer kernel, and add the bitmap back.
>
> # remove
> mdadm --grow --
I ran into this or something similar. My system would boot fine on
an older kernel but fail on a new oue. Can't remember which one worked
and which didn't. The solution I found was remove the bitmap, re-boot on
the newer kernel, and add the bitmap back.
# remove
mdadm --grow --bitmap=none /dev/
So despite grub2 acknowledging that the currently running system has
RAID support, provides a hint for the md device, loads the mdraid1x
and other RAID drivers and modules, it for some reason changed to not
automatically starting any RAID devices on boot.
Added "rd.auto" to the linux16 command lin
HI,
I have a fedora22 system that's been working fine for some time, but
any new kernels fail to boot properly. The system is configured with
/boot and / on RAID1. The rdsosreport.txt that dracut produces shows
no indication of md RAID support in /proc/mdstat and no RAID devices
listed with blkid
