[EMAIL PROTECTED] wrote on 05/16/2008 07:01:11 AM:
> Hi Dale,
>
> Can you send me the output of "cat /proc/sys/dev/cdrom/info" and "cat
> /proc/diskstats" please? Can you also send the content of the /etc/fstab
and
> /boot/grub/menu.lst from a compute node after the image has been pushed?
>
> With that it should be possible to check if the compute node
configuration is
> correct or not.
>
OK, I booted the node into rescue mode using the RedHat installation
disc1. So, here are the cdrom-info and the diskstats files from the
rescue mode. I don't know if it'll be as helpfull as the same files from
the PXE boot installation session, but here they are.
diskstats:
1 0 ram0 0 0 0 0 0 0 0 0 0 0 0
1 1 ram1 0 0 0 0 0 0 0 0 0 0 0
1 2 ram2 0 0 0 0 0 0 0 0 0 0 0
1 3 ram3 0 0 0 0 0 0 0 0 0 0 0
1 4 ram4 0 0 0 0 0 0 0 0 0 0 0
1 5 ram5 0 0 0 0 0 0 0 0 0 0 0
1 6 ram6 0 0 0 0 0 0 0 0 0 0 0
1 7 ram7 0 0 0 0 0 0 0 0 0 0 0
1 8 ram8 0 0 0 0 0 0 0 0 0 0 0
1 9 ram9 0 0 0 0 0 0 0 0 0 0 0
1 10 ram10 0 0 0 0 0 0 0 0 0 0 0
1 11 ram11 0 0 0 0 0 0 0 0 0 0 0
1 12 ram12 0 0 0 0 0 0 0 0 0 0 0
1 13 ram13 0 0 0 0 0 0 0 0 0 0 0
1 14 ram14 0 0 0 0 0 0 0 0 0 0 0
1 15 ram15 0 0 0 0 0 0 0 0 0 0 0
9 0 md0 0 0 0 0 0 0 0 0 0 0 0
7 0 loop0 0 0 0 0 0 0 0 0 0 0 0
7 1 loop1 0 0 0 0 0 0 0 0 0 0 0
7 2 loop2 0 0 0 0 0 0 0 0 0 0 0
7 3 loop3 0 0 0 0 0 0 0 0 0 0 0
7 4 loop4 0 0 0 0 0 0 0 0 0 0 0
7 5 loop5 0 0 0 0 0 0 0 0 0 0 0
7 6 loop6 0 0 0 0 0 0 0 0 0 0 0
7 7 loop7 0 0 0 0 0 0 0 0 0 0 0
8 0 sda 296 80 1840 479 30 2 256 55 0 519 534
8 1 sda1 10 36 0 0
8 2 sda2 104 768 32 256
11 0 sr0 1285 39261 162184 437187 0 0 0 0 0 209535 437187
8 16 sdb 0 0 0 0 0 0 0 0 0 0 0
cdrom-info:
CD-ROM information, Id: cdrom.c 3.20 2003/12/17
drive name: sr0
drive speed: 1
drive # of slots: 1
Can close tray: 1
Can open tray: 1
Can lock tray: 1
Can change speed: 0
Can select disk: 0
Can read multisession: 1
Can read MCN: 1
Reports media changed: 1
Can play audio: 1
Can write CD-R: 0
Can write CD-RW: 0
Can read DVD: 0
Can write DVD-R: 0
Can write DVD-RAM: 0
Can read MRW: 1
Can write MRW: 1
Can write RAM: 1
And now, here is where the problem seems to lie:
etc-fstab:
/dev/sdb1 swap swap defaults 0 0
/dev/sdb2 / ext3 defaults 1 2
/dev/shm /dev/shm tmpfs defaults 1 2
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
none /dev/pts devpts defaults 0 0
none /proc proc defaults 0 0
nfs_oscar:/home /home nfs rw 0 0
menu.1st:
##################################################
# This file is generated by System Configurator. #
##################################################
# The number of seconds to wait before booting.
timeout 5
# The default kernel image to boot.
default 0
# The splash image (this line will be empty if nothing was found)
splashimage=(hd0,1)/boot/grub/splash.xpm.gz
# kernel0
title 2.6.9-55.ELsmp_(hd0,1)
root (hd0,1)
kernel /boot/vmlinuz-2.6.9-55.ELsmp ro root=/dev/sdb2
initrd /boot/sc-initrd-2.6.9-55.ELsmp.gz
# kernel1
title 2.6.9-55.EL_(hd0,1)
root (hd0,1)
kernel /boot/vmlinuz-2.6.9-55.EL ro root=/dev/sdb2
initrd /boot/sc-initrd-2.6.9-55.EL.gz
I am going to edit the fstab and then reboot. I'll change the
root=/dev/sdb2 parameter during the grub process and see if it'll boot.
Thank you for pointing me in this direction. I'll keep you posted.
Also, I'm still curious to find out why the UYOK installation image
detects the first hard drive as /dev/sdb instead of /dev/sda.
~Dale
--
Dale Schuster
Systems Administrator
Sierra Nevada Corporation
Information Systems
444 Salomon Circle
Sparks, NV 89434
775-849-6308
> Thanks,
>
>
> Selon Dale Schuster <[EMAIL PROTECTED]>:
>
> > [email protected] wrote on 05/13/2008 08:02:31 PM:
> >
> > > > OK, I think I'm making progress. It seems the following line in
> > > > oscarimage.master is used to determine which of the devices is a
> > CD-Rom.
> > > > cdroms=`cat /proc/sys/dev/cdrom/info 2>/dev/null | sed -ne
"s/^drive
> > > > name:[[:space:]]*//p"`
> > > >
> > > > On my system $cdrom expands to "sr0" not "sda" which is derived
out of
> > > > /proc/sys/dev/cdrom/info
> > > >
> > > > Then further on in the script is
> > > >
> > > > for dev in `cat $diskfile | sed -ne
> > "s/.*\($type[a-z]\+\).*/\1/p" |
> > > > sort -u` ; do
> > > > skip=0
> > > > for cdrom in $cdroms; do
> > > > if [ "$dev" = "$cdrom" ]; then
> > > > skip=1
> > > > break
> > > > fi
> > > > done
> > > > if [ $skip -eq 0 ]; then
> > > > logmsg " $dev"
> > > > eval DISK$DISKS=/dev/${dev}
> > > > DISKS=`expr $DISKS + 1`
> > > > fi
> > > > done
> > > >
> > > > which is comparing "$dev" to "$cdroms". $dev is derived from
> > > > /proc/diskstats which makes no mention of "sr0" at all, only
"sda",
> > "sdb",
> > > > etc.
> >
> > I was wrong in my previous posts. /proc/diskstats does in fact list
sr0,
> > I just didn't see it originally.
> >
> > I was able to get the master installation script to write the image to
> > /dev/sdb by manually adding "DISK0=/dev/sdb" before the "IF" statement
as
> > shown below.
> >
> > # END disk enumeration
> >
> >
>
################################################################################
> >
> > DISK0=/dev/sdb
> > if [ -z $DISKORDER ] ; then
> > DISK0=/dev/sdb
> > elif [ -z $DISK0 ] ; then
> > echo "Undefined: DISK0"
> > shellout
> > fi
> > ### BEGIN partition $DISK0 ###
> >
> > I'm still unsure why the script didn't correctly detect /dev/sda as a
> > CD-Rom device but I think I'm comfortable moving past that issue for
now.
> >
> > I'm still hung up on a problem however. After the image installation
> > process the compute node reboots. Upon reboot I get
> >
> > Creating /dev
> > Starting udev
> > Loading jbd.ko module
> > Loading ext3.ko module
> > Creating root device
> > Mounting root filesystem
> > mount: error 6 mounting ext3
> > mount: error 2 mounting none
> > Switching to new root
> > switchroot: mount failed: 22
> > umount /initrd/dev/failed: 2
> > Kernel panic - not syncing: Attempted to kill init!
> >
> > This seems to be a problem with grub, or somthing similar. I've seen
> > e-mail forum threads stating this problem could be that the ext driver
> > isn't compiled into the kernel. This hasn't been a problem with Oscar
in
> > the past. I think it's something to do with the device name being
called
> > /dev/sdb1 during the installation push, and /dev/sda1 after the
reboot.
> > I've tried to edit the grub parameters during the reboot and changing
the
> > root=/dev/sdb1 to /dev/sda1, but I still get the same errors.
> >
> > I'm starting to go into panic mode and appreciate all help that anyone
can
> > offer. Thank you all in advance.
> >
> >
> > ~Dale
> >
> > --
> > Dale Schuster
> >
> >
-------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Oscar-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/oscar-devel
> >
>
>
>
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Oscar-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oscar-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
