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. 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
