You are not logged in.
Pages: 1
---------------------------------------------------------------------------------------------------------------------------
Solved: http://bbs.archlinux.org/viewtopic.php?id=85669
---------------------------------------------------------------------------------------------------------------------------
Today I started off installing Arch, I fallowed the Beginner guide: http://wiki.archlinux.org/index.php/Beginners%27_Guide to a T, One thing that I believe may have caused the majority of my troubles here is that fact that I opted to use persistent block device naming for my system: http://wiki.archlinux.org/index.php/Per … ice_naming, because I often swap out my HDD's and have different disks loaded at any give time.
In any case I go through the install doing little adjustment to the default configuration outside of that and changing my host name in the etc/hosts/ file.
Basically the only place i veered off at was when as i said decided to do persist block device naming, which required me to change my fstab:
from this:
/dev/sdb1 /boot ext2 defaults 0 1
/dev/sdb2 swap swap defaults 0 0
/dev/sdb3 / ext3 defaults 0 1
/dev/sdb4 /home ext3 defaults 0 1
to this:
#sdb1 boot
/dev/disk/by-uuid/04a8052f-7649-4fa0-9164-6e5d7e4973c2 /boot ext2 defaults 0 1
#sdb2 swap
/dev/disk/by-uuid/cd713305-30b9-4bb2-a28a-a7ff82f1490a swap swap defaults 0 0
#sdb3 /
/dev/disk/by-uuid/a9ac24c9-69d9-4669-a28c-1fb270fa87d3 / ext3 defaults 0 1
#sdb4 /home
/dev/disk/by-uuid/1619dbeb-c30c-40fb-a94b-9356089c1aea /home ext3 defaults 0 1
It required that I modify my grubs menu.lst from using the "kernal /vmlinuz26 root=/dev/sdb1 ro vga=773 to this:
# (0) Arch Linux
title Arch Linux
root (hd1,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/04a8052f-7649-4fa0-9164-6e5d7e4973c2 ro vga=773
initrd /kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd1,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/04a8052f-7649-4fa0-9164-6e5d7e4973c2 ro
initrd /kernel26-fallback.img
BTW /kernal26.img and /kernal26-fallback.img are located at 04a8052f-7649-4fa0-9164-6e5d7e4973c2 (sdb1 or /boot) as it shows here... I still don't understand why it's saying they can not be found....
I've played around with it a bit, but I can't seem to find where the problem is... could anyone here see an error that I do not?
Last edited by cynicalpsycho (2009-12-24 10:54:07)
Offline
i'm thinkin it's got somethin to do with this...
GRUB
The provided GRUB configuration (/boot/grub/menu.lst) should be sufficient, but verify its contents to ensure accuracy (specifically, ensure that the root (/) partition is specified by UUID on line 3). You may want to alter the resolution of the console by adding a vga=<number> kernel argument corresponding to your desired virtual console resolution. (A table of resolutions and the corresponding numbers is printed in the menu.lst.)
Example:
title Arch Linux (Main)
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/sda1 ro vga=773
initrd /boot/kernel26.img
Line 1: title: A printed menu selection. "Arch Linux (Main)" will be printed on the screen as a menu selection.
Line 2: root: GRUB's root; the drive and partition where the kernel (/boot) resides, according to system BIOS. (More accurately, where GRUB's stage2 file resides). NOT necessarily the root (/) file system, as they can reside on separate partitions. GRUB's numbering scheme starts at 0, and uses an hdx,x format regardless of IDE or SATA, and enclosed within parentheses.
The example indicates that /boot is on the first partition of the first drive, according to BIOS, or, (hd0,0).
Line 3: kernel: This line specifies:
* The path and filename of the kernel relative to GRUB's root.
In the example, /boot is merely a directory residing on the same partition as / and vmlinuz26 is the kernel filename; /boot/vmlinuz26. If /boot were on a separate partition, the path and filename would be simply /vmlinuz26, being relative to GRUB's root.
* The root= argument to the kernel statement specifies the partition containing the root (/) directory in the booted system, (more accurately, the partition containing /sbin/init).
* An easy way to distinguish the 2 appearances of 'root' in /boot/grub/menu.lst is to remember that the first root statement informs GRUB where the kernel resides, whereas the second root= kernel argument tells the kernel where the root filesystem (/) resides.
* Kernel options.
In our example, ro mounts the filesystem as read only during startup, (usually a safe default; you may wish to change this in case it causes problems booting) and the "vga=773" argument will give a 1024x768 framebuffer with 256 color depth.
Line 4: initrd: (For Initial RAM disk) The path and filename of the initial RAM filesystem relative to GRUB's root. Again, in the example, /boot is merely a directory residing on the same partition as / and kernel26.img is the initrd filename; /boot/kernel26.img. If /boot were on a separate partition, the path and filename would be simply /kernel26.img, being relative to GRUB's root.
Install the GRUB bootloader (to the master boot record, sda in our example).
Last edited by cynicalpsycho (2009-12-24 08:43:58)
Offline
Your kernel line has root= pointing at the boot partition instead of the root partition. That is problem one. As to why GRUB can't find your kernel and initrd I'm not sure. You could try mounting the boot partition using a livecd and double check the correct files are in there.
Offline
Just replied you in LQ forum, I haven't used grub in a long time but try this:
# (0) Arch Linux
title Arch Linux
root (hd1,0)
kernel vmlinuz26 root=/dev/disk/by-uuid/a9ac24c9-69d9-4669-a28c-1fb270fa87d3 ro vga=773
initrd kernel26.img
Offline
Your kernel line has root= pointing at the boot partition instead of the root partition. That is problem one. As to why GRUB can't find your kernel and initrd I'm not sure. You could try mounting the boot partition using a livecd and double check the correct files are in there.
kernal26.img is in my boot partition.
Offline
Just replied you in LQ forum, I haven't used grub in a long time but try this:
# (0) Arch Linux title Arch Linux root (hd1,0) kernel vmlinuz26 root=/dev/disk/by-uuid/a9ac24c9-69d9-4669-a28c-1fb270fa87d3 ro vga=773 initrd kernel26.img
when i tried this it gives me error 1 fille name mnust be either an absolute pathname or blocklist, i'm guessing it's requiring that there be a / before vmlinuz26 and kernal26, which i tried and also got the file not found error...
Offline
mikesd wrote:Your kernel line has root= pointing at the boot partition instead of the root partition. That is problem one. As to why GRUB can't find your kernel and initrd I'm not sure. You could try mounting the boot partition using a livecd and double check the correct files are in there.
kernal26.img is in my boot partition.
root= doesn't point to your initrd. It points to your root filesystem.
Offline
cynicalpsycho wrote:mikesd wrote:Your kernel line has root= pointing at the boot partition instead of the root partition. That is problem one. As to why GRUB can't find your kernel and initrd I'm not sure. You could try mounting the boot partition using a livecd and double check the correct files are in there.
kernal26.img is in my boot partition.
root= doesn't point to your initrd. It points to your root filesystem.
you are correct, but that still didn't solve the problem.
there was a rather strange answer that i'm still not sure i understand...
http://bbs.archlinux.org/viewtopic.php?id=85669
seems rather glitchy but the answer was making the menu.lst file read that grub was booting on my sda drive instead of the one it was installed on...
Offline
Pages: 1