fsck error Couldn't find matching filesystem: LABEL=/var

[David Tonhofer]

Mermaid140 at aol.com wrote:
> During a required fsck session several filesystems returned this error 
> message.  I can't get beyond that.  Is there a way to fix this or is the system just 
> dead in the water?
>
>   
What if you "fsck"  by  device instead of by label, i.e. run

fsck /dev/hda4

instead of

fsck /var

If the ext2 label is gone, it can be rewritten with e2label. Do not do 
this yet, though.

 From the man page:

       fsck is used to check and optionally repair one  or  more  Linux  
file
       systems.  filesys can be a device name (e.g.  /dev/hdc1, 
/dev/sdb2), a
       mount point (e.g.  /, /usr, /home), or an ext2 label or UUID 
specifier
       (e.g.  UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root).  
Nor-
       mally, the fsck program will try to run filesystems on different 
phys-
       ical  disk drives in parallel to reduce total amount time to 
check all
       of the filesystems.


       e2label will display or change the filesystem label on the ext2 
filesystem located on device.
       If the optional argument new-label is not present, e2label will 
simply display the current filesystem label.
       If the optional argument new-label is present, then e2label will 
set the filesystem label to be new-label.  Ext2 filesystem labels can be 
at most 16
       characters long; if new-label is longer than 16 characters, 
e2label will truncate it and print a warning message.
       It is also possible to set the filesystem label using the -L 
option of tune2fs(8).