[root@monkey alen]# mount -a [mntent]: line 0 in /etc/fstab is bad [mntent]: line 0 in /etc/fstab is bad Likewise, this error appears about 10 times during boot up, though, as far as I can tell, everything mounts. A search on DejaNews revealed the same problem on a debian mailing list, with the suggested solution of adding a newline (\n) to the last line in /etc/fstab. This did not remedy the problem for me.
Please show us the contents of your fstab file.
/dev/hda3 / ext2 defaults 1 1 /dev/hda1 /dos/c vfat exec,dev,suid,rw,umask=000 0 0 /dev/hdc1 /dos/d vfat exec,dev,suid,rw,umask=000 0 0 /dev/hdc5 /dos/f vfat exec,dev,suid,rw,umask=000 0 0 /dev/cdrom /mnt/cdrom iso9660 user,noauto,ro #0 0 /dev/fd0 /mnt/floppy3.5 ext2 user,noauto #0 0 /dev/fd1 /mnt/floppy5.25 ext2 user,noauto /dev/hdc3 /data ext2 defaults 1 2 /dev/hdc4 /usr ext2 defaults 1 3 /dev/hdc2 none ignore 0 0 0 none /proc proc defaults /dev/hda2 none swap sw
Op. I think I just found the problem. mount must not be parsing the file for comments correctly anymore. Hmm, that sounds like a relatively easy fix in the source code... For know, here is my solution. The lines that were: ----------------- /dev/cdrom /mnt/cdrom iso9660 user,noauto,ro # 0 0 /dev/fd0 /mnt/floppy3.5 ext2 user,noauto # 0 0 ----------------- become: ----------------- /dev/cdrom /mnt/cdrom iso9660 user,noauto,ro /dev/fd0 /mnt/floppy3.5 ext2 user,noauto ----------------- And my warnings disappear.
assigned to Cristian
There is also a line that has three zeros at the end, and that is an invalid line too. The parser in the new mount is far from perfect; however, this is what should be expected when the fstab is invalid.