RAID mounts read-only now

hi all,
After doing an in-place upgrade to 10.6, an attached RAID device, connected via an Apple Fibre Channel HBA, now mounts as read-only. It is a shared device using Server Admin.
The message specifically was: "Mac Os X can't repair the disk (disk name). YOu can still open or copy files on the disk, but you can't save changes to files on the disk. Back up the disk and reformat as soon as you can."
Backing up isn't really an option at this point, as this is a huge repository of video, and I have no other device that could hold all the data.
Any thoughts out there as to why this may have happened, and what I can do to get it back to normal?

If you have run Disk Utility and it kicked back an 'invalid sibling link' error you may have luck with the following link - http://www.macosxhints.com/article.php?story=20070204093925888.
By your description it sounds like this is your only copy, even if you can fix the original problem you may need to erase the drive to eliminate a possible corruption in the future. I recommend Data Rescue 3 if you are sunk and cannot repair the damaged drive structure. It's not a free application but it can easily pay for itself by recovering lost or damaged files. Although it can recover data from one partition to another (expert mode) you will need another drive of sufficient capacity for it to copy the rescued files to.
Another application that assists with data recovery is DiskWarrior. It can repair a damaged directory with the data in place, but I haven't used the software for some time to give you much of a detailed description. Both applications can be researched on the net, you will find people who have had good and bad experiences with both.

Similar Messages

"underlying task reported failure..." & "root device is mounted read-only"

My ibook is not starting up. It was having problems loading up and getting in interminable spinning ball fits as I tried to use the computer for basic things like surfing internet, word processing, itunes. I ran disk repair several times, and the problems would resume. Finally I left it on, afraid to turn it off, but my boyfriend unplugged it, and it eventually ran out of juice. Now I hear it power up, but it doesn't start up all the way (it's gotten to different points in start-up process after I took each step below, but never all the way).
What I've tried so far:
1. I've run disk repair from the start-up disk, and got the "The underlying task reported failure on exit" message.
2. I did the archive reinstall, did not work either. Tried disk repair again and still getting same message as #1.
3. Also tried starting up in single-user mode and running fsck, but getting message "root device is mounted read-only." Not sure what this means. Ran disk repair again after this, gets me same message as #1.
I'm hesitant to do a complete reinstall, as I have documents and music files that haven't been backed up. I have an external hard drive to move files if I could just start up my computer.
My questions:
1) Any thing else I can try short of complete reinstall to fix the problem?
2) Any way I can save my files if I can't get the computer fully loaded?
3) Would a 3rd-party disk repair program allow me to fix the problem without wiping out my files?
4) Why is fsck not running?
Any advice would be appreciated!

Hi, tgt. DiskWarrior would be a good bet to fix the "keys out of order" errror, if things haven't gotten much worse since you saw that message. You can order it direct from its developer, Alsoft, or you can call around to Mac dealers in your area to see if one carries it. If you already have a bootable external hard drive with OS X 10.3.9 or better installed on it, you can boot to the external drive, buy DW from Alsoft via download, install it on the external drive, and use it to therapize the internal drive. If you don't have an external drive with 10.3.9 or better installed, you'll need the DW CD to start up from.
To shut your computer down while it isn't working properly, just press and hold down the power button for a few seconds.

Why is SD Card mounted Read-only?

Hey all. I've had my HTC Incredible for about 6 months. Recently upon starting it up I get the message something like "There is a problem with your SD Card, it has been mounted Read-only". I have taken it out and tried to reseat it with no change. Any idea? Thanks.

I have had the HTC thunderbolts for about a month now and I got this problem today. I was on the phone with tech support for a while and was not able to fix it (due to I do not want to loose my pictures on my sd card) so I have to go into a store tomrw and see a tech person...idk what happen, but my phone did this on its own mid day.

Sanyo Phone always mounts read-only

I recently purchased a Sanyo M1 phone that has a USB mass storage mode.
The phone has 1GB of internal memory that is formatted with FAT16. When connected via a USB cable, a "SANYO" drive appears on the desktop, and is labeled "/Volumes/SANYO".
This drive shows as locked in the finder, and the permissions information says "You can only read."
Going to the command line, shows that it is mounted read-only:
/dev/disk2s1 on /Volumes/SANYO (local, nodev, nosuid, read-only)
If I attempt to remount it as read-write:
Lappy-386:~ greg$ mount -u -o rw /dev/disk2s1
mount_msdos: /dev/disk2s1: Resource busy
Lappy-386:~ greg$ sudo !!
sudo mount -u -o rw /dev/disk2s1
mount_msdos: /dev/disk2s1: Resource busy
I have heard that this may be because Mac OS doesn't react well to devices that don't respond to it's mode sensing. I don't really care about mode sensing, I care about being able to forcibly mount this device as read-write, as it works perfectly well in Windows (even under Parallels) and Linux.
For a platform that prides itself on 'plug it in and it works', not being able to plug in a simple mass storage device is a huge mistake. What's even worse is that there is no option to forcibly mount it as read-write, and there is no error message that tells you why it is mounted read only. The console (in system.log) has:
Apr 18 14:16:46 Lappy-386 kernel[0]: USBF: 691451.613 AppleUSBEHCI[0x4344000]::Found a transaction past the completion deadline on bus 253, timing out!
The question is, how do I make this device show up read-write? Who can I contact at Apple to explain this problem? I do have AppleCare.
MacBook Mac OS X (10.4.9)

Any ideas...?
MacBook Mac OS X (10.4.6)

Make a volume mount read-only

Rather than dig for my Mac OS X Server DVD, I find it easier to clone the disc onto a small partition on a hard drive.
However, the volume always mounts read-write, and I always get warnings about low disk space because of it. (I made the partition as small as possible.) Plus, I don't want to have anything mess with my Mac OS X Server "DVD".
I noticed that Mac OS X doesn't use fstab for mounting volumes… is there a way to make a disc mount read-only all of the time? (chmod -R a-w * doesn't cut it for me.)

I don't mean having it mount read-only when booting from it. I mean, while the server is running normally (not booted from the "disc").
For peace of mind, I'd like to have my "disc" always be read-only, just to make sure that it isn't modified unless I explicitly allow it.
On Linux, I could add "ro" to the mount options. Since Mac OS X doesn't use fstab, is there some plist that determines how volumes are mounted? I'd rather not edit the /etc/rc.* files unless absolutely necessary.

Set sharing on system to read only now computer wlll not boot up

set sharing on system to read only now computer wlll not boot up

Hello skiboat2,
Because the permissions have been changed, you will need to put them back to what they were before. One of the ways to do that is to reinstall your OS X to make sure that everything permission wise gets put back to what it needs to be to work properly. Based of to the operating system that you say you have, I have provided the steps for reinstalling Snow Leopard. When doing this, it does not overwrite your personal data; it only touches the operating system.
Mac OS X 10.6: Reinstalling Mac OS X
http://support.apple.com/kb/PH6606
Regards,
-Norm G.

RAID Goes Read-Only (-50 Error)

I have a first-revision xserve raid, connected via a Vixel 335 to 4 servers, zoned so there are two on each RAID controller, with LUN masking allowing one volume to appear on each server.
One pair of servers tends to break each other whenever something happens. I restart one server and the other one stops being able to write to the xserve raid. Any write attempt results in a -50 error. Then if I restart the one that went bad, it breaks the other the same way. If I restart them at the same time, it usually works, but sometimes does not, sometimes the volumes won't even mount. RAID admin loggs a "Fiber LIP" when either server restarts. That seems normal, but it why does the RAID stop allowing writes on the other volume? Anyone seen anything like this before?
This pair of servers are second-revision G4 xserves with the pre-installed FC cards.
Thanks for any input.
Mark Mayfield
Roseville Area Schools
Network Manager

I did a little more research and there are quite a few people who've seen this error. I don't think it's the drive.
I suspect the controller in the enclosure, a jmicron 0x2336, is responsible for my problems. It looks like Linux and FreeBSD both had software updates to work around bugs in the controller. If OS X did not get updated, it would explain everything. The drive sleeps and then won't wake up fully and OS X marks it as in error and goes read only.
The enclosure is a Thermaltake Silver II USB + esata. It looks like a lot of people have had similar problems with them. I saw posts on macrumors, adobe's support forums, etc.

Floppy always mounts read-only.

I've had this problem for a while with arch but it never bothered me. But now I really want to get my hands dirty with OpenBSD and cant bring myself to waste a cd for a 4meg iso. So i have to use the boot floppy. However when i mount any floppy, it mounts it as read-only. I've checked the on/off tab. I know the drive and floppy are both good as I can mount it and write to it in a gentoo live-cd. The fstab line is:
/dev/fd0 /mnt/fl vfat user,noauto 0 0
any thoughts?

grab a livecd if that works (as user!) then check modules loaded against Arch ...
If you can mount drive as root then its just a permissions thing .. udev maybe
I cannot be too much help as my box does not have a floppy drive
O the write protect thing I that missed that sorry ....

USB Drive Mounts Read Only

For some reason now on all my Linux systems but particularly Arch Linux, my USB thunb drive gets auto mounted in Gnome when I plug it in but for some reason it's 'read only'.
[carlos@tuna ~]$ cd /media/usb/
[carlos@tuna usb]$ ls -l
total 3722352
drwx------ 2 carlos users 8192 Feb 11 10:34 files
drwx------ 2 carlos users 8192 Feb 13 20:32 movies
drwx------ 2 carlos users 8192 Jan 31 19:18 music
drwx------ 4 carlos users 8192 Feb 11 10:34 pics
drwx------ 2 carlos users 8192 Jan 28 12:17 tv
-rw-r--r-- 1 carlos users 1564807588 Feb 14 17:40 WELCOM~1.AVI
/dev/sdg1 on /media/usb type vfat (rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=100,shortname=mixed,dmask=0077,utf8=1,showexec,flush)
Both on CLI & through my Gnome file browser (Nautilus), I can't re-name, delete, or create new files. I don't understand what has changed. I then tested this on a spare laptop running Ubuntu 10.10 and it too has the same issue.
Can anyone please explain this to me or help me resolve this problem?

Correct. In both cases (CLI & GUI) I can't remove, add, or change existing files:
[carlos@tuna ~]$ cd /media/
[carlos@tuna media]$ ls -l
total 8
drwx------ 9 carlos users 8192 Dec 31 1969 CORSAIR
[carlos@tuna media]$ cd CORSAIR/
[carlos@tuna CORSAIR]$ ls -l
total 3722352
drwx------ 2 carlos users 8192 Feb 11 10:34 files
drwx------ 2 carlos users 8192 Feb 13 20:32 movies
drwx------ 2 carlos users 8192 Jan 31 19:18 music
drwx------ 4 carlos users 8192 Feb 11 10:34 pics
drwx------ 2 carlos users 8192 Jan 28 12:17 tv
-rw-r--r-- 1 carlos users 1564807588 Feb 14 17:40 WELCOM~1.AVI
[carlos@tuna CORSAIR]$ rm WELCOM~1.AVI
rm: cannot remove `WELCOM~1.AVI': Read-only file system
I can't even change the permissions on the file:
chmod: changing permissions of `WELCOM~1.AVI': Read-only file system

Hard drive is read only now

My brother hooked my external hard drive to his computer and now that I plugged it back into mine, it is read only. How can I change it back? I need to access all of my info.

Without know what he did to screw up your drive we would only be guessing.
If you would post a screen shoot of the information pane for the drive that might give a clue as to what he did to you.
Allan

Filesystem mounts read only during reboot [solved]

Hi folks,
after shredding my last Arch installation I'm trying to set everything up again using the new released image.
generating the /etc/fstab file by
genfstab -p /mnt >> /mnt/etc/fstab
creates the following code:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
# UUID=6c76fc7c-45d9-43e5-8530-7d098a58ca76
/dev/sdb3 / ext4 rw,relatime,data=ordered 0 1
# UUID=8ac179e7-b291-440a-839c-0fd476abcf1c
/dev/sdb2 /boot ext2 rw,relatime 0 2
after rebooting I get the message:
fsck.ext4: No such file or directory while trying to open /dev/sdb3
Possibly non-existent device?
and my file-system is mounted as read-only.
after changing the /etc/fstab by gaining rw-access using "mount -o remount,rw /" to
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
I once again get the file-system mounted as read-only. I would appreciate your suggestions on how to get rw-Access each reboot.
LG UnRoot
===================================================================================
additional informations:
I'm using a dual-boot-system with the following partition table:
Name Flags Part Type FS Type mountpoint Size (MB) purpose
Unusable 1.05
sda1 Primary ntfs 214748.37 Windows 7
sda2 Boot Primary ext2 /boot 104.86 boot
sda3 Primary ext4 / 64424.51 root
sda5 NC Logical swap swap 8590.99 swap
sda6 NC Logical ntfs 712334.38 shared space
Logical Free Space 0.75
Last edited by UnRoot (2012-08-05 22:15:11)

I'm sorry for that confusion, I copied the partition table by hand and mixed that up. It is always /dev/sdb.
Edit: just corrected that in the first post
You are right
Last edited by UnRoot (2012-08-05 22:04:27)

JFS root file system will only mount read-only

Hi, everybody!
I have been running this filesystem for months with no issues. The only thing I can think of that I changed recently was that I ran pacman -Syu.
When I boot there is no indication that there are errors with the file system. It simply mounts as read-only.
I have tried running
mount -n -o remount,rw /
, and it says "mount: / not mounted already, or bad option".
When I run just
mount -n -o rw /
it appears to work, in that there is no error message, but the file system is still read-only.
I have been able to mount it read-write successfully with the install disc, but only after I ran a fsck on it, also from the install disc. However, each time I have run fsck, it has reported no errors. I also tried forcing the check, with the same result.
Even after mounting it successfully with the install disc, it still will not mount read-write from my hard-disk install.
My DE (gnome) locked up a few days ago and I had to do a hard reboot, but it still functioned fine after that, so it doesn't seem related.
I would like to not have to reinstall, but I can if I need to. I would also like to find out how this happened, so that it does not happen again.
Any suggestions would be greatly appreciated.
Thanks for your help,
Jefferson

I got it working. I was running the fsck on the wrong partition. I am still curious as to why it happened, though.
@Marcel-: I don't think there was anything strange in my logs, but I'm not sure. I will look them over some more. Is there a particular one I should be looking in?
@seiichiro0185: Yes, the passno-flag is set to 1 for my rootfs.
Thank you both very much for helping me!

Make USB mount read only.

Hello again,
I am looking to make any USB mounted devices read only by default. Is there a way to do this in Leopard?

Greetings,
While you can make a USB device read only, you can't make a port read only. There are ways to disable a USB port, but that's about it.
You can also use a OS X Server and with it, you can deny access to the device, but to make it (the port) read only, I don't think that's possible with any OS. You could mark the internal hard drives read only, as well, but that would be a major pain.
I have hundreds of machines, and the open labs are the only ones I disallow the use of USB devices for security reasons, PeeCee or Mac. Using the OS X Server, we can apply restrictions, as I do with Active Directory for the PeeCees.
Cheers,
M.

/sys mounted read only

Hi,
Trying to get suspend working on a desktop system, and getting the following:
Oct 29 11:46:29 mars sudo[9754]: cbrake : TTY=pts/3 ; PWD=/home/cbrake ; USER=root ; COMMAND=/usr/bin/systemctl suspend
Oct 29 11:46:29 mars sudo[9754]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 29 11:46:29 mars systemd[1]: Starting Sleep.
Oct 29 11:46:29 mars systemd[1]: Reached target Sleep.
Oct 29 11:46:29 mars systemd[1]: Starting Suspend...
Oct 29 11:46:29 mars systemd-sleep[9757]: Failed to open /sys/power/state: Read-only file system
Oct 29 11:46:29 mars systemd[1]: systemd-suspend.service: main process exited, code=exited, status=1/FAILURE
Oct 29 11:46:29 mars systemd[1]: Failed to start Suspend.
Oct 29 11:46:29 mars systemd[1]: Dependency failed for Suspend.
Oct 29 11:46:29 mars systemd[1]: Unit sleep.target is not needed anymore. Stopping.
Oct 29 11:46:29 mars systemd[1]: Unit systemd-suspend.service entered failed state.
Oct 29 11:46:29 mars sudo[9754]: pam_unix(sudo:session): session closed for user root
Oct 29 11:46:29 mars systemd[1]: Stopping Sleep.
Oct 29 11:46:29 mars systemd[1]: Stopped target Sleep.
I then checked, and /sys is indeed mounted RO:
sys on /sys type sysfs (ro,nosuid,nodev,noexec,relatime)
Does anyone have ideas how to encourage /sys to be mounted RW?
Thanks,
Cliff

here is my fstab -- I don't see anything too alarming there. I do noticed that on newer arch installs, the tmpfs line is not there.
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
# /dev/sda2
UUID=8a08179d-aa48-4c76-9735-a0be09a06098 / ext4 rw,relatime 0 1
# /dev/sda1
UUID=24C4-C206 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
UUID=08ec403b-a035-4285-b9eb-03900711cb2b /scratch ext4 defaults 0 2
/dev/sda3 /scratch2 ext4 defaults 0 2
cbrake@mars:/home/fileserver /media/fileserver fuse.sshfs defaults,_netdev,port=26,idmap=user,IdentityFile=/home/cbrake/.ssh/id_dsa,allow_other,reconnect 0 0

My SD card mounts read only

Help,
I use Petalinux 2014.4 and the hardware is PicoZed with the SD socket on a carrier card. I can mount the SD
#mount /dev/mmcblk0p1 /media
But it is only read only and does not support write. As thus
# mount
rootfs on / type rootfs (rw,size=448908k,nr_inodes=112227)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=64k,nr_inodes=112227,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /var/volatile type tmpfs (rw,relatime)
/dev/mmcblk0p1 on /media/card type vfat (ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
Shows.
What is needed is write support a config option?
Thanks
Dave

In case it might help some one :-
The write protect was connected to a pin that was floating. I needed to change that and tie the signal low. What is a pain is hardware changes don't easily feed forward in petalinux, it was quicker to start again than try to update the hardware.

RAID mounts read-only now

Similar Messages

Maybe you are looking for