Drive auto mounting as read only (errors=remount-ro)
My system is auto-mounting as read only and I have no idea why.
Output of fstab:
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=28db2489-f60e-456c-9efd-7a961f3e970a / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=106e4470-d734-4cec-98a6-c7859aaedf18 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
Output of mount:
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
I have searched all night including:
Ubuntu 12.04 SSD root frequent random read only file system
I have no idea why this is going on. I did run fsck at boot and it didn't find errors.
The disk is fine (500GB, user 38GB)
mount
edited Apr 13 '17 at 12:24
Community♦
1
asked Jan 8 '14 at 1:05
greycode
11115
add a comment |
My system is auto-mounting as read only and I have no idea why.
Output of fstab:
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=28db2489-f60e-456c-9efd-7a961f3e970a / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=106e4470-d734-4cec-98a6-c7859aaedf18 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
Output of mount:
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
I have searched all night including:
Ubuntu 12.04 SSD root frequent random read only file system
I have no idea why this is going on. I did run fsck at boot and it didn't find errors.
The disk is fine (500GB, user 38GB)
mount
edited Apr 13 '17 at 12:24
Community♦
1
asked Jan 8 '14 at 1:05
greycode
11115
add a comment |
My system is auto-mounting as read only and I have no idea why.
Output of fstab:
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=28db2489-f60e-456c-9efd-7a961f3e970a / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=106e4470-d734-4cec-98a6-c7859aaedf18 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
Output of mount:
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
I have searched all night including:
Ubuntu 12.04 SSD root frequent random read only file system
I have no idea why this is going on. I did run fsck at boot and it didn't find errors.
The disk is fine (500GB, user 38GB)
mount
edited Apr 13 '17 at 12:24
Community♦
1
asked Jan 8 '14 at 1:05
greycode
11115
My system is auto-mounting as read only and I have no idea why.
Output of fstab:
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=28db2489-f60e-456c-9efd-7a961f3e970a / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=106e4470-d734-4cec-98a6-c7859aaedf18 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
Output of mount:
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
I have searched all night including:
Ubuntu 12.04 SSD root frequent random read only file system
I have no idea why this is going on. I did run fsck at boot and it didn't find errors.
The disk is fine (500GB, user 38GB)
mount
mount
edited Apr 13 '17 at 12:24
Community♦
1
asked Jan 8 '14 at 1:05
greycode
11115
edited Apr 13 '17 at 12:24
Community♦
1
asked Jan 8 '14 at 1:05
greycode
11115
edited Apr 13 '17 at 12:24
Community♦
1
edited Apr 13 '17 at 12:24
Community♦
1
edited Apr 13 '17 at 12:24
Community♦
1
1
asked Jan 8 '14 at 1:05
greycode
11115
asked Jan 8 '14 at 1:05
greycode
11115
asked Jan 8 '14 at 1:05
greycode
11115
11115
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
When you say you ran the fsck at boot and didn't find any errors, do you know that from watching it run or from the log files in /var/log/fsck? If it's from those log files, know that they haven't worked in years (see bug 513644).
How do you know your drive has no errors? Did you run the manufacturer tool from a boot CD such as UBCD?
I would boot to a LiveUSB/LiveCD and check the filesystem manually:
sudo fsck /dev/sda1
answered Jan 11 '14 at 21:50
Sean Fenton
3316
A path in Linux has no backslashes.
– A.B.
Jul 23 '15 at 4:47
@A.B. The other path already has forward slashes.
– Sean Fenton
Jul 24 '15 at 17:13
Yes, I know. What do you mean?
– A.B.
Jul 24 '15 at 17:17
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f401892%2fdrive-auto-mounting-as-read-only-errors-remount-ro%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
When you say you ran the fsck at boot and didn't find any errors, do you know that from watching it run or from the log files in /var/log/fsck? If it's from those log files, know that they haven't worked in years (see bug 513644).
How do you know your drive has no errors? Did you run the manufacturer tool from a boot CD such as UBCD?
I would boot to a LiveUSB/LiveCD and check the filesystem manually:
sudo fsck /dev/sda1
answered Jan 11 '14 at 21:50
Sean Fenton
3316
A path in Linux has no backslashes.
– A.B.
Jul 23 '15 at 4:47
@A.B. The other path already has forward slashes.
– Sean Fenton
Jul 24 '15 at 17:13
Yes, I know. What do you mean?
– A.B.
Jul 24 '15 at 17:17
add a comment |
When you say you ran the fsck at boot and didn't find any errors, do you know that from watching it run or from the log files in /var/log/fsck? If it's from those log files, know that they haven't worked in years (see bug 513644).
How do you know your drive has no errors? Did you run the manufacturer tool from a boot CD such as UBCD?
I would boot to a LiveUSB/LiveCD and check the filesystem manually:
sudo fsck /dev/sda1
answered Jan 11 '14 at 21:50
Sean Fenton
3316
A path in Linux has no backslashes.
– A.B.
Jul 23 '15 at 4:47
@A.B. The other path already has forward slashes.
– Sean Fenton
Jul 24 '15 at 17:13
Yes, I know. What do you mean?
– A.B.
Jul 24 '15 at 17:17
add a comment |
When you say you ran the fsck at boot and didn't find any errors, do you know that from watching it run or from the log files in /var/log/fsck? If it's from those log files, know that they haven't worked in years (see bug 513644).
How do you know your drive has no errors? Did you run the manufacturer tool from a boot CD such as UBCD?
I would boot to a LiveUSB/LiveCD and check the filesystem manually:
sudo fsck /dev/sda1
answered Jan 11 '14 at 21:50
Sean Fenton
3316
When you say you ran the fsck at boot and didn't find any errors, do you know that from watching it run or from the log files in /var/log/fsck? If it's from those log files, know that they haven't worked in years (see bug 513644).
How do you know your drive has no errors? Did you run the manufacturer tool from a boot CD such as UBCD?
I would boot to a LiveUSB/LiveCD and check the filesystem manually:
sudo fsck /dev/sda1
answered Jan 11 '14 at 21:50
Sean Fenton
3316
edited Jul 24 '15 at 17:12
answered Jan 11 '14 at 21:50
Sean Fenton
3316
answered Jan 11 '14 at 21:50
Sean Fenton
3316
answered Jan 11 '14 at 21:50
Sean Fenton
3316
3316
A path in Linux has no backslashes.
– A.B.
Jul 23 '15 at 4:47
@A.B. The other path already has forward slashes.
– Sean Fenton
Jul 24 '15 at 17:13
Yes, I know. What do you mean?
– A.B.
Jul 24 '15 at 17:17
add a comment |
A path in Linux has no backslashes.
– A.B.
Jul 23 '15 at 4:47
@A.B. The other path already has forward slashes.
– Sean Fenton
Jul 24 '15 at 17:13
Yes, I know. What do you mean?
– A.B.
Jul 24 '15 at 17:17
A path in Linux has no backslashes.
– A.B.
Jul 23 '15 at 4:47
A path in Linux has no backslashes.
– A.B.
Jul 23 '15 at 4:47
@A.B. The other path already has forward slashes.
– Sean Fenton
Jul 24 '15 at 17:13
@A.B. The other path already has forward slashes.
– Sean Fenton
Jul 24 '15 at 17:13
Yes, I know. What do you mean?
– A.B.
Jul 24 '15 at 17:17
Yes, I know. What do you mean?
– A.B.
Jul 24 '15 at 17:17
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f401892%2fdrive-auto-mounting-as-read-only-errors-remount-ro%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
