I 'just' noticed that at some point, my USB backup drive on my server is mounted as read-only and all of my background sync cron jobs have been failing.
So I need to fix this without rebooting the server.
I can VNC into the server and running "mount" shows:
/dev/sdc1 on /media/HD103SI type ext4 (rw,nosuid,nodev,uhelper=udisks)
and umount gets:
# umount /dev/sdc1 umount: /media/HD103SI: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))
How can I get this drive r/w?
I 'just' noticed that at some point, my USB backup drive on my server
is mounted as read-only and all of my background sync cron jobs have been failing.
So I need to fix this without rebooting the server.
How can I get this drive r/w?
Have you tried "mount -o remount,rw <mountpoint>"?
The unanswered question here is why did it go read only, and does this condition still exist?
Barry
On 10/25/2015 11:12 AM, Barry Brimer wrote:
I 'just' noticed that at some point, my USB backup drive on my server
is mounted as read-only and all of my background sync cron jobs have been failing.
So I need to fix this without rebooting the server. How can I get this drive r/w?
Have you tried "mount -o remount,rw <mountpoint>"?
# mount -o remount,rw /media/HD103SI/ mount: cannot remount block device /dev/sdc1 read-write, is write-protected
The unanswered question here is why did it go read only, and does this condition still exist?
The burning question of the day......
Should I 'just' unplug it, power cycle it and reconnect it?
Just disconnected, power-cycled then reconnected the drive. /var/log/messages tell me:
Oct 26 20:50:10 homebase kernel: EXT4-fs warning (device sdd1): ext4_clear_journal_err: Filesystem error recorded from previous mount: IO failure Oct 26 20:50:10 homebase kernel: EXT4-fs warning (device sdd1): ext4_clear_journal_err: Marking fs in need of filesystem check. Oct 26 20:50:10 homebase kernel: EXT4-fs (sdd1): warning: mounting fs with errors, running e2fsck is recommended Oct 26 20:50:10 homebase kernel: EXT4-fs (sdd1): recovery complete Oct 26 20:50:10 homebase kernel: EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts:
First it comes in as sdd when previously it was sdc. But the drive is now R/W.
So do I run e2fsck, and with what options. From the manpage I am assuming I better umount it first...
On 10/25/2015 11:16 AM, Robert Moskowitz wrote:
On 10/25/2015 11:12 AM, Barry Brimer wrote:
I 'just' noticed that at some point, my USB backup drive on my server
is mounted as read-only and all of my background sync cron jobs have been failing.
So I need to fix this without rebooting the server. How can I get this drive r/w?
Have you tried "mount -o remount,rw <mountpoint>"?
# mount -o remount,rw /media/HD103SI/ mount: cannot remount block device /dev/sdc1 read-write, is write-protected
The unanswered question here is why did it go read only, and does this condition still exist?
The burning question of the day......
Should I 'just' unplug it, power cycle it and reconnect it?
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
-
Barry Brimer -
Robert Moskowitz