Backup Fails to Work "not enough disk space" C:55GB In Use, E:(USB Drive) 233GB Free

T61, 2GB RAM, C: 100GB Drive, E: 320GB USB Drive, Windows Vista Home Premium
A month ago I started getting message "Rescue and Recovery does not have enough disk space to perform the requested operation" when attempting a backup from C: to E: (USB Drive).  Ran diagnostics on C:, D: and USB Ports and all passed
C: 86.76GB  Total   E: 298GB
    31.99GB   Free        233GB  
Not sure how to resolve issue, should be plenty of space to do backup.              

I've had the same problem on a T60p and on a W500.  I have been able to get RnR going again by deleting several of the backups on the USB drive and then backing up again.  This puts my system at risk because I have no backup while doing this procedure.  Now recently RnR has been telling me there is not enough space to delete any of the backups.  So I'm limping along by growing the number of backups RnR is configured to keep but I'll eventually run out of space on my USB drive.
Did you ever get any support or find a solution?
I'm getting to the point where the amount of space in use on my C: drive is about equal to the free space on my USB drive.  I'm up to around 12 backups and eventually my USB drive really will have insufficient space.

Similar Messages

  • Clean Install G4 Dual 1 GHz-Not enough Disk Space Error? -SLOW USB copies

    HELP puhleeeeze!
    This seems to be an issue on various sites with no one being able to figure out what is the cause and a solution. One person stated his problem went away with a fullwipe and clean-reinstall of everything. But this is what I did already. 
    What is the reason for the "Not Enough Disk Space" error message when both my hard drives have gigs of space available. If I had hair I'd be pulling it out by now!   When trying to copy a file to my 2 internal hard drives that have a lot of space available, but only by the USB port?!!
    I have a Power Mac G4 Mirrored Door (MDD) Dual 1 GHz with a clean install of 10.5.8 from the Original Mac OS X Leopard DVD. Both internal hard drives are 60GB and 100GB. The hard drives were wiped clean with Disc Utilities and reformatted to Mac OS Extended (Journaled). The Power Mac only has the OS and a few music apps installed. Easily over 30 GB of space left on the the main G4 interal hard drive and about 75 GB on the other internal hard drive.
    The error seems to only happen when I connect a USB flash drive to the USB port. I tried to copy a 50MB update to the desktop-"Not Enough Disk Space" error message happened.
    I know that the G4 MDD Power Macs only have USB 1.0. Is this a USB 2.0 issue? Another issue is that it has very slow USB speed (dramtically slower than normal USB 1.0 copying of files. And this is only when it is successful. Is it a USB format issue? I know I couldn't get an external USB 2.0 drive to mount on the Power Mac at all. Disc Utilities could see it but it still would not mount. I have a friend who has an older G4 single processor Mac that doesn't experience these issues with its USB 1.0 ports.
    Now here's the kicker:
    If I put in a CD disc in the DVD/RW drive, it copies with no problems to either hard drive. If I connect to the Power Mac  via the ethernet network, files can copy with no problems. But any USB connection -  I get a the "Not Enough Disk Space" error message. I know this is an old mac... but it's never been problematic until this latest wipe and update to Leopard 10.5.8.
    Is there a solution to this? Any and all help, feedback, comments, thoughts are greatly appreciated in advance!!!

    Hello everyone,
    Ok, I did the ultimate task. I erased the hard drives, AGAIN. Just to start fresh from scratch. Hard drives were erased. Did a new install of Mac OS 10.5. And all was well. I could copy with no problems. I gave the computer to my friend and all was good for a couple of days and then the issue came back again. He couldn't copy anything to his internal hard drives and we received the "Not enough disk space" error message! I was baffled. A complete hard drive erase 2 times, 2 fresh Mac OS 10.5 installs and it works for a few days and then coping to HD we got the same **** problem again! THEN - I remembered that the PRAM battery was dead on this G4 Mirrored-Door Dual 1GHz PowerMac. I had recommended that he get a new battery, because this computer would always have the incorrect date and time after every restart. So with recalling this, I had him reset the PRAM by holding down the CMD+OPT+P+R keys after a restart (start-up Chime). I had him hold the keys for at least 3 start-up-chimes. Soon as the G4 Power Mac started up everything was fine again. He was able to copy files to his hard drives again with the "Not enough disk space" error message.
    So everyone! Try zapping your PRAM (resetting the PRAM) and see if this solves your problem. I told my friend to get a new PRAM battery to replace the old one that is completely dead. I have not heard back from him.  I will ask him again if the problem has come back.
    If that fails: My only other solution would be to consider that it is possible that Mac OS 10.5 has a conflict or issue with the G4 Processors and maybe it is safer to install Mac OS 10.3 or 10.4. Because this problem only has occured after installing Mac OS 10.5, the highest version of the Mac OS the Dual 1GHz Mirrored-Door G4 can be installed.
    Cheers,
    B

  • Hyper-V client backups fail - not enough disk space

    Freeing up space on the host won't help - you want to make a copy of a 500GB guest to a NAS with 600GB.
    If your guest has 500GB an dis only using 50GB why allocate it 500GB?

    Rod-IT wrote:
    Bare metal backup, sounds like it is using CIFS as a windows share - you're going to need 500GB for the system, plus space to make it recoverable. I wouldn't expect you to need 600GB but if it says there isn't enough, there isn't enough.
    Do other smaller systems work ok?
    Why not look at Veeam free edition or EUB to backup your machines instead?
    Yeah the whole "not enough disk space" is boggling me. I'm freeing up some additional space on the C drive of the host atm just to try it and see what happens. I'm also downloading the veeam free... no idea they had a free version. I tried to get funding for the real version but as denied so I'll give this a shot. 

  • There is not enough disk space to download new messages. How can I backup my old emails onto my hard drive to create room for new message?

    When trying to download new email messages I receive an error "There is not enough disk space to download new messages. Try deleting old mail, emptying the Trash folder, and compacting your mail folders, and then try again." I have emptied my trash, removed all the junk, deleted about 1gig worth of email and im still having problems.
    I have a ton of folders that I store all of my emails in, so that I can easily find older emails. This email has been working fine for me for about the pass 5-6 years and now I have problems. I would like to be able to back up my emails onto my hard drive so that I have them on hand. What is the best way to go about this? Because of my file structure I am not able to see all of my messages on one screen. Is there a way to select emails from a certain year?
    Thanks in advance for any help or suggestions.

    ''Try deleting old mail, emptying the Trash folder, and'' '''compacting your mail folders'''
    If you did not compact the folders after marking the messages for deletion, you have not deleted anything.
    http://kb.mozillazine.org/Keep_it_working_-_Thunderbird

  • The SCE1010 alert "Not enough disk space"

    My SCE1010 show the alert "Not enough disk space" in log.
    I find old discuss , someone say can delete the file: /tffs0/SYSTEM/PREVDBG.TXT , because the file is too big.
    But I don't confirm  delete the file will not effect system work fine.
    Could everyone help me to solve the problem ?
    Thank you very much.
    Log shows:
    SCE#>show log | i disk
    2012-12-25 00:50:44 | WARN  | CPU #000 | Not enough disk space.
    2012-12-25 00:50:44 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2012-12-26 09:07:57 | WARN  | CPU #000 | Not enough disk space.
    2012-12-26 09:07:57 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2012-12-27 17:40:09 | WARN  | CPU #000 | Not enough disk space.
    2012-12-27 17:40:09 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2012-12-29 01:57:20 | WARN  | CPU #000 | Not enough disk space.
    2012-12-29 01:57:20 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2012-12-30 11:54:34 | WARN  | CPU #000 | Not enough disk space.
    2012-12-30 11:54:34 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2012-12-31 20:51:49 | WARN  | CPU #000 | Not enough disk space.
    2012-12-31 20:51:49 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-02 05:19:01 | WARN  | CPU #000 | Not enough disk space.
    2013-01-02 05:19:01 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-03 13:31:12 | WARN  | CPU #000 | Not enough disk space.
    2013-01-03 13:31:12 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-05 03:28:45 | WARN  | CPU #000 | Not enough disk space.
    2013-01-05 03:28:45 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-06 13:21:00 | WARN  | CPU #000 | Not enough disk space.
    2013-01-06 13:21:00 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-07 21:18:05 | WARN  | CPU #000 | Not enough disk space.
    2013-01-07 21:18:05 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-09 05:00:04 | WARN  | CPU #000 | Not enough disk space.
    2013-01-09 05:00:04 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-10 14:52:16 | WARN  | CPU #000 | Not enough disk space.
    2013-01-10 14:52:16 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-12 03:29:34 | WARN  | CPU #000 | Not enough disk space.
    2013-01-12 03:29:34 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-13 13:01:44 | WARN  | CPU #000 | Not enough disk space.
    2013-01-13 13:01:44 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-14 21:28:53 | WARN  | CPU #000 | Not enough disk space.
    2013-01-14 21:28:53 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-16 05:30:58 | WARN  | CPU #000 | Not enough disk space.
    2013-01-16 05:30:58 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-17 19:43:29 | WARN  | CPU #000 | Not enough disk space.
    2013-01-17 19:43:29 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-19 02:45:28 | WARN  | CPU #000 | Not enough disk space.
    2013-01-19 02:45:28 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-20 13:22:47 | WARN  | CPU #000 | Not enough disk space.
    2013-01-20 13:22:47 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-21 21:14:55 | WARN  | CPU #000 | Not enough disk space.
    2013-01-21 21:14:55 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-23 05:22:05 | WARN  | CPU #000 | Not enough disk space.
    2013-01-23 05:22:05 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-24 19:14:35 | WARN  | CPU #000 | Not enough disk space.
    2013-01-24 19:14:35 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-26 04:01:48 | WARN  | CPU #000 | Not enough disk space.
    2013-01-26 04:01:48 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-27 12:53:58 | WARN  | CPU #000 | Not enough disk space.
    2013-01-27 12:53:58 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-28 20:36:09 | WARN  | CPU #000 | Not enough disk space.
    2013-01-28 20:36:09 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-30 06:03:35 | WARN  | CPU #000 | Not enough disk space.
    2013-01-30 06:03:35 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-01-31 18:56:02 | WARN  | CPU #000 | Not enough disk space.
    2013-01-31 18:56:02 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-02 02:48:06 | WARN  | CPU #000 | Not enough disk space.
    2013-02-02 02:48:06 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-03 10:55:07 | WARN  | CPU #000 | Not enough disk space.
    2013-02-03 10:55:07 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-03 11:50:10 | WARN  | CPU #000 | Not enough disk space.
    2013-02-03 11:50:10 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-04 21:37:16 | WARN  | CPU #000 | Not enough disk space.
    2013-02-04 21:37:16 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-06 10:44:39 | WARN  | CPU #000 | Not enough disk space.
    2013-02-06 10:44:39 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-07 18:46:44 | WARN  | CPU #000 | Not enough disk space.
    2013-02-07 18:46:44 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-09 03:23:55 | WARN  | CPU #000 | Not enough disk space.
    2013-02-09 03:23:55 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-10 11:36:02 | WARN  | CPU #000 | Not enough disk space.
    2013-02-10 11:36:02 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-11 19:53:10 | WARN  | CPU #000 | Not enough disk space.
    2013-02-11 19:53:10 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-13 09:55:40 | WARN  | CPU #000 | Not enough disk space.
    2013-02-13 09:55:40 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-14 19:57:55 | WARN  | CPU #000 | Not enough disk space.
    2013-02-14 19:57:55 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-16 04:20:07 | WARN  | CPU #000 | Not enough disk space.
    2013-02-16 04:20:07 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-17 12:12:19 | WARN  | CPU #000 | Not enough disk space.
    2013-02-17 12:12:19 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-19 02:09:51 | WARN  | CPU #000 | Not enough disk space.
    2013-02-19 02:09:51 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-20 09:41:58 | WARN  | CPU #000 | Not enough disk space.
    2013-02-20 09:41:58 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-21 17:39:08 | WARN  | CPU #000 | Not enough disk space.
    2013-02-21 17:39:08 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-23 03:21:28 | WARN  | CPU #000 | Not enough disk space.
    2013-02-23 03:21:28 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-24 11:18:43 | WARN  | CPU #000 | Not enough disk space.
    2013-02-24 11:18:43 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-26 00:36:10 | WARN  | CPU #000 | Not enough disk space.
    2013-02-26 00:36:10 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-02-27 08:13:12 | WARN  | CPU #000 | Not enough disk space.
    2013-02-27 08:13:12 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-03-27 14:51:13 | WARN  | CPU #000 | Not enough disk space.
    2013-03-27 14:51:13 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-03-28 22:43:19 | WARN  | CPU #000 | Not enough disk space.
    2013-03-28 22:43:19 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-03-29 22:44:54 | WARN  | CPU #000 | Available disk space at '/tffs0' is 31MB which is under 45MB. Some management operations may fail to execute.
    2013-03-30 07:00:26 | WARN  | CPU #000 | Not enough disk space.
    2013-03-30 07:00:26 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-03-31 07:02:00 | WARN  | CPU #000 | Available disk space at '/tffs0' is 35MB which is under 45MB. Some management operations may fail to execute.
    2013-03-31 21:27:56 | WARN  | CPU #000 | Not enough disk space.
    2013-03-31 21:27:56 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-04-02 05:10:02 | WARN  | CPU #000 | Not enough disk space.
    2013-04-02 05:10:02 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-04-03 13:57:11 | WARN  | CPU #000 | Not enough disk space.
    2013-04-03 13:57:11 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-04-04 21:24:16 | WARN  | CPU #000 | Not enough disk space.
    2013-04-04 21:24:16 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-04-05 21:25:51 | WARN  | CPU #000 | Available disk space at '/tffs0' is 31MB which is under 45MB. Some management operations may fail to execute.
    2013-04-06 11:11:45 | WARN  | CPU #000 | Not enough disk space.
    2013-04-06 11:11:45 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-04-07 18:33:53 | WARN  | CPU #000 | Not enough disk space.
    2013-04-07 18:33:53 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-04-09 02:46:02 | WARN  | CPU #000 | Not enough disk space.
    2013-04-09 02:46:02 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-04-10 02:47:40 | WARN  | CPU #000 | Available disk space at '/tffs0' is 29MB which is under 45MB. Some management operations may fail to execute.
    2013-04-10 08:08:00 | WARN  | CPU #000 | Not enough disk space.
    2013-04-10 08:08:00 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-04-11 08:09:38 | WARN  | CPU #000 | Available disk space at '/tffs0' is 32MB which is under 45MB. Some management operations may fail to execute.
    2013-04-11 17:35:16 | WARN  | CPU #000 | Not enough disk space.
    2013-04-11 17:35:16 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-04-12 17:36:51 | WARN  | CPU #000 | Available disk space at '/tffs0' is 34MB which is under 45MB. Some management operations may fail to execute.
    2013-04-13 07:12:46 | WARN  | CPU #000 | Not enough disk space.
    2013-04-13 07:12:46 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-04-14 07:14:24 | WARN  | CPU #000 | Available disk space at '/tffs0' is 31MB which is under 45MB. Some management operations may fail to execute.
    2013-04-14 12:54:48 | WARN  | CPU #000 | Not enough disk space.
    2013-04-14 12:54:48 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2013-04-15 12:56:25 | WARN  | CPU #000 | Available disk space at '/tffs0' is 30MB which is under 45MB. Some management operations may fail to execute.
    SCE#>

    Dear Minja.
    I have the same problem
    Can you see my dir -r ?
    SCE#dir -r
    File list for /tffs0/
         512    WED AUG 13 19:01:34 2008       DIAG                   DIR
         512    WED AUG 13 19:04:00 2008       SYSTEM                 DIR
         512    WED AUG 13 19:13:50 2008       APP                    DIR
         512    WED AUG 13 19:13:50 2008       IMAGES                 DIR
         512    TUE NOV 18 08:48:18 2008       ENGAGE                 DIR
    18189911    TUE APR 16 23:08:26 2013       RELEASE_.SLI          
        2356    TUE JUN 02 17:14:46 2009       SCRIPT.TXT            
                    7 File(s)               18194827 bytes
    File list for /tffs0/DIAG
         512    WED AUG 13 19:01:34 2008       .                      DIR
         512    WED AUG 13 19:01:34 2008       ..                     DIR
                    2 File(s)               1024 bytes
    File list for /tffs0/SYSTEM
         512    WED AUG 13 19:04:00 2008       .                      DIR
         512    WED AUG 13 19:04:00 2008       ..                     DIR
       25643    FRI MAY 03 12:02:50 2013       BOOTLOG.TX2           
         512    WED AUG 13 19:12:46 2008       BACKUP                 DIR
       25441    MON FEB 11 21:30:54 2013       BOOTLOG.TX3           
       39115    TUE MAY 14 01:29:42 2013       CONFIG.TXT            
       25658    FRI MAY 03 12:34:36 2013       BOOTLOG.TX1           
           0    MON FEB 11 13:48:44 2013       BSPFAIL.TXT           
       25647    SAT MAY 11 06:01:36 2013       BOOTLOG.TXT           
           0    WED OCT 07 10:18:02 2009       USRCONST.TXT          
         512    THU OCT 09 05:31:36 2008       PREVCONF               DIR
         512    WED OCT 07 10:23:12 2009       PQIINST                DIR
                    12 File(s)              144064 bytes
    File list for /tffs0/SYSTEM/BACKUP
         512    WED AUG 13 19:12:46 2008       .                      DIR
         512    WED AUG 13 19:12:46 2008       ..                     DIR
    9151426    MON FEB 11 21:29:48 2013       DBG_LOG.DF1           
       16310    MON FEB 11 13:48:56 2013       FAIL.DFL              
                    4 File(s)               9168760 bytes
    File list for /tffs0/SYSTEM/PREVCONF
         512    THU OCT 09 05:31:36 2008       .                      DIR
         512    THU OCT 09 05:31:36 2008       ..                     DIR
       39115    MON MAY 13 16:06:16 2013       CONFIG.TX8            
       39115    MON MAY 13 16:26:16 2013       CONFIG.TX7            
       39115    MON MAY 13 17:24:02 2013       CONFIG.TX6            
       39115    MON MAY 13 17:28:44 2013       CONFIG.TX5            
       39115    MON MAY 13 17:51:52 2013       CONFIG.TX4            
       39115    TUE MAY 14 00:56:44 2013       CONFIG.TX3            
       39115    TUE MAY 14 01:13:00 2013       CONFIG.TX2            
       39115    TUE MAY 14 01:29:46 2013       CONFIG.TX1            
       39115    MON MAY 13 15:38:40 2013       CONFIG.TX9            
                    11 File(s)              353059 bytes
    File list for /tffs0/SYSTEM/PQIINST
         512    WED OCT 07 10:23:12 2009       .                      DIR
         512    WED OCT 07 10:23:12 2009       ..                     DIR
                    2 File(s)               1024 bytes
    File list for /tffs0/APP
         512    WED AUG 13 19:13:50 2008       .                      DIR
         512    WED AUG 13 19:13:50 2008       ..                     DIR
    17184659    MON FEB 11 21:48:58 2013       EN37592.SLI           
                    3 File(s)               17185683 bytes
    File list for /tffs0/IMAGES
         512    WED AUG 13 19:13:50 2008       .                      DIR
         512    WED AUG 13 19:13:50 2008       ..                     DIR
    113609411    MON FEB 11 21:09:14 2013       SEOS.PKG              
                    3 File(s)               113610435 bytes
    File list for /tffs0/ENGAGE
         512    TUE NOV 18 08:48:18 2008       .                      DIR
         512    TUE NOV 18 08:48:18 2008       ..                     DIR
      647546    TUE MAY 14 00:55:44 2013       MYENGAG2.PQB          
      580274    TUE MAY 14 01:28:48 2013       BATCH.SER             
        3673    TUE MAY 14 01:29:38 2013       TEMP.DSS              
      647559    TUE MAY 14 01:11:58 2013       MYENGAG1.PQB          
      647347    TUE MAY 14 01:28:44 2013       MYENGAGE.PQB          
      647557    MON MAY 13 17:50:54 2013       MYENGAG3.PQB          
                    8 File(s)               3174980 bytes
                            373579776  total bytes used
                            20791296   total bytes free

  • OS X Mountain Lion Install - Not Enough Disk Space

    I am installing OS X Mountain Lion.   The download went fine.   It rebooted and began the install then failed because there is not enough disk space.  The solution is obviously to make more room on the disk. 
    The problem is that everytime I boot my Macbook now, it takes me immediately into the installation for OS X Mountain Lion.  I cant seem to get back into the OS to clean up disk space.  
    Is there any way to force my Macbook to boot to Snow Leopard again?   If not, is there any way to clear up disk space from within the OS X Mountain Lion installer or the OSX Utilities?   I'd prefer not to have to wipe my entire Macbook and restore from backup then go through the upgrade again after freeing up disk space.
    Thanks,
    JG

    Can't be that, [64bit] as this MacPro I have is fully capable, and is running 64bit.
    In fact, as far as memory serves, this one I bought [B.T.O. option] was one of the 1st 64bit offerings made available.
    But thanks for weighing in …
    Anyone else have a suggestion?
    Mac Pro
    MacBook Pro
    Hardware Overview:
      Model Name:    Mac Pro
      Model Identifier:    MacPro2,1
      Processor Name:    Quad-Core Intel Xeon
      Processor Speed:    3 GHz
      Number Of Processors:    2
      Total Number Of Cores:    8
      L2 Cache (per processor):    8 MB
      Memory:    24 GB
      Bus Speed:    1,33 GHz
      Boot ROM Version:    MP21.007F.B06
      SMC Version (system):    1.15f3
    Hardware Overview:
      Model Name:    MacBook Pro
      Model Identifier:    MacBookPro3,1
      Processor Name:    Intel Core 2 Duo
      Processor Speed:    2,4 GHz
      Number of Processors:    1
      Total Number of Cores:    2
      L2 Cache:    4 MB
      Memory:    4 GB
      Bus Speed:    800 MHz
      Boot ROM Version:    MBP31.0070.B07
      SMC Version (system):    1.18f5
    Even the graphics capabilities, are in the favor of the MacPro, which I opted for:
    ATI Radeon X1900 XT, rather than the default option at the time.
    This graphics card is due to be replaced with the newer 5870 upgraded card.
    Just have not slipped it in the case, as yet.
    But even without the graphics card update, it is still better than the MacBook's graphics capabilities, surely?

  • "Unable to Consolidate Library, not enough disk space on C:\"

    This is a very annoying bug and i'm certain it is a software bug and nothing that I can fix on my end without an iTunes update. The goods news, is that it should be very easy to change (I say this as a programmer myself.)
    The problem: I do not keep all my mp3's on my internal hard drive. This would be impossible since I have a 60gb ipod and my laptop only has a 60gb drive to begin with -- i'd never be able to hold my library on my laptop without using an external for storage. So in iTunes, I have my preferences setup to store music files on this external drive. It is working great. The actual database file is still stored on C:\ (internal) and this is fine since it is rather small. However, when I choose consolidate library, iTunes thinks for a few minutes and then claims that it is unable to perform the action because there is not enough disk space available on C:\. This is silly for several reasons: 1) iTunes should not be coded such that it copies all files to C:\temp (or wherever it does its temp work for that matter) before copying the files to thier final destination. This is just one extra disk read/write that is unneeded. 2) If, for whatever reason, using the internal drive as a temporary buffer is required, then just copy one song at a time. As long as I have enough free space to copy the largest song that needs to be moved, consilidation should be possible. There is no reason to copy all 60gb of music to the temp, then copy all 60gb to my external drive. Instead, it is much smarter to copy one song at a time (and deleting the copy in the temp folder after you are done with it.) 3) An example: My internal drive has 10gb of free space, my external has 55gb of music and 45gb of free space. My library contains 5gb of music that is located on my internal drive. Even if iTunes were to copy all 5gb to the temp space on c:\ before the final copy operation, this should be able to consolidate without a problem. However, it doesn't. For some reason, iTunes thinks that it has to copy all 60gb of music (including 55gb of music that is not going to move anywhere.)
    Recently I started storing all my music on a samba server. Simply changed the itunes preferences once again to point to //ipaddress/sharename and it works great. I can even sync my ipod on my laptop with the songs stored on my samba server without any trouble. However, consilidate library still fails for the same reason.

    Assuming there are enough space available on the filestore folder? Did you check system log during failure? If possible enable CMS trace, that may help you for further investaigation.

  • Problem "There is not enough disk space ..." when transferring tracks back to compu

    Hi All,?I am recovering from a massi've hard dri've failure so no lectures about backups for my library please. I am trying to transfer all of my mp3's back from my Zen Xtra 30GB to my computer. I am using Creative MediaSource and it worked for about 800 of them but now has stopped. Now any track will report an error "There is not enough disk space at the destination for this transfer". Checking my disk, I have 6GB of space left, so I am left in the dark as to how to fix this. I can't even get an individual track. Trying to troubleshoot this on my own, I've deleted my temp files but still no luck. Has anyone here has this problem? Better yet, does anyone have a solution?Thanks all!

    and now it doesn't. 8GB free and a few more tracks to go.

  • "Not enough disk space" when there seems to be (+ rapid memory consumption)

    [Note: I originally posted this in the iDVD section, but due to an answer I got there to another question and further conversations with my daughter, figured out this is probably an iMovie question?]
    I'm a newbie to iDVD and iMovie and Forums (my last Mac was a Performa 6360--still using it for the family budget). I got my daughter a MacBook as a graduation gift. She is using it to combine movie inputs from a wedding/reception that come from digital camreas and a couple of video cameras. We went to Flip4Mac to get the necessary software/features to import .wmv files (only way we could download one of the video cameras was by going from PC to Mac--can't remember if it was a Sony or Canon).
    Issue: When she tries to import vidoes into iMovie HD 6.0.3 which have already been transferred to her computer, she gets: "The file could not be imported: There is not enough disk space to import Macintosh HD/Users/julie/pictures/iPhoto Library/Originals/2007/Roll8/CIMG1442.AVI" [She says this is about a 4 min. clip.]
    Basically the question is how to get more room on her disk to import and to save? She seems to only be able to Save--she can't Save Project as an option because it says she doesn't have enough disk space (she's already deleted the Trash). Help says you need to have more than 400mb of free space or it gets difficult but the indicator shows 28.8GB free space left...so there seems to be some kind of disconnect?? (Or maybe we're talking apples and oranges?)
    [Even more disturbing, just in the last couple of days with only a little time spent on the computer, the 28.8 GB has dropped to 2.3GB--obviously there is something she is doing that she is not aware of or shouldn't be doing that is consuming memory at a rapid pace.] On top of that, she also gets the same error message when she tries to burn the project onto a disk using iDVD???
    I went through the first 5 pages of the forum and couldn't see a similar problem, but then I may have not known what to look for?
    Any help would be greatly appreciated...she's trying to give the DVD as a Wedding gift--somewhat belated.

    Hello Karstn Schluter,
    This is fm's daughter who is havin ghte difficulites. at the end you tell me to try to answer 1-8 so i will try.
    1- how can you tell if the avi is containing divx? or not?? do I need to just keep this in mind when importing these files
    2- I have not brought in an external drive. I did try making my laptop computer a harddrive so I could import my imovie poject to my eMAC at one point, but it was not allowing me to do that either. Because I had to have it in DVD form or something
    3- No I did not segment the internal drive....sorry How do you do that??? Right now I am trying to find out what is taking up all the memory and Hard Disk Drive space....i do not know how to do that either....Do you know how???
    4-Yes I know flip4mac is for wmv....I guess what that question was emplying was that I also have wmv files that I am trying to import to imovieHD and that is not working either...I can get my avi to get into imovieHD, but not my wmv. files
    5-THank you for the tip with the trash then another question to this one how do you delet projects that are taking up memory that are no longer in use?
    6-Thank you for the tip...so then ignore the not enough disk space.....how can you alter the disk space so that you can save the project under save project as and not just save project?
    7- Sorry my dad was miss informed I cannot import the wmv. files to imovie and I cannot import imovie to iDVD I only have transferred one and then all of the other files are not seen as movies so I can not import them?? Does that make since
    8- When we were useing the Sony Camera originally we could not import the video to the MAC because it did not have the correct firewire cable and it would not been read onto the MAC computer. So, we have to buy the flip4mac equipment so that I would be able ot download the inoformation to the computer by a wmv.file dvd so we are having difficulites trying to import that file.
    I hope these answers clear up the question a little bit more and sorry that your answers brought out more questions. Thank you very much for helping me. I was using a different program in my college class so changing to imovie and idvd has been a huge struggle for me. Thank you once again.

  • This message may contain a virus or there is not enough disk space. Skip this message?

    I have been randomly getting the following message for example for the past couple of weeks and it seems to be getting worse:
    There was an error downloading the following message:
    From: Popular Science <[email protected]>
    Subject: The Coolest Cars We Saw At The Detroit Auto Show
    This message may contain a virus or there is not enough disk space. Skip this message?
    I have also noticed that that there is an issue when I select the option to skip the message by selecting '''Yes'''. The body of a one message is replacing the body of one of the other messages that is downloaded (i.e. body of facebook message replacing body of message from amazon). This has been seen multiple times.
    I am using Thunderbird ver. 31.4.0 on Windows 8.1 and the latest Norton Security with Backup software for my antivirus and all software has the latest updates.

    Hi. Thanks for your prompt reply. The error message is generated in Thunderbird and not by my anti-virus software. It is also specific to one email account and does not affect the others.
    I have around 40Gb unused space on my hard drive.
    The From and Subject fields in the error message contain the sender's email address and subject header respectively (these didn't show in my original email)
    I have also moved a lot of messages from mu inbox.
    I have not changed my anti-virus software (and have been using the same package for years
    Regards

  • I am getting the following message "safari could not download the file (440MB) because there is not enough disk space.  disk utility says i have 249.8 GB of available disk space.  any suggestions as to what is the problem would be appreciated

    i am getting the following message "safari could not download the file (440 MB) because there is not enough disk space.  please delete files or download to another disk."  when i check system information it tells me i have 249.82 GB of disk space available.  any suggestions as to what i can do to resolve this problem.

    don
    thanks for your suggestion.  that is the same advice that i got from the geek squad at the local apple store.
    i did what he instructed but it did not work.  i have since called apple support twice regarding the problem.  they had me start the computer in safe mode, going into the library and deleting a phlist file (i think) do a repair disk permissions, do a repair disk, empty the cache, and finally the last guy told me to unplug the computer from the wall socket and restart.
    when i mentioned the advice you and the apple store guy gave me they sort of poo pooed it saying that was done when they did all this other stuff.
    i am now waiting for the download to be completed to see if unplugging the computer had any effect.
    thanks again for your kindness in answering my concern.

  • FCP X version 10.1.1.  When Sharing to DVD I get the following alert " There was an error burning your discd.  Not enough Disk Space in Target Folder"  I have 700GB   free.  Where is this target folder located?  how can I fix this problem? not space prob

    Sharing to DVD I get the following alert " There was an error burning your disc.  Not enough Disk Space in Target Folder"  I have 700GB   free.  Where is this target folder located?  How can I fix this problem? This is definitely not a space problem. 
    Since starting with FCP X, there has been tons of issues, now that the product actually works with the exception above, makes it impossible to share the production.  Has Apple fixed this problem.  is there a knowledge base article on this?
    On another note, One reason I have not purchased support on FCP X is because you sold a product that never worked for almost an entire year or more.   Now I can finally finish my project,  I cannot share it.....Really.  This has to be fixed now, I am loosing money as I typed this.
    Regards,
    Rob Harris

    Just curious, why would repairing permissions, rebooting ( rebooted 2 times already today) or creating a new user possibly fix this.
    I cannot create a new user, that is way too much work.  I will repair permissions again,  I repaired permissions just a few days ago. Then I will reboot, login and turn off App Nap and rerun the Share DVD.
    There must be something seriously wrong with the OS if your are suggesting creating another user.   WOW!
    Rob H.

  • Exporting to external harddrive "not enough disk space"

    imac   Mac OS X (10.3.9)  
    I'm having several problems while trying to export my entire iphoto library as a backup to an external harddrive...
    The main on is I am getting a "not enough disk space error". There is 95 GB available on the harddrive and the library is approximately 20 GB.
    I've been doing it in smaller increments b/c I thought it might be an issue of not enough space on my mac's harddrive as I only have like 6GB left (the reason I'm backing up and deletiing photos) but it gets to a certain point and then says no more.
    I've been using the export function, but I've also tried just dragging and dropping them and get the same error.
    I'm runnning iphoto 4.0.3.
    Of course I've tried restarting to no avail...
    Any suggestions would be welcome...
    Another issue is the filenames. Of course many have the same names from the camera. Is there a way to get them to automatically put them in folders on the harddrive. I've been doing this manually and it's tiresome.
    Finally, is there a way to get it keep the "date created" information. When I look on the harddrive it says they were all created 12/31/1903! That's going to make it very difficult to find something later should I need it...
    Thanx so much!
    JT

    < The library is like 30 GB while the pictures are only 20GB.>
    If you have rotated, cropped, or edited any pictures in iPhoto, the originals are all kept inside the iPlibrary in case you want to "revert to the originals"... it's good to know it's there, but you are less likely to revert to an original, since there's a reason you edited the pics in the first place.
    Anyway, those originals are taking "wasted space" in your iPlibrary.
    If you want to reduce the size of the iPlibrary from 30GB to close to 20GB, (because the thumbnails will remains and must), then you should get rid of the superfluous duplicates! I did.
    if you want to clean you iPlibrary and get rid of duplicates, you can use iPhoto diet. Free download.
    My advice, is do a drop and copy the entire iPlibrary to the external, as suggested by eww, because imagine a day, when the internal HD iPLibrary crashes on you, and becomes not salvageable, you will have a mirror copy, to copy back to your internal drive, with all it's albums, names, favorites ,star ratings etc....... If you export to the external HD, and if your iP library crashes on you.... you are to re-import from scratch.... and you will go %#%^&$&@$$@#
    I have been there myself... now I have 3 differents external HD that I back up to. 9 different iPlibraries, and 3 copies of each on 3 separate HD..... Photos are too important to me.....
    Reading this discussion group, you see many people writting thing such as "my library is gone what do I do?"
    it's not a matter of if but when!
    You be the judge...
    Michel

  • Not enough disk space in target folder?

    I am trying to burn a 3.7GB project on a dvd that holds 4.7 GB. The log says there's not enough disk space in the target folder. I've never had this problem before - what's going on and how do I fix it?
    PowerBook G4   Mac OS X (10.4.3)  

    not enough disk space in the target folder.
    This refers to the hard disk where DVD SP does the build. 'The target' is usually set to a folder called something like 'DVDStudioProDisc' somewhere on your main internal hard-drive. You need to have at least (say) 5GB free space on your working drive for the build. How much disk space do you have left?
    BTW it is possible to change the build drive & folder location in settings.

  • Not enough disk space error

    I have a macbook Pro with 640gb. I barely used any of the HD space and keep getting the "not enough disk space" anytime I try to download anything. Any help to resolve would be appreciated. Thanks

    OmniDiskSweeper
    https://www.omnigroup.com/products/omnidisksweeper/
    maybe you have pending backups being held.
    maybe you had a disk drive problem and instead of writing data to the disk, it was actually written to
    ./Volumes/"mydiskdrive -1" instead of "mydiskdrive"
    Direct you to the proper forum for MacBook :
    MacBook Series Forumshttps://discussions.apple.com/community/notebooks?view=discussions
    Mac OS X Forums
    https://discussions.apple.com/community/mac_os?view=discussions 
    http://www.apple.com/support/macbookpro

Maybe you are looking for