Thanks, Mark, for your reply, very interesting and informative. Werner
"Post, Mark K" wrote: > > Werner, > > Look in /usr/src/linux/Documentation/devices.txt. '58 block' is "Reserved > for logical volume manager." You've basically run into a restriction > imposed by silo, zilo, and zipl. All the files that are used to define an > "IPL set" (for lack of a better term) _must_ reside on the same physical > volume that is going to be the IPL volume. The way it checks for this is by > comparing the major and minor device nodes for that volume against that of > all the files used. In your case, 58/0 does not match 94/0. Bang, you're > dead. > > You're going to need to create a non-LVM file system on the volume from > which you wish to IPL. Or, if you've got VM, you can IPL from the virtual > reader, freeing you from any restrictions imposed by silo, zilo, and zipl. > > Mark Post > > -----Original Message----- > From: Werner Kuehnel [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 26, 2002 3:28 AM > To: [EMAIL PROTECTED] > Subject: Re: SILO refuses to work > > > Mark, > > I think your guess is correct. I'm curious as to why you want to make > your > > root file system an LVM volume, though. Do you really think you'll need > to > > expand it that much, instead of just adding additional file systems on > > various mount points? > > > to be honest, I just wanted to try out the LVM. And since our AIX guys has > also > a volume group for the root filesystem I thought that would be the normal > way to > define all available space in volume groups and logical volumes. I'm just > starting with LINUX and try out things to get familiar with it. > Can I have a mixture of non-LVM space and LVM-space? Is it not usual to have > the > root fs in an VG/LV? > > How can I find out what device 58/0 is (/boot/ipleckd.boot is not on device > (94/0) but on (58/0)) ? > > > In any case, one way to test your assumption is to get rid of the > > root-on-LVM setup and try it with just a "normal" ext2 file system on > > /dev/dasda. I strongly suspect that will work for you. > > VGROOT spans over 2 disks, but it includes several LVs: > /dev/vgroot/lvroot vgroot 2048 1 > /dev/vgroot/lvusr vgroot 2048 1 > /dev/vgroot/lvvar vgroot 256 1 > /dev/vgroot/lvhome vgroot 128 1 > > 1 disk has a capacity of approx. 2,5 GB, so anything (including /boot, > excluding > /usr, /var, /home) should be on the first disk, shouldn't it? > > -- > > Werner Kuehnel > IMD GmbH (Mannheimer Versicherung) > Mannheim - Germany -- Werner Kuehnel IMD GmbH (Mannheimer Versicherung) Mannheim - Germany
