mdadm crashed with SIGABRT in raise()
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
ProcVersionSign
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelMo
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:
MBR Magic : aa55
Partition[0] : 62498816 sectors at 2048 (type fd)
Partition[1] : 894255152 sectors at 62500864 (type 05)
MDadmExamine.
MDadmExamine.
/dev/sdb4:
MBR Magic : aa55
Partition[0] : 62498816 sectors at 2048 (type fd)
Partition[1] : 31250432 sectors at 62500864 (type 05)
MDadmExamine.
MachineType: Gigabyte Technology Co., Ltd. GA-MA785GMT-USB3
ProcCmdline: /sbin/mdadm --monitor --pid-file /var/run/
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: mdadm
StacktraceTop:
raise () from /lib/x86_
abort () from /lib/x86_
?? () from /lib/x86_
__fortify_fail () from /lib/x86_
__chk_fail () from /lib/x86_
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:bvnAwardSof
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'
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.