{"action":"created","issue":{"url":"https://api.github.com/repos/rear/rear/issues/649","labels_url":"https://api.github.com/repos/rear/rear/issues/649/labels{/name}","comments_url":"https://api.github.com/repos/rear/rear/issues/649/comments","events_url":"https://api.github.com/repos/rear/rear/issues/649/events","html_url":"https://github.com/rear/rear/issues/649","id":105609476,"number":649,"title":"wrong uuid in initrd for bootfs","user":{"login":"mattihautameki","id":14105791,"avatar_url":"https://avatars.githubusercontent.com/u/14105791?v=3","gravatar_id":"","url":"https://api.github.com/users/mattihautameki","html_url":"https://github.com/mattihautameki","followers_url":"https://api.github.com/users/mattihautameki/followers","following_url":"https://api.github.com/users/mattihautameki/following{/other_user}","gists_url":"https://api.github.com/users/mattihautameki/gists{/gist_id}","starred_url":"https://api.github.com/users/mattihautameki/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mattihautameki/subscriptions","organizations_url":"https://api.github.com/users/mattihautameki/orgs","repos_url":"https://api.github.com/users/mattihautameki/repos","events_url":"https://api.github.com/users/mattihautameki/events{/privacy}","received_events_url":"https://api.github.com/users/mattihautameki/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/rear/rear/labels/bug","name":"bug","color":"d7e102"},{"url":"https://api.github.com/repos/rear/rear/labels/support","name":"support","color":"02d7e1"}],"state":"open","locked":false,"assignee":{"login":"gdha","id":888633,"avatar_url":"https://avatars.githubusercontent.com/u/888633?v=3","gravatar_id":"","url":"https://api.github.com/users/gdha","html_url":"https://github.com/gdha","followers_url":"https://api.github.com/users/gdha/followers","following_url":"https://api.github.com/users/gdha/following{/other_user}","gists_url":"https://api.github.com/users/gdha/gists{/gist_id}","starred_url":"https://api.github.com/users/gdha/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gdha/subscriptions","organizations_url":"https://api.github.com/users/gdha/orgs","repos_url":"https://api.github.com/users/gdha/repos","events_url":"https://api.github.com/users/gdha/events{/privacy}","received_events_url":"https://api.github.com/users/gdha/received_events","type":"User","site_admin":false},"milestone":null,"comments":1,"created_at":"2015-09-09T14:34:29Z","updated_at":"2015-09-10T07:36:49Z","closed_at":null,"body":"Hi! \r\n\r\nI am having problems with the uuid of /dev/sda1 in the initrd created within the recovery process.\r\nmy setup:\r\n * SLES12 with latest patches applied\r\n * Relax-and-Recover 1.17.1 / Git\r\n * /boot on /dev/sda1\r\n * the rest on lvm with /dev/sda2 as PV\r\n\r\nI do a restore of the same machine where the backup comes from. Before the restore my disks are discoverd like this:\r\n<pre>\r\nRESCUE BLIXESX3:/dev/disk/by-uuid # ls -l\r\ntotal 0\r\nlrwxrwxrwx 1 root root  9 Sep  9 14:27 2015-09-02-16-23-48-00 -> ../../sr0\r\nlrwxrwxrwx 1 root root 10 Sep  9 14:27 ef2113b0-9341-415d-a45d-6835beae7148 -> ../../sda1\r\n</pre>\r\n\r\nAfter the restore i have strange devicelinks underneath /dev/disk/by-uuid/. Sadly the links in there are used by the systemd in the initrd. \r\n\r\n<pre>\r\nRESCUE BLIXESX3:/dev/disk/by-uuid # ls -l\r\ntotal 0\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 0e7135a4-1606-443c-99c5-064a03f26932 -> ../../dm-3\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 0fcf1353-0909-4423-a88f-c00f5272b6ab -> ../../dm-3\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 128f2ecd-a000-46f6-933f-2b6661458544 -> ../../dm-1\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 14208f02-35c0-47cd-8201-c1fd12042f68 -> ../../dm-6\r\nlrwxrwxrwx 1 root root  9 Sep  9 13:20 2015-09-02-16-23-48-00 -> ../../sr0\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 47378618-9b36-4a4e-8d5a-195a6e0e4e8a -> ../../dm-1\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 5907f02a-b6e4-4729-82e3-a234ebea3fea -> ../../dm-8\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 5f5c8f2a-789f-43b4-ae84-f7c737a3c2e9 -> ../../dm-4\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 641a1c07-3107-43e5-b458-5afcf288562c -> ../../dm-2\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 81cc7d96-07c2-4518-a036-9c1c37d9a0ec -> ../../dm-4\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 83da97b5-5b9c-40aa-bf6e-1caaad73b2b2 -> ../../dm-5\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 a99b81a7-90b5-45e2-8816-352f9cdd9097 -> ../../dm-0\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 bc597625-8240-45c7-a389-d5abae9cb5ef -> ../../dm-8\r\n<b>lrwxrwxrwx 1 root root 10 Sep  9 13:20 c9227301-e341-47df-970f-46f786beead8 -> ../../sda1</b>\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 d5f49f17-21c6-4415-9a1b-a496ef5fee88 -> ../../dm-2\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 ed9f0cef-ef0f-4640-b7ae-73811d5162d2 -> ../../dm-6\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 f0811e55-82a6-41d7-85ed-fa3231c5105c -> ../../dm-0\r\nlrwxrwxrwx 1 root root 10 Sep  9 13:20 f5729f73-47dc-4bed-8671-6e4e8a8465a8 -> ../../dm-7\r\n</pre>\r\nI don't know why there are 2 links for every dm-file. But in my opinion the link for **/dev/sda1** should match the output of blkid:\r\n<pre>\r\nRESCUE BLIXESX3:/dev/disk/by-uuid # blkid /dev/sda1\r\n/dev/sda1: UUID=\"<b>ef2113b0-9341-415d-a45d-6835beae7148</b>\" TYPE=\"xfs\" PARTUUID=\"000dc137-01\"\r\n</pre>\r\nThis is also the uuid which is defined in disklayout.conf and according to the logfile, the creation of the xfs filesystem on /dev/sda1 works without errors.\r\n<pre>\r\nRESCUE BLIXESX3:/var/lib/rear/layout # cat disklayout.conf | grep sda1\r\npart /dev/sda 270532608 1048576 primary boot /dev/sda1\r\nfs /dev/sda1 /boot xfs uuid=ef2113b0-9341-415d-a45d-6835beae7148 label=  options=rw,relatime,attr2,inode64,noquota\r\n</pre>\r\n\r\n\r\nThe problem is that the generated initrd searchs for the disk **c9227301-e341-47df-970f-46f786beead8** and therefore the restored system won't boot. \r\n\r\nchrooted to /mnt/local/\r\n<pre>\r\nBLIXESX3:/ # lsinitrd | grep \"initrd.target.wants/dev\"\r\nlrwxrwxrwx   1 root     root           78 Sep  9 15:22 etc/systemd/system/initrd.target.wants/dev-disk-by\\\\x2duuid-c9227301\\\\x2de341\\\\x2d47df\\\\x2d970f\\\\x2d46f786beead8.device -> ../dev-disk-by\\\\x2duuid-c9227301\\\\x2de341\\\\x2d47df\\\\x2d970f\\\\x2d46f786beead8.device\r\n</pre>\r\n\r\nThe expected result would be a unitfile for ef2113b0-9341-415d-a45d-6835beae7148 in the initrd.\r\nAs a workaround I can again reboot the system with to rear iso, mount all the filesystems and recreate the initrd with dracut. this way the correct unitfile is created. \r\nIf its a bug maybe it is fixed in 1.17.2 but I didn't find anything that sounds related to me. \r\n\r\nPlease excuse my bad english! "},"comment":{"url":"https://api.github.com/repos/rear/rear/issues/comments/139145225","html_url":"https://github.com/rear/rear/issues/649#issuecomment-139145225","issue_url":"https://api.github.com/repos/rear/rear/issues/649","id":139145225,"user":{"login":"gdha","id":888633,"avatar_url":"https://avatars.githubusercontent.com/u/888633?v=3","gravatar_id":"","url":"https://api.github.com/users/gdha","html_url":"https://github.com/gdha","followers_url":"https://api.github.com/users/gdha/followers","following_url":"https://api.github.com/users/gdha/following{/other_user}","gists_url":"https://api.github.com/users/gdha/gists{/gist_id}","starred_url":"https://api.github.com/users/gdha/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gdha/subscriptions","organizations_url":"https://api.github.com/users/gdha/orgs","repos_url":"https://api.github.com/users/gdha/repos","events_url":"https://api.github.com/users/gdha/events{/privacy}","received_events_url":"https://api.github.com/users/gdha/received_events","type":"User","site_admin":false},"created_at":"2015-09-10T07:36:49Z","updated_at":"2015-09-10T07:36:49Z","body":"@mattihautameki I am trying to understand where the `c9227301-e341-47df-970f-46f786beead8 -> ../../sda1` is coming from. Did you check the rear.log after the recovery?\r\nIf I understand it well in the savelayout file and before the recovery the UUID was the correct one (`ef2113b0-9341-415d-a45d-6835beae7148`)? Therefore, we need to find out why the UUID was changed after recovery? Was it forced somehow?"}}