LinuxQuestions.org - edit a file /etc/fstab , what parameters can be changebale and which parameters

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - edit a file /etc/fstab , what parameters can be changebale and which parameters (https://www.linuxquestions.org/questions/debian-26/edit-a-file-etc-fstab-what-parameters-can-be-changebale-and-which-parameters-4175597990/)

edit a file /etc/fstab , what parameters can be changebale and which parameters

Hi guys,
I can't find any detail explanation which parameters on /etc/fstab file I can change and not cause critical errors for system. Which values they can get.

After i change some parameters I stuck after reboot system on "Emergency-mode" and sometimes system changed to red-only.

Hi,

/etc/fstab is very sensitive file.
ALL parameters can bring your system enter the emergency mode.

You really need to know what you are doing while editing that file.
You can find good tutorial in the man page or googling.

If you provide specific information as to what settings you have attempted to change and what you wish to accomplish, perhaps more precise responses could be provided.

When I edit /etc/fstab, I commonly comment out the line I intend to change and create a new line with the changes I wish to make. That way, I can quickly restore the original line if I break something.

The Arch wiki has a good article about /etc/fstab: https://wiki.archlinux.org/index.php/Fstab

The man page (man fstab) is also a good reference.

Can you please post the contents of your /etc/fstab here. That will allow us to better answer your question.

Quote:

Originally Posted by hydrurga (Post 5658886)

Can you please post the contents of your /etc/fstab here. That will allow us to better answer your question.

This is content of my

Code:

fstab

file

Code:

# Use 'blkid' 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>

# / was on /dev/mmcblk0p2 during installation

UUID=568132ff-7f47-48f2-aaae-87454a461df2 /              ext4    errors=remount-ro 0      0

# /boot was on /dev/mmcblk0p1 during installation

UUID=85074b4a-e89a-48d6-aa48-0dbc3ead6839 /boot          ext2    defaults        0      0

# swap was on /dev/mmcblk0p5 during installation

UUID=4382df77-81fe-4310-9e1f-b92ce6b551fe none            swap    sw              0      0

#10.0.0.1:/home/developer/devel /root/devel nfs rw,async,hard,intr 0 0

When I change <dump> or <pass> to 1 instead of 0 system start behave strange

Quote:

Originally Posted by lenin99 (Post 5659324)

This is content of my

Code:

fstab

file

Code:

# Use 'blkid' 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>

# / was on /dev/mmcblk0p2 during installation

UUID=568132ff-7f47-48f2-aaae-87454a461df2 /              ext4    errors=remount-ro 0      0

# /boot was on /dev/mmcblk0p1 during installation

UUID=85074b4a-e89a-48d6-aa48-0dbc3ead6839 /boot          ext2    defaults        0      0

# swap was on /dev/mmcblk0p5 during installation

UUID=4382df77-81fe-4310-9e1f-b92ce6b551fe none            swap    sw              0      0

#10.0.0.1:/home/developer/devel /root/devel nfs rw,async,hard,intr 0 0

When I change <dump> or <pass> to 1 instead of 0 system start behave strange

Can you try setting <pass> to 1 for / and 2 for /boot. Leave it as 0 for the swap partition, and leave all the <dump>s as 0 (assuming you're not using the dump utility).

Let us know what happens.

As a side question, are you using Grub? If so, after you've rebooted, can you run update-grub as root and paste the output here?

Quote:

Originally Posted by hydrurga (Post 5659329)

I use bootloader

Quote:

Originally Posted by lenin99 (Post 5659356)

I use bootloader

I've never heard of that (the term "bootloader" on its own seems kind of generic).

Is it one of the ones listed here?: https://en.wikipedia.org/wiki/Compar...f_boot_loaders or https://wiki.debian.org/BootLoader