From: Michael Havens
> Is my USB drive dead?
> bmike1@PresarioLapTop1:~/Desktop$ ./Backup\ bmike1
> rsync: mkdir "/mnt/backup/bmike1" failed: Read-only file system (30)
> bmike1@PresarioLapTop1:~/Desktop$ dmesg | tail -n 30
> [74384.693378] type=1701 audit(1373570392.790:842): auid=4294967295
> uid=1000 gid=1000 ses=4294967295 pid=7116 comm="chromium-browse"
> reason="seccomp" sig=0 syscall=33 compat=0 ip=0xb63eb424 code=0x50000
[snip a lot of very similar lines]
disk-related. In the long term, it'd probably be a good idea to find out
what's dumping this to the kernel log buffer and tell it to stop doing that.
However, the timestamps on the first and last messages differ by 3084 seconds.
Provided you tried to do something to /mnt/backup , then ran dmesg fairly
soon after that (< 3084 seconds), then there are no messages in the kernel log
buffer about disk problems. This is a good sign (maybe).
What's the output from "mount | grep backup"? It should say something like:
/dev/sdd on /mnt/backup type ext3 (rw)
...if it says (ro), then for some reason, your distro is doing something dumb.
In that case, edit your fstab and change "noauto,users" to "noauto,users,rw".
Then umount and remount the disk, and it should work better. You still may
have to mkdir /mnt/backup/bmike1 and chown that dir to bmike1, but at least
you'd be able to do this if the filesystem's mounted rw.