We suffered a system crash last week, on a Multiprise 3000, due to an unexpected OS/2 dump and reboot. When the system was restarted, our Linux image hung in the boot fsck step, which apparently failed due to an excessive number of parallel fsck's being attempted. I brought up the CD-ROM image, did the "insmod dasd dasd=...", a "mount /dev/dasdb1 /mnt", a "chroot /mnt", then "cd /etc" and "vi fstab". I then changed the rightmost column to serialize the fsck's (see below).
Original /etc/fstab: jimrich@dalvs1:/etc > cat fstab.orig /dev/dasda1 swap swap defaults 0 0 /dev/dasdb1 / ext2 defaults 1 1 /dev/dasdc1 /w1 ext2 defaults 1 2 /dev/dasdd1 /w2 ext2 defaults 1 2 /dev/dasde1 /w3 ext2 defaults 1 2 /dev/dasdf1 /w4 ext2 defaults 1 2 /dev/dasdg1 /w5 ext2 defaults 1 2 /dev/dasdh1 /w6 ext2 defaults 1 2 /dev/dasdi1 /w7 ext2 defaults 1 2 /dev/dasdj1 /w8 ext2 defaults 1 2 /dev/dasdk1 /w9 ext2 defaults 1 2 /dev/dasdl1 /wa ext2 defaults 1 2 /dev/dasdm1 /wb ext2 defaults 1 2 /dev/dasdn1 /wc ext2 defaults 1 2 /dev/dasdo1 /wd ext2 defaults 1 2 /dev/dasdp1 /we ext2 defaults 1 2 /dev/dasdq1 /wf ext2 defaults 1 2 /dev/dasdr1 /usr ext2 defaults 1 2 /dev/dasds1 /opt ext2 defaults 1 2 /dev/dasdt1 /pub ext2 defaults 1 2 /dev/dasdu1 /home ext2 defaults 1 2 /dev/dasdv1 /usr/lib ext2 defaults 1 2 /dev/dasdw1 /usr/local ext2 defaults 1 2 /dev/dasdx1 /usr/share ext2 defaults 1 2 proc /proc proc defaults 0 0 # End of YaST-generated fstab lines Edited /etc/fstab: jimrich@dalvs1:/etc > cat fstab /dev/dasda1 swap swap defaults 0 0 /dev/dasdb1 / ext2 defaults 1 1 /dev/dasdc1 /w1 ext2 defaults 1 2 /dev/dasdd1 /w2 ext2 defaults 1 3 /dev/dasde1 /w3 ext2 defaults 1 4 /dev/dasdf1 /w4 ext2 defaults 1 5 /dev/dasdg1 /w5 ext2 defaults 1 6 /dev/dasdh1 /w6 ext2 defaults 1 7 /dev/dasdi1 /w7 ext2 defaults 1 8 /dev/dasdj1 /w8 ext2 defaults 1 9 /dev/dasdk1 /w9 ext2 defaults 1 10 /dev/dasdl1 /wa ext2 defaults 1 11 /dev/dasdm1 /wb ext2 defaults 1 12 /dev/dasdn1 /wc ext2 defaults 1 13 /dev/dasdo1 /wd ext2 defaults 1 14 /dev/dasdp1 /we ext2 defaults 1 15 /dev/dasdq1 /wf ext2 defaults 1 16 /dev/dasdr1 /usr ext2 defaults 1 17 /dev/dasds1 /opt ext2 defaults 1 18 /dev/dasdt1 /pub ext2 defaults 1 19 /dev/dasdu1 /home ext2 defaults 1 20 /dev/dasdv1 /usr/lib ext2 defaults 1 21 /dev/dasdw1 /usr/local ext2 defaults 1 22 /dev/dasdx1 /usr/share ext2 defaults 1 23 proc /proc proc defaults 0 0 # End of YaST-generated fstab lines I then did a "shutdown -h now" on the CD-ROM system, and brought up the Linux image. It did the individual fsck's fairly rapidly, and came up! You may want to take the conservative approach, and edit your fstab's now, to avoid having to recover later. I expect the Linux distributors will fix this glitch on future releases. Otherwise, Linux for S/390 has been extremely stable for us, and a pleasure to work with. Regards, Jim Rich BEA Systems, Inc.
