*Read-only file system* #65

New Issue

Benjamin_Loison · 2025-02-13T13:11:50+01:00

Benjamin_Loison commented

2025-02-13 13:11:50 +01:00

On OverClock3000 running on Pegasus Virtual Machine Manager after days of working fine:

touch test

touch: cannot touch 'test': Read-only file system

The Ask Ubuntu answer 868792:

fsck

Output:

Command 'fsck' is available in the following places
 * /sbin/fsck
 * /usr/sbin/fsck
The command could not be located because '/usr/sbin:/sbin' is not included in the PATH environment variable.
This is most likely caused by the lack of administrative privileges associated with your user account.
fsck: command not found

sudo fsck

output.txt

Still face touch issue.

sudo fsck

Output:

fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
/dev/vda1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (9009859, counted=9016698).
Fix<y>? yes to all
Free inodes count wrong (11380279, counted=11380297).
Fix? yes


/dev/vda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/vda1: ***** REBOOT SYSTEM *****
/dev/vda1: 3881399/15261696 files (0.4% non-contiguous), 52018310/61035008 blocks

Same output if run again.

Still unable to touch.

reboot

makes touch works fine.

Should test the Ask Ubuntu answer 287024 next time to avoid rebooting.

On OverClock3000 running on Pegasus Virtual Machine Manager after days of working fine: ```bash touch test ``` ``` touch: cannot touch 'test': Read-only file system ``` [The Ask Ubuntu answer 868792](https://askubuntu.com/a/868792): ```bash fsck ``` <details> <summary>Output:</summary> ``` Command 'fsck' is available in the following places * /sbin/fsck * /usr/sbin/fsck The command could not be located because '/usr/sbin:/sbin' is not included in the PATH environment variable. This is most likely caused by the lack of administrative privileges associated with your user account. fsck: command not found ``` </details> ```bash sudo fsck ``` [output.txt](/attachments/79c61690-8f84-4c44-992d-4f7743edd416) Still face `touch` issue. ```bash sudo fsck ``` <details> <summary>Output:</summary> ``` fsck from util-linux 2.38.1 e2fsck 1.47.0 (5-Feb-2023) /dev/vda1 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong (9009859, counted=9016698). Fix<y>? yes to all Free inodes count wrong (11380279, counted=11380297). Fix? yes /dev/vda1: ***** FILE SYSTEM WAS MODIFIED ***** /dev/vda1: ***** REBOOT SYSTEM ***** /dev/vda1: 3881399/15261696 files (0.4% non-contiguous), 52018310/61035008 blocks ``` </details> Same output if run again. Still unable to `touch`. ```bash reboot ``` makes `touch` works fine. Should test [the Ask Ubuntu answer 287024](https://askubuntu.com/a/287024) next time to avoid rebooting.

output.txt

448 KiB

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Benjamin_Loison/linux#65