I can't create a new folder and i can't dowload files

[Sasa]

Hello,

When i try to create a new folder i get this message: cannot create folder - error creating directory - read only file system and when i want to dowload something i get this message: failed - insufficient permissions.
(I tried to make an eos-diagnostic log file and the message was: can’t save diagnostic file to/sysroot/home…read-only file system)
What should i do?
I have 3.7.7. (200210-144002) version.

Thanks for the help

[egrath]

Can you please post the output of the following commands:

journalctl -b -l | grep -i "mounting"

and

journalctl -b -l | grep "sd[a-z]"

(Preferrably take a Photo and upload it here as the output might get rather long)

[Sasa]

IMG_20200318_214306.jpg

IMG_20200318_214521.jpg

IMG_20200318_214540.jpg

IMG_20200318_214610.jpg

Egon via Endless Community community@bot.endlessm.com ezt írta (időpont: 2020. márc. 18., Sze, 7:31):

[egrath]

It seems like your filesystem got corrupted somehow. This can have two reasons:

1. There was a unclean shutdown during a write operation (power loss, …)
2. The Disk is failing (but i don’t see any indicator in the screenshots)

To attempt to fix it, try to run the following command:

sudo e2fsck -y -c /dev/sda3

Reboot after it finishes.

[Sasa]

It doesn’t work

This is the end of the message in english:

sudo: / var / lib / sudo directory creation failed: read only file system

e2fsck 1.44.5 (15-Dec-2018)

/ dev / sda3 is attached.

e2fsck: Unable to continue, interrupt.

I attached the photo from the screen, but it is hungarian

IMG_20200319_170659.jpg

Egon via Endless Community community@bot.endlessm.com ezt írta (időpont: 2020. márc. 19., Cs, 10:55):

[LeandroStanger]

Open the application called Disks
Click

Click Repair Filesystem…

[Sasa]

I did it, but the problem remained.

LeandroStanger via Endless Community community@bot.endlessm.com ezt írta (időpont: 2020. márc. 19., Cs, 20:58):

[egrath]

It seems that your disk still has the errors which prevent from mounting it read-write.
Perform the following steps:

• Boot from a Live Installer Media

• Open a Terminal and type:

sudo blkid

This will yield some output. We need to determine which device contains your root partition. It will look something like:

Look for the device with the label “ostree” and a device name like /dev/sd…. In my case the root device is /dev/vda2 (as it’s a virtual machine). Now enter:

sudo fsck -y -c /dev/vda2

(Substitute the device name)
This will take some time as it checks the entire filesystem structure:

Now try to mount the filesystem in question to see if it has been fixed by:

sudo mount /dev/vda2 /mnt

If the command above yielded no error, chances are good that the repair was successful. In this case, reboot your machine with

reboot

If it was not successfull, run:

journalctl -k -l -n 20

This will output the last 20 lines of the kernel message buffer, which should include some indication that the device has a hardware defect. Take a photo of it and upload it here.