Lost HardDrive Space After Deleting Bootcamp Partiton

Hello, Everyone
I have a small issue i open finder window and it says that i have 398.18GB Available but when i go into Disk Utility and go to the top result which is called WDC WD6400AAKS-40H2B0 Media it says that my Total Capacity is 640.14 GB so i go to the Partition Tab and it says the following Available Space: 533.58 and the HD Size 639.66 so i go to my Desktop and Get Info on my Macintosh HD and it says my Capacity is 493.79GB and i don't understand where the rest of my space has gone the Macintosh HD says that i have only used 95.61 GB on disk so if you can help me get my rest of my space back it would be much appreciated.
I have tried repairing it in disk utility but it hasn't worked
Thanks, Sean

HI,
Try repairing disk permissions...
Quit any open applications/programs. Launch Disk Utility. (Applications/Utilities) Select MacintoshHD in the panel on the left, select the FirstAid tab. Click: Repair Disk Permissions. When it's finished from the Menu Bar, Quit Disk Utility and restart your Mac. If you see a long list of "messages" in the permissions window, it's ok. That can be ignored. As long as you see, "Permissions Repair Complete" when it's finished... you're done. Quit Disk Utility and *restart your Mac*.
Carolyn

Similar Messages

  • Release of space after delete/truncate table

    Hello,
    How does release of space after delete/truncate table works? Is the space used before deletion released once delete is complete or not? Will I see the space occupied by deleted table as free in dba_segments or will I need to reorganize the table (drop and recreate again?). Reason why I am asking is that I can see table with 0 rows, but in dba_segment I can see it is occupying few gigabytes....
    Thank you

    Here is a little illustration for you;
    SQL> conn ogan/password
    Connected.
    SQL> create table ogan_deneme as select * from all_objects;
    Table created.
    SQL> select count(*) from ogan_deneme;
      COUNT(*)
        228470
    SQL> set line 1000
    SQL> set pagesize 1000
    SQL> select * from dba_segments where owner='OGAN';
    OWNER    SEGMENT_NAME        PARTITION_NAME           SEGMENT_TYPE       TABLESPACE_NAME                HEADER_FILE HEADER_BLOCK      BYTES     BLOCKS    EXTENTS INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS MAX_EXTENTS PCT_INCREASE  FREELISTS FREELIST_GROUPS RELATIVE_FNO BUFFER_
    OGAN      OGAN_DENEME          TABLE              SYSTEM                                 854       319981   *30408704*       *1856*         *44*          65536                       1  2147483645                       1               1          854 DEFAULT
    SQL> truncate table ogan_deneme;
    Table truncated.
    SQL> select * from dba_segments where owner='OGAN';
    OWNER    SEGMENT_NAME        PARTITION_NAME           SEGMENT_TYPE       TABLESPACE_NAME                HEADER_FILE HEADER_BLOCK      BYTES     BLOCKS    EXTENTS INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS MAX_EXTENTS PCT_INCREASE  FREELISTS FREELIST_GROUPS RELATIVE_FNO BUFFER_
    OGAN      OGAN_DENEME           TABLE              SYSTEM                                 854       319981      *65536*          *4*          *1*          65536                       1  2147483645                       1               1          854 DEFAULT
    SQL>Hope it Helps,
    Ogan

  • External HD won't free-up space after deleting files

    Hello. My old Maxtor 500 Gb external hard-drive won't free-up any space after deleting many, many files. I'm using a late 2009 iMac i5 desktop with Snow Leopard. I had 6 Time Machine backups of my old MacBook Pro on the drive - each taking up roughly 70-80 Gb of space. I deleted 3 of the Time Machine backups as they were close enough in date to other backups so I wasn't going to lose any data. This should have freed up more than 200 Gb of space on the external hard drive. However, the hard drive still shows having only 10 Gb of space available. I deleted the Trash from the Dock. The Trash is empty. I unmounted the hard drive, turned it off and reconnected it. I restarted the computer. Still no change. Please help me. Thanks!

    Welcome to Apple Discussions-
    Are you using FileVault? If so, you have to log out or restart in order for the disk space to be reclaimed.

  • Exfat drive does not free up space after deleting files

    My external exfat formatted drive does not free up space after deleting files using a mac....however if I delete files using a PC, it will free up space.
    I've even tried the *erase free space* using Disk Utility, but nothing.....
    Thoughts/Suggestions??

    Thanks for the suggestion.
    I ran WhatSize and here is the result. Oddly, it says there is 40.2 GB used (in the top-left) which conflicts with the information directly below it: "Capacity 108 GB, Used 103GB, Available 4.27 GB". Not so helpful.
    Disk Inventory X solved the problem, however. Much thanks! I wasted most of my weekend troubleshooting this sad issue. Anyway, Disk Inventory X revealed a bug where my external hard drive for photos was still appearing as a mounted volume, even though the HD was no longer connected. Freaky.
    After moving it to the trash and deleting it, I've recovered the space.
    Again, thanks! Contact me if you're curious about the details, as this might help you diagnose similar problems in the future.
    - Mike

  • Freeing space after deleting files

    Has anyone tried to free the LOB space after deleting a file? We've been using the aging feature but none of the space utilized by files that have been migrated to disk was freed after the file was moved to BFILE.

    Hi,
    there is old posting from you,
    Questions with Third-Party Access Management Systems
    I am trying integration of Oracle SSO and Oracle EBS but headers are not reaching in custom java file. Would be very thankful if you could help
    thanks in advance.
    prakash

  • Help I lost my email after deleting my mail acount

    I lost my email after deleting my mail acount there was nothoing in the trash and I have important email whish were in the reception folder. What can I do ? Thanks

    It all depends on the type of account and how it was configured. For IMAP-type accounts, mail is stored on the server, and setting up the account again is all that's needed to regain access to your mail.
    If you deleted a POP account, however, then all your mail stored locally in that account's mailboxes has certainly been wiped out, not just moved somewhere, and you were warned that this would happen by the following alert:
    Remove Account
    Are you sure you want to remove the <AccountType> account "<AccountName>"?
    This will permanently delete the account setup information, mailboxes, and messages from your computer. Messages stored on the mail server will not be affected.
    For each mail account, Mail creates a folder within ~/Library/Mail/ whose name starts with the account type (POP, IMAP, .Mac), followed by the account username and the incoming mail server. Deleting the account causes this folder and everything within it to be deleted as well.
    If the POP account was configured to leave mail on the server for some time instead of removing it right away, incoming mail that's still on the server can be downloaded by setting up the account again, just like for IMAP accounts, but keep in mind that this would only work for received (i.e. not sent) mail that has not yet been removed from the server.
    If the messages are not on the server, and you don't have a backup, your only option is to try to salvage as many deleted *.emlx files as possible with a data recovery tool such as Data Rescue II, TechTool Pro, or FileSalvage. Of these, the only one I know for sure that can recover deleted *.emlx files is FileSalvage. Stop using your computer right now if you want to try that, as anything you do with the computer may cause the deleted files to be overwritten.

  • Nas drive does not recalculating space after deleting files on Nas Drive??

    Greetings to Respected expert,
    Actually we have configure Window server 20082 Storage server.We have NAS drive configured which have 300GB quota limit. The actual data in the folder is 185 GB but it shows only 15 GB free and shows a warning .Please assist me why NAS server does not re-calculate
      the space after deleting files or does not leave space. Pardon me if I am not able to clear you my problems.this is very urgent for me.
    Thanks And Regards
    Rajnish Singh

    Hi Rajnish,
    As you mentioned "quota limit", it is set via FSRM or specific function on NAS?
    Meanwhile could you confirm the number 185GB is accurate? Sometimes a part of used space is just not calculated. You can confirm with checking the total space on NAS locally.
    If the number is correct and quota is set via FSRM, check if it is the Disk Quota which not re-calculated the released space. Try to clear the Quota setting and reconfig with 300GB limitation and see if issue still exists.
    If you have any feedback on our support, please send to [email protected]

  • [Solved] Can't boot into Arch after deleting some partitons

    About 6 months ago I installed Arch on a machine that used to run Ubuntu. Had some trouble at the time getting to boot into Arch but somehow managed. Now eventually decided to delete the old Ubuntu partitons to free up some space using gparted. Arch partition number changed from sda12 to sda6.
    On rebooting after deleting ubuntu partitions with gparted, I got an ubuntu splash screen and a whole lot of ubuntu boot options. Somehow these were all contained in my Arch's /boot/grub/menu.lst. Arch is all on one partition and no separate boot partition (which I had with Ubuntu - maybe I haven't deleted that and this is the problem?). Will need to check that out.
    I can chroot into Arch and did the following -
    grub> find /boot/grub/stage1
    (hd0,5)
    grub> root (hd0,5)
    Filesystem type is ext2fs, partition type 0x83
    grub> setup (hd0)
    Checking if "/boot/grub/stage1" exists... yes
    Checking if "/boot/grub/stage2" exists... yes
    Checking if "/boot/grub/e2fs_stage1_5" exists... yes
    Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
    succeeded
    Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,5)/boot/grub/stage2 /boot/grub/menu.lst"... succeed
    ed
    Done.
    grub>
    The Arch /boot/grub/menu.lst had a whole lot of ubuntu stuff in it but I edited to the following -
    # menu.lst - See: grub(8), info grub, update-grub(8)
    # grub-install(8), grub-floppy(8),
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default 0
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 3
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    hiddenmenu
    # Pretty colours
    #color cyan/blue white/blue
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    # examples
    # title Windows 95/98/NT/2000
    # root (hd0,0)
    # makeactive
    # chainloader +1
    # title Linux
    # root (hd0,1)
    # kernel /vmlinuz root=/dev/hda2 ro
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,3)
    title Arch uuid
    #root (hd0,5)
    uuid d15cf4f9-18ca-4ec5-95bc-db0f6f264736
    kernel /boot/vmlinuz26 root=/dev/sda6 ro vga=775
    intrd /boot/kernel26.img
    title Arch hd
    root (hd0,5)
    kernel /boot/vmlinuz26 root=/dev/sda6
    intrd /boot/kernel26.img
    I have a bootinfo script which gives the following (from the chroot environment) -
    Boot Info Script 0.55 dated February 15th, 2010
    ============================= Boot Info Summary: ==============================
    => Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
    in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
    => No boot loader is installed in the MBR of /dev/sdb
    sda1: _________________________________________________________________________
    File system: swap
    Boot sector type: -
    Boot sector info:
    sda2: _________________________________________________________________________
    File system: Extended Partition
    Boot sector type: -
    Boot sector info:
    sda5: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Mounting failed:
    mount: /dev/sda5 already mounted or sda5 busy
    sda6: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Mounting failed:
    mount: /dev/sda5 already mounted or sda5 busy
    mount: /dev/sda6 already mounted or sda6 busy
    sda7: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs:
    sda3: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System: Ubuntu 10.04.1 LTS
    Boot files/dirs: /etc/fstab
    sda4: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs: /grub/menu.lst /grub/grub.cfg /grub/core.img
    sdb1: _________________________________________________________________________
    File system: xfs
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs:
    =========================== Drive/Partition Info: =============================
    Drive: sda ___________________ _____________________________________________________
    Disk /dev/sda: 750.2 GB, 750155292160 bytes
    255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    Partition Boot Start End Size Id System
    /dev/sda1 417,690 6,554,519 6,136,830 82 Linux swap / Solaris
    /dev/sda2 25,414,954 1,465,144,064 1,439,729,111 5 Extended
    /dev/sda5 25,414,956 1,360,287,809 1,334,872,854 83 Linux
    /dev/sda6 1,360,287,873 1,423,198,349 62,910,477 83 Linux
    /dev/sda7 1,423,198,413 1,465,144,064 41,945,652 83 Linux
    /dev/sda3 6,554,520 25,414,829 18,860,310 83 Linux
    /dev/sda4 * 63 417,689 417,627 83 Linux
    Drive: sdb ___________________ _____________________________________________________
    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    Partition Boot Start End Size Id System
    /dev/sdb1 2,048 1,953,523,711 1,953,521,664 83 Linux
    blkid -c /dev/null: ____________________________________________________________
    Device UUID TYPE LABEL
    /dev/loop0 squashfs
    /dev/sda1 2a95d85a-45fe-4584-88dd-0ee20e651ec5 swap
    /dev/sda2: PTTYPE="dos" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x5" PART_ENTRY_NUMBER="2"
    /dev/sda3 32495e1a-227c-4d23-9f63-b1319def0dd9 ext3
    /dev/sda4 d6dc69b0-967d-4886-b62d-8c0d6be06b41 ext3
    /dev/sda5 37971286-b8d3-4a1b-9f94-4008288fed6d ext3 data
    /dev/sda6 d15cf4f9-18ca-4ec5-95bc-db0f6f264736 ext3 30GB-02
    /dev/sda7 eb736131-b558-4404-9b83-7f1e6d9e76ae ext3 var
    /dev/sda: PTTYPE="dos"
    /dev/sdb1 0e83045d-a0bd-4d36-b61d-bdb905130dc2 xfs 1TB-04
    /dev/sdb: PTTYPE="dos"
    ============================ "mount | grep ^/dev output: ===========================
    Device Mount_Point Type Options
    /dev/sda12 / ext3 (rw,commit=0)
    =============================== sda3/etc/fstab: ===============================
    # /etc/fstab: static file system information.
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc defaults 0 0
    # /dev/sda1 = swap
    /dev/sda1 none swap sw 0 0
    # /dev/sda3 = root
    #UUID=32495e1a-227c-4d23-9f63-b1319def0dd9
    /dev/sda3 / ext3 relatime,errors=remount-ro 0 1
    # /dev/sda4 = boot
    # UUID=d6dc69b0-967d-4886-b62d-8c0d6be06b41
    /dev/sda4 /boot ext3 relatime 0 2
    # /dev/sda5 = home
    # UUID=670eee83-0a3e-429c-863f-b9ecced9f97e
    /dev/sda5 /home ext3 relatime 0 2
    #/dev/sda6
    #UUID=37971286-b8d3-4a1b-9f94-4008288fed6d
    /dev/sda6 /home/ben/Data ext3 defaults,relatime 0 0
    # /dev/sda7
    # UUID=fdb14ca4-d71d-489f-a00e-6e608770674c
    /dev/sda7 /var ext3 relatime 0 2
    # /dev/sda8
    /dev/sda8 /opt ext3 relatime 0 2
    # /dev/sda10 - Arch
    /dev/sda10 /mnt/arch ext3 relatime 0 2
    # Not sure what this is doing here
    # Have commented it out - May be the reason why xbmc and mythtv were crashing on dvd insert and play
    # /dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
    # /dev/sde1
    # uuid appears to be 644406B3570C1846 -> ../../sde1
    #/dev/sde1 /home/ben/Data/TVRecordings-1TB01 xfs defaults,relatime 0 0
    #1TB-01
    UUID=76f3823a-81dc-45c9-a0b7-2bc6c3beb2f8 /media/1TB-01 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 1TB-02
    UUID=59cbf7a1-7008-40d0-96ed-c6f231823d4f /media/1TB-02 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 1TB-03
    UUID=0e936800-3c53-4b87-abc8-19be0ffca7f9 /media/1TB-03 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 750GB-02 ext3 Partition
    # UUID giving problems, trying with dev
    # UUID=c23b9c9a-66fc-4256-9211-73156c1ac64a /media/750GB-02_ext3 ext3 defaults,relatime 0 0
    /dev/sde2 /media/750GB-02_ext3 ext3 defaults,relatime 0 0
    ============================= sda4/grub/menu.lst: =============================
    # menu.lst - See: grub(8), info grub, update-grub(8)
    # grub-install(8), grub-floppy(8),
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default 0
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 3
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    hiddenmenu
    # Pretty colours
    #color cyan/blue white/blue
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    # examples
    # title Windows 95/98/NT/2000
    # root (hd0,0)
    # makeactive
    # chainloader +1
    # title Linux
    # root (hd0,1)
    # kernel /vmlinuz root=/dev/hda2 ro
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default options below
    ## DO NOT UNCOMMENT THEM, Just edit them to your needs
    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specific kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    ## kopt_2_6_8=root=/dev/hdc1 ro
    ## kopt_2_6_8_2_686=root=/dev/hdc2 ro
    # kopt=root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,3)
    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ## alternative=false
    # alternative=true
    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ## lockalternative=false
    # lockalternative=false
    ## additional options to use with the default boot option, but not with the
    ## alternatives
    ## e.g. defoptions=vga=791 resume=/dev/hda5
    # defoptions=quiet splash
    ## should update-grub lock old automagic boot options
    ## e.g. lockold=false
    ## lockold=true
    # lockold=false
    ## Xen hypervisor options to use with the default Xen boot option
    # xenhopt=
    ## Xen Linux kernel options to use with the default Xen boot option
    # xenkopt=console=tty0
    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ## altoptions=(recovery) single
    # altoptions=(recovery mode) single
    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ## howmany=7
    # howmany=all
    ## should update-grub create memtest86 boot option
    ## e.g. memtest86=true
    ## memtest86=false
    # memtest86=true
    ## should update-grub adjust the value of the default booted system
    ## can be true or false
    # updatedefaultentry=false
    ## should update-grub add savedefault to the default options
    ## can be true or false
    # savedefault=false
    ## ## End Default Options ##
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-26-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-26-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-24-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-24-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-23-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-23-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-22-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-22-generic
    title Ubuntu 10.04.1 LTS, memtest86+
    root (hd0,3)
    kernel /memtest86+.bin
    quiet
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    ============================= sda4/grub/grub.cfg: =============================
    # DO NOT EDIT THIS FILE
    # It is automatically generated by /usr/sbin/grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    set default="0"
    if [ ${prev_saved_entry} ]; then
    set saved_entry=${prev_saved_entry}
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z ${boot_once} ]; then
    saved_entry=${chosen}
    save_env saved_entry
    fi
    function recordfail {
    set recordfail=1
    if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
    insmod ext2
    set root='(hd0,3)'
    search --no-floppy --fs-uuid --set 32495e1a-227c-4d23-9f63-b1319def0dd9
    if loadfont /usr/share/grub/unicode.pf2 ; then
    set gfxmode=640x480
    insmod gfxterm
    insmod vbe
    if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
    fi
    fi
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    set locale_dir=($root)/grub/locale
    set lang=en
    insmod gettext
    if [ ${recordfail} = 1 ]; then
    set timeout=-1
    else
    set timeout=10
    fi
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/05_debian_theme ###
    set menu_color_normal=white/black
    set menu_color_highlight=black/light-gray
    ### END /etc/grub.d/05_debian_theme ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Ubuntu, with Linux 2.6.32-26-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-26-generic
    menuentry 'Ubuntu, with Linux 2.6.32-26-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-26-generic ...'
    linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-26-generic
    menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-24-generic
    menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-24-generic ...'
    linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-24-generic
    menuentry 'Ubuntu, with Linux 2.6.32-23-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-23-generic
    menuentry 'Ubuntu, with Linux 2.6.32-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-23-generic ...'
    linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-23-generic
    menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-22-generic
    menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-22-generic ...'
    linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-22-generic
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_memtest86+ ###
    menuentry "Memory test (memtest86+)" {
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux16 /memtest86+.bin
    menuentry "Memory test (memtest86+, serial console 115200)" {
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux16 /memtest86+.bin console=ttyS0,115200n8
    ### END /etc/grub.d/20_memtest86+ ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry "Arch Linux (on /dev/sda10)" {
    insmod ext2
    set root='(hd0,10)'
    search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
    linux /boot/vmlinuz26 root=/dev/sda10 ro
    initrd /boot/kernel26.img
    menuentry "Arch Linux Fallback (on /dev/sda10)" {
    insmod ext2
    set root='(hd0,10)'
    search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
    linux /boot/vmlinuz26 root=/dev/sda10 ro
    initrd /boot/kernel26-fallback.img
    #### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    # From Arch grub menu.lst
    # (0) Arch Linux
    #title Arch Linux [/boot/vmlinuz26]
    #root (hd0,0)
    #kernel /vmlinuz26 root=/dev/sda3 ro
    #initrd /kernel26.img
    #Note: With a separate boot partition, omit /boot from the path, (i.e. type set prefix=(hdX,Y)/grub and insmod
    (hdX,Y)/grub/linux.mod).
    #This introduces the "linux" and "initrd" commands, which should be familiar (see #Configuration).
    #An example, booting Arch Linux:
    #set root=(hd0,5)
    #linux /boot/vmlinuz26 root=/dev/sda5
    #initrd /boot/kernel26.img
    #boot
    ###menuentry "Arch1" {
    ###insmod ext2
    ###set root='(hd0,10)'
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    ###search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UU
    ID
    ###linux /boot/vmlinuz-26 root=635d7d02-3f5b-4af6-9c74-16b2af8cc7fd ro quiet splash # ARCH'S ROOT UUID
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ###menuentry "Arch2" {
    ###insmod ext2
    ###set root='(hd0,4)' #= TRYING UBUNTU'S BOOT
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
    ###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ###menuentry "Arch3" {
    ###insmod ext2
    ###set root='(hd0,10)' #= TRYING UBUNTU'S BOOT IN HD FORMAT
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
    ###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ### END /etc/grub.d/40_custom ###
    =================== sda4: Location of files loaded by Grub: ===================
    .0GB: grub/core.img
    .0GB: grub/grub.cfg
    .0GB: grub/menu.lst
    .0GB: grub/stage2
    .0GB: initrd.img-2.6.32-22-generic
    .0GB: initrd.img-2.6.32-23-generic
    .1GB: initrd.img-2.6.32-24-generic
    .1GB: initrd.img-2.6.32-26-generic
    .0GB: vmlinuz26
    .0GB: vmlinuz-2.6.32-22-generic
    .0GB: vmlinuz-2.6.32-23-generic
    .1GB: vmlinuz-2.6.32-24-generic
    .0GB: vmlinuz-2.6.32-26-generic
    =============================== StdErr Messages: ===============================
    No volume groups found
    mdadm: No arrays found in config file or automatically
    [/quote]
    Output of fdisk -l from chroot is -
    [quote]Disk /dev/sda: 750.2 GB, 750155292160 bytes
    255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x0000b084
    Device Boot Start End Blocks Id System
    /dev/sda1 417690 6554519 3068415 82 Linux swap / Solaris
    /dev/sda2 25414954 1465144064 719864555+ 5 Extended
    /dev/sda3 6554520 25414829 9430155 83 Linux
    /dev/sda4 * 63 417689 208813+ 83 Linux
    /dev/sda5 25414956 1360287809 667436427 83 Linux
    /dev/sda6 1360287873 1423198349 31455238+ 83 Linux
    /dev/sda7 1423198413 1465144064 20972826 83 Linux
    Partition table entries are not in disk order
    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk identifier: 0x00025bd3
    Device Boot Start End Blocks Id System
    /dev/sdb1 2048 1953523711 976760832 83 Linux
    I need to post this now and come back from a different machine to note the error messages I am now getting on boot. ...
    Note that when I boot and press esc to get the menu I get the menu.lst I created (in the second quote) above in /dev/sda6, ie the one with the Arch hd and uuid entries - so grub is looking there and finding that menu.lst, but something goes wrong after that.
    OK. Have now booted the machine and after pressing esc and selecting the uuid entry (the same thing happens with the hd entry) I get a whole lot of stuff, but what seems relevant is (typing it out) -
    List of all partitions:
    No filesystem could mount root, tried:
    Kernel panic - not syncing: VS: Unable to mount root fs on unknown-block(0,0)
    Pid: 1, comm: swapper Not tainted 2.6.39-Arch #1
    If anyone can help I'd really appreciate it. This is my MythTV machine so the WAF is about to take a big dive!
    If I could just install grub to the MBR as if this was a new installation of Arch that would be great.
    I am really lost as to what is going on, which I'm sure is evident.
    Thanks a lot
    belbo
    Last edited by belbo (2011-08-12 13:31:23)

    Hi. Unfortunately that didn't help.
    So next, based on this post https://wiki.archlinux.org/index.php/Ke … el_version I chrooted into Arch and (a) rolled back and (b) reinstalled my kernel but that didn't help either. I suspected it wouldn't because the kernel was working fine before I deleted the partitions in question.
    [2011-08-08 23:32] ==> Image generation successful
    [2011-08-08 23:32] upgraded kernel26 (2.6.39.3-1 -> 2.6.39.3-1)
    I then did a pacman -Suy and the linux package has now replaced kernel26. ( See this wiki entry http://www.archlinux.org/news/changes-t … filenames/). I didn't change anything in menu.lst owing to this and it seems there is no need to. Unfortunately this hasn't helped either - still getting the kernel panic. 
    Pacman.log relating to the new kernel package below -
    [2011-08-09 00:22] Running 'pacman -Suy'
    [2011-08-09 00:22] synchronizing package lists
    [2011-08-09 00:23] starting full system upgrade
    [2011-08-09 00:23] Running 'pacman -Suy'
    [2011-08-09 00:23] synchronizing package lists
    [2011-08-09 00:23] starting full system upgrade
    [2011-08-09 00:26] removed python-mygpoclient (1.5-1)
    [2011-08-09 00:26] removed kernel26 (2.6.39.3-1)
    [2011-08-09 00:26] warning: /boot/grub/menu.lst installed as /boot/grub/menu.lst.pacnew
    [2011-08-09 00:26] upgraded grub (0.97-17 -> 0.97-19)
    [2011-08-09 00:26] upgraded icu (4.8-1 -> 4.8.1-1)
    [2011-08-09 00:26] upgraded linux-firmware (20110512-2 -> 20110727-1)
    [2011-08-09 00:26] >>> Updating module dependencies. Please wait ...
    [2011-08-09 00:26] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2011-08-09 00:26] ==> Building image from preset: 'default'
    [2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    [2011-08-09 00:26] ==> Starting build: 3.0-ARCH
    [2011-08-09 00:26] -> Parsing hook: [base]
    [2011-08-09 00:26] -> Parsing hook: [udev]
    [2011-08-09 00:26] -> Parsing hook: [autodetect]
    [2011-08-09 00:26] -> Parsing hook: [pata]
    [2011-08-09 00:26] -> Parsing hook: [scsi]
    [2011-08-09 00:26] -> Parsing hook: [sata]
    [2011-08-09 00:26] -> Parsing hook: [filesystems]
    [2011-08-09 00:26] -> Parsing hook: [usbinput]
    [2011-08-09 00:26] ==> Generating module dependencies
    [2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
    [2011-08-09 00:26] 7079 blocks
    [2011-08-09 00:26] ==> Image generation successful
    [2011-08-09 00:26] ==> Building image from preset: 'fallback'
    [2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    [2011-08-09 00:26] ==> Starting build: 3.0-ARCH
    [2011-08-09 00:26] -> Parsing hook: [base]
    [2011-08-09 00:26] -> Parsing hook: [udev]
    [2011-08-09 00:26] -> Parsing hook: [pata]
    [2011-08-09 00:26] -> Parsing hook: [scsi]
    [2011-08-09 00:26] -> Parsing hook: [sata]
    [2011-08-09 00:26] -> Parsing hook: [filesystems]
    [2011-08-09 00:26] -> Parsing hook: [usbinput]
    [2011-08-09 00:26] ==> Generating module dependencies
    [2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
    [2011-08-09 00:26] 23360 blocks
    [2011-08-09 00:26] ==> Image generation successful
    [2011-08-09 00:26] installed linux (3.0.1-1)
    I don't think I've mentioned that my old menu.lst seems to have disappeared and so must have been on one of the partitions that were deleted. I did have 2 Arch installations when I was setting things up months ago and that menu.lst may have been on the other partition but pointing to this partiton's kernel for booting. Presumably that's possible since this partiton is definitely the one I have been using for the last several months (confirmed by log and other files updated in the last few days etc). Even so, I suppose that probably wouldn't be relevant to this issue, since grub is finding the menu.lst on this partition when it boots so it is looking in the intended place now.
    It seems I'm at a bit of a dead end. It seems these kernel panics are usually because there is something wrong with the kernel - which there wasn't with mine (and presumably the kernel in the new linux package is fine) or there is a typo in menu.lst (I can't see one and nobody has pointed one out yet) or menu.lst is pointing to the wrong partition (mine is pointing to the same partition and /boot directory that is found by grub - which is where my boot image is located - so it seems to be correct). I have nevertheless tried editing the menu.lst entry when booting to boot from different partitions but so far that hasn't worked either.
    If anybody has other ideas I'd really appreciate it.
    If not, some suggestions on re-installing would also be appreciated. I have a recent tar archive of the partition, but presumably reinstalling that wouldn't be of much use since it would just put back what is currently there. I guess that I need to format the partition, create a separate boot partition, do a fresh install of Arch into the formatted partition (and with boot in the new boot partition). And then restore my tar backup (excluding the boot directory) into the formatted partition?
    Any assistance greatly appreciated.
    Thanks
    belbo
    Last edited by belbo (2011-08-08 23:17:49)

  • How to reclaim the space after delete

    Hi All,
    Today we deleted large number of rows from one table, but we didn't get free space after that. So for testing purpose, I have created one test tablespace with 5mb size .Created a table and inserted n number of rows in that table and made the tablespace full.I checked in dba_segments(5mb) and dba_free_space tables.It shows perfectly.After that I deleted all the records and try to create a simple table,but it returns (ORA-01658: unable to create INITIAL extent for segment).I read some time back in tom's forum that delete willn't reclaim the space ,instead it will go to freelist of table..Is there any way to reclaim the space?(after delete)
    and also I used to see the tablesize by using dba_segments table.but now it shows 5mb of size for the empty table.Is there any query to get the exact table size?Please help me to understand the concept.
    Thanks,Jvel

    880401 wrote:
    Hi All,
    Today we deleted large number of rows from one table, but we didn't get free space after that. So for testing purpose, I have created one test tablespace with 5mb size .Created a table and inserted n number of rows in that table and made the tablespace full.I checked in dba_segments(5mb) and dba_free_space tables.It shows perfectly.After that I deleted all the records and try to create a simple table,but it returns (ORA-01658: unable to create INITIAL extent for segment).I read some time back in tom's forum that delete willn't reclaim the space ,instead it will go to freelist of table..Is there any way to reclaim the space?(after delete)
    and also I used to see the tablesize by using dba_segments table.but now it shows 5mb of size for the empty table.Is there any query to get the exact table size?Please help me to understand the concept.
    Thanks,JvelDELETE simply deletes the specified rows. The blocks/extetents that were allocated to hold those rows remain allocated. The theory is that if the table once needed sufficient blocks/extents to hold 'x' rows, it may need so again at some time in the future. Allocating and de-allocating extents is a pretty expensive operation, so oracle is not going to waste time and resources constantly doing that just because you delete rows, which is a perfectly normal DML operation. Unless you don't expect that table to grow again, I'd not waste my time trying to reclaim the space.

  • Reclaim disk space after delete an index

    Hi ,
    I have deleted unused indexes from a history table to reclaim the disk space was allocated for these indexes , yet the size on the disk is the same , any steps I can follow to achieve this would be greatly appreciated..
    indexes size is 70 GB
    table size is 45 GB , # of rows is above 200 Million
    Thanks in advance

    in order to reclaim space after your big delete.  Don't shrink your data files unless you have no other choice.
    The space will automatically go back to SQL server. You don't have to do anything.
    The database size will be the same plus the growth of your log file due to logging the transactions. However, internally, SQL server knows that it still has that space to play with.
    Other wise you can go for  update the statistics and rebuild indexes . but I think it would be the part of your normal weekend nightly maintenance plan
    Please click "Propose
    As Answer" if a post solves your problem, or "Vote
    As Helpful" if a post has been useful to you

  • Reuse of freed space after DELETE statement (ASSM)

    Dear Members,
    After DELETE of records in tables, the USED SPACE in tablespace still grows when new records are inserted. So the freed space is apparently not reused!
    DB is Oracle 9.2. and ASSM is used.
    Does anyone knows how to solve this problem?

    1) Table (heap) space will continue to grow after deletes if the new rows are appended (APPEND HINT). Appending rows does not reuse free space in existing blocks.
    2) Index space will continue to grow after deletes if the leaf blocks could not be reused. Index leaf blocks will be reused only if a) new data index keys will fit in on of the existing leaf blocks that still has entries after the delete completes; b) all of the entries in the leaf block were deleted and a new leaf block needs to be added to the index. It is possible to shrink/coalesce or rebuild an index to cure this phenomenon.

  • Slow reboot after deleting bootcamp partition

    Hello,
    I was just told by a tech store that my bootcamp partition was slowing down my computer incredibly. I no longer need this partition so I went into Disk Utility, clicked the partition, and deleted it. I also had my RAM updated from 4GB to 8GB. I have an Early 2011 Macbook Pro, operating on Yosemite.
    The only question I have is, when I rebooted my computer for the first time after deleting the partition, the restarting process took much longer than normal. Without the bootcamp startup, I figured the startup time would be less, when in reality, it was longer. Is there something I missed while deleting my partition, and is there a way to fix this and speed up the reboot time? If not, will this slow reboot be a one time issue?
    Any comments would be appreciated!
    Thanks,
    Rachel

    There is a hidden Recovery HD between the OS X and the deleted BC partition, which you can verify using
    sudo gpt -vv -r show /dev/disk0
    in OSX Terminal.
    BCA does a better job by also relocating the Recovery HD appropriately and giving you a contiguous partition.
    The only other method is to subsume Recovery HD in OS X partition and then re-install OS X which will rebuild Recovery HD. This does not modify any of you files, but just the OS.
    You will also need to clean the Hybrid MBR which is now dangling and inappropriate for your case.

  • Lost space after deleted podcasts while downloading.

    I've had this happen twice: once on my iPhone 5S and once on my iPad 2.  I start a download of a podcast in the iOS Podcast app and then cancel the download.  In the case of my iPad 2, it froze and eventually when to the Apple logo screen.  When it was done, I lost about 6 GB of storage space and needed to reset my settings and data on my iPad to get it back.
    On my iPhone 5S, I had the podcast add crash bug, so I removed and reinstalled it.  I forgot to change the settings to not download so it started downloading about 50 podcasts at once.  I started swiping to delete them (which inadvertently unsubscribed from all my podcasts).  When I was done, the downloads had stopped, but I lost 4 GB of space, which was not reclaimed when I deleted the podcast app again.   What's weird is iTunes still shows my iPhone as having 4.5 GB free, but the phone itself said it only had 909 MB free.  I tried re-installing the podcast app, but the podcasts didn't show up there.  I tried restarting and hard resetting, but that didn't help.   Basically the space was gone.  I called Apple Support and was told I needed to do a restore. 

    I have the same problem, but it happened when I downloaded a sample of a book so I can not do the solution offered by Beachdogz. I would just buy the book but I can't because it says downloading so there's no buy option. Actually it says downloading downloading (twice) if that helps.
    Would appreciate any help.
    Thanks

  • Lost 110 GB of disk space after deleting files in target mode... A mystery?

    Dear all,
    Yesterday, I used my MBP in Target Disk mode and deleted a directory with approx. 110 GB of files in it. Now I found out that this space is mysteriously gone: the available free space on my hard disk did not increase, and the files are not in the trash or anywhere where I can find them.
    I tried Disk Utility doing ‘Verify Disk’ as well as ‘Repair Disk Permissions’, but with no success.
    Could any one advice me how I can recover my disk space?
    Thanks in advance....
    /Rudi

    Thanks, Tony.
    No, they are not in the trash of the other computer. It would also have taken the computer a while to transfer these files (110 GB takes a while, even over FireFire 800).
    The issue is not that I want to recover these files (I have backup copies), I just would like to have my disk space back. It is siting somewhere but 'lost' to the DOS.
    Best, Rudi

  • Lost disk space after each reinstall.

    I've had to reinstall leopard on my macbook three times in the last week for different reasons. After each reinstall(erase and install) it appeared that I lost a little more GB to the HDD. I have a 250GB HDD, and I know it actualls reads as 232.87, but without uploading any media and only using the reinstall disks that came with the box, I have only 218 or so GB. Is this normal? I can't find the numbers anywhere; they just don't add up.

    Anthony Turtzo wrote:
    I can't find the numbers anywhere; they just don't add up.
    My guess is that you have added up the sizes of the folders visible in Finder at the root level of the drive (Applications, Library, System, & Users) & compared that total to the total space used on the drive. The two numbers will not match because there are also hidden files & folders at the root level of the drive that Finder does not normally show. The hidden items are necessary for the proper operation of the Mac & in normal use are managed by the system. Since users should not tamper with them directly without good reason & it requires expert knowledge to do so without breaking anything, they have been made invisible in the Finder view.
    It is normal for the drive space used by these items to fluctuate, & for the total to grow somewhat after first installing the OS. Some of the items contain temporary files that are created & destroyed as needed. Some contain usage, crash, & other informational logs that are managed by routines that the system automatically runs periodically to keep their total from becoming too large. Others contain initialization data gathered over time that the system uses to start up or to run processes efficiently.
    Thus, there is no fixed correct number for their total size since that depends on the history & current state of the machine. On my iMac G5, one large hidden folder ("var") currently uses about 1.05 GB of drive space, but consider that only a ballpark number since it may be considerably different on different Macs at different times.
    If you are still concerned about the health of the drive, especially that something is eating up disk space unnecessarily, then run Disk Utility to check it. In the "First Aid" tab select your drive & click the "Verify Disk" button. If this reports no problems then you can be pretty sure there is nothing to worry about.

Maybe you are looking for