Hi Tyler:
 
/boot should be created, however, it's possible that it was simply not mounted.
 
When you boot into rescue mode, it'll ask whether you want it to search for installed Red Hat OS on the HD, if you say yes it should automatically mount all the partitions under /mnt/sysimage (or something like that).  So you should look inside /mnt/sysimage/boot in that case.
 
If it did not, you can manually mount it by doing:
 
mkdir -p /mnt/boot
mount /dev/hda1 /mnt/boot (substitute "sda" with "hda" if you're using SCSI HD).
 
Then cd into /mnt/boot and look for grub/menu.lst, it should be there...
 
As for the directory listing you showed from the "ash shell", the "boot" directory should reside in /a/boot if it was mounted.  /a/ is the temporary mount point for your compute node's /root partition.
 
Cheers,
 
Bernard


From: Tyler Cruickshank [mailto:[EMAIL PROTECTED]
Sent: Monday, June 19, 2006 13:12
To: Bernard Li; oscar-users@lists.sourceforge.net
Subject: RE: [Oscar-users] Network Boot Problem & Grub

Bernard,
 
Thank you again for your speedy and helpful responses.  We all appreciate your efforts.
 
Well, no wonder I couldn't find the .img ... I dont have a /boot directory.  I went ahead and used cd 1 to boot into rescue mode.  No menu.lst file was created and no /boot directory exists.  I can show you what directories were created ... from the ash shell:
a/  etc/  linuxrc*  old_root/  sbin/  usr/
bin/  floppy/  my_modules/  proc/  scripts/  var/
dev/  lib/  new_root/  root/  tmp/
 
Thoughts on this dilemma?
 
Thanks.
 
-ty

>>> "Bernard Li" <[EMAIL PROTECTED]> 6/19/2006 1:50:50 PM >>>
Hi Tyler:
 
Do you have both IDE and SCSI HDs in your compute nodes?
 
Can you boot one of your compute nodes (which failed installation) into rescue mode (using the first CD of RHEL4 and typing "linux rescue" at the prompt) and show us the contents of /boot/grub/menu.lst (of the HD).
 
It looks like Grub was not installed properly...
 
P.S. Kernel and initrd.img of your installed node should reside in /boot - SystemConfigurator creates a ramdisk for you on the fly though, and the filename is prefixed by "sc-".
 
Cheers,
 
Bernard


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tyler Cruickshank
Sent: Monday, June 19, 2006 8:01
To: oscar-users@lists.sourceforge.net
Subject: [Oscar-users] Network Boot Problem & Grub

Hi.
 
I have successfully created an image and am now trying to network boot a single node.  The network install finishes (apparently with success) but it does give some "problem" messages before the boot process is done (see below).  After the network boot, I reboot again (from the hard drive), but I get a grub> prompt.  From the prompt, I have tried to load the kernel but I dont know where it lives.  I have also tried to "find" the image, based on the name I originally gave it, but it cant seem to find it.  So, it seems something is not right.  Where should I look to investigate the problem further?
 
Thanks.
 
-Tyler
 Utah Division of Air Quality
—-------------------------------------------------------------------------------------------
mv: cannot stat '/boot/grub/device.map' : No such file or directory
Probing deivices to guess BIOS drives.  This may take a long time.
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
Installation finished.  No error reported.
This is the contents of the device map /boot/grub/device.map.
.. blah blah blah ...
(fd0) /dev/flopy/0
(hd0) /dev/ide/host0/bus0/target0/lun0/disc
(hd1) /dev/scsi/host0/bus0/target0/lun0/disc
Use of unitintialized value in concatenation (.) or string at /usr/lib/systemcnfig/Boot/Grub.pm line 315
Probing deivices to guess BIOS drives.  This may take a long time.
end_request: I/O error, dev fdo, sector 0
run_post_install_scripts
... blah blah ...
Reboot me already.
—-------------------------------------------------------------------------------------------
 
Finally, is there a file created that contains all of the network boot screen output?  I found one file in /tmp called si.log, but it contains only a small bit of the process.
_______________________________________________
Oscar-users mailing list
Oscar-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-users

Reply via email to