[quote=“SGS, post:3, topic:39175”]
Check /etc/fstab for the UUID in picture.
New hard drive installed.
Try to boot from BIOS with correct drive, check with [/quote]
No, not a new hard disk.
The memory has been in use for approx. 1 year =
Crucial, sata, 2.5”, - no problems
I only have the hard disk + Garuda OS from a
defective
computer ( Lenoxo X240 , with defective usb port -
probably cold solder joints and keyboard defect ) into a Lenovo T450
rebuilt.
Had worked for 3 weeks without any problems, as already with
X times other distributions = SSD change in other hardware -
(
use a removable frame on the PC desktop with 1 x 2.5” Windows 10 OS +
a SATA SSD with Linux in alternation -
also works in the Lenovos when I rebuild )
Possible,
that the hardware change could be a problem ? But not for me
understandable,
if the computer with Garuda OS works for 3 - 4 weeks without any problems
worked -
Nothing was missing - updates made and just worked with it -
I just wonder - how can it be that the system is so capitalized?
crashes ,
so that nothing works anymore?
[quote="SGS, post:3, topic:39175"]
First try last working
[/quote]
can no longer test anything.
Can access system data with external controller
system data,
on a replacement computer or desktop computer -
But I am only a user and
have no plan,
how to install the boot loader )
partition a partition with gparted - no problem
but in the system there
fiddling around ?
Honestly, ...I have too little idea. I use over 20
years of Linux distributions,
but this crash is the over-kill for me ....where I no longer
get any further.
I've had a case like this before with Garuda, but with System
reboot again -
But I've only had similar phenomena under AntergOS so far.
and manjaro.
AntergOS was discontinued - unfortunately - after 5 years of use -
-
with Manjaro I had several system crashes, which is why
then switched to
Garuda ( Endovour-OS did not appeal to me )
But I've never had such problems with buntu, debian derivatives.
Could possibly be a Garuda system error ?
What exactly is the cause - I can not analyze now -
-
I will reinstall the system and then observe again ?
Thank you very much
best regards
Use live ISO, chroot (in the welcome app), try to update.
Maybe the update was in action when you shut down the system.
Thank you very much - That would be a solution - I have already tried with a
already tried to boot with another live USB OS -
but unfortunately unsuccessful
That would be possible that the update process has been interrupted.
has been interrupted -
I’ll have to be more careful next time
Very good tip - (I had carried out an update -)
and then the computer
shut down )
