On Wed, 2005-04-13 at 16:49 -0600, Guy Fraser wrote: [snip] > Run a second program designed just to > install the MBR on the real device name that you earlier had to > create a reference for. I haven't read the rest of your post yet, but here is one problem that appears possible to narrow down to your usage of grub. You do NOT need (as a matter of fact, SHOULDN'T) re-run grub-install (if that's what you are referring to, which seems to be the case according to the context) when you update the grub config file. That's one of the (major, IMO) benefits of grub over lilo. Even that *other* OS doesn't need to re- install the boot block every time the boot config (boot.ini?) is updated. It's something you should not be doing all that often, and really should be reserved for install only. By saying this, I'm not trying to exonerate grub completely (yet). It most certainly *may* still have problems (which is what I hope you are here to test for), but in this particular case, it sure seems like you are using grub in a way it was not intended to be used. Perhaps grub- install should print out a big, honking warning when run interactively that says something to the effect of "You shouldn't be doing this unless running from a rescue disk, you boot block got broken somehow, or you ARE 'The Anaconda Installer' ;-)". -- -Paul Iadonisi Senior System Administrator Red Hat Certified Engineer / Local Linux Lobbyist Ever see a penguin fly? -- Try Linux. GPL all the way: Sell services, don't lease secrets