Need boot manager help: Win7, Ubuntu, FreeBSD on ZFS

sim

sim

Hi

I'm trying to triple boot the following on my new Thinkpad T510:

  • Window 7 Pro (64bit)
  • FreeBSD 8-STABLE (amd64) Pure ZFS
  • Ubuntu 10.10 (ext4)

All three systems appear in the FreeBSD boot manager menu, but the problem is that it seems unable to boot the Linux partition. Instead the boot option prompt just sits there showing a hash sign.

Does the FreeBSD boot manager have a problem with ext4? If so, any suggestions?

I can't use GRUB because that doesn't see the ZFS FreeBSD partition. In anycase I don't like GRUB as it is prone to reconfiguring itself and always boots the first item by default, instead of the last used, which IMO is far more useful.

Not really sure what to try next. Ideas?

sim
 
If you've got to deal with Windows 7, either alpha (Vista) or beta (Windows 7 sp1), EasyBCD is pretty nice. ZFS probably complicates things.
 
Hi wblock

Ironically the Windows side is not giving me any problems either with the FreeBSD boot manager or (when I tried it) GRUB.

I'm wondering whether I installed Ubuntu incorrectly. Should the FreeBSD boot manager be able to start it? ext3, ext4?

sim
 
EasyBCD is just another boot loader, but it deals well with newer Windows variants. It certainly can start FreeBSD and it would be surprising if it didn't handle Ubuntu. The FreeBSD boot manager is so bare-bones that I generally don't use it.

The boot manager, whichever it is, shouldn't care about filesystems, just chain to the boot block of whichever partition is chosen by the user. Then it's up to that loader to be able to deal with the filesystem on that partition.
 
sim said:
I'm wondering whether I installed Ubuntu incorrectly. Should the FreeBSD boot manager be able to start it? ext3, ext4?
Click to expand...
A boot manager shouldn't care about file system. Unfortunately though, GRUB does, and linux installers seem to be tailored to assume you'll be running it in your MBR and don't put any boot code at the start of linux's boot partition. Try reinstall it and specify that you want boot code installed at the start of your linux partition.
 
Hi aragon

That's what I thought, that the Boot Manager shouldn't care about file systems. I have found a solution though. I retained the FreeBSD Boot Manager (good), and reinstalled Ubunutu on what it calls /dev/sda3. This time set it to install GRUB on the same partition (slice), sda3. This means I go through two boot managers to get to Ubuntu but it works:

Code: 
+ FreeBSD boot manager
  + Windows 7
  + FreeBSD
  + Ubuntu [GRUB]
    + Ubunutu
    + Windows 7
    + other GRUB options
I guess GRUB on sda3 could be replaced with a simple boot loader but for now it's fine.

Thanks for you input guys.

sim

PS am I being thick? Can't see how to set the thread as solved!
 
sim: edit first post -> go advanced -> pull down next to title
 
sim said:
I guess GRUB on sda3 could be replaced with a simple boot loader but for now it's fine.
Click to expand...
Lilo is pretty old fashioned these days, but I imagine it still works with modern kernels and ext3...
 
aragon said:
A boot manager shouldn't care about file system.
Click to expand...

Well, if it's going to do anything more complicated than grabbing the first N block(s) of the slice (or partition) and executing it, it must needs grok the filesystem.

In particular, with ZFS there's no guarantee that the boot code is even on the first drive that the boot-loader might encounter, hence a special ZFS bootloader.
 
You must log in or register to reply here.
Back
Top