Skip to main content
Missed some useful information
Source Link
sqwale
  • 141
  • 1
  • 8

I logged on to my debian box and tried running some commands and I was presented with the following message.

sudo: Can't open /var/lib/sudo/username/0: Read-only file system 

After doing some digging I discovered that the fstab had an option on the root partition that would remount it as read only: errors=remount-ro

I suspect it remount the error in case of a file system consistency issue.

Now I have come across a tool fsck and some say it may resolve the issue using the command

sudo fsck -t ext3 /dev/sda[n] 

according to this article.

I suspect i could remount it and change the read only restriction however if the debian changed it to avoid further damage or loss of information i think it wouldn't be a good idea.

However there is no guarantee it would work for mine and it may even cause more issues.

Does anyone have any advice on what steps to take?

EDIT

Below is the first section of the FSTAB

UUID=e2887ae1-xxxx-xxx-xxx-xxxxxxxx / ext3 errors=remount-ro 0 1

I logged on to my debian box and tried running some commands and I was presented with the following message.

sudo: Can't open /var/lib/sudo/username/0: Read-only file system 

After doing some digging I discovered that the fstab had an option on the root partition that would remount it as read only: errors=remount-ro

I suspect it remount the error in case of a file system consistency issue.

Now I have come across a tool fsck and some say it may resolve the issue using the command

sudo fsck -t ext3 /dev/sda[n] 

according to this article.

I suspect i could remount it and change the read only restriction however if the debian changed it to avoid further damage or loss of information i think it wouldn't be a good idea.

However there is no guarantee it would work for mine and it may even cause more issues.

Does anyone have any advice on what steps to take?

I logged on to my debian box and tried running some commands and I was presented with the following message.

sudo: Can't open /var/lib/sudo/username/0: Read-only file system 

After doing some digging I discovered that the fstab had an option on the root partition that would remount it as read only: errors=remount-ro

I suspect it remount the error in case of a file system consistency issue.

Now I have come across a tool fsck and some say it may resolve the issue using the command

sudo fsck -t ext3 /dev/sda[n] 

according to this article.

I suspect i could remount it and change the read only restriction however if the debian changed it to avoid further damage or loss of information i think it wouldn't be a good idea.

However there is no guarantee it would work for mine and it may even cause more issues.

Does anyone have any advice on what steps to take?

EDIT

Below is the first section of the FSTAB

UUID=e2887ae1-xxxx-xxx-xxx-xxxxxxxx / ext3 errors=remount-ro 0 1

added 12 characters in body
Source Link
MadHatter
  • 81.7k
  • 20
  • 190
  • 235

I logged on to my debian box and tried running some commands and I was presented with the following message.

sudo: Can't open /var/lib/sudo/username/0: Read-only file system

sudo: Can't open /var/lib/sudo/username/0: Read-only file system 

After doing some digging I discovered that the fstab had an option on the root partition that would remount it as read only.

errors=remount-ro: errors=remount-ro

I suspect it remount the error in case of a file system consistency issue.

Now I have come across a tool fsck and some say it may resolve the issue using the command

sudo fsck -t ext3 /dev/sda[n]

sudo fsck -t ext3 /dev/sda[n] 

according to this article.

I suspect i could remount it and change the read only restriction however if the debian changed it to avoid further damage or loss of information i think it wouldn't be a good idea.

However there is no granteeguarantee it would work for mine and it may even cause more issues.

Does anyone have any adviseadvice on what steps to take?

I logged on to my debian box and tried running some commands and I was presented with the following message.

sudo: Can't open /var/lib/sudo/username/0: Read-only file system

After doing some digging I discovered that the fstab had an option on the root partition that would remount it as read only.

errors=remount-ro

I suspect it remount the error in case of a file system consistency issue.

Now I have come across a tool fsck and some say it may resolve the issue using the command

sudo fsck -t ext3 /dev/sda[n]

according to this article.

I suspect i could remount it and change the read only restriction however if the debian changed it to avoid further damage or loss of information i think it wouldn't be a good idea.

However there is no grantee it would work for mine and it may even cause more issues.

Does anyone have any advise on what steps to take?

I logged on to my debian box and tried running some commands and I was presented with the following message.

sudo: Can't open /var/lib/sudo/username/0: Read-only file system 

After doing some digging I discovered that the fstab had an option on the root partition that would remount it as read only: errors=remount-ro

I suspect it remount the error in case of a file system consistency issue.

Now I have come across a tool fsck and some say it may resolve the issue using the command

sudo fsck -t ext3 /dev/sda[n] 

according to this article.

I suspect i could remount it and change the read only restriction however if the debian changed it to avoid further damage or loss of information i think it wouldn't be a good idea.

However there is no guarantee it would work for mine and it may even cause more issues.

Does anyone have any advice on what steps to take?

Source Link
sqwale
  • 141
  • 1
  • 8

debian Read-only file system error

I logged on to my debian box and tried running some commands and I was presented with the following message.

sudo: Can't open /var/lib/sudo/username/0: Read-only file system

After doing some digging I discovered that the fstab had an option on the root partition that would remount it as read only.

errors=remount-ro

I suspect it remount the error in case of a file system consistency issue.

Now I have come across a tool fsck and some say it may resolve the issue using the command

sudo fsck -t ext3 /dev/sda[n]

according to this article.

I suspect i could remount it and change the read only restriction however if the debian changed it to avoid further damage or loss of information i think it wouldn't be a good idea.

However there is no grantee it would work for mine and it may even cause more issues.

Does anyone have any advise on what steps to take?