Jump to content

invalid btree node size

intradink

By intradink,
in OSx86 10.4 (Tiger)

 Share
21 posts in this topic

Recommended Posts

intradink
intradink
Posted
Posted

Hi,

 

I'm really hoping someone will be able to help with this problem.

 

:blink:Background

I have successfully had OSx running without issue, dual boot from a partition (using the deadmoo image -dd'd across), sound, 1280x800 QE, rosetta, deerpark, iTunes etc... all good.

 

:)Issue

I somehow managed to trash it! Thought, no problem, I know now how to get it up and running again. Unfortunately I've tried for days now without success.

 

The problem is soon after booting into OSx (safe mode):

** Checking HFS Plus
** Invalid btree node size (8,0)
** Volume check failed

Continuing
CPU Halted

 

Single user mode, running /sbin/fsck gives the same result.

 

:DOptions Tried

I figured that there was a problem with the partition, so have: -

 

1. Deleted and recreated the partion (using knoppix), and tried the install again

2. Deleted the osx partition and created a NTSF partition in it's place, then tried the knoppix cfdisk > type = AF > dd install

3. Deleted the osx partition, resized the XP partition to take up the entire disk, run chkdisk, booted XP successfully, resized it back, created a new partition, dd install

4. For resizing and formatting I've used PartitionMagic, QTParted, and cfdisk.

5. About 20 combinations of the above 4

 

I think I've tried everything I could think of. I know OSx runs on my hardware, but just can't get past the invalid btree problem....

 

B) "help me Obi-wan, your my only hope"

Link to comment
https://www.insanelymac.com/forum/topic/1015-invalid-btree-node-size/
Share on other sites
intradink
intradink
Posted
  • Author
Posted

Alternatively, does anyone know how to disable the checking the file system during safe mode boot? It appears to boot much further without the safemode switches, but fails as expected since none of the patches are applied yet.

 

I'm hoping if I can boot into safe mode successfully, then I can run the disk utilities to try and correct any btree node issues that might be there.

nadnerb
nadnerb
Posted
Posted

hey, im having the same problem now.

 

i did have it working fine, dual booting and had reinstall OSX a few times.

but then something messed up so i reinstalled again and now during boot up it says

** Volume check failed
???????  ??????... killing all processes

Continuing
CPU Halted

 

im trying a reinstall now :blink:

fingers crossed

madtk
madtk
Posted
Posted

Hey Nadnerb,

 

also tried to reinstall (after the good news of getting the QE to work for 855GM) but also the same error as you got: CPU halted.

 

It used to work fine,

 

I think I'm going to do a full format of my partition that used to had OSX, I keep you informed. Very strange

psychonaut
psychonaut
Posted
Posted
Hmm did a full ntfs format under windows of the partition, reinstalled and the same error...cpu halted...

 

How could this be? Had it up and running earlier...

Same problems here. Not sure if its related but it started just after I had installed MacDrive on the windows partition and was browsing my Tiger drive.

nadnerb
nadnerb
Posted
Posted

i found a way to boot when u get this error

 

use the boot option:

-s -x

 

then wait for it to load, then type sh /etc/rc (i think thats it)

then wait again and type exit.

 

it should now boot in safe mode.

i guess it somehow bypasses the disk checking.

 

once in safe mode i removed some kexts that normally prevent booting (i guess you dont need to do this as this is just specific to my chipset) and then ran the disk utility.

i selected 'repair disk permissions'

 

then rebooted and it loaded up normally without giving the btree error.

 

hope that helps someone :)

 

*edit*

now its not working, go figure!

i swear what happens is totally random after a reboot, it doesnt seem to follow any patterns

i give up

intradink
intradink
Posted
  • Author
Posted

Weird... I'd given up on this thread since I hadn't received any mail for replies. Anyway, I managed to work out what the problem was/is...

 

After resizing or messing with partitions (using a linux live cd for me), it seems that there is a quirk in using fdisk/cfdisk or similar, in that the first few bytes are screwed up in the changed partition (after writing type AF). The solution is simple in that you have to dd a few zeros to the first few bytes. After doing that you can dd the deadmoo image without problem.

 

If you are using cfdisk in linux (knoppix in my case), then read the man (> man cfdisk), it explains the problem and how to resolve it.

 

Damn thing drove me mad! I'm up and running now, just can't seem to get QE working again.

minde924
minde924
Posted
Posted
Weird... I'd given up on this thread since I hadn't received any mail for replies.  Anyway, I managed to work out what the problem was/is...

 

After resizing or messing with partitions (using a linux live cd for me), it seems that there is a quirk in using fdisk/cfdisk or similar, in that the first few bytes are screwed up in the changed partition (after writing type AF).  The solution is simple in that you have to dd a few zeros to the first few bytes.  After doing that you can dd the deadmoo image without problem.

 

If you are using cfdisk in linux (knoppix in my case), then read the man (> man cfdisk), it explains the problem and how to resolve it.

 

Damn thing drove me mad!  I'm up and running now, just can't seem to get QE working again.

 

Hi,

 

Could you explain for me how to dd a few zeros under windowsXP using DD for windows.

 

Regards,

madtk
madtk
Posted
Posted
thats interesting because i also installed MacDrive.

im not sure when i installed it so i cant be sure thats what caused the problem. (i couldnt get it to read my tiger drive anyway)

 

madtk, did u install macdrive too?

 

Ps: Also had Macdrive,

 

don't do Macdrive kids :)

intradink
intradink
Posted
  • Author
Posted
Could you explain for me how to dd a few zeros under windowsXP using DD for windows.

Hi minde,

I've not used DD under windows (for some reason I don't trust it). I'd imagine it comes with a manual, so it might be worth checking that out. If not then I'd suggest downloading and burning the knoppix live cd. It's very useful when trying to do this kind of thing, and also less likely to screw with your machine.

 

If you don't know, a live cd will just boot into that operating system *without* installing anything on the host machine. This is very useful in recovery situations. You need a little linux knowledge (not much), but this will probably be helpful when you come to messing with the osx terminal commands.

 

I'll try and lookup the command on knoppix when I get home

intradink
intradink
Posted
  • Author
Posted

Google is your friend ;)

 

Note the following is in reference to the linux cfdisk application. I used this to set partitions on my disk, and then used it to correct them when resizing existing disk. My suggestion is that you backup everything before playing with partitions and potentially writing zeros to your hardisk.

 

Everytime I used cfdisk, I received a DOS 6 warning, but didn't think it applied to me since I was working generally with HFS (AF) partitions.

 

DOS 6.x WARNING

      The  DOS  6.x FORMAT command looks for some information in
      the first sector of the data area of  the  partition,  and
      treats this information as more reliable than the informa­
      tion in the partition table.  DOS FORMAT expects DOS FDISK
      to  clear the first 512 bytes of the data area of a parti­
      tion whenever a size change occurs.  DOS FORMAT will  look
      at  this extra information even if the /U flag is given --
      we consider this a bug in DOS FORMAT and DOS FDISK.

      The bottom line is that if you  use  cfdisk  or  fdisk  to
      change  the  size of a DOS partition table entry, then you
      must also use dd to zero the first 512 bytes of that  par­
      tition  before  using  DOS FORMAT to format the partition.
      For example, if you were using cfdisk to make a DOS parti­
      tion  table entry for /dev/hda1, then (after exiting fdisk
      or cfdisk and rebooting Linux so that the partition  table
      information  is  valid)  you  would  use  the  command dd
      if=/dev/zero of=/dev/hda1  bs=512  count=1  to  zero  the
      first 512 bytes of the partition. Note:

      BE  EXTREMELY  CAREFUL  if you use the dd command, since a
      small typo can make all of the data on your disk  useless.

 

So the dd command I used was:

 

dd if=/dev/zero of=/dev/hda1  bs=512  count=1

 

This sorted out my issues, and is a good first step if you've been messing around with partition sizes. You should also note that the part of the command that is

 

of=/dev/hda1

 

is referring to the dodgy partition that you want to correct. Change the hda1 to whatever is appropriate to your system.

intradink
intradink
Posted
  • Author
Posted
did I miss something?

 

As far as I can tell you should have a well formed partition to dd onto after the above process.

 

Boot with -x -v and see what it's failing on. Maybe re-extract the image to make sure it isn't corrupted. Check your hardware config and browse these forums for some specific help - maybe checkout the hardware compatibility list on the wiki site.

Archalien
Archalien
Posted
Posted
As far as I can tell you should have a well formed partition to dd onto after the above process.

 

Boot with -x -v and see what it's failing on.  Maybe re-extract the image to make sure it isn't corrupted.  Check your hardware config and browse these forums for some specific help - maybe checkout the hardware compatibility list on the wiki site.

 

Doubt it can be nething else as nothing has changed. Image burned on dvd.

 

-v -x doesnt help cuz booting into safe quickly crashes to a power-off state.

-v by itself provides the btree error everyone is getting which seems indicative only for people trying to do reinstalls after a successful install went awry later down the road for whatever reason.

 

what to do?

Archalien
Archalien
Posted
Posted

Ill do u one better swited from deadmoo image to Marklar bootable dvd iso with sse2 boot patch, sse3->sse2 patch to allow for non sse3 proc, and sse2->sse3 patch that enables rosetta. DVD boots installs, regular installation, a little slower than deadmoo prolly cuz of the sse3->sse2 rosetta conversions, but everything works perfect, super stable!! cant compile java 1.5, no wireless nic, no hardware vid accel so no dvd but thats it!!!

 

I suggest everyone switch.

New problem is that dvd install overwrote MBR and f'd up windows boot, coulndt fix so Im starting over installing OSX, then Windows, the Linux(Grub) and see how that goes.

intradink
intradink
Posted
  • Author
Posted
I suggest everyone switch.

New problem is that dvd install overwrote MBR and f'd up windows boot, coulndt fix so Im starting over installing OSX, then Windows, the Linux(Grub) and see how that goes.

 

Can't you just set Windows as the active partition, using any partition software?

 Share
Go to topic listing
×
×
  • Create New...