Extra Folder in my /Volumes folder

R

richie66

Registered
On the 23rd I started to build a usb boot drive for a OSX PC
When it came time to run the terminal commands I made a bad move.
I ran this command.
/bin/cp /Volumes/Tigger/Downloads/boot /Volumes/Mac OS X Install DV
without quotes. I know my bad no quotes

Now I have an issue where when I reboot there is a folder created in my volumes folder, /Tigger/Downloads The folder is named the same as my second partition. This pushes the mount point for my second partition to /Tigger 1. To get my applications to work again I have to delete the /Volumes/Tigger folder unmount the drive Tigger and then remount it.

Any one know how I can reverse the command? Or how I can repair?
 
I did not right get it, but if I understood right, you have a directory named /Volumes/Trigger and you need to remove it. Why not first rename it something else, in case some problems come. Use command "mv /Volumes/Trigger /oops" and then reboot. If the original Trigger comes without "1", it should be ok remove the /oops directory.
 
I have to delete the folder each time I restart. It would appear some how the link between the folder and the command run have created a link Hard or symbolic I can not find it.
The Reason behind this idea it that the folder name /Tigger/Downloads and the /Volume/Mac OS in the CP command fail because the volume Mac was not found so it fell back to the folder I was in when the command was run. I can not find anything called boot, the file that was to be copied, or Mac the volume that was not found. But each time I restart there is it. The folder is created by root and admin has rights.
I can find nothing in the console at the time of creation.
 
Unmount and disconnect your external hard drive. Then, head over to the Terminal, 'cd' to the /Volumes folder, and perform a 'sudo rm -rf [volumename]' where [volumename] is the name of the duplicated volume.

That will get rid of the duplicated volume name you created.

Remember to use quotes this time!
 
Thanks Guys for the Ideas! While this is not and external hard drive but a partition the issue has been resolved. It just so happened that at the same time I created the USB drive Net barrier updated. I have the log files from NB export everyday. I removed the folder that was being used to store the files. So after looking at the logs. I found NB was the root cause. the file was being created at boot and since the folder was no longer present it created it as part of the start up process.
 
You must log in or register to reply here.
Back
Top