Disk Utility errors: No such file -or- No space left on device (50GB+ free)

I am trying to make an image out of a _NTFS formatted_ parition, using around 4,5GB of data, of a freshly installed Windozs. It's for debugging tons of machines I have been given (to debug..) and I need an image done. Note that debating if using an image as a solution is good or not is not the point of this thread.
When I try to make a new image out of the parition (clicking "New Image"), using the defaults settings, I enter my admin pass, then I'm being shown "No space left on device". Wierd. The device I am writing the image onto has 51GB left, and the Trash is emptied.
I tried changing the image format to all the possible types in Disk Utility, but I get the same error: No space left on device.
I then changed the device, this time I used a volume with 10GB free on it. Then, I only managed to get a standard DMG compressed image, where I need a "DVD/CD master" one. I'm still confused, because no other image type worked.
Then I tried making a new image (not from a disk or volume, empty) and then just copy data to it (I'm sure it's really not the way to go, but still). After creating the empty image (I opted for an 8GB, DVD burnable style, "DVD/CD master"), I got the wierd error: No such file (straigth after the image creation, in Disk Utility).
More info about volumes and stuff:
Data to be imaged:
A single partition on a volume (connected with IDE to Mac Pro, but I don't see why it would matter)
Where I can save it:
I got a big bunch of volumes right here, internally.
I tried one with 50GB free, but failed. Another one, on another disk, with 10GB, but failed.
Also, this error comes often in Disk Utility and other unix OS I think, and mostly for no real known reason (in OS X), as most issues I found were still unresolved.
Thanks for any help

Hey,
Im having the same exact problem.
Toast even says it has a medium error with this drive.
I cant burn with toast and it wont play other DVD-R movies
that I have burnt on other systems.
What is the fix?

Similar Messages

Disk Utility error: "No such file or directory."

I'm trying to copy a DVD I made in iDVD. What I've always done in the past is to open Disk Utility, put the DVD in the optical drive, select "Images...New...Image From [optical drive]". But today when I do this I get an error message that says "No such file or directory."
I've tried selecting the drive ("2.0 GB PIONEER DVD-R...") and selecting the DVD ("CFTPRODUCTDEMO").
The DVD plays in DVD Player no problems. I have 11 GB free on my hard drive. I'm using a new Pioneer DVR-111D external optical drive (the internal 106D won't read DVDs it makes).
What's wrong?

Hey,
Im having the same exact problem.
Toast even says it has a medium error with this drive.
I cant burn with toast and it wont play other DVD-R movies
that I have burnt on other systems.
What is the fix?

Why do I get error 'Could not create temporary file. No space left on device" when I use the Engine Installation Wizard in TestStand?

The process gets to the NIVISA\SETUP.INI step, then I get this error.
I've tried with installing the MDAC and not, and it happens both times.
The drive I'm trying to create the file to has 7.4GB open on it, so I'm not sure why this is happening.
Thank you,
Dave Neumann

Dave,
This is documented in the KnowledBase 2D6A63VW titled: "Error: Could Not Create Temporary File, No Space Left on Device".
As RByrd suggested, you might need to free up some memory space in your System Temp directory, OR you may change the location of your System Temp directory to one with more space (such as the directory where you want the TestStand Engine files to be saved). The Knowledbase shows how to do this step by step. This is its URL:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/46f99e55650d8d5b86256ac00059018e?OpenDocument
Regards,
Carlos Leon

Disk Utility Error: The underlying task reported failure on exit 1

    #!/bin/bash
      # Author : Bill Hernandez
    # Location : Plano, Texas
    # Updated : Saturday, June 6, 2009 (1:48 PM)
    # script name : setdisk_ownerenabled
    # make sure to set permissions to execute
    <hr>
    # Description :
    <hr>
    # I've noticed that sometimes when using disk utility I cannot repair permissions, or I might get :
    # ERROR: The underlying task reported failure on exit 1
    # This shell script seems to have solved the problem.
    # It worked very well for me,
    # IF YOU USE THIS SCRIPT, IT IS AT YOUR OWN RISK...
    # DO NOT USE IT UNLESS YOU UNDERSTAND WHAT IT DOES
    # After running it, it is best to restart before using Disk Utility again
    <hr>
    # Details :
    <hr>
    # After partitioning a disk using "Disk Utility", and then begin using it, at some point I would get
    # an arror message when trying to save to one of the partitions, yet when I looked at the permissions
    # everything looked fine. I would then try to use Disk Utility to repair permissions and end up with a
    # cryptic error that pretty much told me nothing.
    # I noticed that while in Disk Utility, if I selected a partition the lower LH corner of the dialog
    # showed : Owners Enabled : No
    # I tried selecting the partitions at the Desktop and doing a (CMD-I) and at the very bottom of each
    # info dialog there was a checkbox :
    # [ ] ignore ownership of this volume
    # which I would check, even after logging in as root, and I couldn't seem to get a consistent way
    # to get rid of the permissions dialog failure, so I found the vsdbutil command which can be used
    # as follows to get partition, or disk info :
    # $ vsdbutil -c /Volumes/driveor_partitionname
    # ----> Permissions on '/Volumes/driveor_partitionname' are enabled.
    # if it is not enabled you can enable the disk or partition using :
    # $ vsdbutil -a /Volumes/driveor_partitionname
    # It will set "Owners Enabled : Yes"
    # This below script loops through the mounted disks, partitions, etc. and gives you information.
    # You can leave the three flags below all set to TRUE, or selectively use what you want and change
    # the rest to false...
    <hr>
    # CHOOSE {"TRUE", "FALSE"}
    <hr>
    getvolumestatus="TRUE"         # get "Owners Enabled : (Yes|No)" status
    setvolumestatus="TRUE"         # set "Owners Enabled : Yes"
    list_volumes="TRUE"                   # show volume names
    <hr>
    # DO NOT CHANGE ANYTHING BELOW HERE
    <hr>
    if [ $getvolumestatus == "TRUE" ]; then
     echo '============================='
     echo '$getvolumestatus'
     echo '============================='
     # get "Owners Enabled : (Yes|No)" status
     for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
     vsdbutil -c $i
     done
    fi
    <hr>
    if [ $setvolumestatus == "TRUE" ]; then
     echo '============================='
     echo '$setvolumestatus'
     echo '============================='
     sudo echo -n
     # set "Owners Enabled : Yes"
     for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
     sudo vsdbutil -a "$i"
     echo "setting Owners Enabled : Yes for ---> $i"
     done
    fi
    <hr>
    if [ $list_volumes == "TRUE" ]; then
     echo '============================='
     echo '$list_volumes'
     echo '============================='
     for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
     echo $i
     done
    fi
    <hr>


As it turns out, this didn't completely solve the problem, it solved part of the problem.
Here is a summary to the root cause of the problem.
SUCCESS...
Problem Summary : The system crashed and would hangup during boot, tried many things, until I eventually erased the disk and started over again.
iMacG5 24 GHZ Intel with One internal disk partitioned into 3 logical drives
Cub_1 OS X 10.5.7
Cub_2 OS X 10.5.7 (Carbon Copy Cloner backup of Cub_1)
Cub_3 OS X Server 10.5.7 (standard os x server setup)
At some point after setting up standard preferences, OS X Server crashed.
When I tried to restart, the machine would hang up during boot.
Finally after several attempts, ran Disk Utility from install dvd and repaired Cub_3
When I tried to run "Repair Permissions" on Cub_3 from install dvd, I got an error
Disk Utility Error: The underlying task reported failure on exit 1.
Rebooted, and started in single user mode (CMD-S) during boot until I saw the unix commands on the screen
RAN : root # fsck -fy
Then I began seeing the same command filling the screen :
posix_spawnp("/usr/sbin/mDNSResponder") could not find file or directory
Called Enterprise Support and spoke to Frank Alcorn, he said this was most likely a permissions problem and asked me to try repairing permissions from the install dvd. I told him about the error, but nevertheless I tried it again and got the same Disk Utility Error: The underlying task reported failure on exit 1..
He asked me to try booting into single user mode again, and to try
root # chmod 775 /
root # reboot
During the reboot process the machine got hung up again, and could not get the single user mode to work at all.
Frank said the command needed to be :
root # chmod 1775 /
Frank asked me if I had changed anything in file sharing, and I told him I had. He asked me what I had shared, and I said the entire drive Cub_3. He asked me what I had done for permissions, if I had denied permissions to anyone. I told him that I had set myself up as the only user that could have access to it, and when he said that's where the problem was the lightbulb went off, and it made sense.
Shortly after I set the sharing preferences is when the server crashed. It all makes sense now...
Frank said not to share the entire disk, only portions (share points) of it. I had done this in Panther Server, and Tiger Server and it worked fine, but apparently Leopard Server works a little differently, maybe more secure.
It seems to me that if sharing the entire disk, which is what I needed would cause such a problem there should have been some sort of warning from the operating system, but there wasn't. I had run into this problem several times over the past three weeks since I had started working with Leopard Server, but in each case I ended up re-installing OS X Server and starting over again.
I told him I would try to reboot from the OS X partition (Cub_1) and try it from there.
He asked me to let him know if it worked, and I said I would...
Problem FIX :
I booted back into the partition containing OS X (Cub_1) and did the following via the Terminal.
$ su - root
$ chmod 1775 /
$ reboot
During the reboot process I held down the (OPTION) key, and selected Cub_3 (the os x server partition) and sure enough after a few minutes of holding my breath the login window magically appeared. So I logged in, and did not have to re-install the server. Hallellujah....
This solved the boot hang problem. It is great to finally have an answer. In retrospect it makes sense, but that's why its hindsight...
The reason for sharing the entire disk in my mind was that since I was the only user on the system, it was easier to have one disk mounted on my workstation rather than several folders. It made sense to me, it still does. I don't need a bunch of folders, just one disk is easier...

Disk utility error when erasing an external hard drive

Hi,
Not sure if this is the most appropriate fourm list to post this but I thought I'd give it a try.
I am running snow leopard on my MBP and am trying to use disk utility to erase and format an ext. HD. While the disk icon does not show up on the desktop when I connect it to my mac, Disk utility does show the ext. hd in the left column, but no matter what format I try, even just using one partition and selecting zero out all data, I get the following error: "disk erase failed with the error: POSIX reports: The operation couldn't be completed. Cannot allocate memory".
Is the hd dead? Are there other options? I do have disk warrior, version 4.1.1 and it does not regonize the ext. hd.
Please advise.
Thanks,

Thanks for the reply. Yes, I did select the ext hd as the one I wanted to erase (my internal hd is my start up drive). After I selected the ext hd, (there is no volume listed under it so the only thing I can select is the hd itself). that is when I selected erase and then Mac journaled, then named the hd and then after selecting erase, I got the error. Also as a matter of note, if I select firstaid, both the repair and verify permissions are dimmed, so I can't even try to repair the disk. That is when I tried disk warrior hoping that could examine the hd, but since it is not mounted on the d/t, it doesn't show as a drive to check. I don't understand why the ext hd shows up in disk utility, but not the d/t. Also of note is the fact that when I connect that ext had to my Mac with a fw cable, a window opens saying that the drive is not readable and do I want to initialize it or ignore. I choose to initialize and that is when I get the error. Also of note is that I have tried both security options of "don't erase data" and "zero out data" and still get the same error.
Hope this clarifies things a bit.

Disk Utility hangs during DMG file creation

I use disk utility to create DMG files from folders (with the corresponding command from the File -> New menu). Every now and then (and quite often, really), Disk Utility will not complete this process, but instead hang forever. It seems that something in the kernel gets stuck, because the machine can get increasingly unresponsive after the hang has started (for instance, I wanted to look in the system log right now, but running less on /var/log/system.log would create long hangs on the whole UI). The only way out is a reboot.
The machine is otherwise very stable.
(Ah, and Time Machine started at the same time now, and doesn't seem to be able to run - maybe disk utility and time machine are creating some deadlock situation?)
Anyone who has seen similar behaviour?

I haven't had this issue this since upgrading to Snow Leopard, so I assume it has been fixed.

Mavericks/Disk Utility error msg:

Hi,
Started to have these problems:
Disk Utility msg:
Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
ACL found but not expected on “private/var/root/Library”
ACL found but not expected on “private/var/root/Library/Preferences”
Since upgrading to Mavericks my xhd is not seen when starting the iMac. I have to reboot it each time for the iMac to see it. It is also making sounds.

Hi,
Thanks for the reply.
I had problems with an update from DevonThink. That's why I ran Disk Utility.
I usually run it after I notice a problem. Then I do a restart.
The problem with the xhd-A is new. It started after the Mavericks install. During the install I also had a xhd-B plugged in, but no problem with that. I've run Disk Utility on xhd-A. Problem still exisits.
To recap when xhd-A is plugged in when I start my iMac everyday it isn't seen.
Then I unplug the xhd-A power cord, plug it back in, and it is seen.
To answer your question, I've already tried your idea. I ejected the xhd-A, shut down the iMac. Then restarted it, then plugged in the xhd-A and it is seen.
The specific problem is I can't leave xhd-A plugged in to the iMac. I have to remove the power cord, then plug in the power cord each time for it to be seen. Frustrating. This didn't happen in the past.

Oracle Secure Backup error: 'No such file or directory'

Hi,
could you help me to fix the following issue?
RMAN> run { ALLOCATE CHANNEL c1 DEVICE TYPE sbt PARMS='SBT_LIBRARY=C:\windows\
system32\orasbt.dll' ; backup database format 'CF_%d_%T_s%sp%pt%t'; }
using target database control file instead of recovery catalog
allocated channel: c1
channel c1: SID=8 device type=SBT_TAPE
channel c1: Oracle Secure BackupStarting backup at 26-OCT-09
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
input datafile file number=00001 name=C:\APP\AIME\ORADATA\ORCL\SYSTEM01.DBF
input datafile file number=00002 name=C:\APP\AIME\ORADATA\ORCL\SYSAUX01.DBF
input datafile file number=00003 name=C:\APP\AIME\ORADATA\ORCL\UNDOTBS01.DBF
input datafile file number=00004 name=C:\APP\AIME\ORADATA\ORCL\USERS01.DBF
input datafile file number=00005 name=C:\APP\AIME\PRODUCT\11.2.0\DBHOME_1\DATABA
SE\TBS_5.F
channel c1: starting piece 1 at 26-OCT-09
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c1 channel at 10/26/2009 00:20:54
ORA-19506: failed to create sequential file, name="CF_ORCL_20091026_s10p1t701223
652", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
sbt__rpc_cat_query: Query for piece CF_ORCL_20091026_s10p1t701223652 failed.
(Oracle Secure Backup error: 'No such file or directory').
Thanks,
jun

You can work entirely in Xcode by using the command-line tool template in C. Xcode > File > New > Project > Command-Line Tool > Next > Language: C > Next > Create.
If you do want to work on the command line, you may as well just use the "clang" program instead. The "gcc" tool is just a compatibility tool for existing scripts that are expecting the actual "gcc" program. Apple hasn't used the real "gcc" for years. (Read up on the GPLv3 for more information.)
The gcc/clang arguments are the same. The "-c" flag instructs the compiler to only compile a single .c file into a .o object file. It won't create an executable. If you are only compiling a single source file, just omit the "-c" flag and the compiler will create an executable named "a.out" that you can run by typing "./a.out". You can specify "-o <executable name>" if you want to specify a name. Once you get more than a handful of source files, using the terminal starts to become a hassle. At that point, you definitely want to start using Xcode.
I'm not sure why you would try to compile "helloworlddot1.c" and then get an error message about "filename.c". Something else is wrong.
If you are working in the Terminal, it is easiest to use the "cd" command to move into the same directory as your source files. Then you don't have to keep typing the full path.
It is hard to say what the "best" community is. There are many to choose from.

There is error 'No such file or directory' during loading custom authentica

Hi,
I am working on OBIEE authentication using Hyperion shared services. I did the necessary changes in config file, like modifying config.xml to enable HSSauthenticator and enabling external authentication to instanceconfig.xml. However BI Server is unable to load the driver file for the Hyperion custom authenticator. Here is the error message.
There is error 'No such file or directory' during loading custom authentication module '/opt/local/usr/home/Oracle/OracleBI/web/bin64/libsawobisauthenticatorproxy643r.so'.
2011-06-26 21:04:05
[nQSError: 13011] Query for Initialization Block 'Hyperion EPM' has failed.
I have set the env variable LD_LIBRARY_PATH to this path but still I am getting the same error msg. I also have full previleges on this file. Would be really great if anyone can tell me why I am unable to load this driver file on to server. Thanks in advance

I think I figured out. Instead of giving path thru bin64 , I gave it thru bin folder, which is a 32bit file. I think they installled a 32bit OBIEE.

Fatal error: No such file or directory: Unable to open VLDC instance

Hi,
Been researching this one for a few days and seems no one has an answer that works. I've been through over 200 pages and couldn't find the answer.
Environment:
Server: Blade 6000 -- T6300 blade module
OS: Solaris 10 05/08
T6300 ALOM version:
System Firmware 6.3.6 Sun Blade[TM] T6300 2007/03/23 12:45
Host flash versions:
Hypervisor 1.3.3 2007/03/23 12:28
OBP 4.25.3 2007/03/02 20:24
Sun Blade T6300 Server Module POST 4.25.3 2007/03/02 20:53
LDOMs Manager: 1.0.3
The following entry shows up in my log file:
[ Sep 5 16:29:26 Method "start" exited with status 1 ]
[ Sep 5 16:29:26 Executing start method ("/opt/SUNWldm/bin/ldmd_start") ]
Added to channel ds, service dr-cpu, versions 1.0
Added to channel ds, service fma-cpu-service, versions 1.0
Added to channel fmactl, service fma-phys-cpu-service, versions 1.0
Added to channel ds, service fma-mem-service, versions 1.0
Added to channel fmactl, service fma-phys-mem-service, versions 1.0
Added to channel fmactl, service fma-pri-service, versions 1.0
Added to channel spds, service mdstore, versions 1.0
Added to channel ds, service md-update, versions 1.0
Added to channel ds, service domain-shutdown, versions 1.0
Added to channel ds, service domain-panic, versions 1.0
Added to channel spds, service pri, versions 1.0
Added to channel ds, service var-config, versions 1.0
fatal error: No such file or directory: Unable to open VLDC instance /devices/virtual-devices@100/channel-devices@200/virtual-channel@0:hvctl fo
contacting hypervisor
[ Sep 5 16:29:27 Method "start" exited with status 1 ]
Any help would be greatly appreciated!!!

Hi Every one,
I after installing Ldom , when I try to start ldom
I am getting same error ..any fix or any suggestion ?
./ldmd_start
Added to channel ds, service dr-cpu, versions 1.1 1.0
Added to channel ds, service dr-crypto-mau, versions 1.0
Added to channel ds, service dr-crypto-cwq, versions 1.0
Added to channel ds, service dr-vio, versions 1.0
Added to channel ds, service fma-cpu-service, versions 1.0
Added to channel fmactl, service fma-phys-cpu-service, versions 1.0
Added to channel ds, service fma-mem-service, versions 1.0
Added to channel fmactl, service fma-phys-mem-service, versions 1.0
Added to channel fmactl, service fma-pri-service, versions 1.0
Added to channel ds, service keystore, versions 1.0
Added to channel spds, service mdstore, versions 1.0
Added to channel ds, service md-update, versions 1.0
Added to channel ds, service domain-shutdown, versions 1.0
Added to channel ds, service domain-panic, versions 1.0
Added to channel spds, service pri, versions 1.0
Added to channel ds, service var-config, versions 1.0
fatal error: No such file or directory: Unable to open VLDC instance /devices/vi rtual-devices@100/channel-devices@200/virtual-channel@0:hvctl for contacting hyp ervisor

Clang: Error: No Such File or Directory

Hello Mac Communities,
I have recently installed Xcode 6.1.1, but currently just want to compile C files. I would like some help with a rather irritating error.
Here are the commands I try and their results.
command: gcc -c /Users/(my username)/Documents/C/helloworlddot1.c
result: error: no such file or directory: filename.c
or, after filename is changed to helloworld00.c;
command: ]gcc -c /Users/(my username)/Documents/c/helloworld00.c
result: (no text is displayed) The file helloworld00.o is created
That seemed to work for the moment, until I tried to compile/convert the machine code into a program:
command: gcc -c /Users/(my username)/Documents/c/helloworld00.o
result: clang: error: no input files
...which is weird.
Can anyone help with this?
P.S. Is this the best community to post this type of thing to?

You can work entirely in Xcode by using the command-line tool template in C. Xcode > File > New > Project > Command-Line Tool > Next > Language: C > Next > Create.
If you do want to work on the command line, you may as well just use the "clang" program instead. The "gcc" tool is just a compatibility tool for existing scripts that are expecting the actual "gcc" program. Apple hasn't used the real "gcc" for years. (Read up on the GPLv3 for more information.)
The gcc/clang arguments are the same. The "-c" flag instructs the compiler to only compile a single .c file into a .o object file. It won't create an executable. If you are only compiling a single source file, just omit the "-c" flag and the compiler will create an executable named "a.out" that you can run by typing "./a.out". You can specify "-o <executable name>" if you want to specify a name. Once you get more than a handful of source files, using the terminal starts to become a hassle. At that point, you definitely want to start using Xcode.
I'm not sure why you would try to compile "helloworlddot1.c" and then get an error message about "filename.c". Something else is wrong.
If you are working in the Terminal, it is easiest to use the "cd" command to move into the same directory as your source files. Then you don't have to keep typing the full path.
It is hard to say what the "best" community is. There are many to choose from.

Can't resize/repartition in Disk Utility: "No space left on device"

So I'm trying to get my Macbook (early 2008, base model) set up for triple-booting Leopard, Linux, and Windows XP. I've been using Boot Camp for about a month or so, and yesterday I used Boot Camp Assistant to remove the XP partition and make the Leopard partition 100% of the drive. Fine. After that, I was following this guide, and installed rEFIt to be able to choose from three operating systems on boot (as Apple's included bootloader only lets you choose Leo and Windows). Immediately after that (without restarting, maybe I should have) I tried to partition using diskutil from Terminal, with the following command:
*sudo diskutil resizeVolume disk0s2 60G "MS-DOS FAT32" "Linux" 30G "MS-DOS FAT32" "Windows" 21G*
After going through Verifying, Resizing Volume, Adjusting Partitions, it finally giving me an error: "*Resizing encountered error on disk disk0s2 Macintosh HD: No space left on device (28)*", even though my drive is 120GB (around 111.8GiB) and I entered 60 + 30 + 21 GiB = 111 GiB. As per the above guide, I then tried:
*sudo diskutil resizeVolume disk0s2 60G*
The above command should resize my main volume to 60GiB and leave empty space after. It also fails the same way. I then tried doing it using Disk Utility, but it gave me the same error. (Keep in mind that I am in Leopard during all this). I then attempt to restart, to see if maybe rEFIt changed something. I could not restart, due to my Mac not finding a boot drive (flashing folder with question mark). After a while of troubleshooting, I finally burned a rEFIt emergency CD and booted. I selected something like "Repair boot record" and restarted, which got rid of the flashing folder problem, but gave me "Cannot find operating system". I booted from the rEFIt CD again and selected "Boot from hard drive", which finally got me to boot Leopard. I went yet again into Terminal and tried a repairDisk, but I don't think that worked (since I was running off the internal drive). I booted from my Leopard CD and opened Disk Utility and tried: repairing the disk, repairing permissions, and partitioning. Repairing didn't find any errors, but partitioning gave me the same error as before, even though it is impossible to partition more than available in Disk Utility. I am currently sitting in Terminal, running off my Leopard CD, trying to figure out how to fix this. I have tried searching Google to no avail
Anyone have any idea on how to fix this? I could even do a reinstall if necessary, since I have a backup (good old Time Machine).
Summary:
Can boot from drive after booting rEFIt CD.
Can boot from Leopard CD.
Error when trying to partition.
Goal: make 3 partitions.
Thanks much!
Josh

Update:
If I choose my boot partition as the Startup Disk while booted from the Leopard DVD and let it restart, it boots successfully. If I try to restart after that, I get "Error loading operating system" again.

Partition failed with the error: No space left on device

I used Boot Camp Assistant (for instaling Windows XP) and there was Partition error:
+*The disc cannot be partioned because some files cannot be moved.*+
+Back up the disk and use Disk Utility to format it as a single Mac OS Extended (journaled) volume. Restore your information to the disk and try using Boot Camp Assistand again.+
so I tried Yasu, verified permission, verified disk, and everything was ok, but in Disk Utility I was trying to split or change size of my disk but there is one error again:
+*Partition failed.*+
+Partition failed with the error: No space left on device+
but I have 64GB free space!
how must I "+Restore your information to the disk+" or what else can I do?
thanks!

arajs wrote:
I used Boot Camp Assistant (for instaling Windows XP) and there was Partition error:
+*The disc cannot be partioned because some files cannot be moved.*+
+Back up the disk and use Disk Utility to format it as a single Mac OS Extended (journaled) volume. Restore your information to the disk and try using Boot Camp Assistand again.+
so I tried Yasu, verified permission, verified disk, and everything was ok, but in Disk Utility I was trying to split or change size of my disk but there is one error again:
+*Partition failed.*+
+Partition failed with the error: No space left on device+
but I have 64GB free space!
how must I "+Restore your information to the disk+" or what else can I do?
thanks!
This is a standard error message.
If you would have checked into the bootcamp forum you would have instantly found the solution.
http://discussions.apple.com/forum.jspa?forumID=1244&start=0
All that error message means is that you do not have enough conguous disk space available. No big deal at all for an older system. You have bits of files strewn over the "free space."
The solution as you would find in the bootcamp forum is to clone your HD, using a file-file clone, then test the clone to be sure it is working and then to erase your HD and clone back.
Works every time.
Message was edited by: Theodore

Internal error during pvc call: No space left on device (errno:28)

Hi
When we am exproting the objects ( using File System) we are getting the following error
Internal error during pvc call: No space left on device (errno:28) For more information, see the server log.
Please help us how to resolve this problem
Thanks & Regards
Sowmya

Hi
Check with the export directory file system. Looks like space issue for the .tpz you are trying to export.
Thanks
Gaurav

Error while taking a backup, BR0253E errno 28: NO space left on device

Dear Experts,
Since 2 days we are facing a problem with the online backup that is fired from DB13, the following is the error message that we are getting,
BR0051I BRBACKUP 7.00 (18)
BR0055I Start of database backup: bdxultsi.ant 2008-04-28 12:15:52
BR0252E Function fflush() failed for '/oracle/PRD/sapbackup/bdxultsi.ant' at location main-9
BR0253E errno28: No space left on device
BR0121E Processing of log file /oracle/PRD/sapbackup/bdxultsi.ant failed
BR0561I End of database backup : bdxultsi.ant 2008-04-28 12:15:52
BR0280I BRBACKUP time stamp: 2008-04-28 12:15:53
BR0054I BRBACKUP terminated with errors
External program terminated with exit code 3
We have checked with 2 different tapes, its the same problem still.
I understand that the problem is in initilization of the tape.
Please help me with this.. as we are not having a good backup since 3 days and its on the PRD server.
Reward points assured
Regards
Hunky

Hi,
First off all run CleanupLogs in DB13, if it is not working then check core files in /oracle/<SID>/saptrace/background/. If they are present move one of them to the other place, then again run CleanupLogs, after move back the core file, and again start CleanupLogs. Also check available space in sapbackup folder. After you can take your backup.
Regards,
Zeynal Aliyev
Edited by: Zeyn Ali on Oct 22, 2009 10:53 AM

Disk Utility errors: No such file -or- No space left on device (50GB+ free)

Similar Messages

Maybe you are looking for