You are not logged in.

#1 2020-07-29 10:32:23

sonphantrung
Member
Registered: 2020-07-16
Posts: 11

Nitrogen corrupt file systems

I have recently installed Xmonad on my system, with nitrogen, but every time nitrogen restores, file systems always become read-only, so I have to fsck the partition manually. Is there any way to stop the corruptions of the file system, I have Cinnamon, Plasma, Xfce, Awesome and Xmonad. Thank you.

Offline

#2 2020-07-29 11:32:58

ondoho
Member
Registered: 2013-04-30
Posts: 638
Website

Re: Nitrogen corrupt file systems

I had to check, there's only one software called nitrogen on ArchLinux: a "Background browser and setter for X windows".
IMHO it cannot be responsible for this, at least not directly.
Execute the command manually, if possible with a verbose switch, and show us what it says. Also dmesg & journal entries for that time span.


However studied and stilted your rant, it can never hide the base and primitve emotion that inspired it.

Offline

#3 2020-07-30 02:09:29

sonphantrung
Member
Registered: 2020-07-16
Posts: 11

Re: Nitrogen corrupt file systems

After launching nitrogen, I got this:

(nitrogen:3509): Gtk-WARNING **: 09:07:57.240: Unable to locate theme engine in module_path: "murrine",

(nitrogen:3509): Gtk-WARNING **: 09:07:57.240: Unable to locate theme engine in module_path: "murrine",

(nitrogen:3509): Gtk-WARNING **: 09:07:57.241: Unable to locate theme engine in module_path: "murrine",
UNKNOWN ROOT WINDOW TYPE DETECTED (Nemo-desktop), please file a bug

I launched it in Cinnamon, Is there any problem in here?

Offline

#4 2020-07-30 04:50:14

Awebb
Member
Registered: 2010-05-06
Posts: 5,523

Re: Nitrogen corrupt file systems

You stopped halfway through ondoho's instructions and left out the juicy bits that could help us help you.

Offline

#5 2020-07-30 08:04:47

sonphantrung
Member
Registered: 2020-07-16
Posts: 11

Re: Nitrogen corrupt file systems

So, how to do it?I only know how to do journalctl, but not dmseg

Offline

#6 2020-07-30 08:22:37

Awebb
Member
Registered: 2010-05-06
Posts: 5,523

Re: Nitrogen corrupt file systems

Type "dmesg". The timestamps might be confusing, so look up the -e and/or -T switches.

Offline

#7 2020-07-31 10:20:28

sonphantrung
Member
Registered: 2020-07-16
Posts: 11

Re: Nitrogen corrupt file systems

Finally, I have the error:

[Fri Jul 31 17:01:25 2020] ata1.00: exception Emask 0x0 SAct 0x640008 SErr 0x50000 action 0x0
[Fri Jul 31 17:01:25 2020] ata1.00: irq_stat 0x40000001
[Fri Jul 31 17:01:25 2020] ata1: SError: { PHYRdyChg CommWake }
[Fri Jul 31 17:01:25 2020] ata1.00: failed command: READ FPDMA QUEUED
[Fri Jul 31 17:01:25 2020] ata1.00: cmd 60/00:18:f8:9d:21/01:00:0e:00:00/40 tag 3 ncq dma 131072 in
                                    res 41/40:b0:c8:a0:8f/00:00:00:00:00/40 Emask 0x9 (media error)
[Fri Jul 31 17:01:25 2020] ata1.00: status: { DRDY ERR }
[Fri Jul 31 17:01:25 2020] ata1.00: error: { UNC }
[Fri Jul 31 17:01:25 2020] ata1.00: failed command: READ FPDMA QUEUED
[Fri Jul 31 17:01:25 2020] ata1.00: cmd 60/00:90:70:a0:8f/01:00:00:00:00/40 tag 18 ncq dma 131072 in
                                    res 41/40:00:c8:a0:8f/00:01:00:00:00/40 Emask 0x409 (media error) <F>
[Fri Jul 31 17:01:25 2020] ata1.00: status: { DRDY ERR }
[Fri Jul 31 17:01:25 2020] ata1.00: error: { UNC }
[Fri Jul 31 17:01:25 2020] ata1.00: failed command: READ FPDMA QUEUED
[Fri Jul 31 17:01:25 2020] ata1.00: cmd 60/00:a8:10:0c:a5/01:00:01:00:00/40 tag 21 ncq dma 131072 in
                                    res 41/40:b0:c8:a0:8f/00:00:00:00:00/40 Emask 0x9 (media error)
[Fri Jul 31 17:01:25 2020] ata1.00: status: { DRDY ERR }
[Fri Jul 31 17:01:25 2020] ata1.00: error: { UNC }
[Fri Jul 31 17:01:25 2020] ata1.00: failed command: WRITE FPDMA QUEUED
[Fri Jul 31 17:01:25 2020] ata1.00: cmd 61/b8:b0:c8:27:94/00:00:0f:00:00/40 tag 22 ncq dma 94208 out
                                    res 41/40:b0:c8:a0:8f/00:00:00:00:00/40 Emask 0x9 (media error)
[Fri Jul 31 17:01:25 2020] ata1.00: status: { DRDY ERR }
[Fri Jul 31 17:01:25 2020] ata1.00: error: { UNC }
[Fri Jul 31 17:01:25 2020] ata1: hard resetting link
[Fri Jul 31 17:01:25 2020] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[Fri Jul 31 17:01:26 2020] ata1.00: configured for UDMA/100
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=4s
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#3 Sense Key : Medium Error [current] 
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#3 Add. Sense: Unrecovered read error - auto reallocate failed
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 0e 21 9d f8 00 01 00 00
[Fri Jul 31 17:01:26 2020] blk_update_request: I/O error, dev sda, sector 237084152 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=4s
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#18 Sense Key : Medium Error [current] 
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#18 Add. Sense: Unrecovered read error - auto reallocate failed
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#18 CDB: Read(10) 28 00 00 8f a0 70 00 01 00 00
[Fri Jul 31 17:01:26 2020] blk_update_request: I/O error, dev sda, sector 9412808 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=4s
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#21 Sense Key : Medium Error [current] 
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#21 Add. Sense: Unrecovered read error - auto reallocate failed
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#21 CDB: Read(10) 28 00 01 a5 0c 10 00 01 00 00
[Fri Jul 31 17:01:26 2020] blk_update_request: I/O error, dev sda, sector 27593744 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=3s
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#22 Sense Key : Medium Error [current] 
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#22 Add. Sense: Unrecovered read error - auto reallocate failed
[Fri Jul 31 17:01:26 2020] sd 0:0:0:0: [sda] tag#22 CDB: Write(10) 2a 00 0f 94 27 c8 00 00 b8 00
[Fri Jul 31 17:01:26 2020] blk_update_request: I/O error, dev sda, sector 261367752 op 0x1:(WRITE) lags 0x800 phys_seg 23 prio class 0
[Fri Jul 31 17:01:26 2020] ata1: EH complete
[Fri Jul 31 17:01:26 2020] Aborting journal on device sda2-8.
[Fri Jul 31 17:01:26 2020] EXT4-fs error (device sda2): ext4_journal_check_start:83: Detected aborted journal
[Fri Jul 31 17:01:26 2020] EXT4-fs (sda2): Remounting filesystem read-only
[Fri Jul 31 17:01:35 2020] ata1.00: exception Emask 0x0 SAct 0x78ffc23f SErr 0x40000 action 0x0
[Fri Jul 31 17:01:35 2020] ata1.00: irq_stat 0x40000008
[Fri Jul 31 17:01:35 2020] ata1: SError: { CommWake }
[Fri Jul 31 17:01:35 2020] ata1.00: failed command: READ FPDMA QUEUED
[Fri Jul 31 17:01:35 2020] ata1.00: cmd 60/78:70:00:70:a4/00:00:01:00:00/40 tag 14 ncq dma 61440 in
                                    res 41/40:78:00:70:a4/00:00:01:00:00/40 Emask 0x409 (media error) <F>
[Fri Jul 31 17:01:35 2020] ata1.00: status: { DRDY ERR }
[Fri Jul 31 17:01:35 2020] ata1.00: error: { UNC }
[Fri Jul 31 17:01:35 2020] ata1: hard resetting link
[Fri Jul 31 17:01:36 2020] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[Fri Jul 31 17:01:36 2020] ata1.00: configured for UDMA/100
[Fri Jul 31 17:01:36 2020] sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=6s
[Fri Jul 31 17:01:36 2020] sd 0:0:0:0: [sda] tag#14 Sense Key : Medium Error [current] 
[Fri Jul 31 17:01:36 2020] sd 0:0:0:0: [sda] tag#14 Add. Sense: Unrecovered read error - auto reallocate failed
[Fri Jul 31 17:01:36 2020] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 a4 70 00 00 00 78 00
[Fri Jul 31 17:01:36 2020] blk_update_request: I/O error, dev sda, sector 27553792 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[Fri Jul 31 17:01:36 2020] ata1: EH complete
[Fri Jul 31 17:02:10 2020] audit: type=1130 audit(1596189731.034:71): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rtkit-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'f

Offline

#8 2020-07-31 10:47:39

ondoho
Member
Registered: 2013-04-30
Posts: 638
Website

Re: Nitrogen corrupt file systems

Check health & connectivity of your disk(s).

Probably better to do this "from the outside", i.e. booting a live USB.


However studied and stilted your rant, it can never hide the base and primitve emotion that inspired it.

Offline

#9 2020-08-01 02:07:02

sonphantrung
Member
Registered: 2020-07-16
Posts: 11

Re: Nitrogen corrupt file systems

It's weird that only Xmonad got the error, while other DE didn't

Offline

#10 2020-08-01 11:37:14

ondoho
Member
Registered: 2013-04-30
Posts: 638
Website

Re: Nitrogen corrupt file systems

Are you saying you are not seeing these dmesg errors with other DE's?
Even if you use nitrogen from these other DE's?

I have a wild theory: your hard drive is broken in one very specific sector that is only accessed by nitrogen.
The recommendation from my previous posts still stands, as well as the statement that neither nitrogen nor xmonad could've caused this directly.

Instead of blaming software, you should take a long hard look at these hard drive errors and see what you can find/do about them.


However studied and stilted your rant, it can never hide the base and primitve emotion that inspired it.

Offline

#11 2020-08-02 07:35:40

sonphantrung
Member
Registered: 2020-07-16
Posts: 11

Re: Nitrogen corrupt file systems

So, what software should I use to check my drive health? Any recomendations for me?

Offline

#12 2020-08-02 09:35:29

ondoho
Member
Registered: 2013-04-30
Posts: 638
Website

Re: Nitrogen corrupt file systems

sonphantrung wrote:

So, what software should I use to check my drive health? Any recomendations for me?

Am I the only one who finds this sort of question passive-aggressive? The "So" indicating "Well, you said that I was wrong, now you fix it"? (*)

Anyhow, it's all but a web search away:
https://duckduckgo.com/?q=linux+check+drive+health
Or, to keep it local: https://wiki.archlinux.org/index.php/S.M.A.R.T.

(*) and literally 5s after I pressed reply, here's another "So". big_smile

Last edited by ondoho (2020-08-02 09:37:33)


However studied and stilted your rant, it can never hide the base and primitve emotion that inspired it.

Offline

#13 2020-08-03 02:43:29

sonphantrung
Member
Registered: 2020-07-16
Posts: 11

Re: Nitrogen corrupt file systems

I have done the short test on the live cd, I see that It passed the test. Is the short test reliable?

Offline

Board footer

Powered by FluxBB