"O_TMFILE" ; apps aren't responding not even "eos-diagnostics" from Terminal

#1

Help me out in hurry, troubles here with everything


Problem with 0_TMFILE for apps
How to fix read only file error
#2

Open a terminal and run this command:

journalctl > /tmp/journal.txt

Then attach the file /tmp/journal.txt here. (You can press Ctrl-L in the file chooser to show an address bar where you can just type that path straight in.)

#3

No response from machine,although spelling was correct,and now i cant rename any file of any type too (last image)


#4

You can’t rename files because (I believe) your hard disk is read-only, which (I am guessing) is due to some corruption. That is why getting the journal file would be useful. Please repeat the command in the terminal (it is normal for it to produce no output) then attach it to this forum by clicking the upload button:

Click Home

Click the left-arrow beside the “:houses: [your name]” button at the top, click the hard disk symbol, and pick tmp from the list. You should see journal.txt there:

#5

Here it is i had to manually search for it
Journal.txt
journal.txt (161.5 KB)

#6

Do you have any idea whats goin on with this, how to fix

#7

And it hard to see how late this community replies… To problem

#9

Are these all distinct commands? Let me have a try in these

#10

Not working
Terminal displays

#12

@LeandroStanger both your suggestions are unhelpful. @Akshansh_Rawat has already tried and failed to run eos-diagnostics, and since he can’t create files he’s not going to be able to download eos-fix-ostree. (Besides, there is no indication of the problem that script is designed to fix.) Please can you not blindly paste these two sets of instructions into every thread?

1 Like
#13 
Feb 14 14:54:42 darkesta kernel: ata1.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x0
Feb 14 14:54:42 darkesta kernel: ata1.00: irq_stat 0x40000008
Feb 14 14:54:42 darkesta kernel: ata1.00: failed command: READ FPDMA QUEUED
Feb 14 14:54:42 darkesta kernel: ata1.00: cmd 60/08:28:18:95:c4/00:00:00:00:00/40 tag 5 ncq dma 4096 in
                                          res 41/40:00:18:95:c4/00:00:00:00:00/00 Emask 0x409 (media error) <F>
Feb 14 14:54:42 darkesta kernel: ata1.00: status: { DRDY ERR }
Feb 14 14:54:42 darkesta kernel: ata1.00: error: { UNC }
Feb 14 14:54:42 darkesta kernel: ata1.00: configured for UDMA/133
Feb 14 14:54:42 darkesta kernel: sd 0:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 14 14:54:42 darkesta kernel: sd 0:0:0:0: [sda] tag#5 Sense Key : Medium Error [current]·
Feb 14 14:54:42 darkesta kernel: sd 0:0:0:0: [sda] tag#5 Add. Sense: Unrecovered read error - auto reallocate failed
Feb 14 14:54:42 darkesta kernel: sd 0:0:0:0: [sda] tag#5 CDB: Read(10) 28 00 00 c4 95 18 00 00 08 00
Feb 14 14:54:42 darkesta kernel: print_req_error: I/O error, dev sda, sector 12883224
Feb 14 14:54:42 darkesta kernel: ata1: EH complete
Feb 14 14:54:42 darkesta kernel: EXT4-fs error (device sda3): ext4_find_entry:1431: inode #402229: comm gnome-shell: reading directory lblock 0
Feb 14 14:54:42 darkesta kernel: Aborting journal on device sda3-8.
Feb 14 14:54:42 darkesta kernel: EXT4-fs (sda3): Remounting filesystem read-only

This indicates that there is a physical problem with your computer’s hard disk. Please contact Acer customer support.

#14

What does it mean?? Withdrawal by auther??? Didnt get it

#15

Thank you for your attention, i will get to Acer now

#16