• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Consistent kernel panic on volume mount
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Consistent kernel panic on volume mount


  • Subject: Consistent kernel panic on volume mount
  • From: Carsten G Pedersen <email@hidden>
  • Date: Wed, 19 Jan 2005 10:20:49 +0100


I've run into quite a scary issue. Some defect RAM has managed to mess up my internal SATA drive - and yes I know this happens all the time and nothing special about that!  Well the thing is that not only does this lead to a kernel panic when booting on the drive - it seems that whenever this drive is mounted on any Mac running 10.3.x it leads to an instant kernel panic similar to this one:


panic(cpu 0): jnl: do_overlap: overlap of 0 is not multiple of 24

Latest stack backtrace for cpu 0:
       Backtrace:
          0x000833B8 0x0008389C 0x0001ED8C 0x000CF86C 0x000CFAEC 0x000CFE80 0x000D0B08 0x001E476C
          0x001DEA54 0x001DD4F0 0x000C4700 0x0023DD24 0x00093D20 0x00000000
 Proceeding back via exception chain:
    Exception state (sv=0x17BFEA00)
       PC=0x9005392C; MSR=0x0000D030; DAR=0xBFFFCF40; DSISR=0x0A000000; LR=0x00002CF8; R1=0xBFFFF930; XCP=0x00000030 (0xC00 - System call)

Kernel version:
 Darwin Kernel Version 7.2.0:
 Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC


I'm guessing that journaling is involved here and I'll have to disagree with the statement that 0 is not a multiple of 24 :) Booting in single user mode on the drive leads to a similar message. I've also tried booting in single user on another drive and mounting it with mount_hfs -j which supposedly turns of journaling but the result is exactly the same.

It seems to me that this is a pretty serious problem since not only does it prevent the usage of standard disk recovery tools - it even prevents the normal user from reformatting such a drive. So apart from the fact that I'd love to be able to recover some data from this drive I also think it would be great if someone knew how to fix the code - seems kind of ironic if it is in fact journaling that prevents disk recovery!

Oh and if someone  could tell me whether it would be appropiate to file a bug on an issue like this please let me know.

Carsten
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Consistent kernel panic on volume mount
      • From: Karl Magdsick <email@hidden>
    • Re: Consistent kernel panic on volume mount
      • From: William Kucharski <email@hidden>
    • Re: Consistent kernel panic on volume mount
      • From: Felix Kronlage <email@hidden>
  • Prev by Date: Re: Documentation for frame header somewhere?
  • Next by Date: Re: Consistent kernel panic on volume mount
  • Previous by thread: Re: Documentation for frame header somewhere?
  • Next by thread: Re: Consistent kernel panic on volume mount
  • Index(es):
    • Date
    • Thread