Help! - Hosed my fstab file

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
tracyandskye

Help! - Hosed my fstab file

Post by tracyandskye »

Is there a fairly simple way to recreate the default fstab file? I deleted everything without making a backup - duh.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
fwc

Re: Help! - Hosed my fstab file

Post by fwc »

You should be able to find examples online. Here is an example to base yours on from LM8:

Code: Select all

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda8 during installation
UUID=XXX-XXX-XXX-XXX-XXX /               ext4    errors=remount-ro 0       1
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto,exec,utf8 0       0
/dev/sda1       /mnt/windows           ntfs-3g    defaults        0 0
The first UUID is based around the Linux home disk. The second is the mount information for the CD ROM and the last is the mount information for a windows partition. You have to remember to create the folders in the /mnt directory if you want to use this system.
tracyandskye

Re: Help! - Hosed my fstab file

Post by tracyandskye »

Using some instructions and my fstab from a UNR installation on the same machine, I created this:

Code: Select all

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda5 during installation
0cc11d19-0bc1-4a5c-aa52-6ee2db9ee046 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda6 during installation
UUID=9cd69055-c746-4ac1-97ee-4a89feced20f none            swap                sw              0       0

192.168.0.194:/media/Data/server/Business/BPS /home/beautybooty/Documents/BPS nfs rsize=8192,wsize=8192,timeo=14,intr
The problem is that it keeps locking up. It started doing that after I messed up the fstab file, but I think I made some other changes that weekend too. Nothing else that should have cased a problem like this. I'm not sure but I think the problem may be coming from the USB ports. It seems like it's only locking when I have a mouse or mouser & keyboard plugged in (it's an Asus 1201N netbook). Does anything look wrong there? Do I need anything in reference to the USB ports?
distrohopper

Re: Help! - Hosed my fstab file

Post by distrohopper »

Code: Select all

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sda7 during installation
UUID=8056853d-8693-445b-bbf4-ab20af6c0886 /               ext4    errors=remount-ro 0       1
# /home was on /dev/sda8 during installation
UUID=b90219b1-8a5c-408a-9fa2-2604666a4b63 /home           ext4    defaults        0       2
# swap was on /dev/sda3 during installation
UUID=20186df7-065b-4670-b2f9-6e53b08cd4d5 none            swap    sw              0       0

# /data on /dev/sda2 (custom)
UUID=14a70acb-2754-4da9-9c6a-a34fa2790436 /data		ext4	defaults	0	2
This is my fstab file, it looks like your /proc may be improperly setup. Hope this helps.
altair4
Level 20
Level 20
Posts: 11461
Joined: Tue Feb 03, 2009 10:27 am

Re: Help! - Hosed my fstab file

Post by altair4 »

For one thing this line is incorrect - at least the syntax is incorrect:
0cc11d19-0bc1-4a5c-aa52-6ee2db9ee046 / ext4 errors=remount-ro 0 1
Should be:

Code: Select all

UUID=0cc11d19-0bc1-4a5c-aa52-6ee2db9ee046 /               ext4    errors=remount-ro 0       1
That's assuming the UUID numbers are correct.

To make sure use the LiveCD to open a Terminal and type:

Code: Select all

sudo blkid -c /dev/null
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
distrohopper

Re: Help! - Hosed my fstab file

Post by distrohopper »

That too :). I totally missed the missing UUID.
tracyandskye

Re: Help! - Hosed my fstab file

Post by tracyandskye »

Oops! That was dumb.

Thanks!
tracyandskye

Re: Help! - Hosed my fstab file

Post by tracyandskye »

I'm not 100% certain, but it appears that the last two lines (when they're uncommented of course, cause this machine to lock up randomly. I have the same lines in another machine, running Ubuntu, with no problems. Any ideas on how I can diagnose this?

Code: Select all

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda5 during installation
UUID=0cc11d19-0bc1-4a5c-aa52-6ee2db9ee046 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda6 during installation
UUID=9cd69055-c746-4ac1-97ee-4a89feced20f none            swap                sw              0       0

# 192.168.0.194:/media/Data/server/Business/BPS /home/beautybooty/Documents/BPS nfs rsize=8192,wsize=8192,timeo=14,intr
# 192.168.0.194:/media/Data /home/beautybooty/Documents/Server nfs rsize=8192,wsize=8192,timeo=14,intr
Locked

Return to “Installation & Boot”