rsync showing drive read only

chillyw13 · 13. September 2016

I have an rsync job that is supposed to back up data to a USB drive. WHen I try to run it, I get an error

Code

rsync: mkdir "/media/f3863d78-6648-4e5e-98f2-5041b810ba35/Backup2" failed: Read-only file system (30)
rsync error: error in file IO (code 11) at main.c(605) [Receiver=3.0.9]
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]

What changed to make it read only? How do I fix this?

ryecoaaron · 13. September 2016

The drive must be read-only then. What is the output of: mount

chillyw13 · 13. September 2016

Code

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=4113366,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmod                                       e=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=3292416k,mode=755)
/dev/disk/by-uuid/f06d42b2-7418-477d-947e-1e901cab19bb on / type ext4 (rw,relati                                       me,errors=remount-ro,user_xattr,barrier=1,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
/dev/sda1 on /media/f3863d78-6648-4e5e-98f2-5041b810ba35 type ext4 (ro,noexec,re                                       latime,user_xattr,barrier=1,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjq                                       uota=aquota.group,_netdev)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=7227280k)
/dev/md0 on /media/5ebb5ec3-7ce4-4373-b133-a6c1f6061779 type ext4 (rw,noexec,rel                                       atime,user_xattr,barrier=1,stripe=256,data=ordered,jqfmt=vfsv0,usrjquota=aquota.                                       user,grpjquota=aquota.group,_netdev)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/sdg1 on /media/6b6c361e-501b-4081-af84-98ec59cdae70 type ext4 (rw,noexec,re                                       latime,user_xattr,barrier=1,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjq                                       uota=aquota.group,_netdev)
/dev/sdh1 on /media/81df27e5-5a7b-4444-a6ae-aa9f145820dc type ext4 (rw,noexec,re                                       latime,user_xattr,barrier=1,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjq                                       uota=aquota.group,_netdev)

Alles anzeigen

ryecoaaron · 13. September 2016

It is definitely mounted read only. Something might be wrong with it. Try mount -o remount,rw /dev/sda1

chillyw13 · 13. September 2016

And I do realize the drive is read-only. I'm trying to figure out how it got to be read-only, and how to stop it from happening again.

chillyw13 · 13. September 2016

Zitat von ryecoaaron

It is definitely mounted read only. Something might be wrong with it. Try mount -o remount,rw /dev/sda1

Ahh, but the drive with the issue is /dev/sdh1, not /dev/sda1.

ryecoaaron · 13. September 2016

Zitat von chillyw13

Ahh, but the drive with the issue is /dev/sdh1, not /dev/sda1.

Nope. sda1 is /media/f3863d78-6648-4e5e-98f2-5041b810ba35 according to your mount output and your error says it can't make a directory on /media/f3863d78-6648-4e5e-98f2-5041b810ba35

ryecoaaron · 13. September 2016

Zitat von chillyw13

I'm trying to figure out how it got to be read-only, and how to stop it from happening again.

Did you look at dmesg or /var/log/messages?

chillyw13 · 13. September 2016

Zitat von ryecoaaron

Nope. sda1 is /media/f3863d78-6648-4e5e-98f2-5041b810ba35 according to your mount output and your error says it can't make a directory on /media/f3863d78-6648-4e5e-98f2-5041b810ba35

I understand that, however the drive I am trying to write the files to is /dev/sdh1. When I try to rsync that drive, I get the RO error. I don't know why. According to fstab, /dev/sdh1 is rw. This has nothing to do with /dev/sda1.

ryecoaaron · 13. September 2016

I have no idea why it is trying to create a directory on sda then. I still think you should figure out why that drive is having issues. It still may be the cause of other issues.

chillyw13 · 13. September 2016

I did a df -h and saw where /dev/sda1 was mounted, and it should not have been. I unmounted it and recreated my rsync and all is good in the world. Still puzzled as to why rsync was trying to write to /dev/sda1 when I had /dev/sdh1 specified as the drive to use. Very weird. But it's fixed for now, so I'll keep an eye and see if this happens again. Might be a bug.

rsync showing drive read only

Jetzt mitmachen!

Tags