sparsebundle recovery?

P

peterv6

Registered
I have a 17" MacBook Pro that just died on me, it's getting the "curtain of death" kernel panic errors. I've tried resetting pram, and other resets, but nothing has worked. I don't have the cash to buy any of Apple's overpriced, underperforming replacement components, so I'm trying to find out if there is any way to recover files from sparsebundle files on a Windows machine. I have external drives, but only Windows machines. I've looked at Mac Drive, but that doesn't show anything except the bands files. Any help would be appreciated.
 
My first thought is that the hard drive has possibly failed.
Have you tried booting to your OS X restore/install DVD? You can try Disk Utility from the menus after booting to that disk. If the hard drive appears there, choose it, then click the Repair Disk button (not Repair Disk Permissions, which would not help you)
 
I don't believe it's the hard drive, as I can boot up, and I've done the repair permissions, and repair disk options, and it hasn't helped. Thanks for the reply though.
 
Then I would search through here on kernal panics. It may be a simple matter of failing RAM--and RAM is cheap and easily replaced. With your disk you can run a hardware test described on these fora.

--J.D.
 
Thanks for the tip, I'll search the forum. Do you know if there is a way to test if the RAM is failing? I don't want to replace it if it's not the problem.
 
The BEST test I know--that diagnosed my bad RAM years ago--costs about $1.39:

Memtest

Well worth it. My "bad RAM" was periodic. It would fail under stress which gave periodic--then not so periodic!--kernal panics. It also would result in damaged volumes. Tech Tools and other tests showed no errors. Memtest immediately revealed the error.

The Hardware Test--search for that, I have never done it--may do the same thing, I am not sure.

--J.D.
 
Doctor X,
I took your suggestion and got memtest. Unfortunately, I have no idea how to figure out what the log file is telling me. If I post it or send it to you, would you be willing to have a look at it for me? It shows some failures, but what concerns me is this:

"Mac OS X 10.6.8 (10K540) running in single user mode
Memory Page Size: 4096
System has 2 Intel core(s) with SSE
Requested memory: 3917MB (4108193792 bytes)
Available memory: 3917MB (4108193792 bytes)
NOTE: Memory request is too large, reducing to acceptable value..."

I have a MacBook Pro with 4GB of RAM, and I'm runnining 10.6.8. I don't know if that is incompatible with memtest or not.

I'm hoping that the errors show are the cause of the kernel panics I'm having, but I don't want to buy memory if I'm not positive that's the problem.
Thanks,
Peter V.
 
No, that is okay, though you can e-mail the guy who created it--I tested it on my own which, as you see has not 4 but 6 . . . 6 Gigs of RAM . . . BWA!HA!HA!HA! [Stop that.--Ed.] . . . and that "error" does not seem to be a problem.

What follows is a bunch of tests. THOSE are the ones that matter. Now running the full memtest can take a few hours. In my limited experience--one failing chip--the memory will start failing the tests IMMEDIATELY.

Are those tests showing failures?

--J.D.
 
Memtest gives you that notice because it cannot test all memory. It requires a small amount to run the test, and that amount is not tested.
You said that you got other errors - the normal process then will be to reseat your existing RAM chips (swapping between slots is a Good Thing™ as it should assure a good reseat.) Run the memtest again.
If you still get any errors, replace your RAM.
The final test, is to use your system with new memory. If the panics are gone, then you have a good repair.
 
Dr. X,
Here's the output of memtest. Unfortunately it never completes because I get another kernel panic. Can you tell if these errors mean the memory is bad? (Remember, I have no clue about what these errors mean.)
Thanks,
Peter V.
Code: 
Memtest version 4.22 (64-bit)
Copyright (C) 2004 Charles Cazabon
Copyright (C) 2004 - 2008 Tony Scaminaci (Macintosh port)
Licensed under the GNU General Public License version 2 only

Log file written to /Applications/memtest/memtest.log

Mac OS X 10.6.8 (10K540) running in single user mode
Memory Page Size: 4096
System has 2 Intel core(s) with SSE
Requested memory: 3912MB (4102627328 bytes)
Available memory: 3912MB (4102627328 bytes)
NOTE: Memory request is too large, reducing to acceptable value...
Allocated memory: 3803MB (3987753728 bytes) at local address 0x0000000101000000
Attempting memory lock... locked successfully
Splitting allocated memory into 2 comparison buffers...
Buffer A: 1901MB (1993876864 bytes) starts at local address 0x0000000101000000
Buffer B: 1901MB (1993876864 bytes) starts at local address 0x0000000177d82580

Running 3 test sequences... (CTRL-C to quit)

Test sequence 1 of 3:

Running tests on entire 3803MB region...
  Stuck Address       :    ok
  Linear PRN          :    ok
Running comparison tests using 1901MB buffers...
  Random Value        :    ok
  Compare XOR         :    ok
  Compare SUB         :    ok
  Compare MUL         :    ok
  Compare DIV         :    ok
  Compare OR          :    ok
  Compare AND         :    ok
  Sequential Increment:    ok
  Solid Bits          :    ok
  Block Sequential    :    ok
  Checkerboard        :    ok
  Bit Spread          :    ok
  Bit Flip            :    

FAILURE! Data mismatch at local BUFA address 0x000000013a5445d0, BUFB address 0x00000001b12c6b50
BUFA Data: 0xffffffffffffffdf, BUFB Data: 0xfffffffdffffffdf

  Walking Ones        :    

FAILURE! Data mismatch at local BUFA address 0x0000000138f15088, BUFB address 0x00000001afc97608
BUFA Data: 0xfffffffefdffffff, BUFB Data: 0xfffffffffdffffff

  Walking Zeroes      :    

FAILURE! Data mismatch at local BUFA address 0x000000016d795a80, BUFB address 0x00000001e4518000
BUFA Data: 0x0000000000000200, BUFB Data: 0x0000000000000100


Test sequence 2 of 3:

Running tests on entire 3803MB region...
  Stuck Address       :    

FAILURE! Data mismatch at local address 0x000000012a443000
Actual Data: 0x00000001e4430000

  Linear PRN          :    

FAILURE! Data mismatch at local address  0x000000012a443000
Expected Data: 0x8d0e42ad7f6e5ab5, Actual Data: 0x46ece681bc1ed238

Running comparison tests using 1901MB buffers...
  Random Value        :    

FAILURE! Data mismatch at local BUFA address 0x000000012a443000, BUFB address 0x00000001a11c5580
BUFA Data: 0xfdfd0f9bbb7e71f9, BUFB Data: 0x7ce7f0e47b7d8031

  Compare XOR         :    

FAILURE! Data mismatch at local BUFA address 0x000000012a443000, BUFB address 0x00000001a11c5580
BUFA Data: 0xfdfd0f9bbb7e71f9, BUFB Data: 0x894cee914483d8aa

  Compare SUB         :    

FAILURE! Data mismatch at local BUFA address 0x000000012a443000, BUFB address 0x00000001a11c5580
BUFA Data: 0x05fe2c04bb92216b, BUFB Data: 0x8d4d7cc5c48db063

  Compare MUL         :    

FAILURE! Data mismatch at local BUFA address 0x000000012a443000, BUFB address 0x00000001a11c5580
BUFA Data: 0x0b7a8210cb55466c, BUFB Data: 0x7bb34bbe3f371e4a

  Compare DIV         :    

FAILURE! Data mismatch at local BUFA address 0x000000012a443008, BUFB address 0x00000001a11c5588
BUFA Data: 0x0000000000000000, BUFB Data: 0x0000000000000001

  Compare OR          :    

FAILURE! Data mismatch at local BUFA address 0x000000012a443008, BUFB address 0x00000001a11c5588
BUFA Data: 0xeb7fe8347fbd2312, BUFB Data: 0xeb7fe8347fbd2313

  Compare AND         :    

FAILURE! Data mismatch at local BUFA address 0x000000012a443008, BUFB address 0x00000001a11c5588
BUFA Data: 0x8b6be8207d8d2302, BUFB Data: 0x8b6be8207d8d2303

  Sequential Increment:    

FAILURE! Data mismatch at local BUFA address 0x000000012a443000, BUFB address 0x00000001a11c5580
BUFA Data: 0x7dfdded1ff4adb8e, BUFB Data: 0x7dfdded1f6e6063e

  Solid Bits          :    

FAILURE! Data mismatch at local BUFA address 0x000000016f401008, BUFB address 0x00000001e6183588
BUFA Data: 0xffffffffffffffff, BUFB Data: 0x0000000000000000

  Block Sequential    :    

FAILURE! Data mismatch at local BUFA address 0x000000016f401000, BUFB address 0x00000001e6183580
BUFA Data: 0xffffffffffffffff, BUFB Data: 0x0000000000000000

  Checkerboard        :    

FAILURE! Data mismatch at local BUFA address 0x000000016f401000, BUFB address 0x00000001e6183580
BUFA Data: 0xffffffffffffffff, BUFB Data: 0x5555555555555555

  Bit Spread          :    

FAILURE! Data mismatch at local BUFA address 0x000000016f401000, BUFB address 0x00000001e6183580
BUFA Data: 0xffffffffffffffff, BUFB Data: 0x0000000000000005

  Bit Flip            :    

FAILURE! Data mismatch at local BUFA address 0x000000016f401000, BUFB address 0x00000001e6183580
BUFA Data: 0xffffffffffffffff, BUFB Data: 0xfffffffffffffffe

  Walking Ones        :    

FAILURE! Data mismatch at local BUFA address 0x000000016f401000, BUFB address 0x00000001e6183580
BUFA Data: 0xffffffffffffffff, BUFB Data: 0xfffffffffffffffe

  Walking Zeroes      :    

FAILURE! Data mismatch at local BUFA address 0x000000016f401000, BUFB address 0x00000001e6183580
BUFA Data: 0xffffffffffffffff, BUFB Data: 0x0000000000000001


Test sequence 3 of 3:

Running tests on entire 3803MB region...
  Stuck Address       :    

FAILURE! Data mismatch at local address 0x000000012a443000
Actual Data: 0x00000001e4430000

  Linear PRN          :    

FAILURE! Data mismatch at local address  0x000000012a443000
Expected Data: 0x8d0e42ad7f6e5ab5, Actual Data: 0x46ece681bc1ed238

Running comparison tests using 1901MB buffers...
  Random Value        :    

FAILURE! Data mismatch at local BUFA address 0x000000012a443000, BUFB address 0x00000001a11c5580
BUFA Data: 0x4574e5c17fc5ef05, BUFB Data: 0x0fff60f73ded3b9e

  Compare XOR         :    

FAILURE! Data mismatch at local BUFA address 0x000000012a443000, BUFB address 0x00000001a11c5580
BUFA Data: 0x4574e5c17fc5ef05, BUFB Data: 0x6402a41f02144e43

  Compare SUB         :    

FAILURE! Data mismatch at local BUFA address 0x000000012a443000, BUFB address 0x00000001a11c5580
BUFA Data: 0x457f545ec64659e1, BUFB Data: 0x6407db6da55483b1

  Compare MUL         :    

FAILURE! Data mismatch at local BUFA address 0x000000012a443000, BUFB address 0x00000001a11c5580
BUFA Data: 0x30e1592c42d0d821, BUFB Data: 0xd8d858dd837c6ad1

  Compare DIV         :    

FAILURE! Data mismatch at local BUFA address 0x000000012a443000, BUFB address 0x00000001a11c5580
BUFA Data: 0x0000000000000000, BUFB Data: 0x0000000000000001

  Compare OR          :    

FAILURE! Data mismatch at local BUFA address 0x000000016d67da80, BUFB address 0x00000001e4400000
BUFA Data: 0xe7f652e36ef94e47, BUFB Data: 0xffffffffffffffff

  Compare AND         :    

FAILURE! Data mismatch at local BUFA address 0x000000016d67da80, BUFB address 0x00000001e4400000
BUFA Data: 0xe1f4404002e14e06, BUFB Data: 0xffffffffffffffff

  Sequential Increment:    

FAILURE! Data mismatch at local BUFA address 0x000000012a443000, BUFB address 0x00000001a11c5580
BUFA Data: 0xb5fbd2880d6bb651, BUFB Data: 0xb5fbd2880506e101

  Solid Bits          :    

FAILURE! Data mismatch at local BUFA address 0x000000016f401008, BUFB address 0x00000001e6183588
BUFA Data: 0xffffffffffffffff, BUFB Data: 0x0000000000000000

  Block Sequential    :    

FAILURE! Data mismatch at local BUFA address 0x000000016f401000, BUFB address 0x00000001e6183580
BUFA Data: 0xffffffffffffffff, BUFB Data: 0x0000000000000000

  Checkerboard        :    

FAILURE! Data mismatch at local BUFA address 0x000000016f401000, BUFB address 0x00000001e6183580
BUFA Data: 0xffffffffffffffff, BUFB Data: 0x5555555555555555
 
Reseat your memory chips, and try the test again. If you still get those, or similar errors, then you may assume that memtest (whose prime task is to test your memory) has found errors in your RAM, and you should replace the memory. You don't have to understand every detail about the results to come to a conclusion.

No errors in testing does NOT mean the memory is 100% OK.
But, if you do get errors during a memory test, you should assume the memory is failing, and you are getting errors now. The other fact is that you get kernel panics, which often can point to bad memory.
And, now you have memory errors during an actual memory test. What can you assume now?

Something to think about: RAM that you purchase is often warranted for life. Apple's memory is limited to whatever warranty you have on your Apple product, which is either 12 months, or the AppleCare extended warranty, total of 3 years from original date of purchase for most covered products.
 
DeltaMac,
Thanks for both of your replies. (I didn't see the first one prior to posting my memtest log, as I didn't realize there was a second page of postings x-).

I'm going to try reseating the memory and do a retest, and I've already contacted OWC for an RMA to replace the memory I purchased in 2009. (It did have a lifetime warranty.) I'll post results after my retest. Thanks again for taking the time to help.
Peter V.
 
To All, thanks for all the help. I reseated the memory, and now I'm getting many more errors and they come much sooner during the scan. I'll be replacing the memory asap, and will post the results.
 
You must log in or register to reply here.
Back
Top