Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #52589 > unrolled thread
| Started by | Vladimir K <pzs-fs@yandex.ru> |
|---|---|
| First post | 2016-02-05 17:50 +0100 |
| Last post | 2016-02-05 17:50 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.debian.kernel
Bug#799226: linux-image-4.1.0-2-amd64: Not able to mount LVM RAID1 file system at boot Vladimir K <pzs-fs@yandex.ru> - 2016-02-05 17:50 +0100
| From | Vladimir K <pzs-fs@yandex.ru> |
|---|---|
| Date | 2016-02-05 17:50 +0100 |
| Subject | Bug#799226: linux-image-4.1.0-2-amd64: Not able to mount LVM RAID1 file system at boot |
| Message-ID | <qYRK2-2JM-23@gated-at.bofh.it> |
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_*, but not the root volume itself.
Trying to run 'lvm lvchange -a y' with volume name results in:
device-mapper: reload ioctl on failed: Invalid argument
Had to boot from live system and split the mirror.
Back to top | Article view | linux.debian.kernel
csiph-web