Invalid B-Tree node size: the weird(er) part

Shakabab · September 8, 2005

Hey guys

I've been readin' this forum for a while now and i decided it was

fun to register so i could post as well.

I have, although i hate doing so in my first post, a weird case scenario for you all.

I am using the deadmoo vmware image to install osx86 which actually worked

like 3 times (had to reinstall after messing to much ).

Till i got messing with my harddrive partitions with partition magic to resize

som of my other partitions on the same disc. OsX wouldnt boot anymore then.

So i figured i'd do a reinstall from the image and all would be ok.. gues not.

The disc would boot after the reinstall, and checkin it with the macos dvd

installer (which i downloaded but only works in vmware) i came to figure its

the same b-node-tree problem thing explained here:

Now for the weird part.. its not my own physical hard drive which gives me that

error but its the deadmoo vmware hard drive. I cant open it with

cfdisk because it says something like "Partition cycle ends before first cylinder".

I tried it anyway and dd'ed it to my physical harddrive with the option bs=1M.

Still its not working since obviously the image is already elephanted.

Re-extracted the image from the rar archive 4 times already, wouldnt help.

Any ideas how this is all related and how on earth i get this error on FRESHLY

extracted images?

Tnx in advance for reading this

Shakabab · September 9, 2005

Nevermind me I solved the problem.

Turns out the image was perfectly OK.

I used cfdisk /dev/hdb while i should have used

cfdisk /dev/hdb1 (2nd harddrive 1st partition) to dd it

Case closed.

Recommended Posts