{"action":"created","issue":{"url":"https://api.github.com/repos/archzfs/archzfs/issues/77","repository_url":"https://api.github.com/repos/archzfs/archzfs","labels_url":"https://api.github.com/repos/archzfs/archzfs/issues/77/labels{/name}","comments_url":"https://api.github.com/repos/archzfs/archzfs/issues/77/comments","events_url":"https://api.github.com/repos/archzfs/archzfs/issues/77/events","html_url":"https://github.com/archzfs/archzfs/issues/77","id":177517252,"number":77,"title":"can not boot after switching to linux-lts, linux-lts-headers and archzfs-linux-lts","user":{"login":"stevleibelt","id":2287220,"avatar_url":"https://avatars.githubusercontent.com/u/2287220?v=3","gravatar_id":"","url":"https://api.github.com/users/stevleibelt","html_url":"https://github.com/stevleibelt","followers_url":"https://api.github.com/users/stevleibelt/followers","following_url":"https://api.github.com/users/stevleibelt/following{/other_user}","gists_url":"https://api.github.com/users/stevleibelt/gists{/gist_id}","starred_url":"https://api.github.com/users/stevleibelt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stevleibelt/subscriptions","organizations_url":"https://api.github.com/users/stevleibelt/orgs","repos_url":"https://api.github.com/users/stevleibelt/repos","events_url":"https://api.github.com/users/stevleibelt/events{/privacy}","received_events_url":"https://api.github.com/users/stevleibelt/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/archzfs/archzfs/labels/bug","name":"bug","color":"fc2929"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-09-16T20:48:32Z","updated_at":"2016-09-17T10:23:31Z","closed_at":"2016-09-17T10:23:31Z","body":"Hey,\r\n\r\nAfter waiting for zfsonlinux and releaseing the next package that is supporting the linux 4.7.x, I thought it is a good idea to switch to the linux-lts kernel.\r\nWhat I did was\r\n\r\n```sh\r\npacman -Ss\r\npacman -S linux-lts linux-lts-headers\r\npacman -R archzfs-linux linux linux-headers\r\npacman -S archzfs-linux-lts\r\n#have to do this to prevent error \"failed to get canonical path of\"\r\nln -s /dev/mapper/crypt-br01 /dev/crypt-br01\r\ngrub-mkconfig -o /boot/grub/grub.cfg\r\n```\r\nI have some kind of special system setting which I will explain in the following line. I am simple following my own [notes](https://github.com/stevleibelt/General_Howtos/blob/master/operation_system/linux/arch/installOnZfsWithLuks.md).\r\nMy primary disk is splitted into three partitions.\r\nsda1 is a bios partition\r\nsda2 is the boot partition\r\nsda3 is the zfs root secured with luks\r\n\r\nThe mkinitcpio was running without any issue I could spot.\r\nWhat happens now/after a reboot is the following console output.\r\n\r\n```sh\r\nstarting version 231\r\nash: 1: unknown operand\r\nERROR: Unable to find root devide `ZFS=br01/`\r\nYou are dropped to a recovery shell\r\nType `exit` to try and continue booting\r\nsh: can`t access tty: job control turned off\r\n[rootfs ]#\r\n```\r\n\r\nWhen I try to make a \"zpool status\" I get the message \"The ZFS modules are not loaded. Try running `/sbin/modprobe zfs`.\r\n\r\nI tried to follow [this howto](https://github.com/archzfs/archzfs/issues/76#issuecomment-246949698).\r\n\r\n```sh\r\n/sbin/modprobe zfs\r\ncryptsetup luksOpen /dev/sda3 crypt-br01\r\nzpool import -R /new_root br01\r\nexec /sbin/switch_root /new_root /sbin/init\r\n```\r\n\r\nWhich results in the following output.\r\n\r\n```sh\r\nTrying to run as user instance, but the system has not been bootet with systemd.\r\n/init: line 48: mount: not found\r\nYou are now being dropped into an emergency shell:\r\n/init: line 48: can`t open /dev/console: no such file\r\n/init: line 68: stat: not found\r\nERROR: Failed to mount the real root device.\r\nBailing out, you are on your own. Good luck\r\n\r\n...\r\n\r\nKernel panic ...\r\n```\r\n\r\nI must admint, my force is not strong enough or have reached its limit. I have archiso usb stick with me (with installed archzfs), so I can do some stuff. My problem is so far, I have no idea what to do.\r\nSwitching back to the latest linux and archzfs-linux is currently not possible since there is already a new kernel around which is not supported by archzfs-linux right now.\r\n\r\nCould you give me any hint how I can fix this issue? Why is the modprobe for zfs not working? There is an entry in `/etc/modules-load.d`. Is switching to the lts kernel from the regular kernel such a bad idea?\r\nThanks in advance,\r\nstev\r\n\r\n[edit: 2016-09-16: 23:09, Europe/Berlin Time]\r\n\r\nAlso doing the follwing steps after the initial boot does not work.\r\n\r\n\r\n```sh\r\n/sbin/modprobe zfs\r\ncryptsetup luksOpen /dev/sda3 crypt-br01\r\nexit\r\n```\r\n\r\nResults in the output.\r\n\r\n```sh\r\nfilesystem `ZFS=br01/`cannot be mounted, unable to open the dataset\r\n...\r\n```\r\nSince there is nothing I can break so far, I did `zpool import br01` which results in the following output.\r\n\r\n```sh\r\ncannot mount `/`: directory is not empty\r\nexit\r\nno pools availabe to import\r\nERROR: Failed to mount the real root device.\r\nBailing out, you are on your own. Good luck.\r\n...\r\n```\r\n\r\nI think this is it for today. I am off to go to bed. Again, thanks for any kind of response."},"comment":{"url":"https://api.github.com/repos/archzfs/archzfs/issues/comments/247761643","html_url":"https://github.com/archzfs/archzfs/issues/77#issuecomment-247761643","issue_url":"https://api.github.com/repos/archzfs/archzfs/issues/77","id":247761643,"user":{"login":"stevleibelt","id":2287220,"avatar_url":"https://avatars.githubusercontent.com/u/2287220?v=3","gravatar_id":"","url":"https://api.github.com/users/stevleibelt","html_url":"https://github.com/stevleibelt","followers_url":"https://api.github.com/users/stevleibelt/followers","following_url":"https://api.github.com/users/stevleibelt/following{/other_user}","gists_url":"https://api.github.com/users/stevleibelt/gists{/gist_id}","starred_url":"https://api.github.com/users/stevleibelt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stevleibelt/subscriptions","organizations_url":"https://api.github.com/users/stevleibelt/orgs","repos_url":"https://api.github.com/users/stevleibelt/repos","events_url":"https://api.github.com/users/stevleibelt/events{/privacy}","received_events_url":"https://api.github.com/users/stevleibelt/received_events","type":"User","site_admin":false},"created_at":"2016-09-17T10:23:31Z","updated_at":"2016-09-17T10:23:31Z","body":"@demizer, I have fixed it and I guess this is nothing you could fix from your side :-). Thanks for your quick response :+1: \r\n\r\nI had an older version of my grub.cfg backup-ed $somewhere so I could do a vimdiff :-).\r\n\r\nMost important line change is.\r\n\r\n```sh\r\n #generated entry by grub-mkconfig\r\nlinux /vmlinuz-linux-lts root=ZFS=br01/ rw quiet\r\n#to this line\r\nlinux /vmlinuz-linux-lts zfs=br01 rw cryptodevice=/dev/disk/by-uuid/<uuid>:crypto-br01 quiet\r\n```\r\n\r\nSystem is up and running again, repeatable :-D.\r\n\r\nEnjoy the day."}}
{"actor":{"display_login":"stevleibelt"}}