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 [email protected] 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/
