A little more info.  I just discovered pvdisplay in the lvm utility and 
here's what it says:
lvm> pvdisplay
  --- Physical volume ---
  PV Name               /dev/sda2
  VG Name               VolGroup00
  PV Size               232.78 GB / not usable 0
  Allocatable           yes
  PE Size (KByte)       32768
  Total PE              7449
  Free PE               5
  Allocated PE          7444
  PV UUID               DL5p6b-SHMB-8Q6a-ysSl-EX0B-hvgn-jCTcGD

so doesn't that mean /dev/sda2 IS assigned to VolGroup00?

-mark

Mark Seger wrote:

> I hate to come across as a nag, but...
> I just tried imaging a new system with RHEL4/Update4 on it (the update 
> was just released the other day).  Anyhow, I grabbed an image and 
> decided to run si_prepareclient with the -no-uyok switch because I was 
> getting impatient - my vote would be to make that the default, but I'm 
> sure there was already a lot of discussion around that and so don't 
> really care all that much.
>
> Anyhow, prepage client went smoothly and when I retrieved the image, 
> the very last thing is did was:
>
> Press <Enter> to continue...
> Couldn't open 
> /var/lib/systemimager/images/rhel4-U4-poker/etc/systemimager/boot/ARCH 
> for reading
> No such file or directory at 
> /usr/lib/systemimager/perl/SystemImager/Server.pm line 75.
>
> A little more digging shows there is no /etc/systemimager/boot 
> directory on the client.  How can that be as I did install 
> initd-templace as you can see from this:
>
> [EMAIL PROTECTED] ~]# rpm -qa | grep systemi
> systemimager-i386initrd_template-3.7.4r3676_arighi-1
> systemimager-common-3.7.4r3676_arighi-1
> systemimager-client-3.7.4r3676_arighi-1
>
> could it be that in previous installations that did work I simply had 
> that directory hanging around from past installs?  I looked inside the 
> init-template rpm and there's nothing in there that install in 
> /etc/systemimager or ARCH.
>
> As a further suggestion, and I know this can be a pain, I think every 
> 'open' failure on an expected file should print a message something 
> like "are you should you installed rpm xyz?" just to let those not 
> capable of reading the code what might be wrong.
>
> but wait - I tried running prepareclient again without -no-myok and it 
> failed too!  Finally dawned on me that I had installed the i386 
> initrd-template instead of the x8664 one, but again a friendlier 
> message could help the less informed - though given my blunder I *am* 
> one of the less informed.
>
> So I installed the right template and ran prepareclient without 
> -no-uyok and this time I got a boot directory so all seems ok.  
> Unfortunately I now have to regrab the image - at least I think I do - 
> but at least it will only pull the few files that have changed.
>
> OK, now I'm getting warnings:
> Are you satisfied? ([y]/n):
> WARNING: LVM partition "/dev/sda2" is not assigned to any group!
> WARNING: LVM group "VolGroup00" doesn't have partitions!
>
> and not being an LVM kind of a person, have no idea what these mean.  
> All I know is I have a valid, running system and here's what parted 
> shows:
>
> (parted) print
> Disk geometry for /dev/sda: 0.000-238475.179 megabytes
> Disk label type: msdos
> Minor    Start       End     Type      Filesystem  Flags
> 1          0.031    101.975  primary   ext3        boot
> 2        101.975 238472.688  primary               lvm
>
> -mark
>


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Reply via email to