Werner, 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?
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. Mark Post -----Original Message----- From: Werner Kuehnel [mailto:[EMAIL PROTECTED]] Sent: Monday, November 25, 2002 7:56 AM To: [EMAIL PROTECTED] Subject: SILO refuses to work Although reading and searching huge amounts of threads I can't figure out how to come around this problem. After installation of SLES for S/390 YaST tries to run SILO. It doesn't work, because YaST does not fill the -d option with the DASD (at least this is my opinion): The command chroot /mnt /sbin/silo -d -t2 resulted in an error. The command gave the following output: silo.c (line:280) 'stat (name, &dst)' returned 2='No such file or directory' o->ipldevice set to -t2 Anyway, I tried to run SILO manually and got: SuSE Instsys suse:/root # chroot /mnt /sbin/silo -d /dev/dasda -F /etc/silo.conf -t2 o->ipldevice set to /dev/dasda o->conffile set to /etc/silo.conf Testonly flag is now 0 Testlevel is set to -2 IPL device is: '/dev/dasda' /boot/ipleckd.boot is not on device (94/0) but on (58/0) silo.c (line:366) 'verify_file (o->bootsect, dev)' returned 22='Invalid argument' bootsector is: '/boot/ipleckd.boot'Usage: This is my silo.conf file: ipldevice=/dev/dasda image=/boot/image bootsect=/boot/ipleckd.boot map=/boot/boot.map root=/dev/dasda1 parmfile=/boot/parmfile testlevel=-2 readonly This is /proc/dasd/devices: 3397(ECKD) at (94:0) is dasda:active at blocksize: 4096, 601020 blocks, 2347MB 3398(ECKD) at (94:4) is dasdb:active at blocksize: 4096, 601020 blocks, 2347MB 3399(ECKD) at (94:8) is dasdc:active at blocksize: 4096, 601020 blocks, 2347MB 1097(ECKD) at (94:12)is dasdd:active at blocksize: 4096, 601020 blocks, 2347MB How can I find out what device (58/0) is where it finds /boot/ipleckd.boot? Volume group VGROOT is spanned over 2 devices, 3397 and 3399. Could that be the problem, that /mnt/boot is on the other device than 3397? Any help is very welcome. Werner -- Werner Kuehnel IMD GmbH (Mannheimer Versicherung) Mannheim - Germany
