...but I think it's probably something I'm doing wrong instead.

Up until recently, my environment which had been based on andrea's 3.7.4 
drop had been working just fine.  Now I installed the 3.7.6 components 
and boel can't even see my disks any more on a system known to have been 
successfully imaged before.  I know I have something left over from the 
earlier release but don't know how to get things back in sync with 
respect to the right versions of everything..

What I'm seeing just before this thing dies is:
get_arch
Partitioning /dev/cciss/c0d0
Old partition table for /dev/cciss/c0d0
Error: Count not stat device /dev/cciss/c0d0 - No such file or directory

In fact if I go into the shell and look in /dev, there is no cciss which 
certainly explains why this if failing.

when I do 'uname -r' I get
2.6.16-boel_v3.7.4r3725_arighi
so clearly this is something old, but what I'm not sure of if how did it 
get there and why wasn't it changed when I installed the new rpms?

if I look in /usr/share/systemimager/boot/i386/standard I see:
-rw-r--r--    1 root     root      5503166 Jan  7 06:01 boel_binaries.tar.gz
-rw-r--r--    1 root     root        32102 Jan  7 06:01 config
-rw-r--r--    1 root     root      6184860 Jan  7 06:01 initrd.img
-rw-r--r--    1 root     root      2172336 Jan  7 06:01 kernel

which I assume came from the 3.7.6 kit.  so why the old kernel?

I've gotta believe I did something silly...  8-(

-mark



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to