Bug#621786: mdadm: invalid pointer or memory corruption on armel system

Hi, Sorry for the late answer, I'm not using this email address very often... You can close this issue, I believe this was more hardware related. I don't remember to encounter this issue since a while and now I'm using a new hardware. Thanks, Arnaud On 05/12/2014 15:59, Michael Tokarev wro

Bug#621786: One Thought/Thing to Try

/dev) ALERT! /dev/disk/by-uuid/695192e7-148e-4d02-8588-4d2fc3f8c978 does not exist. Dropping to a shell! === Arnaud Le 15/07/2011 05:34, Arnaud Desmier a écrit : Hi Neil, I've applied your patch and it is working well, no more crash with DEVICE=

Bug#621786: One Thought/Thing to Try

Hi Neil, I've applied your patch and it is working well, no more crash with DEVICE=partitions in mdadm.conf Thanks, Arnaud Le 15/07/2011 04:25, NeilBrown a écrit : On Thu, 14 Jul 2011 20:24:52 +0200 Arnaud Desmier wrote: Hi Scott, Thanks for your answer, I've changed

Bug#621786: One Thought/Thing to Try

Hi Scott, Thanks for your answer, I've changed /etc/mdadm/mdadm.conf as you requested and "/sbin/mdadm --assemble --scan --auto=yes --symlink=no" didn't crashed but exit with code 2, I don't know what it means. Reboot is now going fine and each array is correctly mounted. Arnaud Le 10/07/20

Bug#621786: mdadm: invalid pointer or memory corruption on armel system

0x40069c24 in abort () from /lib/libc.so.6 #10 0x40069c24 in abort () from /lib/libc.so.6 Is it interesting? Thanks, Arnaud Le 09/04/2011 09:30, martin f krafft a écrit : also sprach Arnaud Desmier [2011.04.09.0923 +0200]: How can I get the stack trace as you requested? Find the exact

Bug#621786: mdadm: invalid pointer or memory corruption on armel system

Hi Martin, I've made the following changes before compiling the debian package version (not the one build from git repository): debian/rules: - change declaration of CXFLAGS to CXFLAGS = -ggdb -DDEBUG -g Before building package: - export DEB_BUILD_OPTIONS="noopt" Starting build of package: