Quickbooks This File Is Set to Read Only

March 02, 2022 Post a Comment

Dear All,

I accept a seperate SATA drive on a CentOS 7 system that I apply to continue backups.

Recently, when I try to create or re-create files to the mounted drive, I get and error maxim
the file organization is read only.

For case, if I try to create a new binder, I go " mkdir: cannot create directory examination': Read-only file system"

Any thought how I can troubleshoot and set up this? Thank you

Moeen Jan 14, 2019 at xv:46 UTC

In that location may have been a problem with Fsck of this file system on previous kicking. I would do the post-obit:

1.) backup contents of this drive to a removable disk
two.) check /etc/fstab to make sure mount options and fs type are right (is it set up for rw admission)
3.) unmount the drive and run Fsck on it with Fsck -y /dev/device. (pay attending to results hither to see whatsoever issues)
four.) after filesystem is fsck-ed mount it again and see if you can write to information technology now

Too, it may be the underlying disk going bad, check this link for instructions on how SMART disk monitoring works in Linux:

https://www.google.com/amp/s/www.cyberciti.biz/tips/linux-find-out-if-harddisk-declining.html/amp

Promise this helps yous observe the problem.
-Moeen

7 Replies

eric ross Jan 14, 2019 at 15:31 UTC

You could endeavour remounting the mounted drive (substitute correct mount directory)

                              mountain -o remount,rw /mountdir

In improver to Eric'due south comment, you could run the mount command to see the what mount options are currently in identify. If y'all run across "ro", that is the problem.

                            $ mount devtmpfs on /dev blazon devtmpfs (rw,relatime,size=3008544k,nr_inodes=752136,manner=755) tmpfs on /dev/shm blazon tmpfs (rw,relatime) tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755) devpts on /dev/pts type devpts (rw,relatime,gid=v,style=620,ptmxmode=000) /dev/sda2 on / type ext4 (rw,relatime,data=ordered)

Moeen January 14, 2019 at 15:46 UTC

In that location may have been a problem with Fsck of this file organisation on previous boot. I would practise the post-obit:

1.) backup contents of this drive to a removable disk
2.) check /etc/fstab to make sure mount options and fs type are correct (is it set for rw access)
three.) unmount the bulldoze and run Fsck on it with Fsck -y /dev/device. (pay attention to results here to see whatsoever problems)
4.) after filesystem is fsck-ed mount it again and meet if yous tin write to it at present

Also, it may be the underlying disk going bad, check this link for instructions on how SMART disk monitoring works in Linux:

https://www.google.com/amp/s/www.cyberciti.biz/tips/linux-find-out-if-harddisk-failing.html/amp

Hope this helps you find the trouble.
-Moeen

MerlinYoda January 14, 2019 at fifteen:54 UTC

eric ross wrote:

You could try remounting the mounted drive (substitute correct mount directory)

                                mount -o remount,rw /mountdir

Huh, I always though you needed to specify the device prior to the directory when doing a remount. I didn't realize it was optional. You lot acquire something new every day.

furicle Jan 14, 2019 at 16:07 UTC

Start by running the 'mount' command - Information technology will give you output like this

                              /dev/mapper/vg_floppyd-lv_root on / type ext4 (rw) proc on /proc blazon proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=v,mode=620) tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0") /dev/sdb1 on /boot type ext4 (rw) /dev/mapper/vg_floppyd-lv_home on /home type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

The (rw) indicates they are currently mounted read-write.

If you lot take a segmentation that is mounted read but when you think it should be read-write, yous'll want to explore why. I'd kickoff by looking at the log when that file system is mounted.

If it mounts on kicking up, try something like 'dmesg | grep test' or but run dmesg and peruse the whole affair.

If it mounts when yous connect it, just scout /var/log/messages every bit you connect it.

Oft information technology means there is some sort of deejay issue that's been detected, and information technology'south mounted it read just to forestall you from making it worse. For case, an NTFS segmentation that's marked equally 'dirty' (needs a disk cheque on reboot) will mount read only in Linux. The right solution here depends on the file system involved and the message you lot see when you lot connect it.

MerlinYoda wrote:
eric ross wrote:

You could attempt remounting the mounted drive (substitute correct mount directory)
                                mount -o remount,rw /mountdir                              
Huh, I always though you lot needed to specify the device prior to the directory when doing a remount. I didn't realize it was optional. You acquire something new every mean solar day.

That's what I similar about these forums--something new every day. :-)

From the "mount" man folio:

                            When mounting a filesystem mentioned in fstab or mtab, information technology suffices to give but the device, or only the mountain indicate.

kajun989 Jan 23, 2019 at 17:37 UTC

PC Pharm Limited is an It service provider.

Update, the disk failed Smart tests. A restart of the server caused the disk to be rw once again. Disk was replaced

This topic has been locked by an ambassador and is no longer open for commenting.

To continue this discussion, please ask a new question.

wethingtonwhicteplethe78.blogspot.com

Source: https://community.spiceworks.com/topic/2186377-read-only-file-system-linux

Wethington Whicteplethe78

Quickbooks This File Is Set to Read Only

7 Replies

Post a Comment for "Quickbooks This File Is Set to Read Only"