[SOLVED] What in my /etc/fstab is causing the parse error

mzsade · 08-15-2015, 12:31 AM

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;

Code:

# UNCONFIGURED FSTAB FOR BASE SYSTEM
proc	/proc	proc	defaults	0	0
# /dev/sda9
PARTUUID=000e68b3-01			/boot/efi	vfat	defaults	0	0
# /dev/sda5
UUID=a75db3f8-503b-49f0-ad36-54dea3542bdf   swap	swap	sw	0	0
# /dev/sda10
UUID=0c3a9cf3-2eec-4690-afe4-2ed2d2db66f4	/	ext4	rw,errors=remount-ro	0	1
# /dev/sda11
UUID=b84d7b4b-9cc7-4b36-99e4-be0cdae6eb46	/home	ext4		defaults        0       2

I have tried using both separately, the UUID and the PARTUUID from my blkid;

Code:

/dev/sda1: UUID="1009-6465" TYPE="vfat" PARTUUID="000e68b3-01"
/dev/sda5: UUID="a75db3f8-503b-49f0-ad36-54dea3542bdf" TYPE="swap" PARTUUID="000e68b3-05"
/dev/sda6: LABEL="LMDEmate" UUID="a8dd5bbe-a6d3-476b-b432-f5000588ce4d" TYPE="ext4" PARTUUID="000e68b3-06"
/dev/sda7: LABEL="LMDExfce" UUID="131d61cd-178c-4229-be08-9fb36db48ebd" TYPE="ext4" PARTUUID="000e68b3-07"
/dev/sda8: LABEL="DebianXFCE" UUID="56bf247c-4533-4320-89cd-7b304016cbcf" TYPE="ext4" PARTUUID="000e68b3-08"
/dev/sda9: UUID="40D3-F34E" TYPE="vfat" PARTUUID="000e68b3-09"
/dev/sda10: UUID="0c3a9cf3-2eec-4690-afe4-2ed2d2db66f4" TYPE="ext4" PARTUUID="000e68b3-0a"
/dev/sda11: UUID="b84d7b4b-9cc7-4b36-99e4-be0cdae6eb46" TYPE="ext4" PARTUUID="000e68b3-0b"

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.

Randicus Draco Albus · 08-15-2015, 12:46 AM

Quote:

Somehow managed to rewrite the /etc/fstab

Code:

# /dev/sda9
PARTUUID=000e68b3-01			/boot/efi	vfat	defaults	0	0

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.)

mzsade · 08-15-2015, 02:41 AM

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..

Randicus Draco Albus · 08-15-2015, 03:15 AM

Then my guess was wrong. I know nothing about setting up EFI/UEFI.

TobiSGD · 08-15-2015, 03:18 AM

I am not sure if the PARTUUID thing is understood by the mount program, try it with the UUID instead.

mzsade · 08-15-2015, 03:56 AM

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.

mzsade · 08-15-2015, 05:55 AM

Hah!

Code:

:~$ sudo fsck -y /dev/sda10
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
/dev/sda10: clean, 57416/1589248 files, 685257/6347520 blocks
:~$ sudo fsck -y /dev/sda9
fsck from util-linux 2.25.2
fsck.fat 3.0.27 (2014-11-12)
/dev/sda9: 5 files, 64/124424 clusters

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?