Hello Kevin, I recommend that you stop using EVMS and start using LVM2. The direction with SLE11 and going forward is to use LVM2 as the logical volume manager and cLVM2 as the clustered filesystem aware volume manager. You will not need to reinstall SLES10, LVM will be able to see the LVM LVs which are just contained within EVMS.
Mike >>> On 3/27/2009 at 2:15 PM, in message <[email protected]>, "George, Kevin A" <[email protected]> wrote: > I am having a problem with SLES 10 where it will not always boot > because it is unable to find any of the file systems that are using > EVMS. I am running under z/VM 5.3 and using mini disks. All are using > ext3 as the file system. When I have this problem I can usually reboot > and it will start correctly. > > I have installed using the following DASD configuration all on 1 > physical mod 9 volume: > > 0201 ROOT 1004 Cyl / > 0202 EVMS 1004 Cyl /home/ > 0203 EVMS 3000 Cyl /opt/ > 0204 EVMS 3000 Cyl /usr/ > 0205 EVMS 1004 Cyl /tmp/ > 0206 EVMS 1004 Cyl /var/ > > When I receive the boot failure I see the following messages in > my log: > > error on stat() /dev/evms/lvm2/home/home: No such file or > directory > error on stat() /dev/evms/lvm2/opt/opt: No such file or > directory > error on stat() /dev/evms/lvm2/tmp/tmp: No such file or > directory > error on stat() /dev/evms/lvm2/usr/usr: No such file or > directory > error on stat() /dev/evms/lvm2/var/var: No such file or > directory > fsck.ext3: No such file or directory while trying to open > /dev/evms/lvm2/home/home > /dev/evms/lvm2/home/home: > > The superblock could not be read or does not describe a correct > ext2 > filesystem. If the device is valid and it really contains an > ext2 > filesystem (and not swap or ufs or something else), then the > superblock > is corrupt, and you might try running e2fsck with an alternate > superblock: > e2fsck -b 8193 <device> > > > > fsck.ext3 /dev/evms/lvm2/home/home failed (status 0x8). Run > manually! > error on stat() /dev/evms/lvm2/opt/opt: No such file or > directory > [/sbin/fsck.ext3 (1) -- /opt] fsck.ext3 -a > /dev/evms/lvm2/opt/opt > fsck.ext3: No such file or directory while trying to open > /dev/evms/lvm2/opt/opt > /dev/evms/lvm2/opt/opt: > > The superblock could not be read or does not describe a correct > ext2 > filesystem. If the device is valid and it really contains an > ext2 > filesystem (and not swap or ufs or something else), then the > superblock > is corrupt, and you might try running e2fsck with an alternate > superblock: > e2fsck -b 8193 <device> > > > > > Any ideas why I am receiving these messages and how to fix it so > it will always boot properly. I do need to have EVMS or lvm for the file > systems and would prefer EVMS. > > > Additional Information: > > SPident > > CONCLUSION: System is up-to-date! > found SLE-10-s390x-SP2 + "online updates" > > Kernel Version - 2.6.16.60-0.34-default > > cat /etc/fstab > > /dev/disk/by-path/ccw-0.0.0201-part1 / ext3 > acl,user_xattr 1 1 > /dev/evms/lvm2/home/home /home ext3 > acl,user_xattr 1 2 > /dev/evms/lvm2/opt/opt /opt ext3 > acl,user_xattr 1 2 > /dev/evms/lvm2/tmp/tmp /tmp ext3 > acl,user_xattr 1 2 > /dev/evms/lvm2/usr/usr /usr ext3 > acl,user_xattr 1 2 > /dev/evms/lvm2/var/var /var ext3 > acl,user_xattr 1 2 > /dev/disk/by-path/ccw-0.0.0200-part1 swap swap none 0 0 > > > > > ------------------- > Kevin George > U.S. Office of Personnel Management > > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
