mdadm crashed with SIGABRT in raise()

Bug #946344 reported by Dan Holm
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mdadm (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Likely occurred during weekly cron for array data check. /dev/sd[ab]9 are not part of an array and are loose swap partitions.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mdadm 3.2.3-2ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Sun Mar 4 03:21:28 2012
ExecutablePath: /sbin/mdadm
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
MDadmExamine.dev.sda4:
 /dev/sda4:
    MBR Magic : aa55
 Partition[0] : 62498816 sectors at 2048 (type fd)
 Partition[1] : 894255152 sectors at 62500864 (type 05)
MDadmExamine.dev.sda9: Error: command ['/sbin/mdadm', '-E', '/dev/sda9'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda9.
MDadmExamine.dev.sdb4:
 /dev/sdb4:
    MBR Magic : aa55
 Partition[0] : 62498816 sectors at 2048 (type fd)
 Partition[1] : 31250432 sectors at 62500864 (type 05)
MDadmExamine.dev.sdb9: Error: command ['/sbin/mdadm', '-E', '/dev/sdb9'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb9.
MachineType: Gigabyte Technology Co., Ltd. GA-MA785GMT-USB3
ProcCmdline: /sbin/mdadm --monitor --pid-file /var/run/mdadm/monitor.pid --daemonise --scan --syslog
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-17-generic root=UUID=98cca835-e9b4-4cf4-8332-8c68937eeda4 ro vt.handoff=7
Signal: 6
SourcePackage: mdadm
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 __fortify_fail () from /lib/x86_64-linux-gnu/libc.so.6
 __chk_fail () from /lib/x86_64-linux-gnu/libc.so.6
Title: mdadm crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/04/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: GA-785GMT-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd01/04/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA785GMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-785GMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA785GMT-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'

Revision history for this message
Dan Holm (8hkfclc5t) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #946758, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mdadm (Ubuntu):
status: New → Confirmed
Revision history for this message
Thomas Antepoth (ta-ubuntu-antepoth) wrote :

The link https://bugs.launchpad.net/bugs/946758 which is mentioned in comment #2 is not accessible or missing.
 Thus I'm subscribing to this bugreport instead.

Excactly the same StacktraceTop on my machine - which is why I found the bugreport on google.

To post a comment you must log in.