Capture Problems long time to allocate disk space

I have FCPHD and OSX 10.3.9. FCP has always worked well on my computer but is now taking a long time to allocate disk space(if that is even what it is doing) when I go to batch capture or capture now the capture window hangs and sometimes I am left with a large file in the capture scratch folder. Any Ideas?

You need to make sure you have set a time limit in Capture Now. Without that limit, FCP can (and sometimes does) allocate your entire Capture Disk as a potential capture file.
Here's an explanation of what is going on ...
When you use Capture Now, the disk system is being asked by FCP to essentially "keep capturing until we tell you to stop ... and no, we don't know HOW much that will be either." It is stressful on the system to be continually wandering around looking for space to stuff those ones and zeros with out any sense of how many they have to accommodate. One solution available to the system is to allocate the ENTIRE empty space on the disk as the potential capture file. This essentially locks the machine as there is no headroom for basic disk operations.
However if you set a limit on capture now, say 60 minutes, the disk system can allocate the space and may seem to be less confused by the process. It still does not know EXACTLY how much you want, but it knows you will not want MORE THAN the limit and therefor can reduce some of the uncertainty.
Better yet is to capture using timecode. This allows you to log the tape, then use batch capture. When you do this, the system knows EXACTLY how much space to allocate for each file and is very efficient.
Good luck.
x

Similar Messages

  • Unable to allocate disk space, disk might be fragmented

    I have a partitioned drive, I switch back and forth between 9.2.2 and 10.4. I use Protools on 9.2.2 and have never had a problem with recording audio until now. Whenever I go to record an audio track, it tells me "Unable to allocate disk space, disk might be fragmented". If I dont have enough space on the internal hard drive, how do I find that out and free up more space? If I need to fragment the drive, how do I do that also. I just now backed up all my files to an external firewire drive, and even when I open the moved files and try to record audio, it gives me the same error message. Can anyone help with this?
    regards
    Danro

    Hi, Danro -
    Welcome to Apple's Discussions.
    If I dont have enough space on the internal hard drive, how do I find that out and free up more space?
    Do a Get Info on the icon of the hard drive. Two of the info items presented in the Get Info window will be "Capacity" and "Available" - the critical one is the one labelled "Available" - that's how much total unused space there is on that partition. For normal usage, this should not be less than about 15% of the "Capacity" figure - i.e., a volume should not be allowed to get more than about 85% full.
    The total unused space ("Available") does not take into account how much the disk may be fragmented.
    To free up space, throw away or archive off files - once they have been archived off the originals can be thrown away.
    Note - before throwing away the originals, confirm that the archived files are indeed copies, and not aliases - you can check for that by looking at the name of the file on the archive volume - names for aliases are shown in italic - or by examining the size of the file - an alias will typically report as being only about 4K in size.
    If I need to fragment the drive, how do I do that also.
    I assume that's a typo - no one should try to fragment a drive; the goal should be to defragment a drive.
    This Apple KBase article discusses file (drive) fragmentation -
    http://docs.info.apple.com/article.html?artnum=17933
    There are two basic ways to defragment a drive -
    • Archive off all the items that you do not want to lose, then erase the volume (partition). This can be done only while booted to another volume - to a CD, or to a different partition (such as the OSX one, in your case). Then re-install the OS and copy back the files needed from the archive volume.
    Note - doing a simple Finder-based erase of the drive will not fix any directory errors; it will only fix file fragmentation. To get rid of any directory errors, you will need to use a utility such as Alsoft's DiskWarrior, or re-initialize and re-partition the entire drive. Note that this second option, re-initialization, will delete everything on the drive as a whole, including all partitions, not just the partition in question.
    • Use a defragmenting utility such as Alsoft's PlusOptimizer or MicroMat's TechTool Pro. A defragmenting utility will not remove anything from the volume - it just moves files around physically on the volume until they are no longer fragmented. In order for it to be able to do that it will need some free space on the volume - usually 15% or so of the volume's capacity is sufficient for that.
    <hr>
    Sometimes an error message is not fully accurate - there is a problem, but the wrong message is generated. To examine for that, boot to an OS Install CD (either OS 9 or OSX, depending what is available), and run Disk First Aid (OS 9) or Disk Utility (OSX). Let the utility examine the drive, and have it repair all that it finds wrong.

  • Capture Ended Due to lack of disk space!?

    It says that the capture ended due to lack of disk space, but the capture window says: 586.2GB Total Free Space and 2713.9 min Total free time??? (im using an external hard drive) It keeps telling me it ran out after 9:50mins of capture now?
    I am trying to capture 40mins of film.

    Back up everything presently on the drive, then use Disk Utility to reformat to Mac OS Extended. If the only things on the drive at present are your captured video clips, you're probably better off simply reformatting and then recapturing. Proper format will eliminate the 2GB/9min limit.
    You haven't said how the drive is connected. It needs to be via firewire. Apple doesn't support use of USB drives with video applications, though some folks have used USB drives successfully.
    Message was edited by: R. Mitchell Fore

  • Problem Export to Excel it takes long time and Takes more space.

    Hello All,
    when we export to Excel in portal(reports), it takes long time and it takes more space.
    how to overcome this problem please any one knows provide the proper solution for this issues
    Regards,
    Ch.

    Hi Chetans,
    I have had the same problem, and I had to create a OSS message to SAP in order to solve this issue, until now I don't have an answer. They made me to change a lot of configuration in Java and BW without luck. To tell you more, when we try to export to excel the java instance restarts aumotatically.
    But we have this problem, when we try to export a huge quantity of data, so I found a note which says the limitation of exporting to excel. Take a special attention to the Performance section.
    Note 1178857
    [https://service.sap.com/sap/support/notes/1178857|https://service.sap.com/sap/support/notes/1178857]
    I recomend you that you create a message to SAP. If you find a solution, please let me know.
    Regards, Federico

  • Lion takes long time to find free space after emptying trash

    After emptying the trash, I've noticed that Lion does not see the additional free space until after doing a reboot, and even after that it takes a long time for it to find all the new free space.  Anybody know what's wrong with the trash system?

    Absolutely nothing is wrong with it.  See Missing disk space in Lion.

  • Installation problems with The Sims 2 (disk space)

    Hey, sorry to bug everyone but I have been having so much trouble trying to install The Sims 2. Whenever I try to open the installer it says..."Package Installer requires at least 1 MB of free disk space. Free up some space on your local disk and then re-lauch Package Installer"
    I am so confused, I got my macbook about a month ago and it is my first mac. I didn't think I would have to "free up space on my local disk" And if I do how do I go about doing that?
    Or am I just screwed? I thought if my macbook wouldn't run this game it may just be very slow because it couldn't keep up with the graphics, I didn't expect it to not even open the installer.
    Please help!

    I had this same thing happen. Its because you are trying to start the game from the DVD instead of the Harddrive as I recall. Make sure you are clicking on the icon in the Applications folder. It was a long time ago this happened to me and I forget all the details.

  • 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.

  • Problem: There is not enough disk space available to process clips. Clear some space and try again.

    Hi there.
    I am running the newest FCPX 10.0.9 and Mavericks, and I am editing a large multicam project. I have approx. 190 GB left on my external event/project disk via USB3 (it has 2TB in total), and I get the error message:
    "There is not enough disk space available to process clips. Clear some space and try again."
    when I am trying to add clips to an angle in one of my multicam clips. I have made more than 8 multicam clips in the same event, without that problem, but now it won't let me add more.
    What's the problem?

    This was driving me nuts as well until I found the sneaky checkbox. In the editing tab in Preferences there is a checkbox for "Optimize media for multicam." If that's checked, Final Cut is rendering ProRes files for every clip you bring into multicam, so it just eats memory. Unchecking that solved my issues; hope it helps you or anyone who comes across this!

  • Time Capsule available disk space...

    I run TM on a 2tb TC. In the TM pane, "Available:", no longer shows the amount of disk space available, it just shows, "--". I recently upgraded the TC and that's when I think it started...but I'm not positive. Any clues?
    Thanks!

    This may be a development with Lion.   Do you run TM from a partition on your machine Hard Drive or do you use an external HD.
    I use a Lacie external HD and when I go to preferences, it shows the amount of available space left.  I've yet to progress to Lion though (waiting for Mountain Lion) 

  • Aperture freezes every time while calculating disk space

    Ok, here is what I've been trying to do:
    I want to get rid of Iphoto alltogether, gave all my pictures and videos in Aperture in one library. I don't want to switch back and forth between libraries. My ultimate goal is to after I get done ipmorting Iphoto into my current Aperture Library, to move most of my masters from Projects that I don't need on a regular basis to my external hard drive to free up space on my MacBook Pro.
    My aperture library is about 217 GB big, my Iphoto library is 141 GB.
    As of right now, I have 149 GB free space on my MacBook Pro.
    My Iphoto library is on a Lacie SSD.
    So what I did in order to move Iphoto into Aperture:
    I have Iphoto and Aperture open.
    I click on Aperture => Import library => I choose Iphoto ( located on my external harddrive).
    Then Aperture starts calculating disk space and freezes and is not responding anymore.
    So what do I have to do defferently to get my Iphoto library back on my Macbook?

    Now I have another question though
    My Iphoto library was 130GB big and as I mentioned before, when I tried to import it said that I needed at least 200 GB free space in order to import.
    I freed up a total of 205 GB by moving a bunch of my master files on an external hard drive and also temporarily moving my itunes library on the extrenal hard drive as well.
    After that, I could import my Iphoto library which was located on an extrenal hard drive into Aperture on my MacBook Pro.
    So, here's what I'm struggeling with now:
    My laptop is only showing me 20 GB of free space now, but it should show about 70 GB of fre space,  right?
    I had 200 GB free and imported 130 GB of pictures ( original size of my old iphoto library). So 200 GB - 130 GB should equal 70 GB of free space. Or what am I missing?
    I hope that doesn't sound too confusing. But now I am confused

  • Can't capture due to a lack of disk space...except the disk is empty!

    Using 5.1.4, I'm attempting to capture some DV footage to an external hard drive with about 60gb free. For some reason, once FCP has captured 2 gigs worth of footage, it stops and claims there isn't enough space on the disk.
    My system settings show that the minimum allowable scratch disc space is 2 gigs, so I don't understand why FCP is acting as if 58 gigs of free space equals zero gigs of free space.

    Nope, you're going to have to move all of the data off of the drive before you reformat or you'll loose it. In Disk Utility, choose the "Erase" tab at the top of the screen and then choose "Mac OS Extended" or Mac OS Extended (journaled) from the drop down menu for Volume Format, the Click on the "Erase" button. After it's done just copy your data back onto the drive and you're all set.
    < Edited by Host >

  • Time Machine and disk space

    I have just created a Time Machine backup on a new 500GB external drive (Mac OS Extended format) attached to a new 2012 Macbook Pro running Mountain Lion 10.8 with a 750GB hard drive (single partition, Macintosh HD).
    If I look at the Info of Macintosh HD drive it shows a total capacity 749.3GB of which 725GB is free. My basic grasp of math tells me therefore that approximately 25GB is being used.
    So, I create my first Time Machine backup that takes about 20 minutes to complete and if I look at the folder with the name made from the date and time of the backup underneath Backups.backupdb\MyMac it shows a size of 18.5GB.
    My first question is whether TM does some compression on the backups that would explain why only 18.5GB has been backed up rather than the 25GB that I was expecting?
    Secondly...
    Over the next few hours three more backups are made so I currently have a total of 4 date/time folders and a Latest link under the Backups.backupdb\MyMac folder. These last three backups were completed in a matter of seconds as nothing has been added/changed on the disk.
    If I check the info of each individual time/date folder they are each displaying around 18.5GB and if I check the info of the Backups.backupdb\MyMac folder it shows that 74GB (4 x 18.5GB) has been consumed on the disk .
    However the Info of the Time Machine disk from the sidebar shows that only approximately 18.5GB has been used with about 471GB of the 500GB still available.
    How come each of the four individual date/time folders are showing they each contain approximately 18.5GB whereas I believe only the first actually contain this amount of data? Are there links in the subsequent backups to the original that are then included in the stats?
    Should I take the space consumed as shown by Finder with a pinch of salt or is there a way to get a more accurate idea of what is contained in each of the backup folders?
    Thanks

    Thanks hpr3... The link http://pondini.org/TM/Works.html explained it very well...
    Sorry for the repost in the Mountain Lion forum but I can't find a way to delete the posts.

  • [SOLVED] Long time with excessive disk access before system reboot.

    I feel I would be grateful for some help here. It's my first go at Arch Linux having used Xubuntu for several years. It may be I'm missing something obvious but then I would be happy if someone could point me in the right direction.
    Problem: When I do a system restart by issuing
    $ systemctl reboot
    I get the following output
    Sending SIGTERM to remaining processes...
    Sending SIGKILL to remaining processes...
    Unmounting file systems.
    Unmounted /sys/kernel/debug.
    Unmounted /dev/hugepages.
    Unmounted /dev/mqueue.
    Not all file systems unmounted, 1 left.
    Disabling swaps.
    Detaching loop devices.
    Detaching DM devices.
    Unmounting file systems.
    Not all file systems unmounted, 1 left.
    Cannot finalize remaining filesystems and devices, giving up.
    Successfully changed into root pivot.
    Unmounting all devices.
    Detaching loop devices.
    Diassembling stacked devices.
    mdadm: stopped /dev/md126
    [ 1654.867177] Restarting system.
    However, after the last line is printed, the system does not reboot immediately but hangs for about 2 minutes with heavy disk activity. I can't say if it is read or write or both, but the led of my HDD is lit constantly. When this activity stops, the machine reboots.
    $ systemctl poweroff
    works as expected, i.e. shuts down immediately without excessive disk access.
    I see this behaviour both with the installed Arch system and when I run the live installation/recovery CD. It is also the same if I boot into the busybox rescue shell and then restarts the machine from there. It also does not seem to matter if any partition on the disk is is mounted or not, the behaviour is always the same with 2 min. heavy activity before reboot.
    System setup:
    Sony Vaio VPZ13. Intel Core i5 M460, 4GB ram, 2x64GB SSD in RAID0 configuration via bios setting (a.k.a. fake raid), partitioned like:
    windows boot
    windows system
    linux swap
    linux "/"
    linux "/home"
    So it's a dual boot setup with Windows 7.
    The raid array is assembled by mdadm, and I have mdadm_udev among my mkinitcpio.conf hooks (after blocks but before filesystems).
    Snip from journalctl log showing actions when reboot has been issued:
    jan 18 12:24:23 wione systemd[1]: Stopping Sound Card.
    jan 18 12:24:23 wione systemd[1]: Stopped target Sound Card.
    jan 18 12:24:23 wione systemd[1]: Stopping Bluetooth.
    jan 18 12:24:23 wione systemd[1]: Stopped target Bluetooth.
    jan 18 12:24:23 wione systemd[1]: Stopping Graphical Interface.
    jan 18 12:24:23 wione systemd[1]: Stopped target Graphical Interface.
    jan 18 12:24:23 wione systemd[1]: Stopping Multi-User.
    jan 18 12:24:23 wione systemd[1]: Stopped target Multi-User.
    jan 18 12:24:23 wione systemd[1]: Stopping Login Prompts.
    jan 18 12:24:23 wione systemd[1]: Stopped target Login Prompts.
    jan 18 12:24:23 wione systemd[1]: Stopping Getty on tty1...
    jan 18 12:24:23 wione systemd[1]: Stopping Login Service...
    jan 18 12:24:23 wione login[333]: pam_unix(login:session): session closed for user root
    jan 18 12:24:23 wione login[333]: pam_systemd(login:session): Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    jan 18 12:24:23 wione systemd[1]: Stopped D-Bus System Message Bus.
    jan 18 12:24:23 wione systemd[1]: Stopped Getty on tty1.
    jan 18 12:24:23 wione systemd[1]: Stopping Permit User Sessions...
    jan 18 12:24:23 wione systemd[1]: Stopped Permit User Sessions.
    jan 18 12:24:23 wione systemd[1]: Stopped Login Service.
    jan 18 12:24:23 wione systemd[1]: Stopping Basic System.
    jan 18 12:24:23 wione systemd[1]: Stopped target Basic System.
    jan 18 12:24:23 wione systemd[1]: Stopping Dispatch Password Requests to Console Directory Watch.
    jan 18 12:24:23 wione systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
    jan 18 12:24:23 wione systemd[1]: Stopping Daily Cleanup of Temporary Directories.
    jan 18 12:24:23 wione systemd[1]: Stopped Daily Cleanup of Temporary Directories.
    jan 18 12:24:23 wione systemd[1]: Stopping Sockets.
    jan 18 12:24:23 wione systemd[1]: Stopped target Sockets.
    jan 18 12:24:23 wione systemd[1]: Stopping D-Bus System Message Bus Socket.
    jan 18 12:24:23 wione systemd[1]: Closed D-Bus System Message Bus Socket.
    jan 18 12:24:23 wione systemd[1]: Stopping System Initialization.
    jan 18 12:24:23 wione systemd[1]: Stopped Setup Virtual Console.
    jan 18 12:24:23 wione systemd[1]: Unmounting Temporary Directory...
    jan 18 12:24:23 wione systemd[1]: Unmounted Temporary Directory.
    jan 18 12:24:23 wione systemd[1]: Unmounted /home.
    jan 18 12:24:23 wione systemd[1]: Starting Unmount All Filesystems.
    jan 18 12:24:23 wione systemd[1]: Reached target Unmount All Filesystems.
    jan 18 12:24:23 wione systemd[1]: Stopping Local File Systems (Pre).
    jan 18 12:24:23 wione systemd[1]: Stopped target Local File Systems (Pre).
    jan 18 12:24:23 wione systemd[1]: Stopping Remount Root and Kernel File Systems...
    jan 18 12:24:23 wione systemd[1]: Stopped Remount Root and Kernel File Systems.
    jan 18 12:24:23 wione systemd[1]: Starting Shutdown.
    jan 18 12:24:23 wione systemd[1]: Reached target Shutdown.
    jan 18 12:24:23 wione systemd[1]: Starting Save Random Seed...
    jan 18 12:24:23 wione systemd[1]: Starting Update UTMP about System Shutdown...
    jan 18 12:24:23 wione systemd[1]: Started Save Random Seed.
    jan 18 12:24:23 wione systemd[1]: Started Update UTMP about System Shutdown.
    jan 18 12:24:23 wione systemd[1]: Starting Final Step.
    jan 18 12:24:23 wione systemd[1]: Reached target Final Step.
    jan 18 12:24:23 wione systemd[1]: Starting Reboot...
    jan 18 12:24:23 wione systemd[1]: Shutting down.
    jan 18 12:24:23 wione systemd-journal[189]: Journal stopped
    -- Reboot --
    Since I have used Xubuntu without hassle for several years, I first thought the problem may be related to systemd reboot and something in my system setup. But I have tried the Fedora 17 live CD and rebooting there works as expected. So, since it works in one systemd distro, it should work with Arch as well.
    Then I thought that it maybe had something to do with the raid-array, something along the lines of
    https://bugzilla.redhat.com/show_bug.cgi?id=752593
    https://bugzilla.redhat.com/show_bug.cgi?id=879327
    But then I found the shutdown hook for mkinitcpio and now I see that the array is stopped and dissassembled. So thats not the problem either. (Or thats what I guess at least.)
    Unfortunately I'm out of ideas. Any help would be grateful.
    Last edited by wingbrant (2013-02-02 22:20:20)

    It turned out that the magic word for me was "reboot=pci" on the kernel command line. With that option set it works lika a charm The machine reboots nice and clean.

  • Time Machine failure: Disk run out of space unexpectedly

    Hi
    I'm having serious problems in the last few days with Time Machine backups.
    I have an iMac '27 (late 2009) running Mountain Lion 10.8.2. The internal disk is 1 TB, and I use an external FW HD LaCie d2 Quadra 1 TB for my TM backups. After 3 years the disk is always full, but old backups were regularly removed. All the possible source of large variable files were excluded long time ago (VM disks, temporary directories, large download files).
    TM used to work quite smoothly, but now, since 10 days, the backup fails with the message
    "The backup disk ran out of space unexpectedly. Time Machine will try to make more space available by removing expired backups during the next scheduled backup."
    I've checked previous messages in the forum about such an error, but the various cases do not seem to match my specific problem (or I was not able to find the message with working answer).
    It seems that the "unexpected" problem is related to the fact that Time Machine is trying to backup again a large part of my filesystem, and it determines this fact only after the backup starts (so there is no pre-cleaning): when it happens I can see that the target size of the backup increases over time, while more and more data are written on the disk, until the disk is full.
    I'll try to summarize my situations with an itemized list:
    The current backup fails because it runs out of space, leaving an .inprogress file behind
    The latest backup did not fail: the log report a successful backup (checked with Time Machine Buddy)
    Examining the content of the latest backup, the one that did not fails, shows that some system directories, /Applications, /usr, and /bin are missing
    So, possibly, the "unexpected" error happens because the system is backing up a lot of stuff (like 60GB), and TM discover this only after it starts writing the files
    I've verified with Disk Utility both the TM disk and the internal HD, and they both report no problem.
    After some digging around, I was able to make TM work again removing the .inprogress file (using the Pondini instructions), removing (using the "Star Wars" interface) the latest backup, the one with the incomplete content, and removing a few older backups to create some more free space.
    The first time I thought it was a transient problem, but it happened again after a few days.
    So the real issue is, why the latest successful backup is actually incomplete, with a large number of directories missing, but there is no hint of this in the logs?
    I've read that old LaCie HDs might have problems with Mountain Lion, and with its power saving settings. May this be the cause? I did already turn off the power saving setting (put HD to sleep when possible) before the latest failure, but nothing changed.
    I've also tried to update the d2 Quadra firmware, as indicated by other messages and on LaCie website, but the update fails and the provided instructions are less than useful (I'll try to contact LaCie on this issue).
    My doubt is that this does not seem a power save issue... the failed backups happen while I'm actually using the machine (so no wake up/disk spin issue seems to happen), and the backups starts with no problem: they just finish abruptly with no apparent reason but with a success message.
    Does anyone have problems similar to mine (successful but incomplete TM snapshots)? Is the problem triggered by the HD firmware, or there are other possible causes?
    I plan to repair the TM one more time, and then keep it turned off to run only manual backups, but I'm aware that there is no guarantee that also a controlled manually started backup is not going to fail in a similar way.
    Thanks for any suggestion.
    Maurizio

    I am not running out of space, but I do have the same problem.  Every so often TM does a backup which is about 60 GB bigger than expected.   The  extra is always a new backup of /System /Applications /usr etc. - that is the 'system files'.
    The key thing is, as you have noticed:
    Examining the content of the latest backup, the one that did not fail, shows that some system directories, /Applications, /usr, and /bin are missing
    As a consequence the next backup is, in my case, 60 GB bigger because it includes all the system files.
    It is as if 'systemFilesExcluded' was turned on for the previous backup (the one that 'did not fail').  But I have looked in the .exclusions.plist for this backup and it is exactly the same as for other backups and does include:
            <key>systemFilesExcluded</key>
            <false/>
    It seems that TM is treating this as if <true/>.
    Like you, I have done a disk verify and it finds no errors.
    I think this must be a bug.  I have had this on four occassions since upgrading to Mountain Lion.  And it is doing a large one right now - I have caught it in the act!

  • Lack of disk space using "Capture Now"

    aright here's the situaton.. evry time i capture footage using "Capture Now" it captures it for a while and then just stops and a window pops up saying: capturing ended due to lack of disk space.
    How can i fix this?

    I'm thinking it might be closer to...
    1) Set a limit on Capture Now. Never have that box unchecked. Set it to 60 min if you want the whole tape.
    2) Do not under any circumstances run any anti-virus/filesaver software. Including Norton and Virex. Sure, Apple doles out Virex for free, but FCP doesn't cooperate with it very well.
    If you absolutely feel you must keep Virex installed on your system then use Kevin's script to shut it off before you use FCP:
    http://discussions.info.apple.com/webx?[email protected]@.68a85d17
    3) Do not capture to your main system drive.
    4) Check the format of the drive you are capturing to. It should be Mas OS Extended, jornalling off. If it isn't, copy your files from it and re-initialize it. If it is any other format, you will encounter problems. If not at first, then eventually.
    Good luck,
    CaptM

Maybe you are looking for

  • Sun Java System Calendar Server 2005q1 configuration issue

    Hello, I have installed Sun Java System Calendar Server (and dependencies systems) using the Java Enterprise System 2005Q1 on a Windows Server 2003 platform for an integration evaluation purpose. While configuring Sun Calendar Server it throw those m

  • Importing vm created on vm server in vm manager

    Hi all, I have created a vm with virt-install on the vm server.This only created a hardisk image file at the location which i specified as /OVS/running_pool/vm_name and one configuration file in /etc/xen. when i try to import this vm in the vm manage

  • Sales text And PO text

    Hi friends, Please somebody tell me what is sales text and Purchase order text???and why these are used???

  • Illustrator CS6 wont update to the latest CC-version, any ideas?

    AI wont update to the new CC-members only features. I would like to have access to the package feature and I have tried both deleting and uninstall AI, but no luck so far. I had CS Design and WebPremium installed before. Adobe Application Manager tel

  • Mac OS X 10.5.7 Finder not displaying items

    Just a blank screen. Couldn't see boot drive and everything else. MBPro running fine though. A bit perplexing, should I say? Help!