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

Question

Level 1

0 points

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

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

iMac (Flat Panel) 700MHz PowerPC G4, Mac OS X (10.3.x), OS 9.2.2 also installed

Posted on Mar 3, 2008 9:01 AM

Reply

Answer 1

Kappy

Level 10

362,007 points

Mar 3, 2008 9:43 AM in response to ErikEren

First, try this (it probably will not help):

Repairing the Hard Drive and Permissions

Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now shutdown the computer for a couple of minutes and then restart normally.

If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger, and 4.1 for Leopard) and/or TechTool Pro (4.6.1 for Leopard) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

You can attempt to fix the disk using Disk Warrior or TT Pro if you have them. Otherwise, you will have to reformat the hard drive.

Reply

Answer 2

ErikEren Author

Level 1

0 points

Mar 3, 2008 11:43 AM in response to ErikEren

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

Reply

Answer 3

Kappy

Level 10

362,007 points

Mar 3, 2008 12:19 PM in response to ErikEren

It wouldn't help any because the drive directory is damaged. It will be damaged regardless of which OS you boot. I'm afraid you need to erase the drive and reinstall OS X. If you have access to another Mac with Firewire you may be able to connect the two via Firewire cable, boot the computer into Target Disk Mode. Boot the other computer normally. You may then be able to access your hard drive from the other computer's Desktop in order to save your personal files, if any.

Reply

Answer 4

ErikEren Author

Level 1

0 points

Mar 3, 2008 12:28 PM in response to Kappy

Hello Kappy

DO YOU HAVE ANY IDEA WHAT THIS COULD MEAN:

This massage up all the time at the COMMAND LINE:

*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

Thank you again.

Reply

Answer 5

Kappy

Level 10

362,007 points

Mar 3, 2008 12:55 PM in response to ErikEren

It means some running process tried to free a memory allocation that was never allocated.

Reply

Answer 6

ErikEren Author

Level 1

0 points

Mar 5, 2008 9:08 AM in response to Kappy

Why would this happen? I mean, was the problems couse low memory?
When this happened, i was only using the Saffari_Browser on the net at a
safe website. No other apps. were open. I had 640 MB Memory, should't ran out of memory. All of a sudden computer froze, i waited for 20min. tryed to force quit the saffari, nothing was possible, the mouse_curser was spinning only...
so i had to force start the computer by holding the power_button and when the competer started again, the apple logo and spinning_thing...stayed like that for a while and all af a sudden black_screen white text: Darwin, UserName, Password...and the rest you know.
So as you wrote some process tryed to allocate memory but could not get it...
Was that the reason, computer had froze the first time?
If so, should not run out of memory.
Or is this "allocated memory" failior happening in the Command LineInterface...
I mean, is it the secondary issue?

Thank you

Reply

Answer 7

Kappy

Level 10

362,007 points

Mar 5, 2008 9:58 AM in response to ErikEren

Why would this happen? Good question but no definitive answer. Could be faulty software, could be a glitch, could be corrupted file, could be a RAM glitch.

When you say no other apps were running you are overlooking the fact that your system has dozens of processes running concurrently even if you didn't launch them as a user.

I did not say the program tried to allocate memory and could not get it. I said that the software tried to de-allocate some memory and that failed because the memory space it tried to de-allocate had not been allocated. This doesn't mean there wasn't enough memory.

Actually, it is possible to run out of memory. Understand the OS uses both "real" RAM and "virtual" RAM. The latter is basically the use of hard drive space in place of physical RAM. The OS creates a Virtual Memory file (VM) at startup - it starts out with 64 MBs and increases as needed first in 64 MB chunks, then 128 MB chunks, etc.. If the OS needs to expand the VM file but cannot find enough space on the hard drive (hard drive is full or the directory is corrupted) then technically you are out of memory. Under normal circumstances, however, the system should not crash but merely warn you. However, if there's hard drive corruption then you may find that the system will crash.

Reply

Answer 8

ErikEren Author

Level 1

0 points

Mar 6, 2008 7:29 AM in response to Kappy

Hi Kappy,

Thank you for the insightful feedbacks.

Eren

Reply