Issue that Brought this Up:

I was trying to read a regular libre office file I had created recently on fedora 35. I had just upgraded the system to fedora 36.

The file seems to be corrupt or it simply wouldn't open - with a different extension than what one would expect.

So, I decided to do some checking of the filesystem.

Started Running a Number of Commands at CLI:

First, wished to do some lvm scans:

# lvm pvscan
File descriptor 16 (anon_inode:inotify) leaked on lvm invocation. Parent PID 30431: bash
File descriptor 40 (/memfdulseaudio (deleted)) leaked on lvm invocation. Parent PID 30431: bash
File descriptor 50 (anon_inode:inotify) leaked on lvm invocation. Parent PID 30431: bash
File descriptor 105 (/memfdulseaudio (deleted)) leaked on lvm invocation. Parent PID 30431: bash
PV /dev/nvme0n1p2 VG vg_q-trak lvm2 [605.37 GiB / 4.00 MiB free]
Total: 1 [605.37 GiB] / in use: 1 [605.37 GiB] / in no VG: 0 [0 ]

Next tried to look at the boot messages: (Found some errors here)

# dmesg |less

memstrack.service - Memstrack Anylazing Service was skipped because all trigger condition checks failed.

It would seem that memstrack is a useful tool to analyze memory - but I have absolutely no clue what it does.

Not Sure What to Do:

At this point, I've discovered all these issues, but, I am not sure how to proceed. They could all be related - but they might not be.

Looking for Suggestions:

I am looking for suggestions - right now I feel like I am running in circles trying to find what is wrong, with no clue as to where any of this is originating from.

If you have memory problems it can make LVM or filesystems look bad, so start with the memory issues. Conventional PC distros may have memtest86 as a grub option. If not, boot a live distro that does, or swap in known good memory. Once you know the memory works you can look at the disk.

Hi Smallpond,

Thank you so much for that information - I will definitely try that - although I am out of town at the moment - so, it'll end up waiting till after July 4rth.

- 6th

You might want to boot to a live media then run fsck on all the linux file systems just in case.

Also as noted, memtest86 is a good tool.
If errors are seen then removing and reinstalling the chips may give a clean contact whereas older connections can become oxidized and flaky.

1 members found this post helpful.

Hi computersavvy,

Thank you for that.

I have a new laptop and I tried to open a slightly older one to repair it and I ended up toasting the ribbon cables to the keyboard - so, now that Laptop's keyboard is working with some keys that are not recognized.... I am not confident in opening my own laptop for that reason (It is a Thinkpad P53s - bought in 2019, with 8th generation Intel core i7, 24 GB RAM, and a 1 TB SSD, a 2GB nvidia P520).

Not sure if I should take it to the hardware guys - but, I will try from a software perspective first - and then, if I can't get it to work properly - I will have the hardware guys reseat the RAM and the wifi card.

- 6th