I always keep a copy of the old file when working with Linux on z - for key files like /etc/fstab especially. That way I can issue single command from the 3270 terminal to get things back and not worry about vi/sed/etc. Next time maybe ;-)
Scott Rohling On Thu, Jun 2, 2011 at 10:19 AM, Brent Kincer <dev.bkin...@gmail.com> wrote: > In case you're not using IUCV terminals and don't have access to something > like 'vi', just use sed to comment out the offending line and reboot. > > Would go something like this: > mount -o remount,rw / > sed -i 's/.*LogVol08.*/#&/g' /etc/fstab > shutdown -r now > > That sed statement will comment out any line containing LogVol08 in > /etc/fstab. Correct your typo after the reboot. > > Hope this helps! > > On , Rogério Soares <rogerio.soa...@gmail.com> wrote: > >> do a CTRL+D, you will got aa single user mode,, just correct you >> > > /etc/fstab and reboot :) >> > > > > > > > > On Thu, Jun 2, 2011 at 12:55 PM, Bauer, Bobby (NIH/CIT) [E] >> baue...@mail.nih.gov> wrote: >> > > > > > I made a typo when I added a new logical volume to fstab, I misspelled >> the >> > > > logical volume mane. The reboot fails with: >> > > > >> > > > [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a >> > > > /dev/mapper/vg_labarc-LogVol08 >> > > > fsck.ext4: No such file or directory while trying to open >> > > > /dev/mapper/vg_labarc-LogVol08 >> > > > /dev/mapper/vg_labarc-LogVol08: >> > > > >> > > > 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 >> > > > >> > > > [FAILED] >> > > > >> > > > *** An error occurred during the file system check. >> > > > *** Dropping you to a shell; the system will reboot >> > > > *** when you leave the shell. >> > > > *** Warning -- SELinux is active >> > > > *** Disabling security enforcement for system recovery. >> > > > *** Run 'setenforce 1' to reenable. >> > > > Give root password for maintenance >> > > > (or type Control-D to continue): >> > > > >> > > > >> > > > If I give it the root password, the filesystem is read only. Not sure >> what >> > > > the Control-D will do for me but I don't seem to be able to pass it to >> the >> > > > system anyway. Any suggestions how to fix fstab without rebuilding the >> > > > system? Or some other method? >> > > > >> > > > Thanks >> > > > Bobby Bauer >> > > > Center for Information Technology >> > > > National Institutes of Health >> > > > Bethesda, MD 20892-5628 >> > > > 301-594-7474 >> > > > >> > > > >> > > > >> > > > ---------------------------------------------------------------------- >> > > > For LINUX-390 subscribe / signoff / archive access instructions, >> > > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 >> or >> > > > visit >> > > > http://www.marist.edu/htbin/wlvindex?LINUX-390 >> > > > ---------------------------------------------------------------------- >> > > > For more information on Linux on System z, visit >> > > > http://wiki.linuxvm.org/ >> > > > >> > > > > ---------------------------------------------------------------------- >> > > For LINUX-390 subscribe / signoff / archive access instructions, >> > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or >> visit >> > > http://www.marist.edu/htbin/wlvindex?LINUX-390 >> > > ---------------------------------------------------------------------- >> > > For more information on Linux on System z, visit >> > > http://wiki.linuxvm.org/ >> > > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
