Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: after migrating Artix to ssd system not logingin to lightdm (Read 2303 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #15 –
From lightdm log:

[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)

Reinstall package plymouth and restart lightdm. If this fails with the same error run plymouth from the command line.

artist

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #16 –
Quote from: Artist – on
From lightdm log:

[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)

Reinstall package plymouth and restart lightdm. If this fails with the same error run plymouth from the command line.

artist
install, reboot, same
no errors at lightdm log about plymoth, but system not loggging in

ps if i did rsync, and source hdd arix have no plyumoth but worked, so issue obviously not at plymoth
-=linux its buggy crap that have no antifool protection (c)=- :)
*linux is free software, and comes with ABSOLUTELY NO WARRANTY* :)
+ALL YOURS ACTIONS at Linux YOU DO at YOUR OWN RISK!+ :)

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #17 –
what this?
htop showing that lightdm is started
reinstall lightdm, lightdm-openrc, lightdm-gtk-greeter, same
-=linux its buggy crap that have no antifool protection (c)=- :)
*linux is free software, and comes with ABSOLUTELY NO WARRANTY* :)
+ALL YOURS ACTIONS at Linux YOU DO at YOUR OWN RISK!+ :)

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #18 –
no any ideas?
-=linux its buggy crap that have no antifool protection (c)=- :)
*linux is free software, and comes with ABSOLUTELY NO WARRANTY* :)
+ALL YOURS ACTIONS at Linux YOU DO at YOUR OWN RISK!+ :)
 

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #19 –
glitchy, buggy artix :)
-=linux its buggy crap that have no antifool protection (c)=- :)
*linux is free software, and comes with ABSOLUTELY NO WARRANTY* :)
+ALL YOURS ACTIONS at Linux YOU DO at YOUR OWN RISK!+ :)

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #20 –
Quote from: deepforest – on
glitchy, buggy artix :)
If you have a working Artix system on the HDD but after cloning to the SSD it isn't working then logic would suggest that you have not created an identical copy.
So maybe glitchy, buggy user error  ;)

Many of those excludes are unneeded (-x, --one-file-system will exclude the mounts anyway) and can cause unexpected results as the PATTERN format that rsync uses confuses the hell out of me. ( I believe I am not alone?)

Run your rsync command again and add --dry-run  --debug=FILTER to the options. rsync will then list all the files and dirs excluded.

While it's certainly possible to clone the rootfs of the running system you'll get more stable results by using a live iso or another install on a different partition from the one you are cloning. Otherwise you are cloning a moving target.

In one of your listed rsync commands you had /* as the source. Generally avoid that as it can cause problems (the shell globs the * not rsync). Just use / or if you've mounted the rootfs on /mnt/hdd use /mnt/hdd/

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #21 –
Why are these lines in Xorg.0.log?
Code: [Select]
[    30.172] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[    32.315] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 38 paused 0
[    32.333] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 41 paused 0
[    32.343] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 42 paused 0
[    32.355] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 43 paused 0
[    32.459] (II) systemd-logind: releasing fd for 13:66
[    32.476] (II) systemd-logind: releasing fd for 13:67
[    32.516] (II) systemd-logind: releasing fd for 13:64
[    32.530] (II) systemd-logind: releasing fd for 13:65

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #22 –
Quote from: nous – on
Why are these lines in Xorg.0.log?
Code: [Select]
[    30.172] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[    32.315] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 38 paused 0
[    32.333] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 41 paused 0
[    32.343] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 42 paused 0
[    32.355] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 43 paused 0
[    32.459] (II) systemd-logind: releasing fd for 13:66
[    32.476] (II) systemd-logind: releasing fd for 13:67
[    32.516] (II) systemd-logind: releasing fd for 13:64
[    32.530] (II) systemd-logind: releasing fd for 13:65
idk, its question to devs, at hdd all working good but at ssd not, i am not make any "criminal" things with os
-=linux its buggy crap that have no antifool protection (c)=- :)
*linux is free software, and comes with ABSOLUTELY NO WARRANTY* :)
+ALL YOURS ACTIONS at Linux YOU DO at YOUR OWN RISK!+ :)

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #23 –
Quote from: gripped – on
So maybe glitchy, buggy user error  ;)
ok, show me my where is my mistake here?

Quote from: gripped – on
Run your rsync command again and add --dry-run  --debug=FILTER to the options. rsync will then list all the files and dirs excluded.
 
i`ll try that

Quote from: gripped – on
While it's certainly possible to clone the rootfs of the running system you'll get more stable results by using a live iso or another install on a different partition from the one you are cloning. Otherwise you are cloning a moving target.
 
i did clone artix from another linux - Devuan

if you say so, this manual lie?
Quote from: Artist – on
You should use rsync to do a full disk copy:
https://wiki.archlinux.org/title/Rsync#Full_system_backup
Quote
rsync will work even while the system is running, but files changed during the transfer may or may not be transferred, which can cause undefined behavior of some programs using the transferred files. For mitigation log out all users and shut down all programs and databases.
-=linux its buggy crap that have no antifool protection (c)=- :)
*linux is free software, and comes with ABSOLUTELY NO WARRANTY* :)
+ALL YOURS ACTIONS at Linux YOU DO at YOUR OWN RISK!+ :)

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #24 –
Quote
Run your rsync command again and add --dry-run  --debug=FILTER to the options. rsync will then list all the files and dirs excluded.
Code: [Select]
root@devuan:/mnt# rsync -aAXH --dry-run  --debug=FILTER --numeric-ids --info=progress2 --one-file-system sdb3/* sdc2/
  9,044,845,321  91% 8423.67GB/s    0:00:00 (xfr#214136, to-chk=0/265281)    
root@devuan:/mnt# 
root@devuan:/mnt# cd /mnt/sdc2/
root@devuan:/mnt/sdc2# ls
lost+found
root@devuan:/mnt/sdc2#
done, destination dir is empy, it coned nothing :o
-=linux its buggy crap that have no antifool protection (c)=- :)
*linux is free software, and comes with ABSOLUTELY NO WARRANTY* :)
+ALL YOURS ACTIONS at Linux YOU DO at YOUR OWN RISK!+ :)

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #25 –
--dry run does a dry run.
I thought me using the long option would make that clear but it clearly didn't.

You are still using sdb3/* with the * on the source dir. It's a bad habit. sdb3/ as the source tells rsync to copy everything under sdb3. Adding the * just causes issues and adds nothing.

Try your command again without--dry-run .

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #26 –
i am tired fitgting with linux glitches,
if rsync did clone everything from source here problem not rsync or cp, somthing changing after cloning but what?
-=linux its buggy crap that have no antifool protection (c)=- :)
*linux is free software, and comes with ABSOLUTELY NO WARRANTY* :)
+ALL YOURS ACTIONS at Linux YOU DO at YOUR OWN RISK!+ :)

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #27 –
done
Code: [Select]
rsync -axHAWXS --info=progress2 --numeric-ids --debug=FILTER  sdb3/ sdc2/
no any warnings
reboot to ssd artix - stuck at tty login :-X
-=linux its buggy crap that have no antifool protection (c)=- :)
*linux is free software, and comes with ABSOLUTELY NO WARRANTY* :)
+ALL YOURS ACTIONS at Linux YOU DO at YOUR OWN RISK!+ :)

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #28 –
The 'destination' should be clean / empty before you copy the files. Is it ?
Or you use the --delete option.
But always do a dry run when using the --delete  option. As a typo can cause a lot of damage.

Re: after migrating Artix to ssd system not logingin to lightdm

Reply #29 –
Quote from: deepforest – on
Quote from: nous – on
Why are these lines in Xorg.0.log?
Code: [Select]
[    30.172] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[    32.355] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 43 paused 0
[    32.530] (II) systemd-logind: releasing fd for 13:65
idk, its question to devs, at hdd all working good but at ssd not, i am not make any "criminal" things with os
I don't have such lines in my Xorg.0.log, your installation shouldn't have it either. The rsync command from the Arch wiki should work. Can you start Xorg as plain user?