You are not logged in.
I have setup a multi-boot environment - Debian, Arch, Fedora and Win8
The Debian Grub2 is installed on the MBR. Fedora and Arch Grub2s are installed on the partitions. So I chainload the Arch grub from the Debian Grub with
menuentry "Arch Linux" {
set root=(hd1,msdos9)
chainloader +1
}The arch partition is
# ls /dev/disk/by-label/ -la
total 0
drwxr-xr-x 2 root root 140 Apr 19 23:57 .
drwxr-xr-x 6 root root 120 Apr 20 2013 ..
lrwxrwxrwx 1 root root 10 Apr 19 23:57 arch -> ../../sdb9This has been working for a long time. At some point I updated the Arch boot via a chroot. Along with updating the Debian install.
Now when I try boot the Arch install I get the message Error: no such partition after selecting the Arch Linux option from the Debian grub.
I am still able to chroot to /dev/sdb9 and perform system maintenance. I just can't boot into it.
This may also be important when run from the chroot environment
# grub-install --force --recheck /dev/sdb9
/usr/sbin/grub-bios-setup: warning: File system `ext2' doesn't support embedding.
/usr/sbin/grub-bios-setup: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
Installation finished. No error reported.Am I missing something?
Last edited by milomak (2013-04-30 22:41:14)
Offline
this isn't an arch related issue. the fedora and win8 entries are
menuentry "Fedora" {
set root=(hd1,msdos8)
chainloader +1
}menuentry "Windows 8" {
set root=(hd0,1)
chainloader +1
}
fedora doesn't boot but win8 does.
both fedora and arch entries have been working for as long as i can remember.
i wonder if i made a change in the bios which i thought was innocuous?
Offline
Why do you do this crazy chainloading? You are making the system much much more complicated than it needs to be. Not to mention installing bootloaders to the PBR (not Pabst Blue Ribbon, the partition boot record) is generally recommended. The only time I think this might be a sane thing to do is with syslinux, which is awesome, but also very primative, in that it cannot look for kernels or boot anything that is not on the same partition as its config.
Look through the grub docs, and figure out how to make your one grub boot all your Linux installations and chainload windows. This is the correct and sane way to do things.
Offline
i wonder if i made a change in the bios which i thought was innocuous?
so this was it
at some point i changed the boot order of disks 2 and 3 (by mistake while trying to get a usb disk to boot i presume). restored this and all is well.
Offline
You should still learn how to use your boot laoder correctly. You are really just asking for something to break, and eventually I can pretty much gaurantee that something will. If you learn how things work now, it will be much less painful when that day comes. Of course, if you learn how to do things now, and you set it up correctly, you also lower the risk of things breaking... so yeah.
Offline
You should still learn how to use your boot laoder correctly. You are really just asking for something to break, and eventually I can pretty much gaurantee that something will. If you learn how things work now, it will be much less painful when that day comes. Of course, if you learn how to do things now, and you set it up correctly, you also lower the risk of things breaking... so yeah.
i am using my bootloader the way that works for me
as long as the bios and grub have the disks in the sam eorder, the way grub currently works means there is no issue.
i have been running this kind of setup before grub2.
all that has happened here is that i mistook a grub issue for an arch issue. and because arch is a secondary distro, it did not matter to me how quickly the issue was solved.
Offline