[solved] issues after cloning an arch installation

quiqueck · 2014-02-03 17:34:19

After moving an existing arch-installation to a new SSD, the Monitor turns off when kdm starts and leaves black. It shows only the message "No Signal" and the LED turns to orange.

Changing to a virtual terminal turns the Monitor on. Now i can log in but the System is very slow. top shows a huge amount of processorusing of the process systemd (50%). Changing the virtual console to tty7 shows a misconfigured graphic. Sometimes it shows the loginmanger, but mostly there is nothing to see but colors...

Disabling kdm, restart, log-in to terminal, and then "startx" works fine. KDE starts up and there are no problems. If i start kdm from terminal ("sudo kdm") it looks fine too.

journalctl shows some strange errors:

Feb 03 17:53:33 kaputtnik-arch kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
[...]
Feb 03 17:53:40 kaputtnik-arch kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb 03 17:53:40 kaputtnik-arch kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!!
Feb 03 17:53:40 kaputtnik-arch kernel: [drm:evergreen_startup] *ERROR* radeon: error initializing UVD (-1).

These errors occur only, if kdm is enabled.

Graphiccard and Driver:

$ lspci -k | grep -A3 VGA
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]
        Subsystem: ASUSTeK Computer Inc. Device 03ca
        Kernel driver in use: radeon
        Kernel modules: radeon[/quote]

I have tried a lot, like reinstalling some packages as: ati-dri, kdebase-workspace (which contains kdm) and xf86-video-ati. I checked all packages if they are complete with
[quote]
sudo pacman -Qk

all ok.

If i boot the other arch-installation from HDD, which is as up to date like the SSD-Copy, kdm starts without any errors.

Any ideas?

Last edited by quiqueck (2014-02-05 08:16:53)

init0 · 2014-02-04 16:35:59

Did you use cp? Did you use it proper?
It's always a good idea to use the --archive flag when cloning /

ewaller · 2014-02-04 16:46:12

I gather that init0's concern is permissions and ownerships. He is probably correct.

How did you clone the system? Did you image it? Did you copy files using cp or rsync? If you copied an entire file system, how did you deal with meta files (/dev, /sys, /tmp, /proc)? Did you get all of the hidden files? etc....

quiqueck · 2014-02-04 20:20:40

ewaller wrote:

How did you clone the system?

I am using rsync like:

sudo rsync --stats --progress --numeric-ids -aAhHSP /opt /mnt/

I copied each Root-folder to the SSD-Root which was mountet on /mnt.

If you copied an entire file system, how did you deal with meta files (/dev, /sys, /tmp, /proc)?

For these Folders i do not rsync'ed the entire folder, created only the Folder. But maybe i have rsync'ed some of them :[]

Hidden files are copyied.

Maybe its a better idea, to rsync an existing arch-installation from a Live-System from one partition to another. So the meta files don't worry...

Any chance to correct the problem without a live-System?

Am i right, that the these meta files (folders like /proc) are empty if the OS is not running? So i could:

- boot from arch-linux-SSD and make a folder tree from the not running arch-installation-HDD
- boot from arch-linux-HDD and compare the folder tree with the arch-Linux-SSD

quiqueck · 2014-02-04 22:03:44

Hey guys, i did it

As mentioned:

quiqueck wrote:

- boot from arch-linux-SSD and make a folder tree from the not running arch-installation-HDD
- boot from arch-linux-HDD and compare the folder tree with the arch-Linux-SSD

I bootet the SSD-System, mounted the HDD-System on /mnt and made a folder list with:

sudo du -d 2 /mnt > folders.txt

This makes a folder list whith all Folders and one subfolder. It looks like (snippet):

4	/mnt/dev
4	/mnt/var/games
25052	/mnt/var/log
4	/mnt/var/local
4	/mnt/var/empty
229084	/mnt/var/cache
4	/mnt/var/opt

The first number tolds me wich folder is empty. 4=empty folder (I know that is somtimes not really true, because little files are stored sometimes in the inode itself, but for my test it would be enough info)

Then i startetd the HDD-System, mounted the SSD-System and compares the Folder. Uh, i've made some mistakes while cloning the HDD-System I rsync'ed to much... I deleted the contents of the folders, wich must be empty and start the SSD-System. It seems to be that i deleted not nessesary things . Enabling kdm and restart the system: tadadaa. Kdm shows up :-)

Many thanks for responding to my question :-)

Would like to mark this as [solved], but the title of the thread seems to be to long. I could only add "[solved]" when i delete some other charakters of the title. What to do?

Last edited by quiqueck (2014-02-04 22:08:51)

ewaller · 2014-02-04 22:24:05

quiqueck wrote:

Would like to mark this as [solved], but the title of the thread seems to be to long. I could only add "[solved]" when i delete some other charakters of the title. What to do?

Don't sweat the small stuff. If the title is more important than the [SOLVED], leave it be. It is up to you. Glad it is solved.

quiqueck · 2014-02-11 10:21:17

The solved-mark was too soon. After a day without any problems the show begun again. From boot to boot different errors from X-server. Sometimes it works, sometimes not. So i thought there is somthing wrong with the SSD-HD or with the SATA-Cable. Changing the SATA-Cable and the next boot runs fine. But it worked not at all. So i exchanged the SSD-HD... Cloning the existend system with rsync as described here. Booting from SSD the errors are the same. The only thing what works allways, was to disable kdm, login to console and run startx ....

I noticed while booting, that the Monitor "switches" 3 times (short flickering and changing resolution):
1. While kernelmessages runs
2. at loginprompt
3. at kdestartup
and i stumble over the message in ~/.xsession-errors:

xrandr: cannot find mode 1680x1050

But this is my prefered resolution and runs fine with the Desktop. Curious. After starting the xserver xrandr shows this resolution too.

So i decided to investigate the graphic system and kms. As described i edited the /etc/mkinitcpio.conf and rebuild the kernel images. Now the flickering at Boot is gone and kdm shows up.

I hope, that this the solution to correct the strange errors ... i will see tomorrow ...

Could it be, that the SSD runs to fast that kms switches the resolution just in time as kdm will show up (see "flickering" #2) and of this it runs in those strange errors? Fell free to post your opinion.

Arch Linux

#1 2014-02-03 17:34:19

[solved] issues after cloning an arch installation

#2 2014-02-04 16:35:59

Re: [solved] issues after cloning an arch installation

#3 2014-02-04 16:46:12

Re: [solved] issues after cloning an arch installation

#4 2014-02-04 20:20:40

Re: [solved] issues after cloning an arch installation

#5 2014-02-04 22:03:44

Re: [solved] issues after cloning an arch installation

#6 2014-02-04 22:24:05

Re: [solved] issues after cloning an arch installation

#7 2014-02-11 10:21:17

Re: [solved] issues after cloning an arch installation

Board footer