[SOLVED] Truecrypt mounts vfat volume as read only

Hey there...
After the recent upgrade to linux 3.0.6-2 truecrypt mounts VFAT volumes as read-only. The file that I usually mount is in a USB which is formated as NTFS (I can copy and delete files from the USB). I think is a problem with the vfat filesystem but I'm not sure.
Any help?
Best
Last edited by mmf1902 (2011-10-11 03:17:31)

I apologize because of this post... The problem was in the file (something was wrong with the container)... so the solution was to do a new volume and copy all the files to the new file.
Best,

Similar Messages

I have an iMac(mid2010) running Pages v5.5.1 on OS X 10.10. Why can I not save or share documents. The error message is You can't save the file "TEST.pages" because the volume is read only.

I have an iMac(mid2010) running Pages v5.5.1 on OS X 10.10. Why can I not save or share documents. The error message is You can’t save the file “TEST.pages” because the volume is read only.
I get the same message when using Numbers so I presume it is a OS problem

Some of your user files (not system files) have incorrect permissions or are locked. This procedure will unlock those files and reset their ownership, permissions, and access controls to the default. If you've intentionally set special values for those attributes, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it, but you do need to follow the instructions below.
Back up all data before proceeding.
Step 1
If you have more than one user, and the one in question is not an administrator, then go to Step 2.
Enter the following command in the Terminal window in the same way as before (triple-click, copy, and paste):
sudo find ~ $TMPDIR.. -exec chflags -h nouchg,nouappnd,noschg,nosappnd {} + -exec chown -h $UID {} + -exec chmod +rw {} + -exec chmod -h -N {} + -type d -exec chmod -h +x {} + 2>&-
You'll be prompted for your login password, which won't be displayed when you type it. Type carefully and then press return. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command may take several minutes to run, depending on how many files you have. Wait for a new line ending in a dollar sign ($) to appear, then quit Terminal.
Step 2 (optional)
Take this step only if you have trouble with Step 1, if you prefer not to take it, or if it doesn't solve the problem.
Start up in Recovery mode. When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open. In that window, type this:
res
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window will open. You’re not going to reset a password.
Select your startup volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button
Select
 ▹ Restart
from the menu bar.

What to do about Backup failed with error: The target volume is read-only

This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again. Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.

Pondini wrote:
odysseus wrote:
This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again.
Try repairing the sparse bundle, per #A5 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
I've tried this before, but it can't be repaired, because it can't be mounted.
Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
One possibility is, the HD in the Time Capsule is beginning to fail (all HDs fail, sooner or later).
I'm backing up to my own sparseimage bundle just fine.
Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.
Those two things may be related. Whatever's going wrong may very well be what's corrupting the backups.
I'd recommend finding out what's wrong with the Powerbook. It's impossible to tell, of course, but that may be the root of the problem.
There's a problem with PowerBooks and Cinema Displays. I've posted a lot about this. Even after a motherboard replacement, my PowerBook G4/1.67 GHz had freezes, and eventually Apple gave me a MacBook Pro, but I think there's a failure involving hardware/software design.
If you haven't yet, I'd start by dong a +*Verify Disk+* on it's internal HD (also per #A5);
That checks out fine.
if there are no errors, or they're fixed and the problem continues, run the +Apple Hardware Test+ from the disc that came with the Mac. (One of the discs should have that, and instructions for running it, printed in tiny type on the label).
If still no help, I'd be inclined to do an +Archive & Install, preserving users & settings,+ of Leopard, then download & install the appropriate "combo" update. That's a combination (thus the clever name) of all the updates to Leopard since it was first released, so installing it should fix anything that's gone wrong since then, such as with one of the normal "point" updates. Info and download available at: http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate (change the last "8" to the desired number). Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.

[SOLVED]pacman -Sf zim makes arch read-only filesystem

Hi,
Last night I was trying to install zim, it looks like there were a couple packages which weren't properly installed before. I googled the error I received and found somewhere on the forum the tip to use
pacman -Sf package
I ran the command and it installed some sort of new kernel, fstab, something with python, and zim of course. While it was installing the packages I noticed it moved a couple files around and I'm not quite sure what it all did. anyway when I booted arch this morning it didn't quite make it to gdm, so I quickly booted into ubuntu, mounted my arch partition changed the inittab to boot to init 3. I then noticed that it mounted the arch / as read-only, I looked around a bit seems like my /etc/fstab was moved to /etc/fstab.pacorig. Now before I start playing around and maybe break things more than they are, anyone have a tip about how to figure out everything that was changed?
I also noticed that I could login as root without having to use a password which I don't like at all, which is a little scary.
Last edited by whitethorn (2010-06-26 13:50:11)

First things first; using the -f/--force flag with pacman is the absolute last resort, when everything else fails, and when you know exactly what you're doing. Using it just because you found a tip on the forum, and clearly without thinking about the potential consequences, is just asking for trouble - and you've got it.
To fix: your pacman log will tall you what packages were installed, and also has a record of any install-time messages. Comb through that, and work out how to revert the major issues.
[edit] overlap with loafer - he was faster because he used fewer words.

Time Machine backup fails w/error: Backup Volume is Read Only

This is another Leopard Bug! My Time Machine has always "just worked," but tonight, backup failed. Looking at the error message, it says, "Backup Volume is Read Only." My Time Machine was set up correctly, and has been working fine for quite some time. Now what?

Update: The next scheduled backup succeeded. I didn't change anything. Doesn't exactly give you that feeling of confidence in your equipment. The whole point of Time Machine is it is supposed to work in the background. If I have to think about it, and check up on it, it is useless, and I may as well return to my old manual backup methods.

The back up volume is read only?

Can anyone help me with this? When time machine tries to run a back-up I get two errors and it fails. The first says:
Time Machine Error
The back up volume is read only.
The second one says:
Disk Repair
The disk was not repairable by this computer. It is being made available to you with limited functionality. You must back up your data and reformat the disk as soon as possible.

AndyPrior wrote:
The back up volume is read only.
see C6 in [this_|http://web.me.com/pondini/TimeMachine/Troubleshooting.html] user guide.
JGG

Error Backup volume is read only

Time machine is giving me an error message of backup volume is read only.
I am using a time capsule for the backup disk
How do I change from read only to read and write?

I erased my TC and started over. It seemed to work fine until I tried to see my backups, it crashed. I've switched to Déjà Vu: http://propagandaprod.com/
I've been using this back up software for years with out ever having problems, I switched to Time Machine because I liked the fact that you could replace one pictures from iPhoto or one Address instead of the hole library. But I can't risk my work, I was never a fan of using Disk Images as backup, they get corrupted to often. Déjà Vu Works perfect with TC so I'm going back to Old Reliable. Plus it doesn't hog up your Hard Drive space. It could Mirror your files, it has a safety net option where you could pick how many days to save, and it only backs up once a Day, Week or month. Which is better than every hour.

HT3275 Any other suggestions for the message the backup volume is read only

I keep getting the message Time machine is unable to complete the backup because it appears the backup volume is read only. I've tried the suggested repairs from apple for this but keep getting the same problem. Any suggestions?

The Master of the Time Machine, Pondini has extensive documentation and he mentions your particular problem in the following link.
http://pondini.org/TM/C6.html

Time Machine reported 'volume is read only' & rolled back to old state

I've been in love with Time Machine ever since Leopard arrived. This has all come crashing down over the last few days...
Firstly I got a new 1tb drive, so I mirrored my old TM drive (using SuperDuper), and all seemed to be fine – backups were chugging along for a week or so as normal on the new, bigger drive.
A few days ago I got a time machine error stating that "The backup volume is read only". I thought this was strange as the drive was working without issue for a week. I checked permissions, format, etc and all were set correctly. I restarted and Time Machine kicked back in and all seemed to work fine other the fact that there seemed to be no backups created for 6 hours before I got the error message. Then I made a scary realisation, somehow the files on my computer had been restored to a state from 6 hours prior, all the work I'd done for the morning was gone.
I put this down to a one off glitch (stupid, stupid, stupid). I've today got the same "backup volume is read only" message again, and this time around my files have been restored to a state from 3 days ago. Fortunately this time around Time Machine has a backup of the important stuff a few hours ago.
I am now very worried about using the same disk with Time Machine. I also have no idea if Time Machine is the culprit (but logic tells me with the rolling back of files it must be). What should I do? How can I figure out what is going on?

This may fix the "read only" problem:
What to do if Time Machine reports you don't have permission
This was posted in the Apple Discussions by V.K. I have only modified it slightly to be more generic.
The problem seems to be that 10.5.6 changes permissions on a file so that even the root user doesn't have write peivileges. I have no idea why they did this. The workaround suggested in [an]other post will probably work, too, but i did something less drastic. Instead of deleting the file I changed permissions on it, and it worked just fine. An added benefit is that the permission change seems to stick, so you don't have to delete the file every time you change a drive.
[Open the Terminal application in your Utilities folder. At the prompt [enter] the following command:
sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx
The name of the file .xxxxxxxxxxxx is based on the MAC address of your computer and will be different for every computer. Put the name of the TM drive in the above and keep the quotes.
You'll have to enter your admin password (which you won't see) which is normal.
This was edited by Kappy just for cleanup.
Enable Finder to Show Invisible Files and Folders
Open the Terminal application in your Utilities folder. At the prompt enter or paste the following command line then press RETURN.
defaults write com.apple.finder AppleShowAllFiles TRUE
To turn off the display of invisible files and folders enter or paste the following command line and press RETURN.
defaults write com.apple.finder AppleShowAllFiles FALSE
Alternatively you can use one of the numerous third-party utilities such as TinkerTool or ShowHideInvisibleFiles - VersionTracker or MacUpdate.

"Time Machine Error The backup volume is read only"

Lately, every time I try to backup to my Time Capsule using Time Machine it fails and I get a message saying "Time Machine Error The backup volume is read only. To select a different volume, open system preferences and choose Time Machine" So I do that and I see the Time capsule listed. I don't want to select anything but the Time Capsule, cuz what else do I have, right? Am I wrong in assuming the "backup volume" is the Time Capsule? Anyway, I have tried changing the permissions on the time capsule, but when I get the "get info" box for the time capsule, there is not an option to change those settings, they are grayed out. Every thing worked well for about a week and then this started. My backup volume must have been "Read & Write" at first, because I can see what was backed up when I open Time Machine. Anybody have a clue what's going on? How can I make the back up volume "Read & Write" again and why did it change to "Read Only?"

Nope, I am using the same passwords as ever, both users have the same password, BTW. The password I gave to the Time Capsule is different, tho, but that password is for the wireless aspect of the Time Capsule, so that wouldn't have anything to do with it, would it?
I also get a message box that says "Disk Repair The disk "Backup of XXX's Computer" was not repairable by this computer, it is being made available to you with limited functionality. You must back up your data and reformat the disk as soon as possible." This box appears in conjunction with the appearance of the Norton's virus scan box scanning the time capsule.

Main Volume blocked (read-only permissions)

Hey,
I have blocked my main volume for mistake, and now i can't unblock it.... could you please help me?
My current permissions on volume:
lrwxr-xr-x l root admin 1 Oct 12 21:05 /volumes/Mac --> /
I was trying to unblock it on my own:
sudo chflags 0 /volumes/*
sudo chmod a+rx /volumes/*
chmod: Unable to change file mode on /volumes/Mac : Read-only file system
chmod go= /volumes/*
chmod: Unable to change file mode on /volumes/Mac : Read-only file system
chmod go-w,a+x /volumes/*
chmod: Unable to change file mode on /volumes/Mac : Read-only file system
Thx in advance
- mstolarz

Ok I've just worked out that 'You can only read' is referring to the fact that I can only view permissions but not add any. Below this statement, no permissions are listed which may explain why I cannot access the files but does not explain why I can copy/access some files, also with no permissions...

Kinit mounts root filesystem as read only [HELP][solved]

hello
I've being messing around with my mkinitcpio trying to optimize my boot speed, i removed some of the hooks at the beginning i couldn't boot, but then now i can boot but the root filesystem mounts as read only, i tried everything my fstab looks fine, / exists with defaults i tried to mount it referencing by it's uuid or by it's name and i get the same results, it mounts the filesystem as root only all the time no mather what i do.
There is not logs since i started playing with mkinitcpio, or anything i searched everywhere in this forum and around the internet, and i can't find any solution that would work, i restored all the hooks and modules on mkinitcpio and the result it's still the same. i also changed the menu.lst in grub to vga=773 but that's about it.
Can anyone help with this please i can't seem to boot properly.
Regards
Last edited by ricardoduarte (2008-09-14 16:16:25)

Hello
Basically what happens it's that it loads all the uDev events then the loopback, it mounts the root read only, then when it checks filesystems it says
/dev/sda4: clean, 205184/481440 files, 1139604/1920356 blocks [fail]
************FILESYSTEM CHECK FAILED****************
* Please repair manually and reboot. Note that the root *
* file system is currently mounted read-only. To remount *
* it read-write: mount -n -o remount,rw / *
* When you exit the maintenance shell the will *
* reboot automatically. *
Now what bugs me its that i can do that mount -n -o remount,rw / with no problems and when i do
e2fsck -f /dev/sda4
it doesn't return any errors just says that 0.9 non continuous.
none of this makes sense to me!! thats why i though that the problem could be coming from mkinitcpio or something
any ideas
Thanks for your help, btw thanks for the quick reply
Regards
Last edited by ricardoduarte (2008-09-14 15:48:49)

How could I create, force mount, and burn a read-only cross-platform .iso image?

Hello,
I am new to this group.
I want to perform the following steps as quickly as possible.
1. Create a cross-platform .iso
2. Mount the cross-platform .iso as read-only
3. Unmount the cross-platform .iso
4. Finally, burn the cross-platform read-only .iso to CD-R media
I need someone to give me an example and step-by-step instructions by using the hdiutil command in Mac Terminal.
Thanks in advance for your responses.
John P.

1. Create a cross-platform .iso
hdiutil makehybrd -o image-file source-directory -iso -iso-volume-name volume-name
2. Mount the cross-platform .iso as read-only
hdiutil attach image-file
3. Unmount the cross-platform .iso
hdiutil detach /Volumes/volume-name
4. Finally, burn the cross-platform read-only .iso to CD-R media
hdiutil burn image-file
For more information, see the man page for hdiutil(1).

Can't copy files from NTFS volume with Read Only permissions?

I am trying to copy files from an NTFS volume used previously for Windows onto another volume which is Mac OS X Extended...
However, certain files fail to copy due to the fact that I 'don't have permission to access some of the items'...
So I found the items which are causing the issue and viewed the permissions for them which display as 'You can only read'... I presume I am correct taking these as read-only permissions which (to my knowledge) should allow the files/folders to be copied accross to a new volume assuming that the existing volume is left without any changes attempted.
So can anyone suggest to me why this is? And how I might rectify the issue?
Thanks in advance

Ok I've just worked out that 'You can only read' is referring to the fact that I can only view permissions but not add any. Below this statement, no permissions are listed which may explain why I cannot access the files but does not explain why I can copy/access some files, also with no permissions...

10.5.5 sets external volume to read-only

Bizarre.
I have 4 external volumes (2 FW800, 2 USB 2.0) and one of the volumes suddenly shifted to read-only status after updating to 10.5.5 this afternoon. At least, that's the error message I get when I try to touch a file anywhere on the volume.
Problem started when I tried to open iTunes and got the error message "The folder 'Music' is on a locked disk or you do not have write permissions for this folder." Get Info indicates that this user account does, in fact, have Read & Write permissions. Group and Other permissions are set to Read Only. Get Info does not allow me to select the lock to make changes, however, but nor is the "Locked" checkbox selected.
In Terminal, permissions for Volume "Little Brother" are indicated as:
drwxrwxr-x 11 <adminuser> staff 442 Aug 13 13:11 Little Brother
The Music folder in question appears to have the appropriate permissions as well:
drwxr-xr-x 14 <adminuser> staff 476 Sep 18 11:17 Music
Aside from the 10.5.5 update there have been no changes to the filesystem, and no files written to this drive.
I can touch files on each volume except for "Little Brother". Aside from chmodding the **** thing, does anyone have any recommendations for what I can do?
Thanks.

I think Ill just keep responding to this, every time Apple issues an update (patch) that causes the problem to resurface. I have contacted tech support. And they tell me they no nothing about this and have never heard about it. Then I tell them to check my support records. The issue is well documented there and goes back for many, many months.
So, today I came home to find that apparently my software update utility (which is set to NOT update the software) has updated my software. My brand new Western Digital external 2TB disk is off line and my Time Machine drive (1.5TB Maxtor) now appears to be completely after being kicked from the USB ever friggin time there is a software patch.
I'm trying one last time to recover following the procedure above - but once again I am running the procedure above against my 2TB user disk - so hopefully in 8 or 12 hours Ill know something. Thanks again to all the Windows developers who are now obviously working at Apple.

[SOLVED] Truecrypt mounts vfat volume as read only

Similar Messages

Maybe you are looking for