ext3grep assert failure: ext3grep: init_consts.cc:44: void init_consts(): Assertion `super_block.s_magic == 0xEF53' failed.

Bug #454050 reported by Maddmaxx
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ext3grep (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: ext3grep

Trying to restore a drive that had the ext3 filesystem forgotten somehow, no mechanical failures, SMART status is okay.

ProblemType: Crash
Architecture: i386
AssertionMessage: ext3grep: init_consts.cc:44: void init_consts(): Assertion `super_block.s_magic == 0xEF53' failed.
CrashCounter: 1
Date: Fri Oct 16 09:38:20 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/ext3grep
Package: ext3grep 0.10.1-2
ProcCmdline: ext3grep --restore-all /dev/sdb
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.152-rt
Signal: 6
SourcePackage: ext3grep
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 __assert_fail () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: ext3grep assert failure: ext3grep: init_consts.cc:44: void init_consts(): Assertion `super_block.s_magic == 0xEF53' failed.
Uname: Linux 2.6.31-9-rt i686
UserGroups:

Revision history for this message
Maddmaxx (maddmaxx666) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:__kernel_vsyscall ()
*__GI_raise (sig=6)
*__GI_abort () at abort.c:92
*__GI___assert_fail (
init_consts () at init_consts.cc:44

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in ext3grep (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Connor Imes (ckimes)
visibility: private → public
Changed in ext3grep (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

Changed in ext3grep (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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