[Bug 946344] Re: mdadm crashed with SIGABRT in raise()

Launchpad Bug Tracker 946344 at bugs.launchpad.net
Sun Jun 3 15:40:09 UTC 2012


*** This bug is a duplicate of bug 946758 ***
    https://bugs.launchpad.net/bugs/946758

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

** Changed in: mdadm (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/946344

Title:
  mdadm crashed with SIGABRT in raise()

Status in “mdadm” package in Ubuntu:
  Confirmed

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'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/946344/+subscriptions




More information about the foundations-bugs mailing list