Or just link the VM minidisk with the root file system for this failing system as R/W on an working linux system, let's call that the maintenance system. On the maintenance system, enable and mount that temporary volume. Now you have a fully functional linux system and can use any tool you like to correct the typo.
Unmount, release/detach the minidisk when done and then boot the original failing system. Aria -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bauer, Bobby (NIH/CIT) [E] Sent: Thursday, June 02, 2011 1:32 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab Thanks to everybody for help, especially for the remount command. Never did find a way to send Control-D The sed command worked perfect when I tested it on a running system but would not work from the maintenance mode. I kept getting the "Unterminated `s'" error and it looked like the # was causing a problem. We escaped the # like this \# and sed added a new line above the LogVol08 line. One of the guys said we should just use sed to delete the line and sure enough, we deleted the bad line in fstab and was able to ipl it. I think I learned my lesson to make backups no matter how simple a change it is. Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -----Original Message----- From: Brent Kincer [mailto:dev.bkin...@gmail.com] Sent: Thursday, June 02, 2011 12:19 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab 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/ ---------------------------------------------------------------------- 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/
