CANNOT_START-UP: Stars in Command-Line-Mode: "Deallocation of a pointer not

Question

HELLO EVERYONE, PLEASE CAN YOU HELP ME...
My computer: Mac OS X (10.3.9) had froze, couldn't force quit..and i forced started it by holding the power button. Restarted it, came on: the grey-screen and apple, spinning-gear...satayed like that long time then it went into Command-Line_Mode.
Darvin,
UserName:
Password:
I enterded UserName and Password, but could not start in normal ways.
Now when I start-up the computer, Command-Line opens with only:
:/root#
and a curser-point.
I have been reading all the leads that I found in the discussions, tryed most of the suggestions: fsck (/sbin/fsck -fy), Safe-Mode (didn't start in), couldn't start up from CD.
COMMAND-LINE (at one time it said like this):
*God boot device= IOService:/MacRISCZPE?pci@f2000000/AppleMacRiscPCI/*
*mac-io@17/AppleKeyLargo/ata-4@1f000/KeylargoATA/ATADeviceNum@0/IOATABlockStorag eDrive/IOATABlockStorageDevice/IOBlockStorageDriver/ST340810A.Media/IOAppleParti tionScheme/MacOS@5 BSD root: diskOs5, Major 14, minor 5*
*Feb 22 14:32:25 mach_init[2]:Started with uid=0 audit-uid=-1*
*Feb 22 14:32:25 init:ignoring exwss arguments/etc/rc.boot:cannot dublicate*
*fd-1048577 to fd 1: Bad file descriptor*
**malloc[3]: Dealocation of a pointer not malloced: 0x710; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug*
*at an other time after using fsck*
Command-Line-Interface:
*:root#/sbin/fsck -fy*
**/dev/rdiskOsF
*Root file System*
*Checking HFS Plus volume.*
*Checking Extents Overflow file.*
*Checking Catalog file.*
*Keys out of order*
*(4, 8874)*
*Rebuilding Catalog B-tree.*
*The Valume Macintosh could not be repaired.*
PLEASE HELP!
WHAT Should i do?
If nothing works, could i start-up from OS 9.2.2? (Both Systems OSX and OS_9.2.2 were installed)
If the B-tree is corrupt, does it being shared by both OSX and OS_9.2.2?
THANK YOU

Answer 1

Hi Kappy,
Thank you for taking an interest.
I already tryed to start_up from CD, but it either didn't started-up
or it started still in Command-Line-Mode.
Put the CD in the tray, startedUP with the C_Key Held.
It took a little longer and seemed it was going to start from CD but went into CommanLine again.
but instead of
:/root#
it said something else, something like:
2e_sh.. (Something! i could redo it and write it down here if it will help)
Other times i tryed to bootUP from CD by holding-down the Option-Key and saw the install-CD icon next to
OSX-Icon, so i chose the CD and hit the Straight-ARROW-Icon to start up from the CD, but again it fell
into CommandLine.
If i try the Target-Disk-Mode with a healty-Mac, could i be able to see my HD. Then i can switch to
OS_9.2.2 which i spose is healty because i was using OS_10.3 when this problem happened. And the way
i think, if the B-tree Catalog is not being shared by both Systems, if each have its own one, then the
OSX's B-tree Catalog have been corrupted, not OS9's, and so if i could change the start-up-system(Disk)
somehow, i could be able to start the computer with OS_9.2.2 running. Both systems were installed,
and i was switching back and forth between them. Then i can fix my computer by, at least, starting
to throw away some of the junk and so making some free-space.
I had read that HD should not be full more than 85%. I had 2.5GB space left out of 40GB.
But if there is a risk that things like this could happen because your HD is too full;
why arn't they (Apple) fix this, buy, at least, showing as if you HD is full before it gets
too full to leave a safety net for the B-tree Catalog files evidently that need to be written
in continuous blocks on the HD.
So thank you again, and keep me posted if you might think something else could fix my computer. I need
this computer.
thanks