2.4.x turns devfs on by default on s/390. I'd guess you have "mount devfs on boot" turned on in filesystem options - either turn it off, or edit your init/fstab records to point to the devfs path: /dev/dasd/<Dasd device number>/part1 if I recall, but that's from fuzzy memory.
-m On Fri, Oct 11, 2002 at 11:03:27PM +0100, Eddie Chen wrote: > I am having problem when I IPL 2.4.19 and getting message: > > > "7"[1A""[80C"[10D"[1;32mdone"[m""8Checking file systems..." > Parallelizing fsck version 1.19a (13-Jul-2000)" > fsck.ext2: No such file or directory while trying to open /dev/dasda1"" > (null): " > 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.ext2 /dev/dasda1 failed (status 8)! Run it manually!" > "7"[1A""[80C"[10D"[1;31mfailed"[m""8" > fsck failed. Please repair manually and reboot. The root" > file system is currently mounted read-only. To remount it" > read-write do:" > " > bash# mount -n -o remount,rw /" > " -- Michael Kershaw [EMAIL PROTECTED] Linux Systems Programmer, Information Technology "Don't worry, I'm sure they'll listen to Reason." -- Fisheye, Snowcrash
