[arch-general] gummiboot kernel panic: unable to mount root fs
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I haven't seen this one for a while--a long while. I assume it still means what it used to mean, that is, that I haven't correctly specified the root partition. gummiboot is proving to be a bit of an adventure on this Asus X202E. The gummiboot install command failed to create the boot loader entry, so I was grateful that the Arch Wiki page on UEFI had not yet been updated to eliminate the explanation on how to create the entry using efibootmgr. What gummiboot install *did* do seems a bit strange--particularly as it still works according to the old way as documented in the Arch Wiki page on gummiboot--on my desktop system. It created a loader.conf with a timeout of 3 and a default with a moderately long hex string appended with a '-*'. There are no corresponding entries in the entries subdirectory. The hex string does not appear to correspond to any PARTUUIDs on the system. I commented that out and set it up the old way as documented on the Arch Wiki page, and when that didn't work, discovered that I needed to use efibootmgr. Now the BIOS--or whatever it's supposed to be called these days--sees the Gummiboot option at least as a possible override, but when selected, I get the kernel panic mentioned in the subject. I'm not quite sure what the best way to proceed is at this point. I think I'm awfully close to having it working, but it *is* EFI, and so far, that's always an adventure. Thanks! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRaa3nAAoJELJhbl/uPb4S2w8P/2r2fuUa85pXIjNuQ4+XHbJR NoeqjdcwT+/xlaAsLDh4c9hrcdX+5l4hPvMSib8pJAZWTY+AkUZ52w/t02FC5+hH Djw5e/jidbSCgR72xR2sKZzzqkQvv1WjxMwaayPlK8BTCuQprC3cGyhjTSIOKhXN Xs1w5ZWyOt01J6Chb4KLPFyBEKafxb/0BUgJLrG3i8q+X97BoX2nmjhPB5hGCmZx LCamvBG7pVGwMfikEzkcFl7ASc8YZGlHzGiIfey1SjabXA6xLLTdI8rsNJTuEYvq 34rAMkVozNo5rCyTQU7tJTsg8pA42AL+nrAAmNLDDRKUeEkXryP/gCN7WyzA++Dd y5x7MozO6CUiNcLcpc7ktkye7R/3TO0fGT1LDXrHIT8khRgz4vShvUuEJd5lGuUj bC0R2VXxke/wY3oI3KC3/ZEEqty0ceSCMWisoCNgYqRKjSYyJJV77nBWlVRsvmmI KkPIdIUrtjWCkrksQp8arQhuHc56kl+jr6lc3fIrDTXEZ94vf7dadKGWGS0YamyI BUCnNKFWinqblsl5b5uP4h9nIDOXwndy6PM58heJwwOc1U+M4iGEjBREBsQ3wsAK XZrGvc7LN6t+GlbzKL0qmAes2hvd/emlPo+cahgNEdx3q2A9Sds4VMrzbFfAN97l kv/HOERo0mZW1KH3mnwo =W177 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/13/2013 12:11 PM, David Benfell wrote:
I'm not quite sure what the best way to proceed is at this point. I think I'm awfully close to having it working, but it *is* EFI, and so far, that's always an adventure.
I decided to try rEFInd. It at least gets me someplace a bit different. As near as I can tell it's bombing out while in the initial ram disk. After having mounted the correct partition as root for the ram disk (I can tell by typing 'mount' in the shell it drops me to), it doesn't know what device it should mount as real root. According to the error message, the device is set to '' (yes, apparently null). It drops me to a shell, and if I just exit, that's when it tells me that it's trying to mount '' as real root. Which sounds like a similar problem to what I was seeing with gummiboot, but without the kernel panic. So what needs to be told what where? Thanks! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRafLvAAoJELJhbl/uPb4Se7MP/jySjjpnxUpEx+ypZMnlzjEx OCizYy516XWt3pVq+WgFWf90k5LI2NIxk72m3L6jtEQDGq+RQejlETLObC6qhQ2W WrhhlZrAHQzaQNxMkK9Sw4uHA7bWXc6v/+AeP4BAoFAtUn1vDvVluSlgTuzfGn5o mwZpddgNoCyvzia9KxjoUR+NB/ctgy6Td3gU3AsaCi4tI3STtKbLJ2+vtakK407q N59UszVYeM1mXPVXRW133PmdVnxRXDJTxHwPgYjwL+7wAsQG1hfmPZDyris/31ze HhtT43hWK4B1V08PNwwrGy6BncyjzxkLoRMeByjU6R6ZJIsKoZzgg2WFMzcQKoXN TAW0bNzKe1sfWkVlAXrkFSaHEQWltqA0wbNp3HyLI6BoFdTQTrCBb+/JtxRM+Qx3 KGpQLQEM2sDU3o+/9hfY/bRWLy6Y02DcbmcPS4Az99G9y5qDyQmBTlf/q+4uc1G2 pXmlK48OR3va8f9yKxMvt20woelFbXg9oae7cvSoClbOfvkQfLu1IAWUx4UulXZJ DInYCFtpVbuF1dHp5W3Ge8MmDdmLI515RUEeeNEsyrcIqjgVye2epZ1FeNQwEGS7 epr7KhJ8CrXbFty7wDv+DyiumX5bc7+kg0qZ2uW68KndKWu6iJvNgJDZ9G/PIXj9 axVUucT/CIMPegQxX/vt =Pul8 -----END PGP SIGNATURE-----
Hi David, I have EFI working on an ASUS mobo so maybe I can help. What does you arch.conf look like. Sounds lilke that is where the problems could be. -- Thanks, Dennis
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Dennis, On 04/13/2013 08:28 PM, Dennis Anderson wrote:
Hi David,
I have EFI working on an ASUS mobo so maybe I can help. What does you arch.conf look like. Sounds lilke that is where the problems could be.
Here it is, along with a directory listing of the PARTUUIDs (sorry for linewrap): graton2% ssh 192.168.1.224 bridge-live% sudo -s bridge-live# cat /boot/loader/entries/arch.conf Title Arch Linux linux /vmlinuz-linux initrc /initramfs-linux.img options root=PARTUUID=d5bb2ad1-9e7d-4c75-b9b6-04865dd77782 bridge-live# ls -l /dev/disk/by-partuuid total 0 lrwxrwxrwx 1 root root 10 Apr 15 19:26 0ab4d458-cd09-4bfb-a447-5f5fa66332e2 -> ../../sda6 lrwxrwxrwx 1 root root 10 Apr 15 19:26 3e12caeb-1424-451c-898e-a4ff05eab48d -> ../../sda7 lrwxrwxrwx 1 root root 10 Apr 15 19:26 432a977b-f26d-4e75-b9ee-bf610ee6f4a4 -> ../../sda3 lrwxrwxrwx 1 root root 10 Apr 15 19:26 95a1d2c2-393a-4150-bbd2-d8e7179e7f8a -> ../../sda2 lrwxrwxrwx 1 root root 10 Apr 15 19:26 a4b797d9-0868-4bd1-a92d-f244639039f5 -> ../../sda4 lrwxrwxrwx 1 root root 10 Apr 15 19:26 d5bb2ad1-9e7d-4c75-b9b6-04865dd77782 -> ../../sda8 lrwxrwxrwx 1 root root 10 Apr 15 19:26 ed04135b-bd79-4c7c-b3b5-b0f9c2fe6826 -> ../../sda1 lrwxrwxrwx 1 root root 10 Apr 15 19:26 f64f82a7-8f2b-4748-88b1-7b0c61e71c70 -> ../../sda5 The root partition is supposed to be /dev/sda8, that is: lrwxrwxrwx 1 root root 10 Apr 15 19:26 d5bb2ad1-9e7d-4c75-b9b6-04865dd77782 -> ../../sda8 So the correct PARTUUID followed by the one I have specified in arch.conf is: d5bb2ad1-9e7d-4c75-b9b6-04865dd77782 d5bb2ad1-9e7d-4c75-b9b6-04865dd77782 Thanks! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRbFeuAAoJELJhbl/uPb4SmlYP/isv/CnHmy517lD2pbgIshvf LrAOHpVq7slUEEAqMdZXBKQNYUGitTcniKLLFRHAQu1mqRBXz3ht1nzW2Fz0fzRn k/KsU42iSJC9hv1TEwpC9P5BJkJhydEUSakT7yD3/V2dAYNczZU+cBlLfoFUkGJ0 FZtskMEqn2+fYNxFvaAQ9zF7F5SboZ5ZhazAdvK5ihuTxdE+vc8cMlZ4BB+9Xu+e o6UN1lxaZVzSy8T6dhieONSyPOz+8/K2E9jezvgjZAXnz4Ws9p5pqCJ+YUEC27MQ VIVRwIJ6Q9uveVUq0DqTwExWSr0n6Yp/A1Il8c1tVNvQLyMkA35W/wWH5hBE7UaQ se7Sab09mdyjXzanRNbcr2RGp0PS86npGe6cycub9MS1FbwtUh/XEn1yGnnrtGbn Z0tSEUVtNF6nfRoHVGIyVBS0jlusjHkw+Vdbed0kTpila7rZBnSX8nJHX3noRQCI zmvPz5Rv1oESFKKGQhCtvzkB2XyDMSigX7H3slZVccjuHSDWW4+w+msjNrBAGO2Z fCTIoF7o/FO/+F/LIxQdO5LGMHj8Chkmp8unsEp1DU2enhSF9KQokT0PmfpoMmFP easlShwzD2iQuRLBte7oLYypOFuJ9i2vQR6XuF6+pkj98+uDh3sKUt6MlVSctIcI O8WglFCReoNDTucd9m3i =CFjd -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 15.04.2013 21:40, schrieb David Benfell:
Hi Dennis,
On 04/13/2013 08:28 PM, Dennis Anderson wrote:
Hi David,
I have EFI working on an ASUS mobo so maybe I can help. What does you arch.conf look like. Sounds lilke that is where the problems could be.
Here it is, along with a directory listing of the PARTUUIDs (sorry for linewrap):
graton2% ssh 192.168.1.224 bridge-live% sudo -s bridge-live# cat /boot/loader/entries/arch.conf Title Arch Linux linux /vmlinuz-linux initrc /initramfs-linux.img options root=PARTUUID=d5bb2ad1-9e7d-4c75-b9b6-04865dd77782 bridge-live# ls -l /dev/disk/by-partuuid total 0 lrwxrwxrwx 1 root root 10 Apr 15 19:26 0ab4d458-cd09-4bfb-a447-5f5fa66332e2 -> ../../sda6 lrwxrwxrwx 1 root root 10 Apr 15 19:26 3e12caeb-1424-451c-898e-a4ff05eab48d -> ../../sda7 lrwxrwxrwx 1 root root 10 Apr 15 19:26 432a977b-f26d-4e75-b9ee-bf610ee6f4a4 -> ../../sda3 lrwxrwxrwx 1 root root 10 Apr 15 19:26 95a1d2c2-393a-4150-bbd2-d8e7179e7f8a -> ../../sda2 lrwxrwxrwx 1 root root 10 Apr 15 19:26 a4b797d9-0868-4bd1-a92d-f244639039f5 -> ../../sda4 lrwxrwxrwx 1 root root 10 Apr 15 19:26 d5bb2ad1-9e7d-4c75-b9b6-04865dd77782 -> ../../sda8 lrwxrwxrwx 1 root root 10 Apr 15 19:26 ed04135b-bd79-4c7c-b3b5-b0f9c2fe6826 -> ../../sda1 lrwxrwxrwx 1 root root 10 Apr 15 19:26 f64f82a7-8f2b-4748-88b1-7b0c61e71c70 -> ../../sda5
The root partition is supposed to be /dev/sda8, that is: lrwxrwxrwx 1 root root 10 Apr 15 19:26 d5bb2ad1-9e7d-4c75-b9b6-04865dd77782 -> ../../sda8
So the correct PARTUUID followed by the one I have specified in arch.conf is:
d5bb2ad1-9e7d-4c75-b9b6-04865dd77782 d5bb2ad1-9e7d-4c75-b9b6-04865dd77782
Thanks!
Hi, Dennis, you didn't forget to replace 'sata pata scsi' etc. by 'block' ? That was my fault a few months ago shortly before an update of the kernel. In result, the bootimage couldn't find any harddisk installed. Maybe your problem is not related to gummiboot ... Kind regards, Nelson. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRbFkmAAoJEL11/FaGDdNAPwIIAK+eTwTEwKtFqlvr/A2l+Op/ 0HGCjSiT8ilyXJButsMcKb/9nBtMl4vV9dy0HCyt7Fkeppde6vCsNSnheOYvWuzJ 1x06JGoEv+s2xphfHioLFurlyjNNoV2N2NSs51TLksyeMNsz4Kzo6DZJgV/SW+SV SkUA54DWx++Bkb4yVoUlN1bsJRCnOlEGJVkmGtiLpxY1XJmdPiegpgip7LZV8vnz 1b7daIFOyWacyRKqh4YnZqF3JvT9ODC6gi+vsDtn+R0FtU68lIYnay5/p1sYRq9k tpWFtLFvOYWK4O4l56oDppCmnAoh8b70IaAS8ZdtJpcdYg8v7kshPLSvT7hAW80= =+y3Y -----END PGP SIGNATURE-----
On Mon, Apr 15, 2013 at 09:46:46PM +0200, Nelson Marambio wrote:
Hi, Dennis,
you didn't forget to replace 'sata pata scsi' etc. by 'block' ? That was my fault a few months ago shortly before an update of the kernel. In result, the bootimage couldn't find any harddisk installed.
Maybe your problem is not related to gummiboot ...
I actually followed the direction in the Arch wiki for debugging boot problems, which said to remove the configuration file you're referring to (sorry, not remembering the name at the moment) and reinstall that package, along with linux and udev with pacman -Syyu. So I'm actually working with the default configuration that comes with the most recent version of that package. No joy. Thanks!
On Mon, Apr 15, 2013 at 5:07 PM, David Benfell
On Mon, Apr 15, 2013 at 09:46:46PM +0200, Nelson Marambio wrote:
I actually followed the direction in the Arch wiki for debugging boot problems, which said to remove the configuration file you're referring to (sorry, not remembering the name at the moment) and reinstall that package, along with linux and udev with pacman -Syyu.
So I'm actually working with the default configuration that comes with the most recent version of that package.
No joy.
Thanks!
Well gummiboot looks OK, default mkinitcpio seems OK, (you did run mkinitcpio -p linux after reinstalling right). -- Thanks, Dennis
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 4/16/2013 6:43 PM, Dennis Anderson wrote:
Well gummiboot looks OK, default mkinitcpio seems OK, (you did run mkinitcpio -p linux after reinstalling right).
Yup. I eventually poked around inside the shell that rEFInd was dropping me into. I found that I needed to specify root=/dev/sda8 in buildconfig (which seems to be a copy of mkinitcpio.conf), and that UUIDs will not work here. I also found that I could mount /dev/sda8 as /new_root. It would still drop me back out to a shell once more, but then begin to boot normally. Only, NetworkManager.service, dbus.service, and gdm.service (at least) failed. It then hung trying to initialize the pacman keyring. I'm treating it as a botched install. I'm going to try again after the end of semester rush. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRbxOyAAoJELJhbl/uPb4SJ6sP/1efLBPbfVL1Xte4dzGX5ANO ddwp8u0pHcU2svXAa5AC9nxHZiE7FaxgrJY7Qy1WD1nVtBEXjlAxVmbUzlfnaPXn 9f58g7cO8Gm86FXpRf7y37x6jP5cCk7IEAc1EkAlwfvFGWZZsoWK8wAgLDy943oK IPXyOwiGZpF6XDTPI6CBW6YTKeTDZCEYXgskQqclYoj6bL+5b4lSl/BZX4o3LdlT vPWXg9OehE22uK5w47qbf5k251Vs67sKA1XwHv9O2dPCJVW4K3HR2Rd4moH7jQcn gQDfY0mIpo3lhCyLiec0f88X8Hpa+iVMnNVfWybXFkbmln1XpdnNtYdBtV0dKpxT 6SHWcX+zzxoP/5aF12AMJDQD50Cs2nbdBgD0uwRbL1QEkTta6aj7QEt14A6OrJfh 9UCyTj2aXXaU0Hju/vWQmCJl83kmhTVWeFKSgY1z+5X/c/hif0vXvZ28g0BN+S6Q R/mzU/vC2EKF76cUc16xELLaJG9na7KQ6v0Nr9Ri/vs+CP7Kae9NVsC3nhy8lLuW XtwuU6O7ENN9oRcWwxkl1WjxZF4HRb9KwrcS17tvHXYXm6AH6gYxVffGE78XvnEA MD9LwHWxxO5AkDYMQlWTARfIzLO9l542Ta6nHk4Y5PawNTPmyPsWUaFMFDx3I6qS vL8cDcwuQ4C/rhNuLuUo =GDgG -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 4/17/2013 2:27 PM, David Benfell wrote:
On 4/16/2013 6:43 PM, Dennis Anderson wrote:
Well gummiboot looks OK, default mkinitcpio seems OK, (you did run mkinitcpio -p linux after reinstalling right).
It turns out I had misspelled initrd. Someone on the forums spotted it. But I still have this other problem with gdm.service, dbus.service, and NetworkManager.service failing, followed by a hang on pacman keyring initialization. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRbyFnAAoJELJhbl/uPb4SXqgP/3oQnBTqC/ChP7ynQqGJqn8i 4VzlYEQPht0o77Qh3uwr3BsLRwsTl6QKHLKR1WWZpPEOj1FSv2JEmn+A7hcdNoDF vfInhuMTpgjPXellJjeuO17xTapTocGgoPMCc4BUwNnEaUtYHGDkhiPxwgfWwO0c tf711Mapt77D/YJLNVC/R0EOLPWqTYAJ2b8StMsOo1AMZ6U3POxNV8Yzl387U23S 1MObXa1OjG0SkucqD2vEv9A23WZaxJyxSyKHED7xHnuUkiUDxoeQFBLsrHagN3kL gyX4TOe+s0YxSAWQAi3Ez0flK+9shpJU8L9bEl0T/VdtJ1fAgPIorHltzMrDh77/ tTM+oLz7rmFkrf1qdJNesP5NbAYZogz9zlXYHyosJFgG5Fbr4UuR9ctu/P5+0p9p 91KGn3vK8gw2mfHpM73wntTol2H0lbz1bkC3U/+YWMxkJ+i/QuiLyOH+MXddCbhZ ZY3PC6QMOsd/J6uWsf5HK0XCxAyoksrNIE/wqAlZNtpyBL5POktIt/vMahd0ui/r 6uowAjm0It/m7v3uDlO7VFrUb4WxbHg4uXnJ1AYAYz3H8VWvCo57ONnAk1vi6xn+ /wck919G8BhDtHb0uV+PqPQstLJEpg5fYLic54la9AI3KM6lSznpdGY6wffrMIz6 w7PYQOs5LjULWFDM/Iow =fUkp -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 4/16/2013 6:43 PM, Dennis Anderson wrote:
Well gummiboot looks OK, default mkinitcpio seems OK, (you did run mkinitcpio -p linux after reinstalling right).
Yup. I eventually poked around inside the shell that rEFInd was dropping me into. I found that I needed to specify root=/dev/sda8 in buildconfig (which seems to be a copy of mkinitcpio.conf), and that UUIDs will not work here. I also found that I could mount /dev/sda8 as /new_root. It would still drop me back out to a shell once more, but then begin to boot normally. Only, NetworkManager.service, dbus.service, and gdm.service (at least) failed. It then hung trying to initialize the pacman keyring. I'm treating it as a botched install. I'm going to try again after the end of semester rush. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRbxQsAAoJELJhbl/uPb4SUJoP/0xvbhDaQ9IW5RLNVAWai0ev lryoSOoxqhUIfjYlNnmU/CyNRQjevjkdiULtdyYRycFesyQ8kkB2JTXd8OY9a2ML Rea8zx9sc03LCuesETnizusjk/OBOnB5j5yJ5MFAeNj9bxwdgHOgYJ11hbe5dCEq w4i/8TJLaimaFnKxBrxOctao5FWKql+NA0+HT+nZLp388ZTBLY0L42DgrL2fEFXg n8KQEGKX1h0uZLLeuGF7yomp/BMcMRS+Hxt41eku79uMsoYcunhvcxqQ76aPbfT9 K8lPVlq/H4grAS1ojcFle8NrX0K7ADE85SHasuZYU//iMgyao7gVB+zDUNwTEISe lN5n4GzTnBweTvn1NNqlMXjGdAr3JgkfK4T1H1vx7rtjEzemcspiKSeZKfgpeOJ0 PXRBlcQ/0uhPDjfuK7X3ZJ6qc6SGBuT5vbvK9w01mAs2ASW8tXRuPXmwDnUWO7pT QuGPVC16sI39OfOjK4yNsdr6uO9BU6PQY8Xfh8vCBYuLTU7VLljzOEiEZuP53Tkg 7qfMkzedwTowjKtJcTO8jaBfLvS3L/MwyWPecjOvZ467/dxnVoGm12fBUzex9W5o DsR2ZQt9fthhCzOLizNQJMacoaJ8EdJuuj1PhHZ7xc89IkL51qG4DNgetDno2qQS IthNEUXMdiVY57NQOQYI =qnYL -----END PGP SIGNATURE-----
participants (3)
-
David Benfell
-
Dennis Anderson
-
Nelson Marambio