HD is not writable

Greetings.
I have a brand new Mac mini server: 10.7.4 with 8 gb RAM. Initial setup is complete and it's on the network and accessible through the usual means.
I'm trying to get file serving working properly. I only need local users to be able to share files; this is for a small team within a larger organization. Local users can mount the drive but it's not writable. In Finder, the window says 0 bytes available and all writes fail.
In my efforts to resolve the problem, suddenly the HD itself has become unwritable. Apps (Server, TextEdit, etc.) on the server won't open. The logs are replete with "cannot write file...", "cannot write log file..." etc. I'd been using the Server app from ScreenSharing to manipulate the users when this happened. Now, Server won't open and nothing seems to be operating normally.
I'd appreciate any insights the community can offer.
Jamey

If the BootCamp partition remains as a FAT32 partition, while in Mac OS X, simply rename the hard drive. If the partition is NTFS, you will have to rename the partition while in windows.
In windows, go to the properties of the hard drive and enter in a name.

Similar Messages

  • Image Capture and Preview "folder not writable" error importing to shared folder

    I'm running 10.8.5 on a Late 2012 model Mac Mini. I'm trying to create a folder under my home directory where my wife can import pictures using Image Capture or Preview while logged into her account. I've tried setting permissions on the folder by setting POSIX permissions and ACLs from the command line, and also by setting ACLs using Get Info in Finder, but it seems as though both Image Capture and Preview ignore the ACLs and instead rely solely on the POSIX permissions for everyone/other (even when a relevant group is set). Unless the POSIX permissions for everyone/other are "rwx" Image Capture and Preview both give an error that the import failed, and /var/log/system.log shows errors that the "folder is not writable". I'd like to be able to set this up without making the folder and the files in it writable by everyone. My understanding was that ACLs should take precedence over POSIX permissions, but even the POSIX permissions don't seem to be getting handled properly, because the group is ignored. Any help or explanation of what's happening would be appreciated.
    Here's an example with details:
    Suppose we have the users alice and bob. We want to set permissions on the directory /Users/bob/importdir such that Alice can import files from a camera there using Image Capture (or Preview, either would do), but don't want to relax the permissions more than necessary.
    We create a group named bob_and_alice
    We set the following permissions on /Users/bob:
    POSIX: rwxr-xr-x, owner=bob, group=staff (i.e. default POSIX permissions)
    ACLs:
    0: group:everyone deny delete
    1: group:bob_and_alice allow list,search,readattr,readextattr,readsecurity
    2: user:alice allow list,search,readattr,readextattr,readsecurity
    "Get Info" shows "Read & Write" for bob and "Read Only" for alice, bob_and_alice, staff, and everyone
    We set the following permissions on /Users/bob/importdir:
    POSIX: rwxrwxr-x owner=bob, group=bob_and_alice
    ACLS: (these are already probably more permissive than should be necessary)
    0: group:bob_and_alice allow list,add_file,search,delete,add_subdirectory,delete_child,readattr,writeattr,re adextattr,writeextattr,readsecurity,writesecurity,file_inherit,directory_inherit
    1: user:alice allow list,add_file,search,delete,add_subdirectory,delete_child,readattr,writeattr,re adextattr,writeextattr,readsecurity,writesecurity,file_inherit,directory_inherit
    "Get Info" shows "Custom" for both alice and bob_and_alice, "Read & Write" for bob, and "Read Only" for everyone
    Alice opens a Terminal and cd's to /Users/bob/importdir. Alice can create and delete files in this directory.
    Now Alice opens Image Capture and with our camera connected we try to import a photo to /Users/bob/importdir. Image Capture shows an error dialog with the text "Import error. An error occurred while importing. The item 'foo.jpg' was not imported." /var/log/system.log shows the message: "Jul 20 22:12:34 computer_name.local Image Capture[32804]: Document destination folder is not writable" If instead Alice uses Preview it shows an error dialog with the text "The selected folder is not writable" and /var/log/system.log shows two error messages:
    Jul 20 22:23:45 computer_name.local Preview[33280]: Document destination folder is not writable
    Jul 20 22:23:45 computer_name.local Preview[33280]: Encountered error during image import: Error Domain=com.apple.ImageCaptureCore Code=-9934 "The selected folder is not writable" UserInfo=0x7ffda4881f00 {NSLocalizedDescription=The selected folder is not writable}
    Now we change the POSIX permissions on /Users/bob/importdir to: rwxrwxrwx
    The import succeeds with both Image Capture and Preview
    Can anyone explain what's going on here? Is there another reasonable way to do this without, moving this shared directory to /Users/shared?

    Did you figure out how to fix this?

  • I'm not able to open a catalog. It says it is not writable and cannot be opened.

    This has been happening to me for the past few weeks.  If I close my LR5 program and try to re-open the catalog I get a error message that says
    Lightroom cannot use the catalog named "Lightroom 5 Catalog 2014" because it is not writable and cannot be opened.
    This could be caused by incorrect permissions or because another Lightroom application is using the catalog. You may try to correct the problem or you may select a different catalog.
    Then I have the option to choose a different catalog / try again / Exit
    I have to go to the backup every time.  I am currently working in Windows 8.1
    Please help!

    Try the Firefox SafeMode to see how it works there. <br />
    ''A troubleshooting mode, which disables most Add-ons.'' <br />
    ''(If you're not using it, switch to the Default Theme.)''
    * You can open the Firefox 4.0+ SafeMode by holding the '''Shft''' key when you use the Firefox desktop or Start menu shortcut.
    * Or use the Help menu item, click on '''Restart with Add-ons Disabled...''' while Firefox is running. <br />
    ''Don't select anything right now, just use "Continue in SafeMode."''
    ''To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before using the Firefox shortcut (without the Shft key) to open it again.''
    '''''If it is good in the Firefox SafeMode''''', your problem is probably caused by an extension, and you need to figure out which one. <br />
    http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes
    ''When you figure out what is causing that, please let us know. It might help other user's who have that problem.''

  • Why do i get the following message when i attempt to open my backup file for lightroom cc?  "Lightroom cannot use the catalog named "Lightroom Catalog" because it is not writable and cannot be opened".  This message just started coming  up after downloadi

    why do i get the following message when i attempt to open my backup file for lightroom cc?  "Lightroom cannot use the catalog named "Lightroom Catalog" because it is not writable and cannot be opened".  This message just started coming  up after downloading lightroom cc (previously using lightroom 5)...am i backing up properly or not???

    Open Pictures folder and move the files named lrcat-journal and lrcat.lock to Desktop.
    Make sure that , they are not inside Pictures folder any more and try to open backup from Lighrtroom and check..
    Any LRcat file with .lock extension , move it to Desktop.

  • How do I open an " not writable" catalogue?

    I just upgraded my processor and OS to Windows 7. I reinstalled Lightroom 3. When I try to open a catalogue, I get an error message that it cannot be opened because it is not writable.  Any suggestions?

    There are at least three reasons for that:
    a) You don't have write permission for the drive the catalog sits on. This is a feature in Win 7: for each drive you have to give yourself full permission. Right-click the drive in question, go >Properties >Security tab and highlight your log-on name. You should have check marks for "Full Control", "Modify", and "Write".
    If you don't, click on <Edit>, make sure that you name is highlighted and check the boxes "Full Control", etc.
    BTW you also have to do this for the drive your photos are on, i.e. for every drive that Lr uses (also think Lr cache).
    b) Lr requires enough free space on the hard drive where the catalog sits in order to be able to write to it. If there isn't enough free space left, you ge the message that the catalog is not writeable.
    c) Lock-file: When Lr is open there is a lrcat.lock file that sits right besides your catalog. It prevents that Lr is opened in two instances because that would create problems with the catalog. The lock file should NOT be present when Lr is closed, but sometimes it doesn't disappear for reasons unknown to me. With Lr closed check if you see a lock file (same name as your catalog but with ending "lrcat.lock"). If you do, send it to the Recycle Bin / Trash Can. Don't delete your catalog, the .lrcat file!

  • Content generation [Error: Unable to access the output directory. The directory is not writable, so

    Content generation
    [Error: Unable to access the output directory. The directory is not writable, so the folio cannot be saved.]
    This means?
    This is fun BTW. Two days and two different silly errors applying themselves arbitrarily. Yesterday was the network, today its this.

    heres the fix i used for on a Mac
    1. While in the Finder, select the menu command Finder > Preferences.
    2. In the General panel, ensure the option "Connected Servers" is selected under the heading "Show these items on the desktop:", then close the preferences dialog box.
    3. Choose the menu command Finder > Hide Others.
    4. Close all open Finder windows to ensure you can see all items on your desktop.
    5. If you locate what appears to be a mounted volume with the name "Users", Control + Click on its icon and choose the contextual menu command Eject "Users".
    6.  Add or update your article(s).
    7.  Cross fingers
    8. If doesn't work ask for a refund

  • FIle Not Writable?

    I transfered all my video to an external hard drive before I replaced my internal hard drive and upgraded to iLife & iMovie 08. When I try to import my old video from the external hard drive I get this message - "FIle Not Writable: An error occurred while loading the project. This project seems to be write protected and can't be opened".
    Why won't my new iMovie recognize or import my old video from the external drive?? Any help would be appreciated. Thank you!

    Did you "format" the new drive before moving the files onto it?
    Disk Utility can do that job.

  • Property not Writable on type exception

    I found another post about this problem but the reply was
    Sorry, I have solved the problem.
    I am using JBoss 4.2.1.GA, Facelets and jboss-seam-CVS.2007-09-17_01-34-40. I am trying to do this.
         <h:form>
              <h:panelGrid id="lpg_01" binding="#{conceptManager.letterPanelGrid}"/>
         </h:form>
    Here is the Java code that is in the conceptManager Bean.
         private HtmlPanelGrid letterPanelGrid;
         public HtmlPanelGrid getLetterPanelGrid()
              System.out.println("************ getLetterPanelGrid");
              FacesContext facesContext = FacesContext.getCurrentInstance();
              Application application = facesContext.getApplication();
    //          letterPanelGrid = new HtmlPanelGrid();
              letterPanelGrid = (HtmlPanelGrid)application.createComponent
                                            (HtmlPanelGrid.COMPONENT_TYPE);
              letterPanelGrid.setId("lpg_01");
              List<UIComponent> children = letterPanelGrid.getChildren();
              letterPanelGrid.setColumns(1);
              HtmlCommandLink link = new HtmlCommandLink();
    //          String s = new String("#{conceptManager.testMethod}");
              String s = new String("homePage");
              MethodExpression me = application.getExpressionFactory().
                        createMethodExpression(facesContext.getELContext(), s,
                        null, new Class<?>[0]);
              link.setActionExpression( me );
              link.setId("linkId");
              HtmlOutputText output = new HtmlOutputText();
              output.setValue(new String("ClickMe"));
              link.getChildren().add(output);
              children.add(link);
              return letterPanelGrid;
    When the page is initially displayed everything seems to work fine. I looked at the html in the browser and it looks correct. The problem occurs when I click on the command link. During the Restore View Phase JSF tries to perform the binding again but gives the following problem. I got lost trying to follow the Variable Resolver code, too much abstractness. I haven't given up looking at it but I think I need some help with this.
    exception
    javax.servlet.ServletException: /AZIndexT1.xhtml @26,61 binding="#{conceptManager.letterPanelGrid}": Property 'letterPanelGrid' not writable on type javax.faces.component.html.HtmlPanelGrid
         javax.faces.webapp.FacesServlet.service(FacesServlet.java:256)
         org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
         org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
         org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
         org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
         org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
         org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
         org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44)
         org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
         org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141)
         org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281)
         org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60)
         org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
         org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
         org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
         org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:150)
         org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44)
         org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
    root cause
    javax.el.PropertyNotFoundException: /AZIndexT1.xhtml @26,61 binding="#{conceptManager.letterPanelGrid}": Property 'letterPanelGrid' not writable on type javax.faces.component.html.HtmlPanelGrid
         com.sun.facelets.el.TagValueExpression.setValue(TagValueExpression.java:95)
         com.sun.faces.lifecycle.RestoreViewPhase.doPerComponentActions(RestoreViewPhase.java:244)
         com.sun.faces.lifecycle.RestoreViewPhase.doPerComponentActions(RestoreViewPhase.java:249)
         com.sun.faces.lifecycle.RestoreViewPhase.doPerComponentActions(RestoreViewPhase.java:249)
         com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:193)
         com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
         com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
         javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
         org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
         org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
         org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
         org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
         org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
         org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
         org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44)
         org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
         org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141)
         org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281)
         org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60)
         org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
         org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
         org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
         org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:150)
         org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44)

    public void setLetterPanelGrid( HtmlPanelGrid grid )
              System.out.println("******************** setLetterPanelGrid");
              letterPanelGrid = grid;
    I did have this setter but failed to show it with my example. Hopefully this is all I need for the setter.
    I still received the same error;

  • Oui Inventory dir does not exist or is not writable

    Hello there.
    So this is another problem when installing 9i on HP-UX 11.0.
    After entering the group the oui request to execute the /tmp/OrainstRoot.sh with root privileges.
    Finished the script without any errors as root
    the oui show an error
    The Oracle Universal Installer Inventory on this system does not exists or is not writable.
    - I checked that I really executed the script as root without any error
    - and the install user (oracle) is member of the install group (oinstall)
    So I checked every of the suggested problems without results.
    If you encountered the same problems somewhere...please let me know.
    Thanks
    Sigi

    I'm having exactly the same problem trying to install 10g on HPUX 11.23.
    The orainstRoot.sh script completed successfully but then I get the same error as you.
    Did you manage to resolve this issue? Sorry I'm no help to you,
    cheers,
    Scott

  • Premiere claims Media Cache directory was not found or is not writable.

    Premiere claims Media Cache directory was not found or is not writable. I then change the cache settings to an external drive then it crashes regardless of whether I open an existing file or create a new one. I've re-installed, deleted preferences etc. Often when it doesn't crash, it will say file was created in a newer version of Premiere Pro. Losing hair, please help?

    Okay! So, immediately after my last post, I solved the problem.
    I deleted the cache files in the default directory "C:\Users\"USERNAME"\AppData\Roaming\Adobe\Common"  then this stopped the crashing.
    There appears to have been updates via Creative Cloud so this must've caused dramas with the existing project files. So a fresh install + the deleting of the cache files, then the changed settings of Media cache locations seems to help.
    Thanks for those who tried to help!
    Cheers,
    Tom

  • Specified Folder is Not Writable

    Since installing the 1.1 upgrade I get an error when trying to export to my My Pictures folder. (Specified Folder is Not Writable). I've seen a comment on the web stating that 1.1 has a problem writing to folders with a custom icon. I haven't changed the icon. Any suggestions?

    Yes, and that works but I've always done it this way and suddenly it doesn't work. When exporting I browse to the My Pictures folder and then type in the name of the folder in the blank below the browse.
    It now won't let me browse to My Pictures. Makes no sense.

  • Can't open Lightroom 5.3 catalog. Get  ".. it is not writable and cannot be opened" message.

    Hi everyone,
    I'm having a problem opening a lightroom catalog. I get a message "Lightroom cannot use the catalog because it's not writable and can't be opened".
    The catalog and several thousand RAW files are stored on an external drive.
    Here are the steps which I believe caused the problem:
    1. Worked with the catalog on my PC laptop. Disconnected the drive without closing Lightroom first (big mistake).
    2. Plugged the external drive into desktop PC and did additional work. Closed Ligtroom (on desktop) and disconnected the drive.
    3. Plugged the drive back into the laptop while original catalog was still open (see #1 above). Clicked on an image at which point Lightroom crashed and closed by itself.
    The problem now is that the catalog no longer opens on either computer. Any attempt to open results in  "Lightroom cannot use the catalog because it's not writable and can't be opened" message. There are no lock or journal files that can be deleted, just the lrcat file and tons of folders with preview data.
    I'm hoping that it's not a lost cause and I can still recover the catalog. There are 2 days worth of work there.
    Thank you for any help/advice in advance!

    Ok. I found a solution. Since Ligthroom catalog is a SQLite database, you can use a database tool to fix it. Simply download SQLite from www.sqlite.org for your OS (Windows 7 in my case) and unzip to C:\SQLite for ease of use. Copy your corrupt catalog to C:\SQLite folder as well to keep things simple.
    Go to command prompt Start>Run, type 'cmd' and click Enter. This will open the command prompt where you will need to execute the following commands:
    1. cd sqlite
    2. echo .dump | sqlite3 yourcatalogfilename.lrcat > tempcatalog.sql
    3. sqlite3 -init  tempcatalog.sql  newcatalogfilename.lrcat
    After executing line 3, you may or may not see error messages. No worries, it simply truncated faulty database records which is what cause the catalog to crash.
    Now, copy the newcatalogfilename.lrcat back to your lightroom catalog folder and launch it. You should be able to get things back up and running to where you left of, or to the point where the original Lightroom catalog got corrupted in the first place.
    Hope this helps. It took me a few hours to find a solution, but it saved me at least 2 days of work. The original credit goes to the author of the following article http://www.simplyness.com/more-photography-tips/recover-corrupted-unrepairable-lightroom-3 -catalog-with-sqlite.html. It seemed to have worked for Lightroom 3 and still worked for Lightroom 5.3 in my case.

  • After a power outage, Lightroom won't open.  It says the catalog is not writable and will not open

    How do I get lightroom to open?  It says the catalog is not writable and will not open?

    No, Jim.  I did not know where the backups were!  I've been researching this online, on here, and asking everyone I knew that used lightroom if they had any idea how I could get lightroom to open again. I checked out "permissions" too. Finally, I went to the lightroom folder which was in my PICTURES library and double clicked on "Lightroom 5 Catalog.lrdata" and Lightroom opened up.  I hadn't backed up the images since the 24th so all of those that were edited since then went back to being unedited.  I had already exported them to another folder so I don't have to do anything to those anyway.  Is this lrdata the backup?  I had a couple of people tell me to go to Lightroom and do this and do that, but I couldn't open Lightroom up to do anything at all!  After getting Lightroom back, I got the 5.5 update and everything seems to be back to normal.  I appreciate your help  AND your kindness to someone that hasn't got a clue about computers or how this software works.

  • Catalog not writable

    I just returned from a six-week trip with lots of photos. Used my laptop with an external HD on which I had the trip catalog and files. When I connect the HD to the Desktop and open the trip catalog, I get the message that the catalog cannot be used because it is not writable and cannot be opened. Maybe because of incorrect pemissions or that catalog is being used by another application. Checked the permissions, seems OK, not being used by another application.
    Any suggestions
    Puzzled and frustrated.
    Stan

    Deleted lock file. Did not help.
    Thanks for the suggestion. After two long chats with Adobe, now I can open the catalog, and the folder, but it shows the files in grid (even with flag and tags) but no photo. Adobe suggests I create new catalog and copy the folders to the new catalog. Perhaps I should just move the external hd catalog and folders to my desktop. Any suggestions?

  • T:div throws Component property class is not writable

    I'm using the Tomahawk div-tag including the rendered attribute to check if the wrapped components should be rendered. An exception is thrown indicating the component property is not writable. In other words, I think it means there's no public set-method. However, there is. I'm also using the same rendered expression in t:inputText / t:outputText element/s where it does work.
    What's so specific with the t:div?
    Also I wonder why there's a set-method needed as I don't use it..
    please help,
    thanks,
    dave

    If it says 'component property class is not writable' maybe it is talking about the component property 'class'? not 'rendered'.

Maybe you are looking for