Bug#799226: linux-image-4.1.0-2-amd64: Not able to mount LVM RAID1 file system at boot

2016-10-24 Thread Simon Richter
Source: linux Version: 3.16.36-1+deb8u2 Followup-For: Bug #799226 Hi, this bug is also in the stable kernel, and the one currently in testing. It is caused by the kernel not writing the bitmap information to the meta LV. I can reproduce this here with an Areca RAID controller, but not with

Bug#799226: linux-image-4.1.0-2-amd64: Not able to mount LVM RAID1 file system at boot

2016-02-05 Thread Vladimir K
I also see this happening on Debian Jessie with kernel 3.16.7-ckt20-1+deb8u3 (and older 3.2). Root is on LVM RAID1, boot fails with error: device-mapper: table: 253:11: raid: Fail to run raid array In initramfs prompt I am able to see only technical volumes *_mlog_mimage_*, *_mimage_*,

Bug#799226: linux-image-4.1.0-2-amd64: Not able to mount LVM RAID1 file system at boot

2015-09-16 Thread Olaf Meeuwissen
Package: src:linux Version: 4.1.6-1 Severity: normal Dear maintainer(s), I recently put one of my file systems on LVM RAID1. All is fine when I lvconvert or lvcreate the RAID1 mirror on a running kernel. The problem is when I reboot the system. The linux-image-4.1.0-1-amd64 is affected by the