mdadm segfault on booting Lucid

Bug #766091 reported by crypt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mdadm (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: mdadm

I regularly see on booting that mdadm segfaulted. Don't know, how to debug this on boot time.

Apr 18 23:36:09 sympho kernel: [ 3.372428] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Apr 18 23:36:09 sympho kernel: [ 3.381880] EXT3 FS on sdb1, internal journal
Apr 18 23:36:09 sympho kernel: [ 3.381886] EXT3-fs: mounted filesystem with writeback data mode.
Apr 18 23:36:09 sympho kernel: [ 3.481843] mdadm[320]: segfault at 10e ip 00007fe0aff8935e sp 00007fff3f3bf970 error 4 in libc.so.6 (deleted)[7fe0aff40000+17a000]
Apr 18 23:36:09 sympho kernel: [ 3.544228] md: bind<sdc2>
Apr 18 23:36:09 sympho kernel: [ 3.591523] md: array md3 already has disks!

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: mdadm 2.6.7.1-1ubuntu15
ProcVersionSignature: Ubuntu 2.6.32-30.59-generic 2.6.32.29+drm33.13
Uname: Linux 2.6.32-30-generic x86_64
Architecture: amd64
Date: Tue Apr 19 15:20:35 2011
EcryptfsInUse: Yes
MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda.
MDadmExamine.dev.sda1: Error: command ['/sbin/mdadm', '-E', '/dev/sda1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda1.
MDadmExamine.dev.sda2: Error: command ['/sbin/mdadm', '-E', '/dev/sda2'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda2.
MDadmExamine.dev.sda3: Error: command ['/sbin/mdadm', '-E', '/dev/sda3'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda3.
MDadmExamine.dev.sdb: Error: command ['/sbin/mdadm', '-E', '/dev/sdb'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb.
MDadmExamine.dev.sdb1: Error: command ['/sbin/mdadm', '-E', '/dev/sdb1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb1.
MDadmExamine.dev.sdb2: Error: command ['/sbin/mdadm', '-E', '/dev/sdb2'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb2.
MDadmExamine.dev.sdc: Error: command ['/sbin/mdadm', '-E', '/dev/sdc'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdc.
MDadmExamine.dev.sdd: Error: command ['/sbin/mdadm', '-E', '/dev/sdd'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd.
MDadmExamine.dev.sdd4: Error: command ['/sbin/mdadm', '-E', '/dev/sdd4'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd4.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: root=UUID=a58d0510-7557-4757-bec9-015af429e99b ro modeset=0 nofb
ProcEnviron:
 LC_TIME=C
 PATH=(custom, user)
 LANG=en_US.UTF-8
 LC_MESSAGES=C
 SHELL=/bin/bash
SourcePackage: mdadm
dmi.bios.date: 01/12/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: G41M-S3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd01/12/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG41M-S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'

Revision history for this message
crypt (cryptogranny1) wrote :
Revision history for this message
dino99 (9d9) wrote :

Closing that outdated report as EOL has been reached long time ago

Changed in mdadm (Ubuntu):
status: New → Invalid
Revision history for this message
crypt (cryptogranny1) wrote :

Nice to see the bug in main component was marked outdated after 5 years since it's been reported. Universal solution for any bug. No reasons to report anything again. Thanks from the community.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.