Hdiutil in Terminal.

Hi
I'm trying to create a USB stick with Ubuntu Netbook remix on.
I've found the instructions at https://help.ubuntu.com/community/Installation/FromUSBStick
Under the Mac section it says at point 2 to use hdiutil to convert the file. I've said that the file is at: /Users/Emma/Downloads/netbook.iso (which is what mdfind told me!).
However, it gives me an error:
hdiutil: convert: only a single input file can be specified
Any suggestions as to what I'm doing wrong??

Doh! Clearly something wrong, as i've just tried to re-do what I did to take a screenie of it ... and it's working fine.
Must have put some typo or other in & just been totally unable to see it - so just kept copying it. Whoops.

Similar Messages

.dmg backup file will not mount. Failure not an option.

Let me begin by saying that my lovely wife is, for good reason, currently not very happy with me. Allow me to explain...
I recently decided that it was time to upgrade her iBook G4 from Tiger (10.4.xx, not sure what it was exactly) to Leopard. Her system easily meets the requirements and she would benefit greatly from being able to use Time Machine as a backup solution.
I figured that the first step should be making sure that her existing data was properly backed up and could be selectively restored after the installation of Leopard was complete. I could have performed an Archive Installation of Leopard, but she had data files and folders all over the drive and I felt that a clean installation would be best. So anyway, I booted the system with the Leopard install disc and used Disk Utility to create a .dmg backup of the one and only partition on her hard drive. I used all of the default settings for the creation of this .dmg and saved it to my external USB hard drive which is formatted as a Mac OS Extended volume. Disk Utility gave me no errors at all and the image creation seemed to complete successfully.
With that first step complete, I shut the system down and disconnected the external drive (just to be safe ya know). I, once again, booted the system with the Leopard install disc and "Erase"d the hard drive, created a new Mac OS Extended (Journaled) partition and proceeded with the Leopard installation. Once the installation completed, I ran Software Updates until no more updates were available and I was all the way up to 10.5.5. So far, so good.
With Leopard now installed and fully updated, I connected my external hard drive to the system, transferred my .dmg file to the desktop and attempted to mount the volume so that I could begin copying my wife's data to her Home folder. However, when I double-clicked the .dmg I received an error stating that the image failed to mount and gave a reason of "no mountable file systems".
Now before I go any further, I want to stress that my wife's entire digital life is contained in this disk image. She owns her own business and all of the critical data associated with her business is in there. Financial data, several years of tax information, business contacts, many months worth of email... everything. So needless to say, when I saw that error from DiskImageMounter pop up, I immediately felt a little sick to my stomach. Before anybody asks, I have no idea why I didn't test the image file before erasing the hard drive. I should've, I know that, I don't want to talk about it.
I spent the next 4 - 5 hours desperately trying anything I could think of to get access to the data within this .dmg file. I made a copy of it right away so that I wouldn't inadvertently make the situation even worse. I then tried to use Disk Utility to Restore the image, but received an error stating that the image contained an "Unrecognized Filesystem". I get the same error when I try to either verify or repair the volume with Disk Utility. I tried to attach the image using hdiutil in Terminal but got the same "no mountable file systems" error that I got from DiskImageMounter. I have tried to mount the image with Toast and Mount Me! as well with the same results.
Here's the hdiutil imageinfo that I get from the dmg:
Format: UDRW
Backing Store Information:
Name: Macintosh HD.dmg
URL: file://localhost/Users/barkingshins/Desktop/Macintosh%20HD.dmg
Class Name: CBSDBackingStore
Format Description: raw read/write
Checksum Type: none
partitions:
appendable: false
partition-scheme: none
block-size: 512
burnable: false
partitions:
0:
partition-length: 53948417
partition-synthesized: true
partition-hint: unknown partition
partition-name: whole disk
partition-start: 0
Properties:
Partitioned: false
Software License Agreement: false
Compressed: no
Kernel Compatible: true
Encrypted: false
Checksummed: false
Checksum Value:
Size Information:
Total Bytes: 27621589504
Compressed Bytes: 27621589504
Total Non-Empty Bytes: 27621589504
Sector Count: 53948417
Total Empty Bytes: 0
Compressed Ratio: 1
Class Name: CRawDiskImage
Segments:
0: /Users/barkingshins/Desktop/Macintosh HD.dmg
Resize limits (per hdiutil resize -limits):
53948417 53948417 53948417
I'd be happy to provide any other information that anyone thinks might be useful. I'd also be willing to bring the image file to a professional data recovery center and would welcome any recommendations that you might have. As I state in the subject of this post, failure is not really an option and I owe it to my wife to do everything humanly possible to try and arrive at a favorable resolution to this situation.
The thing that's really prevented me from getting a proper nights sleep for the last two nights is the irony in blowing up her data while trying to get her set up with a decent data backup solution.
Thank you to anyone who is able to help.

Whatever you do do not throw out the disk image. Most likely this is a permissions/user account error involving how the disk image was made.
Try mounting it manually using the Terminal by typing the following into the application:
          hdiutil attach
Ensure there's a space after "attach" and then drag the disk image to the terminal window, which should complete the full path to the disk image. Then ensure there's a space after the disk image path and type "-mount" so the whole command looks something like this:
          hdiutil attach /path/to/file.dmg -mount
Then press enter and hope it attaches. If an error occurs, try the command again with "sudo" in front of it as such:
          sudo hdiutil attach /path/to/file.dmg -mount
Enter your password when prompted and hope that works.

Filevault: Disk space issue

Hello everybody,
I experience these problems using Filevault: I copied files from my iMac to my Macbook to import them into iPhoto. After finishing the import I deleted the pre-import folder and logged out to compact my Filevault. Interestingly the disk space previously claimed by the afore mentioned folder does not seem to be available after the next login. Finder shows 5.12 GB free disk space where about 25 GB had to be.
I used WhatSize to explore the hard disk and discovered my Filevault's sparsebundle to consume all the missing disk space. Although the folder is definitively deleted and the sparsebundle was several times compacted by logging out the disk space does not become available.
My next step was to examine my Filevault's sparsebundle (files) via hdiutil in Terminal after switching to another user's accout:
$ sudo hdiutil info
$ hdiutil imageinfo xyz.sparsebundle
This gave me a first impression of the diskimage settings used by Filevault.
$ hdiutil compact xyz.sparsebundle
I tried to compact the sparsebundle manually. Output:
0 bytes of 23.8 GB possible freed. (Translated from German output.)
As indicated in the hdiutil manpage compacting a sparsebundle makes hdiutil delete the files which are not used any more. Thus, there needs to be some (still used) information left in the 8 MB files that can obviously not be deleted.
So I finally tried to resize the sparsebundle via hdiutil without success. I tought that shinking the sparsebundle's size would force Filevault (or hdiutil in the background) to reorganize the image's content being afterward able to free the disk space via "compact":
$ hdiutil resize -size min xyz.sparsebundle
and
$ hdiutil resize -size 60g xyz.sparsebundle
respectively
did finish without errors but did not resolve the problem.
My next step will have to be to deactivate an re-activate Filevault after copying my files to an external hard disk. But I do want to circumvent this step.
Does anyone have other suggestions how to free the unused used disk space?
Thank you in advance!
Johannes

I find a solution by myself:
*Howto shrink Filevault encrypted home folder (sparsebundle)*
What you need before you start:
1) Filevaulted user account ( user )
2) Drive Genius application by Prosoft
3) A second admin user ( user2 )
4) Three hours (depending on the Filevault‘s size)
What you need to do:
1) Log in as another admin user
2) Open „Terminal“.
3) Navigate to the user‘s folder:
cd /Users/ user
4) Change filevaulted folder‘s and subfolder‘s permissions:
sudo chown -R user.sparsebundle user2
5) Rename sparsebundle file:
mv user.sparsebundle user.dmg
6) Open user.dmg with Drive Genius.
7) Defrag mounted image.
This will take a while depending on the actual size of the sparseimage.
8) Close application and unmount image via Finder or mark mounted folder and press „cmd + E“.
9) Rename image:
mv user.dmg user.sparsebundle
10)Change permissions:
chmod -R user.sparsebundle user
11)Log out current user ( user2 ).
12)Log in user and log out to compact the Filevault‘s sparseimage.
Feel free to comment!

Terminal command hdiutil convert. Where is output file?

Sorry all, I put this in the wrong forum... going to unix forum
I'm trying to use terminal to convert an ISO file to an IMG file. The conversion appears to run but I cannot find the output file.
The command I'm using is;
hdiutil convert -format UDRW -o /convert/newfile/output.img /convert/source.iso
I assume the output.img file should be in the /convert/newfile/ directory.
Message was edited by: Dean

closing this stream. Mistakenly had it in another forum

Terminal says 'unknownf81edfe49998' Huh?

I've been doing some research into defragging on a Mac. Mixed info about it. It seems that it depends on the kind of user you are.
Nice article here http://bit.ly/OSX_defrag with some interesting advice at bottom
+you can simply open the Terminal and type: ’sudo periodic daily weekly monthly’ followed by Return, enter your Administrator password, and OS X will take care of things for you. If your Mac is left on all the time, then the operating system will run these processes automatically in the early hours of the morning.+
Worth knowing.
However when I did it I got this message 'unknownf81edfe49998'
Searched on the net for it with no result. So is that good or bad???
And any thoughts on that article? Or has this subject been done to death here?
Cheers!

Os X does a good job of defragmenting its own System files (under 20MB), but it pretty much
leaves Large files, data files, user files and freespace to fend for itself.
Obviously a heavy photoshop, web developer, music and/or video editing user would make a mess
of large files and freespace and would need a defragmenting solution.
http://www.macattorney.com/ts.html#6
One of the simplest defragmenters comes with OS X: Time Machine. Restoring a Time Machine
backup will put everything right back where it is supposed to be. Usually takes less time than
doing a full defragmentation with with a defrag utility, especially if all System/Data files reside
on a single volume.
I own iDefrag and I love it. I seldom do full defrags with it though. I use the "single file" defrag
option a lot. Usually only a few files get badly defragmented, so I defrag the bad ones and ignore
the rest. On a regular basis, my Safari cache and my mail are the worst offenders. I set iDefrag
to simply delete the Safari cache and tmp files when I run it instead of defragging them.
Large user files many times fragment badly too.
When free space gets badly fragmented, I use the optimize setting in iDefrag, or if it is a
data drive I simply use the compact setting. Occasionally, I will defrag metadata.
On my Mac Pro, my data is kept on separate volumes on separate drives, this keeps
boot volume fragmentation minimal. My User account is on the boot drive and I often have large
video or other data files on my desktop, but I move them to another drive as soon as they are
completed. For convenience, some of my data folders are symlinked to data folders on other
volumes, such as mail, iTunes and work documents.
Keeping your volumes healthy using Disk Warrior and Disk Utility in conjunction with proper
and sensible defragmentation, will help keep performance optimal.
I never have a need to reinstall, nor would I gain anything by reinstalling as long as I am following
the above rules.
I use iDefrag on my data volumes more than my boot volume. One especially useful task is
defragmenting files on sparse bundle disk images with it. After I defrag (files only) on the
sparse bundle, I compact it with hdiutil. No wasted space.

Error when creating an image (dmg) using hdiutil

Hi everybody,
I´m using a script which creates an image (dmg) from a selected folder.
This works without errors.
But I also want to create images from CDs and DVDs using this script. Doing so I always get the error "Only one image can be created at a time"
I thought that a previous imaging process was not finished yet and I rebooted the Mac. But I still get this error. Any idea?
Here is the script:
set Ordner to choose folder
tell application "Finder"
set diskNames to name of Ordner
set myNewPath to POSIX path of (path to desktop folder) as string
set theListe to every process
end tell
set myNewPath to myNewPath & diskNames & ".dmg"
set Quellordner to POSIX path of Ordner as string
set Skript to "hdiutil create -srcfolder " & Quellordner & " " & myNewPath
do shell script Skript
iMac Core Duo/1,5 GB; MacBook Pro Core2Duo 2GB Mac OS X (10.4.4)

I believe this has something to do with terminal and have spaces in folder names / disk names. As it sees the space and thinks it is another command and in this case i believe it thinks you are trying to do two or more disk images at once. Therefore it is important to deal with spaces. Thankfully you should be ablr to get around this by using the quoted form command which i have implemented below.
I repeated your error using a folder called "Cd for Cherie". Folders without gaps such as "pH" worked fine.
I havent tested this with any disk but i believe if you alter it to this hopefully it will work
Also the name of the folder wasnt working for me so i altered to to work for me, i am using 10.4.8 so if it doesnt work for you then change it back.
--Start Code
tell application "Finder"
set infor to info for Ordner
set diskNames to name of infor
-- display dialog diskNames as string
--set diskNames to name of Ordner
set myNewPath to POSIX path of (path to desktop folder) as string
-- set theListe to every process
end tell
set myNewPath to quoted form of (myNewPath & diskNames & ".dmg")
set Quellordner to quoted form of POSIX path of Ordner as string
set Skript to "hdiutil create -srcfolder " & Quellordner & " " & myNewPath
do shell script Skript
--end code

I have Trouble with Terminal.

I have on my desktop a cdr file called Japanese 1-4.cdr.
I read online that I can use terminal to make an iso hybrid using this code.
cd ~/Desktop
hdiutil makehybrid -iso -joliet -o Japanese 1-4.iso Japanese 1-4.cdr
But whenever I put it into Terminal, it replies like this.
hdiutil: makehybrid: multiple sources specified
hdiutil: makehybrid failed - Invalid argument
What should I do?

Hi,
I'm not familiar with that command, but Terminal doesn't like spaces in filenames, and is probably treating the space after Japanese as a file separator rather than as part of the filename. So you could try enclosing both filenames in quotes:
hdiutil makehybrid -iso -joliet -o "Japanese 1-4.iso" "Japanese 1-4.cdr"
I think hyphens in filenames are tolerated in Terminal, but I've read that underscores are preferable. If feasible, you might alternatively first rename your desktop .cdr file to eliminate both spaces and hyphens, say to Japanese14.cdr, then try
hdiutil makehybrid -iso -joliet -o Japanese14.iso Japanese14.cdr

Resizing DMG with Terminal help needed

I've got a DMG file with read/write privileges that I need to increase the size of. I've done a bunch of searching, both here and on the net, and the best I can find is a Terminal script, something I know nothing about. Here's the script I found:
hdiutil resize -size 25g /PATH/TO/DISK/IMAGE.dmg
But before I toss this into terminal with the modifications to make it work for mine, I just wanted to make sure I was doing everything right.
First, the path. The actual path is /Prima/Users/Doug/Desktop/work.dmg, that's how I type it? I've also seen just ~/Desktop/work.dmg so I figured I'd double check that.
Also, 25g, I have no idea what that measurement is since I've seen gb and a few other ones when I tried to search the script a bit more. I want 2.6GB, what would I need for that?
Finally, I'm guessing the "hdiutil" is just telling it that this is going to be working on a volume but I wanted to make sure that I had that right.
Any help you guys can give me would be great! Or if you can tell me another non-Terminal way to do this that'd be even better!
15" MacBook Pro 2.33GHz, 2GB RAM, 160GB internal, glossy. Mac OS X (10.4.8) 1TB My Book Premium II and DVD±RW DL LaCie Burner

Nevermind.
hdiutil resize -size 2.6g ~/Desktop/my.dmg
That did it.

Disk image can mount from local terminal with "open" command but not via ssh

I have a disk image "backup_image.sparsebundle". If I go to the terminal on my machine and type "open backup_image.sparsebundle" the disk image mounts as expected. No problems. If I secure shell (ssh) log in from a remote Mac and execute the same "open backup_image.sparsebundle" a warning dialog pops up and states that "The following disk images couldn't be opened" followed by my disk name. This is incredibly odd because it used to work just fine. I didn't think there were any ACL differences between a local terminal shell and remote ssh. I mean a shell is a shell right? Or, it used to be and now it isn't? I'm not doing anything obviously incorrect (to me); I'm the same user locally and remotely, same path to disk image. This used to work fine before Mountain Lion.
Background: All of this started because I wrote a script that would ssh in to a remote machine, open the disk image on that remote machine, mount it across the network over afp and rsync. If I leave the disk image mounted on the remote machine, the script runs fine but if the image is close and I try to remotely open the image as I always did, it fails. The only thing that has changed in the system is, now, both machines are running Mountain Lion. Odd.
Suggestions?

Storing the password for the remote disk image in the local keychain of the computer running the script (in to a variable), then passing it accross to the remote machine worked. I'm not sure why all of this changed moving from Lion to Mountain Lion but I suppose it is slightly more secure.
To programatically mount and sync a remote encrypted disk:
#!/bin/bash
if [ -n "`mount | grep ~/sync`" ]; then
echo "Already mounted"
else
pw=$(security -v find-generic-password -w -D "application password")
ssh -o ConnectTimeout=1 [email protected] "echo $pw | hdiutil attach /Users/user/backup_image.sparsebundle"
mkdir ~/sync
mount_afp -s "afp://matdup01:[email protected]/Disk Image" ~/sync
fi
if [ $? -eq 0 ]; then
echo "Mount succeeded!"
else
echo "Mount Failed"
exit 0
fi
rsync -vrxtu --delete-before --exclude _* "/Volumes/Media/new Media/" ~/sync/new\ media/
umount ~/sync
rmdir ~/sync
exit

SSL connection works through terminal and Firefox only

I have issue with SSL connection.
It works through terminal and Firefox only. Everything else requiring SSL is down including App Store. I can't fix the problem by updating software, nor reinstalling as softwareupdate and hdiutil mount patch you via SSL at the end.
No apparent reason.... It all worked fine last night.
Does anyone know what is it and how to fix it?
Thanks.

MurphyCooper,
this might be worth a shot: boot your MacBook Pro into Recovery mode by holding down a Command key and the R key as it starts up. Once the Mac OS X Utilities menu appears, select Disk Utility. On the left-hand side of the Disk Utility window, select your internal disk’s boot partition (typically called “Macintosh HD”). On the right-hand side, press the Verify Disk button if it’s not greyed out; if it is greyed out, or if it reports that errors were found, press the Repair Disk button. Once the verification/repair is completed, exit Disk Utility and select Restart from the Apple menu to restart in normal mode. Has this made any difference?

Combining DMGs with 'hdiutil' after splitting

Hello all,
So I've split a DMG into two sections using the terminal command; 'hdiutil' so that I could put it onto my external hard drive. For some reason the hard drive won't let me transfer a file over 6GB without giving me "Error Code 0."
So now that I have CD.dmgpart and CD.dmg on my external drive, does 'hdiutil' have a function that is the opposite of segment?
I looked in the help and all I saw was 'compact' which didn't seem right...
Any suggestions?

Sed_P wrote:
So, I thought it was working but apparently my DMG is now not a mountable file system....
So 'cat' is a no go for dmg's I guess...
It may depend upon how you split the original. If there is data on one or both of them indicating that they were split, that would corrupt the final image.
I know from the old PC days that if I spanned a zip over several floppies, the floppies had special flags and data on them for the software to be able to reassemble them.
Here's what might work. I think split is the command to use to split a binary file that cat can restore.
split the original and then cat the pieces. If that works you are all set.
Message was edited by: nerowolfe
Message was edited by: Fritz

Resize partition using terminal - error:

I am trying to resize my osx partition so i can implement a triple boot. I have an 80gb drive in my macbook - osx uses 43.57GB out of 60GB and xp 20GB GB. I attempted to use this code in terminal:
diskutil resizeVolume disk0s2 56G "Linux" "Linux" 14G
then it says:
verifying
Resizing encountered error The underlying task reported failure on exit (-9972) on disk0s2 Macintosh HD
how should i attempt this? is my code correct?

i took a look, and i believe that the program behind diskutil is hdiutil.
please correct me if im wrong.
in the terminal i typed
man hdiutil
and found resize as a command there:
*resize size_spec image*
Given a read/write partitioned UDIF, if the last partition is
Apple_HFS, attempt to resize the partition to the end of the
image, or to the last used block in the embedded HFS/HFS+
filesystem (depending on size_spec). resize is often used when
a device image needs to be shrunken so that the HFS/HFS+ par-
tition can be converted to CD-R/DVD-R format and still be
burned. Note that gaps cannot be reclaimed as resize does not
move data. -fsargs can sometimes be used to minimize filesys-
tem-generated gaps. resize can also be used to grow a
filesystem and image without bound.
hdiutil burn does not burn Apple_Free partitions at the end of
the devices, so an image with a resized filesystem can be
burned to create a CD-R/DVD-R master that contains only the
actual data in the hosted filesystem (assuming minimal data
fragmentation).
Common options: -encryption, -stdinpass, -srcimagekey, -shadow
with friends, and -plist.
Size specifiers:
-size ??b|??k|??m|??g|??t??p|??e
-sectors sector_count | min | max
Specify the number of 512 byte sectors to
which the partition should be resized. If
this falls outside the min/max values, an
error will be returned and the partition will
not be resized. min automatically determines
the smallest size the partition can be
resized to and uses that value. max automat-
ically determines the largest size to which
the partition can be grown and then uses that
value.
Other options:
-imageonly only resize the image file, not the parti-
tion(s) inside of it. This is the default
for UDIF images (more partitions can then be
added in the new free space).
-partitiononly only resize the partition(s) in the image
(including their embedded filesystems). This
is the default for NDIF images. For a newly-
created SPUD where the partition fills the
image, the partition can only be shrunk. If
there is an Apple_Free partition after an
existing partition, that partition can be
expanded into the space marked by the
Apple_Free. Shrinking a partition results in
a larger Apple_Free partition.
-partitionNumber partitionNumber
specifies which partition to resize (UDIF
only -- see HISTORY below). partitionNumber
is 0-based, but, per hdiutil pmap, partition
0 is the partition map itself.
-growonly only allow the image to grow
-shrinkonly only allow the image to shrink
-nofinalgap allow resize to entirely eliminate the trail-
ing free partition. Such an image restored
to a hard drive will not boot OS 9 nor will
it allow OS X to boot on old-world (beige)
machines.
-limits Displays the minimum, current, and maximum
sizes (in 512 byte sectors) that could be
passed given possible -imageonly or
-partitiononly flags. Does not modify the
image.
-oldlimits behaves like -limits except that it reports
the stretch sizes that OS X version 10.3
would have reported (useful if an image needs
to be used with asr(8) on an older system).
segment
++++++++++++++++++++
I still dont know what exactly to enter but now i feel like this could actually work using terminal. any help is appreciated

Mounting a drive with hdiutil

when I try to mount a drive using hdiutil it keeps asking for my admin password.
Say I type
hdiutil mount /dev/disk2s2
in terminal, and I have to enter the password twice! Is this normal? can it be avoided?

Is disk2s2 a disk image?
What happens with diskutil mount /dev/disk2s2?
or, more simply:
diskutil mount disk2s2?

OSX Terminal problem

Dear friends I'm a new mac user, I lost my recovery HD and searched the web to get it back, i saw an advise to do on terminal which says:
Last login: Wed Nov 6 13:13:23 on ttys000
khattars-mbp:~ Khattar$ history
    1 diskutil list
    2 chmod +x /Users/Khattar/Desktop/recovery.sh
    3 sudo /Users/Khattar/Desktop/recovery.sh
    4 chmod +x ~/Downloads/recovery.sh
    5 sudo ~/Downloads/recovery.sh
    6 exit
    7 chmod +x ~/Downloads/recovery.sh
    8 sudo ~/Downloads/recovery.sh
But it didnt help. I downloaded the Mavericks from the app store and got back my recovery HD.
My question is how to undo this terminal command above in green or what to write in terminal to cancel it's action?
Thanks in advance

well after i pasted that command on terminal i got the file recovery.sh on my download folder. and this is it when open
read -p "Ensure "RecoveryHDUpdate.dmg" and "InstallESD.dmg" are in your Downloads folder and press [Enter]"
#access dmtest from RecoveryHDUpdate.pkg
rm -rf /private/tmp/RecoveryHDUpdate
echo "Expanding RecoveryHDUpdate.pkg"
hdiutil attach -nobrowse ~/Downloads/RecoveryHDUpdate.dmg
pkgutil --expand /Volumes/Mac\ OS\ X\ Lion\ Recovery\ HD\ Update/RecoveryHDUpdate.pkg /tmp/RecoveryHDUpdate
#access BaseSystem.dmg and BaseSystem.chunklist
echo "Expanding InstallESD.dmg"
hdiutil attach -nobrowse ~/Downloads/InstallESD.dmg
#build Recovery partition
echo "Building Recovery Partition. Please Wait"
/tmp/RecoveryHDUpdate/RecoveryHDUpdate.pkg/Scripts/Tools/dmtest ensureRecoveryPartition / /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg 0 0 /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist
#cleanup
echo "Cleaning up"
hdiutil eject /Volumes/Mac\ OS\ X\ Lion\ Recovery\ HD\ Update
hdiutil eject /Volumes/OS\ X\ Install\ ESD/
sudo touch /Library/Preferences/SystemConfiguration/com.apple.Boot.plist
sudo kextcache -f -u /
exit 0
If I delete it i get all this **** finish?
I mean all that terminal command led me to this file? And if I delete it then its done as if nothing happened?

Cannot delete file from external hard drive (error code 36) in Finder, but Terminal is ok

I have a relatively new Macbook Pro Retina 15" and have a Western Digital 1 TB Passport. I've been using the passport for about a year now without any problems on older Macbooks in my house. I used to be able to read and write to this drive no problem. I am using the Paragon NTFS for Mac software in order to read and write to the NTFS drive. When I navigate through the drive in Finder, if I try to create a new folder, I do not have a problem. If I try to delete that folder I just created, I get this error:
The Finder can’t complete the operation because some data in “untitled folder” can’t be read or written.
(Error code -36)
The folder has nothing in it whatsoever. I just created it. But if I go to Terminal and I run
rm -rf "untitled folder"
This works fine. Why is Terminal acting different than Finder? This does not happen on my other Macbooks. Thanks in advance.

Thanx for such qucik reply!!! The pages were great, it had an answer for my problem, but unfortunately it also involved me dealing with it only on the MacIntosh HD itself, not on mounted external drive I suppose... So it didn't work they say that there is an icon in the left corner indicating locked folder - I don't see any icon on it. It says you can untick the box to unlock the folder - there is no tick to be unticked. Finally, they say that if I don't have permition or rights I cannot delete it. But how do i change permittion which already says that i can read and write in it? So everything appears to be normal only I cannot delete it. there is not even any warnig telling me I don't have enough rights, it just requires the password and after me typing it in it makes the sound of scraping paper but does nothing more. I aslo had some problems with emptying Trash after being seemingly succesful with one file and had got so far to have them appear in the Trash (no clue how this one actully got there though..) I followd the advice and emptied the Trash with Terminal. The Folder is still there but it shows 0 Kb... So far so good BUT: It is still on the external drive, so I obviously only managed to copy it into the Trash!!! Phew, innit a bit too tight to poor owners, this macbook?? I want my rights back!

Hdiutil in Terminal.

Similar Messages

Maybe you are looking for