[SOLVED] What in my /etc/fstab is causing the parse error
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Linux Mint 9, Linux Mint 17.2(xfce), LMDE2(Mate), Debian Jessie minimal (with standalone OBox)
Posts: 299
Rep:
[SOLVED] What in my /etc/fstab is causing the parse error
Code:
~$ sudo fsck -y /dev/sda9
fsck from util-linux 2.25.2
fsck: /etc/fstab: parse error at line 4 -- ignore
fsck.fat 3.0.27 (2014-11-12)
/dev/sda9: 5 files, 64/124424 clusters
Buggered up my HDD install while trying to install on a USB flash drive. Somehow managed to rewrite the /etc/fstab, and thanks to reFind for the most part, i am able to boot into it again but please tell me how to rewrite this correctly;
I do not expect you to restrain yourselves from bursting into peals of hysterical laughter, i was creating, deleting, moving and resizing partitions like a drunken monkey..but please do tell what this blighted parse error is.
I am guessing that the problem is your Linux system now has a vfat boot partition. If I remember correctly, it should be ext2 or ext4. (I believe I used to set up my Linux systems with an ext2 /boot, but it has been a while and my memory is getting foggy.)
Last edited by Randicus Draco Albus; 08-15-2015 at 12:48 AM.
Distribution: Linux Mint 9, Linux Mint 17.2(xfce), LMDE2(Mate), Debian Jessie minimal (with standalone OBox)
Posts: 299
Original Poster
Rep:
Efi boot partitions are supposed to be vfat, aren't they? And i always had one, sda1, that's the one on which reFind is installed, has been vfat from the very beginning..
Distribution: Linux Mint 9, Linux Mint 17.2(xfce), LMDE2(Mate), Debian Jessie minimal (with standalone OBox)
Posts: 299
Original Poster
Rep:
Did that too but a sudo fsck -y on it from other partitions still gives me that parse error. I suspect it's because the new UUID after grub rescue and all that messing around with got shortened and the error lies in the insertion of the correct number of spaces/tabbings in the UUID line. I thought of generating new UUIDs with Gparted from another partition or a live CD but i do not want to jeopardize what still works for all purposes, unless it's a sure thing.
Seems the UUIDs of the swap in the /etc/fstab of all my other partitions were outdated, edited them all from one bootable partition and problem solved. I am like a dog with a bone, aren't i?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.