I forgot, you also need to: /etc/init.d/network start before starting sshd /Tore
_________________________________________________ Tore Agblad System programmer, Volvo IT certified IT Architect Volvo Information Technology Infrastructure Mainframe Design & Development, Linux servers Dept 4352 DA1S SE-405 08, Gothenburg Sweden Telephone: +46-31-3233569 E-mail: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bauer, Bobby (NIH/CIT) [E] Sent: den 9 juni 2011 18:18 To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab There have been a couple of other methods that work but this is by far the simplest and it was user data that I had the problem with. I'll give this a try, thanks. Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -----Original Message----- From: Agblad Tore [mailto:tore.agb...@volvo.com] Sent: Thursday, June 09, 2011 11:30 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab I haven't read all the answers, but usually it works fine (when it is a mount for userdata that fails) to just mount everything manually: mount /usr mount /var mount /opt and so on. and after enough mounts just: /etc/init.d/sshd start and you can login as usual and fix the problem Cordialement / Vriendelijke Groeten / Best Regards / Med Vänliga Hälsningar Tore Agblad Volvo Information Technology Infrastructure Mainframe Design & Development SE-405 08, Gothenburg Sweden E-mail: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ ________________________________________ From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Bauer, Bobby (NIH/CIT) [E] [baue...@mail.nih.gov] Sent: Thursday, June 02, 2011 17:55 To: LINUX-390@VM.MARIST.EDU Subject: bad entry in fstab 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 <device> [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/
