In message from Stefan Fent (Tue, 26 Oct 2004 19:05:16 +0200):

* Mikhail Kuzminsky [041026 15:36]:

...

Hello,

I'm installing GRUB into MBR after some unsuccessful (for MBR part) HDD cloning. Now I have (in the server) 1 HDD w/all filesystems ready, and want to install GRUB into MBR. grub-install is in separate /usr HDD partition.

I loaded in rescue mode from SuSE 9.0 for x86-64 distribution media. I mounted root-FS under /mnt mounting point; mkdir /usr2 and mount "usr" p?rtition (/dev/hda5) w/grub-install under /usr2 mount point. /usr2/sbin/grub-install contains references to /usr/blah/..., so I changed grub-install script w/replacing of all of the /usr occurences to /usr2.

But now ./grub-install --root-directory=/mnt --debug /dev/hda

finished w/errors like

/usr2/sbin/grub --batch --device-map=/mnt/boot/grub/device.map no such file or directory

Do you have a seperate /boot partition? Then you should mount it at /mnt/boot No, /boot is part of / (root filesystem)

Yours Mikhail

...

Sorry, where am I wrong - and what should I correct ?

Yours Mikhail Kuzminsky Zelisnky Institute of Organic Chemistry Moscow

-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com

Stefan -- Stefan Fent SuSE Linux AG, Maxfeldstr. 5, D-90409 Nuernberg Phone: +49-911-740 53 - 559 GPG fingerprint = B226 E3DA 37B0 2170 7403 D19C 18AF E579 9161 4BBC

-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com

In message from "Curt Purdy" (Wed, 27 Oct 2004 12:37:42 -0500):

Mikhail Kuzminsky wrote:

...

But now ./grub-install --root-directory=/mnt --debug /dev/hda

finished w/errors like

/usr2/sbin/grub --batch --device-map=/mnt/boot/grub/device.map no such file or directory

I had similar problems but then did a manual install, pick last option (like bootloader or something), it will pick 3 of the first as dependancies, and pick the middle option letting it do setup for you (I wasted a lot of time picking the third manual option.) It rebuilt everything, put it where it was supposed to and booted fine. It's hell when your OS is smarter than you are ;) I'm sorry, I didn't understood your statements about options selections ... :-(

The problem looks for me as some my "head failure" ;-): /usr2/sbin/grub (i.e. "manual" grub execution !) says "No such file or directory". This situation dosn't depend from mounting point (/usr2 or /mnt or /usr etc), grub is executable (from ls -l) etc. So the possible reason of like "behaviour of grub" looks that grub requires some additional file(s) (by default) which is/are not presented on the places (pathes) where grub want "to see" them. Is it right ? Yours Mikhail

Curt Purdy CISSP, GSEC, MCSE+I, CNE, CCDA Information Security Engineer DP Solutions

----------------------------------------

If you spend more on coffee than on IT security, you will be hacked. What's more, you deserve to be hacked. -- former White House cybersecurity adviser Richard Clarke

-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com