[arch-general] linux-3.5.x status
Thomas Bächler
thomas at archlinux.org
Mon Aug 27 12:06:05 EDT 2012
Am 27.08.2012 17:50, schrieb Geert Hendrickx:
> On Thu, Aug 23, 2012 at 18:34:18 +0200, Thomas Bächler wrote:
>> Am 23.08.2012 18:29, schrieb Geert Hendrickx:
>>> Since upgrading to 3.5.x, my system with mdraid mirror boots with either
>>> a degraded RAID array, or not auto-discovering the RAID at all.
>>>
>>> The disks are fine, confirmed by both SMART selftest and badblocks scan.
>>> Downgraded back to 3.4.9 and the problem went away.
>>>
>>> Anyone else experienced this? My setup should be common, with /boot on
>>> /dev/md0 over sda1+sdb1, and the rest on LVM on /dev/md1 over sda2+sdb2.
>>
>> At home, I have sda1+sdb1 on md0 and sda4+sdb4 on md1, and I don't see
>> any problems.
>
>
> For me it's still very much reproducible though, with either 3.5.2 or 3.5.3.
Can you run add 'break=premount' to the kernel command line and try to
get some mdadm output? I don't know exactly what to look for, but maybe
try to assemble the array with verbose output. By using break=premount,
you hook into the boot process _before_ anything has been written to
your disk, so you don't destroy the consistency of your RAID.
Also, can we see your mdadm.conf? Which mdadm hook are you using, mdadm
or mdadm_udev (I use mdadm_udev btw)?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 897 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-general/attachments/20120827/79f514c6/attachment.asc>
More information about the arch-general
mailing list