[arch-general] AARG! kinit: cannot open dev(8,7) kernel panic
Listmates, I am in a fist-fight with grub again most likely due to /dev/disk/by-uuid and I'm losing the battle. First, the situation. I'm moving and resizing partitions from an 80G drive to a 500G drive. No issues there. The partitions setup is: /dev/sda1 WinXP /dev/sda2 Extended /dev/sda5 /home /dev/sda6 / /dev/sda7 swap /dev/sda8 /boot After moving and resizing the partitions windows boot fine and Arch boots until it gets to kinit and then throws a kernel panic. I have updated the disk/by-uuid labels in /boot/grub/menu.lst and in /etc/fstab, but still the kinit error. As far as my grub install goes, the system boot to the grub menu and it is reading /boot/grub/menu.lst because I can boot XP from the grub menu, but not boot Arch. Gurus... What to check? Throw a brother a bone.... Where else is the disk by-uuid stuff hidden? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Sat, 16 May 2009 19:59:38 -0500, "David C. Rankin, J.D.,P.E." <drankinatty@suddenlinkmail.com> wrote:
Listmates,
I am in a fist-fight with grub again most likely due to /dev/disk/by-uuid and I'm losing the battle.
First, the situation. I'm moving and resizing partitions from an 80G drive to a 500G drive. No issues there. The partitions setup is:
/dev/sda1 WinXP /dev/sda2 Extended /dev/sda5 /home /dev/sda6 / /dev/sda7 swap /dev/sda8 /boot
After moving and resizing the partitions windows boot fine and Arch boots until it gets to kinit and then throws a kernel panic. I have updated the
disk/by-uuid labels in /boot/grub/menu.lst and in /etc/fstab, but still the
kinit error.
As far as my grub install goes, the system boot to the grub menu and it is reading /boot/grub/menu.lst because I can boot XP from the grub menu, but not boot Arch.
Gurus... What to check? Throw a brother a bone.... Where else is the disk by-uuid stuff hidden?
Try replacing the disk-by-uuid stuff with direct paths to the device nodes (ex. /dev/sda2, etc). If you can get this to work then start switching back to disk-by-uuid. ~pyther
On or about Saturday 16 May 2009 at approximately 20:13:11 pyther composed:
Try replacing the disk-by-uuid stuff with direct paths to the device nodes (ex. /dev/sda2, etc). If you can get this to work then start switching back to disk-by-uuid.
~pyther
Hmm, I'll give it a go and report back. My fingers are getting sore from all the mount and chroot typing though ;-) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On or about Saturday 16 May 2009 at approximately 20:28:49 David C. Rankin, J.D.,P.E. composed:
On or about Saturday 16 May 2009 at approximately 20:13:11 pyther composed:
Try replacing the disk-by-uuid stuff with direct paths to the device nodes (ex. /dev/sda2, etc). If you can get this to work then start switching back to disk-by-uuid.
~pyther
Hmm,
I'll give it a go and report back. My fingers are getting sore from all the mount and chroot typing though ;-)
Ok, After switching /boot/grub/menu.lst and /etc/fstab from disk/by-uuid labels to the standard /dev/sda# labels everything boots and runs fine. Now the question of why the by-uuid labels did not work? I updated the uuid lables in each file with the right value from /dev/disk/by-uuid using strick copy and paste to eliminate typos and then verified 3 times, they were right. I guess I'll go back and substitute uuid labels one-by-one and see where it fails. My luck, it will work this time. If I find a failure, then we will have narrowed the error down. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Sonntag, 17. Mai 2009 10:02 David C. Rankin, J.D.,P.E. wrote:
After switching /boot/grub/menu.lst and /etc/fstab from disk/by-uuid labels to the standard /dev/sda# labels everything boots and runs fine. Now the question of why the by-uuid labels did not work? I updated the uuid lables in each file with the right value from /dev/disk/by-uuid using strick copy and paste to eliminate typos and then verified 3 times, they were right.
There is a longer existing second mechanism in linux named disklabel. See here: http://wiki.archlinux.org/index.php/Persistent_block_device_naming The advantage is that you can recreate partitions without a problem if you use the same name for a disklabel as before. The disadvantage is that a lot of people think that this labels can get lost instead this never happens to me.-) See this as an optional information about your problem. See you, Attila
participants (3)
-
Attila
-
David C. Rankin, J.D.,P.E.
-
pyther