support, update, problem, kernel 5, issues

Proteus

[deleted]
Ok, ran these commands in terminal. No errors. Is this persistant so it keeps this after reboot?
If I want to turn it all on again? True on the second I guess. But the first?
I'll test and see what happens.

[deleted]

Proteus The crawling interval is -1 and enable-monitors is true by default. Yes, it's persistent

Proteus

dbarron
It could be a bad drive. I know it is old. BUT, I did not have these issues with the previous version of Solus and kernel 4.20.

[deleted]

Proteus Install GSmartControl, select your drive and view it's details. And if possible post a screenshot of the Attributes section

Proteus

[deleted]

Proteus

[deleted]
Does it have any real negative side effects if you turn it off?

[deleted]

Proteus Is that your system drive? Looks ok to me

Proteus

[deleted]
The drive is my /home drive.
But the more I think about it things start to look like there is something in this. Bits of info here and there and they all point in the direction of the drive. It may not be faulty but it could be beginning to become faulty. It's temp has gone up and that could mean a bad motor and/or spinup. Also it is awfully often checked by the journaling system. ALOT more compared to the other drives. So I think it might be prudent to do a full re-install with new drives (which was in the plans anyway). I hope this is not going to pop back up after that (but then I will have newer drives and /home will be re-located to an SSD).

[deleted]

Proteus Can you show the system drive too?

Proteus

But I still wonder how you do a rollback via the history system in eopkg and excluding a package which do no longer exist in the repo?

Proteus

[deleted]

Proteus

[deleted]
I've just posted a short channel update on my twitch account. I'm now going into recovery mode. I will copy all data and then change both the system SSD and also put /home on a another SSD. Then install it all. I had plans doing this anyway but perhaps not so soon ;-)

otavioschwanck

Proteus if you boot with 4.20, problems persist?

Proteus

otavioschwanck

otavioschwanck
I have 4.20 activated in grub but when I try to boot from that option it does not seem to work. I think it might have something todo with drivers being installed to support current kernel version. It does not matter really. I needed to do this anyway. It is just a bit earlier. But next install will be locked to the LTS version just in case ;-)

otavioschwanck

Proteus try the update-grub. You use uefi or legacy?

If legacy, run sudo update-grub

Proteus

otavioschwanck
My mainboard have a few years on its back. So legacy only bios. 🙂

Proteus

otavioschwanck
OK, I've run the command. It said:
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Then it finished with what I assume a ready job.

Proteus

Long selftest has not revealed any warnings or issues with my drive. I've updated grub and will now reboot and try booting into kernel 4.20.

otavioschwanck

Good luck!

nodq

Do you have any other drive to test your system on? You could do an image with Clonezilla for example and install it on another drive and see if the problem persists. And it would take less time than anything else. And if the problem does persist, then you know it is not the drive.

Proteus

nodq
Yeah, I thought about that too. But honestly, since I had plans on re-doing the system anyway this is a better solution. It just happens earlier than I planned. The old drives will be demoted to long time media storage instead. My usual procedure.

« Previous Page Next Page »