Booting into some kind of log instead of GUI

no need

the line usually starts with linux /vmlinuz… and ends with ro
next comes
initrd

before
initrd
after the last item on the prior line

Yes after the last item before the initrd line but theres udev.log_priority=3 before the 1
So it is as follows
… rw udev.log_priority=3 1

I can see the journal now while in chroot they stop right after the problem happen i can see that theres errors but i dont know what to look for

that is the correct place - although my line looks different
but I did edit it to be different :wink:
mine is:
mitigations=off udev.log_priority=3 ro
and I would put the 1 after that
then CTRL-X or F10 to boot

1 Like

yes no problem there then, wonder if i can timeshift from chroot :grinning_face_with_smiling_eyes:
edit: oh wait i can do this from the gui hope this works :crossed_fingers:

any error - when in doubt:
all of them, one by one :wink:
the first one is probably the best candidate

you should be able to copy/paste
from the terminal in the live system you chrooted from …

please format as code
the
</> button …

i am trying the easy way out by using timeshift haha
if that doesnt work ill list what errors i found

so you don’t want to know the cause?
fair enough :wink:

it is indeed intresting and would love to know what the hell caused this… but i dont want to be tortured by using windows tomorrow :laughing:

time to find out whether your timeshift backup restoration procedure works, then :crossed_fingers:

1 Like

Yep back up and running flawlessly, probably some system files were corrupted, yes it sucks that i wasn’t patient enough to figure out the cause…logs were overwrited by the timeshift don’t think we can know now.
Thank you everyone for helping out.
Summary:
Booted to live manjaro boot used the timeshift gui and restored the manjaro installation on my disk to an earlier snapshot and booted it.

Thanks alot for the info you provided been a huge help :+1:

anytime

good on you :ok_hand:

1 Like

The OP (@vermillion ) eventually restored from a timeshift backup he/she had - so we don’t know what was the cause.
But you may use the info here to look for it.
Or open a new thread with all the info you have got re your issue. :wink:

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.