wouldn’t this take a lot of time? but I can see the advantage, being able to just roll back whatever happened

I’ll think about it, thank you very much!

Wow this is amazing! thank you very much for the super detailed answer! exactly what I was looking for!

This is actually very interesting! I’ll gladly look into it, thank you very much!

thanks for the reply! Yes for sure I’m backing up all the /home directory, but I’d like to preserve also important configurations like ssh, cronjob etc, but I don’t really know which directories are important for this and which are not

thanks for the reply!

How do you plan to restore if the whole drive dies?

good point: I guess if the problem is that I messed something up I may just run the backup script in reverse? if the problem is HW then I’d have to reinstall and then restore the backupped directory probably is there a “standard” way?

THANK YOU! The grep command you posted showed me that that UUID was still present in /etc/kernel/cmdline as

resume=UUID=8c53812d-ba43-45e4-b219-8d3ded8548a5

I changed it with the new one and run sudo reinstall-kernels, and now it works correctly! thank you very much for your help!

A start job is running for /dev/disk/by-uuid/8c53812d-ba43-45e4-b219-8d3ded8548a5

it’s really strange, I just noticed that it’s the UUID of… the original swap partition (now gone) the entry is still commented in /etc/fstab:

# UUID=8c53812d-ba43-45e4-b219-8d3ded8548a5 swap             swap    defaults   0 0

is there another place other than /etc/fstab where I should remove it?

thanks for the help!

EDIT: this is the whole output of sudo blkid if needed:

/dev/nvme0n1p3: LABEL="swap" UUID="506d48e6-1cc0-4136-ba55-6f2f187bcdb1" TYPE="swap" PARTLABEL="SWAP" PARTUUID="b4543e4e-4623-4317-99aa-086b0e62836e"
/dev/nvme0n1p1: UUID="467B-65A4" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="53413c1b-04f0-42cf-bd71-15e2796f002a"
/dev/nvme0n1p2: LABEL="endeavouros" UUID="cf0a3420-51e0-40ba-8b86-ae2cc576e5c1" UUID_SUB="faa47171-fc00-4435-8c8f-0b346682071d" BLOCK_SIZE="4096" TYPE="btrfs" PARTLABEL="endeavouros" PARTUUID="dc12b835-18f9-4937-8a58-07b2600012e9"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="d076884c-6236-4e0a-be36-47df3e28d7a3"
/dev/sda3: LABEL="STORAGE" UUID="6EFB-D6EF" BLOCK_SIZE="512" TYPE="exfat" PARTUUID="381ea0c9-7fdd-4a74-a92e-5b450f2001db"
/dev/sda1: LABEL="WINZOZZ" BLOCK_SIZE="512" UUID="7FC0A0D067B4D0F8" TYPE="ntfs" PARTUUID="e4d431c8-06e8-4fac-93e9-342026cc4ff1"

“it’s already installed”

Super Cool! Does it support other formats like epub, cbz etc?

I’ll try other kernels then, but I don’t know how to check if the system is actually powered off or not without waiting 8 hours and checking the battery drain XD perhaps the halt could be the key

thanks!! I’ll update the thread if I’ll discover something new

how do I check this? This is probably the source of the issue (see this comment), but I have no idea on what to do to understand the actual cause

thanks for your time and help!

update: I tried but when off (or at least “apparently off”) the USB ports are off, my phone does not charge when plugged in

okay, I think we have some news: if I kill the pc by holding the power button, after a night the battery loses 0%! so I guess the problem is that it’s not shutting down properly. I tried to sudo halt --poweroff and it drained the battery as usual. I then tried sudo halt -f and something strange happened: the screen immediately turned off, but the red LED on the volume key indicating that the volume is muted stayed on, so the pc wasn’t completely off. what could be the problem? and why does this happen only when I force the halt? could it be a kernel issue?

thanks for the help and for your time!!!

I checked and yes, there’s no cmos battery in it. Do you think this may have something to do with it?

I’ll try it as soon as I can, thanks for the suggestion! I don’t think the battery is dying, because while powered on the battery life is very good

As it should be, the battery life while in use it’s even better than my own pc

Probably there are problems with the report to the OS because the battery health is marked as 100%, which is a bit strange for a 4yo pc. Do you think this may have something to do with the battery drain?

The battery health is marked as 100%, which seems strange to me. However, the battery life while powered on is very good, so I don’t think the battery is old or exhausted. Do you think that changing the battery may be the solution?

As usual :|

I’ll have to check it out then, thanks for your help!