Overlapped extent allocation

My iBook is not starting, so I ran the start up disc, and the diagnostic said I had an overlapped extent allocation. So I want to back up before I reinstall OS X, but I do not not know how to back up from either the start up or safe mode. Can someone help me? Thanks so much.

Angela:
When I ran the Disk Utility it said it was fixed, but I still could not start up the computer. I actually ran the Utility a couple of times.
Yet in your first post in the topic you said:
so I ran the start up disc, and the diagnostic said I had an overlapped extent allocation.
If Disk Utility said it was fixed, what "start up disc" did you run?
As Doug pointed out, overlapping extent allocation files is a directory issue that needs to be addressed by a utility like Disk Warrior or Tech Tool Pro. Backing up and re-installing is an acceptable solution, but much more invasive.
One of the causes of overlapping extent allocation files is an overfull internal Hard Disk Drive. If you have less than 10% of available capacity on your HDD you should consider leaning down the contents of the drive or getting a larger HDD.
Good luck.
cornelius
Message was edited by: cornelius

Similar Messages

  • Overlapped extent allocation, backing up and erase/install

    Can't boot up my G4 flat panel iMac. Have tried safe boot mode - hangs on grey screen and spinning gears. Ran Disk Repair from install disk which reported 'overlapped extent allocation' files - dozens of 'em, so decided to back up users folders to g5 tower using target disk mode and I can access the iMac's hard drive through TDM.
    Having read this technical document:
    http://support.apple.com/kb/HT1553?viewlocale=en_US#3c
    it specifies that that I have to log into the imac as a root user to copy the user folders to the G5 but as I can't log in to it am I OK just to access and copy the user folders from the imac via target disk mode? (I've started this but, for example, when copying one of the user folders - 35GB of content - the copied folder correctly has 16 folders within, but has a few thousand bytes of data less than the original folder - why is this and will it cause problems after erasing the imac's drive and attempting to copy back the user directories?
    I have read elsewhere that I can search for the problematical Overlapped Extent Allocation files in the DamagedFiles directory but can I safely delete these and how can I tell if I can or can't and how do I find them? (the reasoning being that if I can safely delete these then the imac may boot up OK)
    When quitting the installer menu on the imac (when booting from the install disk) I am prompted to either quit or choose startup disk. If I choose the latter option will the imac boot from the install disk enabling me to back up the user folders to an external drive using the method recommended in the technical document I previously referred to (i.e logging in as a root user)?
    Thanks for any help

    There are a couple of ways to deal with the problem. See the following:
    Handling 'overlapped extent allocation' errors reported by Disk Utility or fsck;
    Or buy Disk Warrior which will fix the problem for you and any other directory related problems that Disk Utility does not fix.
    However, the most effective solution is to erase the drive and reinstall OS X. Since you are accessing the drive via TDM, copy your personal data to a backup drive or folder on the other computer. There's no benefit to copying the entire Home folder because it may contain files affected by the problem. Better to copy only your data files. You will have to do some software reinstalling and re-registering, but that's better than having damaged files.

  • Repeated Overlapped Extent Allocation

    I recently began having problems with "Overlapped Extent Allocation" errors on my hard drive on my "Late 2010" MacBook Air. When it first happened, I formatted the drive, reinstalled OSX 10.7, and restored my data. Within a month or so, the drive was corrupted again with the same errors. So, I replaced the hard drive, reinstalled OSX, and restored my data. Now, only a couple weeks after doing this, I am having the same problem yet again. What could be causing this to happen so frequently?

    Linc,
    Thanks for the reply. Unfortunately, I've already replaced the drive and it's doing the same thing on the new drive. I suppose it's possible that I got a bad drive, but it's hard to imagine it having exactly the same error as the previous drive.

  • Overlapped extent allocations

    Hi all,
    I'm trying to solve a number of overlapped extent allocations (OS X 10.2.8) using the command line solution described in http://docs.info.apple.com/article.html?artnum=25770. I have previously tried to fix the HD using Tech Tool deluxe, but the repair phase seems to hang after a few hours when the rate of block processing slows down to one per several minutes - suggesting a time to complete of about 11 days!!
    Starting with 9 overlaps, I've deleted offending files for 6 of them - they were either preference or cache files that could go without any knock-on impact.
    I'm now left with the following affected files:
    Users/mike/Library/Mail/Mailboxes/Mailgroups/GPSrunners.mbox/Incoming_mail
    /private/var/run/cron.pid
    /private/var/run/utmp
    Can anyone please advise how to deal with these?
    I'm happy to lose the mailbox if I delete the first one.
    What do the 2nd and 3rd files do?? Will they cripple my OS if I delete them? I have a backup of my HD on an external drive taken a few weeks ago so the user data will not be current but the OS should be an intact backup of the OS - I can certainly boot from it. Is there a way to replace them from the HD, and if so do I have to do that from the command line (they don't seem to be visible to the finder).
    Grateful for any help - in nice simple steps for someone whose command line knowledge was limited to fsck until today!
    thanks,
    Mike
    iMac800   Mac OS X (10.2.x)  

    Kappy, Fifthwheel, WJ,
    Thanks for your excellent help.
    I've deleted the mbox and cron.pid files - the allocation error asociated with the utmp file just seems to have gone away. Checking the HD by fsck or Disk Uitility/First Aid from an external drive says the disk is OK.
    HOWEVER, I still have the problem reported here:
    http://discussions.apple.com/thread.jspa?threadID=583008&tstart=0
    Could this login difficulty be caused by the utmp file being damaged? If so, how can I replace it by a good one if, as WJ suggests, it will not be recreated automatically if I delete it?
    Can I use the one on my external drive which has the OS backed up, and if so how do I actually move it (command line or finder)?
    thanks,
    Mike
    iMac800 Mac OS X (10.2.x)
    iMac800 Mac OS X (10.2.x)

  • Fixing "overlapped extent allocation (file 7d)"...

    Hi,
    While running fsck i get the error "overlapped extent allocation (file 7d)"
    I've read the guide on how to delete problematic files, but does this apply to my error (i.e. it's not a 7-digit file number)?
    btw, i tried running "find / -inum 7". The hard drive buzzes a bit then displays the normal prompt (sh-2.05) and not the path to my problem file...
    Any ideas?
    Thanks
    mac os x 10.2.3

    By "regular mode", he means after the system has booted to the login window. Most people who run fsck do it from single-user mode (no GUI, no Terminal; just a command line).
    When you try 'sudo -s' from a non-administrator account, it will fail ("(this user) is not in the sudoers file..."). Thus when you typed the 'find / -inum 7', you are doing the search as the non-administrative user rather than as root, which means that your access to the file system is limited to the files and directories that that user is allowed to read (usually only system files and its own home directory). So no, the directories that yield ": Permission denied" are not corrupt; they just aren't yours, so you're not allowed to search them.
    Disk Warrior won't do you much good if you try to run it from a non-administrator account; it'll suffer the same restrictions you encountered with your 'find'.
    Your best bet is to print reboot to single-user mode and attempt to fix the problem there.

  • Why use uniform extent allocation?

    version- 11.2.0.2.0
    Hello guys, I've been reading UNIFORM vs AUTOALLOCATE extent allocation.
    I've read the following articles.
    https://blogs.oracle.com/datawarehousing/entry/parallel_load_uniform_or_autoallocate
    Ask Tom: On Loading and Extents
    https://forums.oracle.com/thread/2518951
    From what I understood, autoallocate trumps the uniform in all scenarios (unless I am missing something).
    In the thread "AUTOALLOCATE vs UNIFORM SIZE"
    for the benefits of autoallocate and uniform size allocation Kh$n wrote
    Benefits of AUTOALLOCATE
    * Prevents space fragmentation.
    Benefits of UNIFORM extent sizes
    * Prevents fragmentation. 
    (I dont understand what is the difference between those two fragmentation prevention, are those benefits one and the same?)
    even in scenarios where we know exactly how much data will be loaded, there is always a chance of extent wastage and with out extent trimming that space will be unusable.
    Can someone please explain in which cases we use uniform extent allocation?
    for suppose we use uniform extent allocation and we have lot of unused space from the extent allocation, can that space be reclaimed using shrink space command for tables and indexes?
    Thank You

    Extent trimming, to the best of my knowledge, is something that only happens when you are using parallel query to do large loads, not something that happens during normal OLTP type operations.  As with anything called "automatic" in Oracle, though, the internals are subject to change across versions (and patchsets) and are not necessarily documented, so it is entirely possible for behaviors to change over time.  Relying on specific internal behaviors is generally not a good idea.
    The example I gave (assuming you reverse the truncating of A and the loading of C, as Hemant pointed out) produces "fragentation" when you're using automatic extent management.  It's not a particularly realistic scenario, but it is possible.  If you never delete data, never truncate tables, (and, presumably, never shrink tables), extents would never be deallocated and there would, therefore, never be holes.  That is just as true of ancient dictionary managed tablespaces as well as locally managed tablespaes whether you're using uniform or autoallocated extents.
    Shrinking a table has nothing to do with defragmenting a tablespace.  It is simply compacting the data in the table and then potentially deallocating extents.  You can do that with any locally managed tablespace.  There is still the possibility, of course, that you have just enough data in the table that you need to allocate 1 extra extent when you only need space for 1 row in 1 block.  So there may be some number of MB of "wasted" space per segment (though, again, this is generally not something that is a practical concern since the data in tables generally changes over time and it's generally not worth the effort of worrying about a few MB).
    Justin
    For your third question, assuming both extents are part of the same segment, assuming that the space is actually usable based on things like the PCTUSED setting of the table, and assuming a nice, simple conventional path insert in a single-user, Oracle would use the free space in the extent for new inserts before allocating a new extent.  Oracle generally doesn't allocate new extents unless it needs to (there are caveats to this-- if the only blocks with free space have a relatively large fraction of their space used such that a particular new insert only fits in 1 of the 1 million blocks in the currently allocated extents, Oracle will potentially give up before finding the 1 in a million block that it would need an may allocate a new extent).
    Message was edited by: JustinCave

  • Determining Extent Allocation Type

    Does anyone know how you tell if a tablespace has been configured to use UNIFORM extent allocation or AUTO ALLOCATE . I can see in dba_tablespaces if the extent is dictionary or locally managed. I can also see if it is using ASSM or not but I am struggling to see where the actual method of extent allocation is recorded
    thanks,
    Jim

    http://docs.oracle.com/cd/B19306_01/server.102/b14237/statviews_4157.htm
    ALLOCATION_TYPE

  • RAC extent allocation

    Hi Guys,
    I had a question regarding extent allocation to a segments. In a RAC environment we allocate extent to specific instance, why is it so?
    As we know extent are the space allocated at stogare level, so why do we allocate to specific instance in RAC?
    Is there any specific reason to do so...
    Please suggest...
    Thanks!

    can you show me an example where you allocated an "extent" to a specific instance? Are you using ASM or shared file system - if shared FS, which one? Bigfile tablespace? Smallfile tablespace?

  • Change extent allocation in tablespace

    Hi All,
    Database Version : 11.1.0.6
    I have a LMT tablespace with uniform extent of 192 K. It has been in use since long .
    Is it possible to change the extent allocation to AUTOALLOCATE now ?
    If not , is there any workaround ..
    Thanks

    hi..
    there is no "alter table space" syntax for changing extent management from uniform to auto allocate. Hence, you must re-define the table space to change the extent management:
    * Backup the table space
    * Export the table space data
    * Drop and re-allocate the table space
    * Import the table space

  • 10g Local Extent Allocation "UNIFORM"

    Hello all,
    I'm in the process of 8i (Dictionary extent) to 10g (Local extent) migration, and I have a question.
    is "USER" allocation in 8i same as "UNIFORM?"
    Thanks!

    ok thank you. Here's the steps I've taken:
    1. Pre-created the tablespace as "UNIFORM" on 10g
    2. Ran IMP (dmp from 8i, as "USER")
    3. ALLOCATION_TYPE still shows as "UNIFORM"
    So basically, because the purpose was to EXP/IMP from server A to server B, I did not do take any upgrade steps, just simple EXP/IMP. Would the upgrade option automatically have changed allocation_type to "USERS" from "UNIFORM?"
    if you see something wrong with below, please kindly let me know...
    SQL> select tablespace_name, extent_management, allocation_type, contents from dba_tablespaces;
    TABLESPACE_NAME EXTENT_MAN ALLOCATIO CONTENTS
    SYSTEM LOCAL USER PERMANENT
    SYSAUX LOCAL SYSTEM PERMANENT
    USERS LOCAL SYSTEM PERMANENT
    TOOLS LOCAL SYSTEM PERMANENT
    TEMP LOCAL UNIFORM TEMPORARY
    TEMP_ACDB LOCAL UNIFORM TEMPORARY
    USERS_ACDB LOCAL SYSTEM PERMANENT
    UNDO01 LOCAL SYSTEM UNDO

  • Asm extent allocation

    Hi ASM experts ,
    this is written in oracle11gr2 workshop1 lesson5 page 22
    for the first 20,000 extents, the extent size is equal to the AU size. After 20,000 extents and up to 40,000 extents, the extent sets are always allocated 8 at a time with the extent size equal to 4*AU size. If the AU size is 1 MB, this means the ASM file will grow 64 MB at a time (8 * 4 * 1 MB). If the file is coarse-grained striped then it is striped across the 8 extent sets with stripes of 1 AU. Striping is always done at the AU level, not at the extent level. Thus every AU of a coarse-grained file is on a different disk than the previous AU of that file no matter how large the file. After 40,000 extents, the extents are still allocated 8 at a time, but with an extent size equal to 16*AU size.
    first of all i don't know how 8*4*1 will be 64
    and my question is does oracle allocate 8 extents at a time whatevre number of previous allocated extents under 20000 or over 40000?
    thank you for reading.

    user475845 wrote:
    Hi ASM experts ,
    this is written in oracle11gr2 workshop1 lesson5 page 22
    for the first 20,000 extents, the extent size is equal to the AU size. After 20,000 extents and up to 40,000 extents, the extent sets are always allocated 8 at a time with the extent size equal to 4*AU size. If the AU size is 1 MB, this means the ASM file will grow 64 MB at a time (8 * 4 * 1 MB). If the file is coarse-grained striped then it is striped across the 8 extent sets with stripes of 1 AU. Striping is always done at the AU level, not at the extent level. Thus every AU of a coarse-grained file is on a different disk than the previous AU of that file no matter how large the file. After 40,000 extents, the extents are still allocated 8 at a time, but with an extent size equal to 16*AU size.
    first of all i don't know how 8*4*1 will be 64
    and my question is does oracle allocate 8 extents at a time whatevre number of previous allocated extents under 20000 or over 40000?
    thank you for reading.Hi,
    Documentation  says:
    The extent size of a file varies as follows:
    Extent size always equals the disk group AU size for the first 20000 extent sets (0 - 19999).
    Extent size equals 4*AU size for the next 20000 extent sets (20000 - 39999).
    Extent size equals 16*AU size for the next 20000 and higher extent sets (40000+).
    Please check : http://docs.oracle.com/cd/E11882_01/server.112/e18951/asmcon.htm#BABCGDBF
    Figure 1-4 Oracle ASM File Allocation in a Disk Group+
    Regards
    Mahir M. Quluzade

  • How many extents allocated when table created?

    I am using Oracle 9,
    is the number going to be what we specified by minextents?
    thanks

    Srinivas,
    You said,
    If its AUTOALLOCATE , Oracle starts with 1 extent of 64KB , then 128KB as the first extent becomes full, then 256KB so on....
    Can you help me in understanding this statement?I don't think that its true. See here,
    SQL> select * from V$version;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    PL/SQL Release 10.2.0.1.0 - Production
    CORE    10.2.0.1.0      Production
    TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    SQL> drop tablespace test including contents and tablespaces;
    drop tablespace test including contents and tablespaces
    ERROR at line 1:
    ORA-00905: missing keyword
    SQL> drop tablespace test including contents and datafiles;
    Tablespace dropped.
    SQL> create tablespace test datafile 'd:\test.dbf' size 100m extent
    ocal autoallocate ;
    Tablespace created.
    SQL> select tablespace_name,initial_extent,next_extent from dba_tab
      2  where tablespace_name='TEST'/
      3
    SQL> select tablespace_name,initial_extent,next_extent from dba_tab
      2  where tablespace_name='TEST'
      3  /
    TABLESPACE_NAME                INITIAL_EXTENT NEXT_EXTENT
    TEST                                    65536
    SQL> --Creating a table inside in this tablespace
    SQL> create table t as select * from dba_objects;
    Table created.
    SQL> alter table t move tablespace test;
    Table altered.
    SQL> select tablespace_name, extent_id, bytes/1024, blocks
      2  from user_extents
      3  where segment_name = 'T';
    TABLESPACE_NAME                 EXTENT_ID BYTES/1024     BLOCKS
    TEST                                    0         64          8
    TEST                                    1         64          8
    TEST                                    2         64          8
    TEST                                    3         64          8
    TEST                                    4         64          8
    TEST                                    5         64          8
    TEST                                    6         64          8
    TEST                                    7         64          8
    TEST                                    8         64          8
    TEST                                    9         64          8
    TEST                                   10         64          8
    TABLESPACE_NAME                 EXTENT_ID BYTES/1024     BLOCKS
    TEST                                   11         64          8
    TEST                                   12         64          8
    TEST                                   13         64          8
    TEST                                   14         64          8
    TEST                                   15         64          8
    TEST                                   16       1024        128
    TEST                                   17       1024        128
    TEST                                   18       1024        128
    TEST                                   19       1024        128
    TEST                                   20       1024        128
    21 rows selected.
    SQL>
    SQL> insert into t select * from t;
    50356 rows created.
    SQL> /
    100712 rows created.
    SQL> /
    201424 rows created.
    SQL> /
    402848 rows created.
    SQL> commit;
    Commit complete.
    SQL> analyze table t compute statistics;
    Table analyzed.
    SQL> select tablespace_name, extent_id, bytes/1024, blocks
      2  from user_extents
      3  where segment_name = 'T';
    TABLESPACE_NAME                 EXTENT_ID BYTES/1024     BLOCKS
    TEST                                    0         64          8
    TEST                                    1         64          8
    TEST                                    2         64          8
    TEST                                    3         64          8
    TEST                                    4         64          8
    TEST                                    5         64          8
    TEST                                    6         64          8
    TEST                                    7         64          8
    TEST                                    8         64          8
    TEST                                    9         64          8
    TEST                                   10         64          8
    TABLESPACE_NAME                 EXTENT_ID BYTES/1024     BLOCKS
    TEST                                   11         64          8
    TEST                                   12         64          8
    TEST                                   13         64          8
    TEST                                   14         64          8
    TEST                                   15         64          8
    TEST                                   16       1024        128
    TEST                                   17       1024        128
    TEST                                   18       1024        128
    TEST                                   19       1024        128
    TEST                                   20       1024        128
    TEST                                   21       1024        128
    TABLESPACE_NAME                 EXTENT_ID BYTES/1024     BLOCKS
    TEST                                   22       1024        128
    TEST                                   23       1024        128
    TEST                                   24       1024        128
    TEST                                   25       1024        128
    TEST                                   26       1024        128
    TEST                                   27       1024        128
    TEST                                   28       1024        128
    TEST                                   29       1024        128
    TEST                                   30       1024        128
    TEST                                   31       1024        128
    TEST                                   32       1024        128
    TABLESPACE_NAME                 EXTENT_ID BYTES/1024     BLOCKS
    TEST                                   33       1024        128
    TEST                                   34       1024        128
    TEST                                   35       1024        128
    TEST                                   36       1024        128
    TEST                                   37       1024        128
    TEST                                   38       1024        128
    TEST                                   39       1024        128
    TEST                                   40       1024        128
    TEST                                   41       1024        128
    TEST                                   42       1024        128
    TEST                                   43       1024        128
    TABLESPACE_NAME                 EXTENT_ID BYTES/1024     BLOCKS
    TEST                                   44       1024        128
    TEST                                   45       1024        128
    TEST                                   46       1024        128
    TEST                                   47       1024        128
    TEST                                   48       1024        128
    TEST                                   49       1024        128
    TEST                                   50       1024        128
    TEST                                   51       1024        128
    TEST                                   52       1024        128
    TEST                                   53       1024        128
    TEST                                   54       1024        128
    TABLESPACE_NAME                 EXTENT_ID BYTES/1024     BLOCKS
    TEST                                   55       1024        128
    TEST                                   56       1024        128
    TEST                                   57       1024        128
    TEST                                   58       1024        128
    TEST                                   59       1024        128
    TEST                                   60       1024        128
    TEST                                   61       1024        128
    TEST                                   62       1024        128
    TEST                                   63       1024        128
    TEST                                   64       1024        128
    TEST                                   65       1024        128
    TABLESPACE_NAME                 EXTENT_ID BYTES/1024     BLOCKS
    TEST                                   66       1024        128
    TEST                                   67       1024        128
    TEST                                   68       1024        128
    TEST                                   69       1024        128
    TEST                                   70       1024        128
    TEST                                   71       1024        128
    TEST                                   72       1024        128
    TEST                                   73       1024        128
    TEST                                   74       1024        128
    TEST                                   75       1024        128
    TEST                                   76       1024        128
    TABLESPACE_NAME                 EXTENT_ID BYTES/1024     BLOCKS
    TEST                                   77       1024        128
    TEST                                   78       1024        128
    TEST                                   79       8192       1024
    TEST                                   80       8192       1024
    TEST                                   81       8192       1024
    82 rows selected.
    SQL>Its not working in the way youmentioned. The extents are of 65kb till 16 extents than it changes to 1024kb untill 78 and then 8192 kb. Is it something that I am missing?
    Aman....

  • Error: The underlying task reported failure on exit / INVALID EXTENT ENTRY

    In trying to verify my HD, I get this error message:
    Verify and Repair disk “Macintosh HD”
    Checking HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Invalid extent entry
    Volume check failed.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    1 volume could not be repaired because of an error
    I've tried Disk Utility (not from startup volume) with no luck. I've also run DiskWarrior several times and still get the same message... What am I missing? How do you repair an INVALID EXTENT ENTRY? Is my HD about to bite the dust?
    Any help would be much appreciated!
    iMac G5   Mac OS X (10.4.6)   1.8 Ghz / 768mb ram

    1derfullymad,
    Welcome to Apple Discussions.
    I am surprised that Diskwarrior was not able to take care of this problem, but Handling "overlapped extent allocation" errors reported by Disk Utility or fsck may provide the ultimate solution for you.
    Make sure to use Disk Utility to check the S.M.A.R.T. status of your drive. If you get a good report the drive should be OK.
    This problem is a characteristic of a full Hard Drive. If that describes your Hard Drive, Freeing space on your Mac OS X startup disk, by Dr. Smoke may prove to be helpful.
    ;~)

  • Data back up from Single User Mode

    Hello,
    I have a problem with my 700 MHz iBook, dual USB, with OS X 10.3.9.
    Unfortunately the OS doesn't start up because of "overlapped extent allocation" problem...
    I would like to re-install the complete OS but before doing it, I would like to back up some directories.
    Is it possible to save some data, by connecting an Ipod or some sort of external peripheral, from the Single User mode?
    If yes, how can I do it?
    Thank you in advance from your kind support.

    Before giving up the ghost check out these:
    http://docs.info.apple.com/article.html?artnum=25770.
    Manually fix Overlapped Extent Allocation Errors without Disk Warrior
    Overlapped overlapped extent allocation errors can be the bane of any Mac user's existence. Often, these errors go unnoticed until the problem becomes visible: your Mac might refuse to boot, crash unexpected, or worse, critical data might disappear from the Finder. Disk Utility can detect, but not fix overlapped extent allocation errors, and certain third-party utilities, such as Alsoft Diskwarrior, can fix them, but generally without reporting the consequences.
    Overlapped extent allocation error occur when the file system thinks that two files are occupying the same area on the hard disk, hence overlapping on the same "inode," which is the structure which holds the location of the data blocks the file occupies, and also file permissions and flags.
    Clearing the "overlapped" or "overallocated" extent allocation essentially means that you'll have to lose some data, because the only way to remove the overlap is to delete the file that's occupying the inode. So, if you suspect, or find out, that the guilty file is a critical system file that resides in one of the hidden system directories such as /etc /var /usr/ or visible system directories such as /System or /Library, and you don't want to reinstall the whole OS (which might not fix the overlapped extent allocation anyway), it's good to have another disk available to copy the files back to your original disk if necessary: a second bootable hard drive or a firewire drive connected to your Mac when you remove the misbehaving file. Just make sure that when you copy the file back to your boot disk that the permissions are correct, so it's best to use the "ditto" command, so that all sticky bits, flags, and permissions are preserved.
    In case you didn't know, you don't have to boot from an install CD in order to check for overlapped extent allocations. All you need to do is restart your Mac, while holding down command + S to boot in "single-user mode."
    At the command prompt that appears, type:
    $ fsck -fy
    If you have an overlapped extent allocation, you'll see:
    "Overlapped Extent Allocation" (File 123456d)
    No matter how many times you run fsck -fy, you'll never be rid of the error.
    So, simply issue the following command:
    find / -inum 123456 -print
    Note the "d" was dropped, or any extra letter that appears after the inode number.
    The find will return a file name that matches with the inode number, and the path to that file. If you remove the file then the fsck will not return this error next time you run it.
    However, before you can delete the file(s) in single-user mode, you'll need to mount the file system. Type:
    $ mount -uw /
    When done, issue the "sync" command, and that will flush the write cache so that all pending writes are written from memory to the disk. Also, since most OS X 10.3 Macs use the HFS+ Journaled file system, it might be a good idea to disable the journal before booting into single-user mode by typing:
    $ sudo diskutil disableJournal /
    then re-enable it when done fixing the overlapped extents and rebooting normally:
    $ sudo diskutil enableJournal /
    Chris Anderson is a long-time Linux propellerhead who just got his first Mac, an ibook G4, and can't keep his hands off of it. He currently works as a "The Architect" and general visionary for a maker of world-class collectibles.
    If you own Disk Warrior then it should be able to repair a drive with overlapped extents.
    There are two backup utilities included in Unix - psync and rsync. You will find them in the /usr/bin/ directory. For documentation simply enter: man psync or man rsync. In order to write data while in single-user mode you need to issue the command: /sbin/mount/ -uw / (Note: there is a "space" between the "uw" and the "/".) To mount an external drive you will need to provide the mountpoint for it in place of the "/", e.g., "/Volumes/volname") without the quotes.

  • 1 of my HD partition suddenly can't mount and want me to initialize! HELP!!

    Hi,
    If anyone who frequented these kind of problems before please let me know your solutions solving these problems. Thanks very much!!
    I'm a musician and a frequent mac user,I have a Power Mac G4 dual 800 with 1.25GMhz ram running on Mac Os 9.21 but with Mac OS X installed (I need to use Mac OS classic due to some of my music softwares still need to be updated before I upgrade to OS X),I've put the Hard Disk in 2 other sub partition HD at the beginning and have been using it to put all my important audio files and songs files. No problems at all before these nightmare started!
    The serious problem I'm having now is I suddenly can't mount one of my partition HD anymore.
    -I heard weird sound when starting & re-starting the Mac. (Heard some Hard Disk weird sound like sound "crutch" sound" and since the partition can't be mounted, the first thing shows up after I boot the computer is asking me if I wanna Initialize the Hard Disk because it's unreadable. There is 2 choices for me "Cancel" & "Initialize" But there is no effect when I choose "Cancel" so I use the Force Quit.
    2 little message saying my Main Hard Disk & the other partition are damaged but they still showing up properly and still running dangerously I think.
    -I have tried to start-up by using the installer Disk came with the computer and runs the First Aid Kit to verify the disk. I can see the partition and can see the icon of it but it's just different from others (in a black tone basic classic icon) and after running the verification some following messages appears:
    "Mountcheck found serious errors" (in red) then "Overlapped extent allocation,2.60" (in red) and "Hard disk need to be repaired" so I run the Repair mode and it just can't fix because it says it's not been mounted.
    I've also checked the main HD and the other partition which sometimes had some problems with it but no problems been found.
    -There was few times my computer do Freeze or appears a Bomb asking me to restart when I recording something using the partition for saving the data and a weird sound of hard disk comes before freezing. It seems it's always the same place of the hard disk. Also When I inserted a blank CD-R disk into the drive it just freeze and appears a Bomb message instead asking me if I wanna use the Toast or i-tunes for preparing the disk which I always used to do.
    I really hope the computer can hang on just for 1 more month before I have a break to fix everything and backup everything inside or initialize everything inside.
    P.S. I've another Powerbook G4 running on OS Tiger but it's mainly for my internet use. ( I don't use internet connection for my PowerMac G4)
    And the Combo super Drive is DOWN,I just can't insert any Disk inside anymore. So if having another Mac is helpful for my issue,anything I would try.
    Due To I'm having some urgent important jobs now so I really can't initialize or setup other new computers for my works now.
    HELP! Thanks!!!

    Just because you can't find them does not mean they aren't there.
    Freeing Up Space on The Hard Drive
      1. See Lion/Mountain Lion/Mavericks' Storage Display.
      2. You can remove data from your Home folder except for the /Home/Library/ folder.
      3. Visit The XLab FAQs and read the FAQ on freeing up space on your hard drive.
      4. Also see Freeing space on your Mac OS X startup disk.
      5. See Where did my Disk Space go?.
      6. See The Storage Display.
    You must Empty the Trash in order to recover the space they occupied on the hard drive.
    You should consider replacing the drive with a larger one. Check out OWC for drives, tutorials, and toolkits.
    Try using OmniDiskSweeper 1.8 or GrandPerspective to search your drive for large files and where they are located.

Maybe you are looking for

  • Aperture 3.0.1  - the more I use it the worse it gets - here is a new one

    Well, at least for me it is. Running Aperture 3.0.1 with the latest proskit installed. I am using the program in split screen mode, in which I have the viewer stacked above the browser and underneath the browse I have the keywords showing. This is wh

  • SQL Code not working in Forms Developer?

    Hi all, I'm using Oracle 10g and I have th following code running on iSQL+ but not working on Forms and I got the following erro The SQL code:      select returningreason         from (                  select returningreason,                  dense_

  • Reconfigure Active Directory External Authentication plug in to use ssl

    Assuming this is the proper place to post this question: I've quickly gone through the IM integration documentation trying to find out how to reconfigure the ad external auth plugin to use ssl and have come up empty handed. Does anyone know how to do

  • Problem opening PSD templates at times in CS5 and CS6

    I have had a problem with opening some PSD template files.  It doesn't happen all the time and it doesn't happen with every template.  All of the templates were downloaded as zip files and opened and saved using Photoshop CS 5 on a Windows XP PC.  Wh

  • Undefined State

    I am trying to refer to States dynamically and keep getting an error telling me that the state is undefined. <mx:RadioButtonGroup id="affiliation" /> <mx:Repeater id="rp" dataProvider="{acArtists}"> <mx:RadioButton label="{rp.currentItem.grouptype}"