Hi @singofy,
This whole thing smells like some kind of hardware failure. Probably a disk drive or something.
At the moment I can’t think of anything other than SMART tests…I don’t know how many disks you’ve got in there, but:
I’m presuming two. So boot into a live environment, and run a smart test on each of your disks:
sudo smartctl --all </path/to/disk>
Where, and this is important, </path/to/disk>
is the path to the disk (e.g.: /dev/sda
) and not the partition (e.g.: /dev/sda2
).
It is also possible to get system logs from a chroot
environment if that doesn’t reveal anything.
How to chroot
-
Ensure you’ve got a relatively new ISO or at least one with a still supported LTS kernel.
-
Write/copy/
dd
the ISO to a USB thumb drive. -
When done, boot with the above mentioned USB thumb drive into the live environment.
-
Once booted, open a terminal and enter the following command to enter the
chroot
encironment:
manjaro-chroot -a
- If you have more than one Linux installation, select the correct one to use from the list provided.
When done, you should now be in the chroot
environment.
But, be careful, as you’re now in an actual root environment on your computer, so any changes you make will persist after a restart.
To get the logs, run the following there, in the chroot
environment:
journalctl --priority=warning..err --no-pager --boot=-1
Where:
- The
--priority=warning..err
argument limits the output to warnings and errors only; - and the
--no-pager
formats the output nicely for use here, on the forum; - the
--boot=-1
argument limits the output to log messages from the previous boot. This can be adjusted to-2
for the boot before that,-3
to the boot before that, and so on and so forth. I’m guessing for you it’d be-1
.
Provide the output here if you wish for us to have a look.