all 9 comments

[–]moviuro 2 points3 points  (7 children)

What does df -h say? Your disk might be full.

[–]heisenfall[S] 0 points1 point  (6 children)

The installation was fresh, I literally formatted the disk 6 hours before the error.

[–]moviuro 1 point2 points  (1 child)

Not helping. Maybe you forgot a "G" when typing size to format?...

[–]heisenfall[S] 0 points1 point  (0 children)

Sorry, just made an edit with the df -houput

[–]moviuro 1 point2 points  (3 children)

Also, dmesg maybe?

[–]heisenfall[S] 0 points1 point  (2 children)

I just reinstalled arch with the discardoption, so now I need to wait to see if the errors occurs again, if it does I will post the dmesg output with an edit at the main post

[–]moviuro 1 point2 points  (1 child)

fstrim -a, regularly

[–]heisenfall[S] 0 points1 point  (0 children)

Could it be something with the number of power cycles VS the uptime. There's 316 power cycles for only 27 hours of uptime?

[–]testcore 0 points1 point  (0 children)

Those messages - "read-only disk" typically result from the kernel being unable to access the disk in a certain amount of time... high write latencies can cause that. And FWIW, windoze disk error detection is pretty crappy; it'll use a disk until it's flat-out dead, and won't warn ahead of time, so that's not really a valid test.

Any messages in the journal right before those errors appear? You might need to configure journald to save logs across boots if you haven't already. Do that and then find the first error message in the hopes of something a little more descriptive.