Bug#830300: RE: Bug#830300: bug in mdadm

2016-07-27 Thread Любен Каравелов
I will give it a try in 5 days (currently I am away from the machine and don't want to experiment if it can boot or not with the new conig) and will report back. Thanks for the suggestion. - Цитат от Michael Biebl (bi...@debian.org), на 26.07.2016 в 15:36 - > On Sat, 9 Jul 2016 19:47:07

Bug#830300: RE: Bug#830300: bug in mdadm

2016-07-26 Thread Michael Biebl
On Sat, 9 Jul 2016 19:47:07 +0300 =?utf-8?B?0JvRjtCx0LXQvSDQmtCw0YDQsNCy0LXQu9C+0LI=?= wrote: > Hi, > > The problem I am trying to solve is that my laptop (ASUS Zenbook UX301LAA) is > using Intel RAID0 setup: > > 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller > [RA

Bug#830300: RE: Bug#830300: bug in mdadm

2016-07-16 Thread Любен Каравелов
- Цитат от Michael Biebl (bi...@debian.org), на 16.07.2016 в 15:10 - > On Sat, 9 Jul 2016 19:47:07 +0300 > =?utf-8?B?0JvRjtCx0LXQvSDQmtCw0YDQsNCy0LXQu9C+0LI=?= > wrote: >> Hi, >> >> The problem I am trying to solve is that my laptop (ASUS Zenbook UX301LAA) >> is using Intel RAID0 setup:

Bug#830300: RE: Bug#830300: bug in mdadm

2016-07-16 Thread Michael Biebl
On Sat, 9 Jul 2016 19:47:07 +0300 =?utf-8?B?0JvRjtCx0LXQvSDQmtCw0YDQsNCy0LXQu9C+0LI=?= wrote: > Hi, > > The problem I am trying to solve is that my laptop (ASUS Zenbook UX301LAA) is > using Intel RAID0 setup: > > 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller > [RA

Bug#830300: bug in mdadm

2016-07-09 Thread Любен Каравелов
Hi, The problem I am trying to solve is that my laptop (ASUS Zenbook UX301LAA) is using Intel RAID0 setup: 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04) But it stopped working 5-6 months ago (3.3.2-5 was the last version that was working out

Bug#830300: bug in mdadm

2016-07-09 Thread Christian Hofstaedtler
* Любен Каравелов [160709 09:11]: [..] > echo "export IMSM_NO_PLATFORM=1" >> /conf/param.conf [..] Note that the mdadm man page makes it quite clear that this is not intended for normal operation, but rather mostly desaster recovery. Putting this into param.conf and having it work was pure l

Bug#830300: bug in mdadm

2016-07-07 Thread Любен Каравелов
Package: mdadm Version: 3.4-2 Severity: critical In the initrd image your script should source the /conf/param.conf. This brakes the boot of certain systems that depend on it (like mine). Here is the long explanation: In /scripts/init-premount/export_md_vars I have: #!/bin/sh # skip broken plat