Write fstab file the right way

Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
To mount my disk, I have to follow the instructions of that question:
vgchange -ay /dev/dataVG --activationmode partial
mount -o ro,noload /dev/dataVG/dataLV /HFT
Otherwise, I got the following error : mount: /HFT: can't read superblock on /dev/mapper/VG-LV
So I modify /etc/fstab/, i.e.
# /etc/fstab: static file system information.
#
# 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>
/dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda2 during installation
UUID=5ee5828f-1dfa-48f3-84bd-7ddf7c33ea80 /boot ext4 defaults 0 2
# /boot/efi was on /dev/sda1 during installation
UUID=5ABB-56A8 /boot/efi vfat umask=0077 0 1
#/dev/mapper/ubuntu--vg-swap_1 none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0
# LVM disks
/dev/dataVG/dataLV /HFT ext4 defaults 0 0
When I reboot my computer, I have got a little problem with that file. I had to comment /dev/dataVG/dataLV /HFT ext4 defaults 0 0 in emergency mode.
How could I fix that it to do not get that problem again?
mount fstab
add a comment |Â
up vote
0
down vote
favorite
To mount my disk, I have to follow the instructions of that question:
vgchange -ay /dev/dataVG --activationmode partial
mount -o ro,noload /dev/dataVG/dataLV /HFT
Otherwise, I got the following error : mount: /HFT: can't read superblock on /dev/mapper/VG-LV
So I modify /etc/fstab/, i.e.
# /etc/fstab: static file system information.
#
# 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>
/dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda2 during installation
UUID=5ee5828f-1dfa-48f3-84bd-7ddf7c33ea80 /boot ext4 defaults 0 2
# /boot/efi was on /dev/sda1 during installation
UUID=5ABB-56A8 /boot/efi vfat umask=0077 0 1
#/dev/mapper/ubuntu--vg-swap_1 none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0
# LVM disks
/dev/dataVG/dataLV /HFT ext4 defaults 0 0
When I reboot my computer, I have got a little problem with that file. I had to comment /dev/dataVG/dataLV /HFT ext4 defaults 0 0 in emergency mode.
How could I fix that it to do not get that problem again?
mount fstab
IIRC, using--activationmode partialis required for a logical volume that is missing physical volumes. If that data is important to you, it may be best to back it all up and recreate the logical volume
â GracefulRestart
May 4 at 5:50
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
To mount my disk, I have to follow the instructions of that question:
vgchange -ay /dev/dataVG --activationmode partial
mount -o ro,noload /dev/dataVG/dataLV /HFT
Otherwise, I got the following error : mount: /HFT: can't read superblock on /dev/mapper/VG-LV
So I modify /etc/fstab/, i.e.
# /etc/fstab: static file system information.
#
# 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>
/dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda2 during installation
UUID=5ee5828f-1dfa-48f3-84bd-7ddf7c33ea80 /boot ext4 defaults 0 2
# /boot/efi was on /dev/sda1 during installation
UUID=5ABB-56A8 /boot/efi vfat umask=0077 0 1
#/dev/mapper/ubuntu--vg-swap_1 none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0
# LVM disks
/dev/dataVG/dataLV /HFT ext4 defaults 0 0
When I reboot my computer, I have got a little problem with that file. I had to comment /dev/dataVG/dataLV /HFT ext4 defaults 0 0 in emergency mode.
How could I fix that it to do not get that problem again?
mount fstab
To mount my disk, I have to follow the instructions of that question:
vgchange -ay /dev/dataVG --activationmode partial
mount -o ro,noload /dev/dataVG/dataLV /HFT
Otherwise, I got the following error : mount: /HFT: can't read superblock on /dev/mapper/VG-LV
So I modify /etc/fstab/, i.e.
# /etc/fstab: static file system information.
#
# 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>
/dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda2 during installation
UUID=5ee5828f-1dfa-48f3-84bd-7ddf7c33ea80 /boot ext4 defaults 0 2
# /boot/efi was on /dev/sda1 during installation
UUID=5ABB-56A8 /boot/efi vfat umask=0077 0 1
#/dev/mapper/ubuntu--vg-swap_1 none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0
# LVM disks
/dev/dataVG/dataLV /HFT ext4 defaults 0 0
When I reboot my computer, I have got a little problem with that file. I had to comment /dev/dataVG/dataLV /HFT ext4 defaults 0 0 in emergency mode.
How could I fix that it to do not get that problem again?
mount fstab
edited May 4 at 2:47
Jeff Schaller
31.1k846105
31.1k846105
asked May 4 at 1:13
Jeremie
83
83
IIRC, using--activationmode partialis required for a logical volume that is missing physical volumes. If that data is important to you, it may be best to back it all up and recreate the logical volume
â GracefulRestart
May 4 at 5:50
add a comment |Â
IIRC, using--activationmode partialis required for a logical volume that is missing physical volumes. If that data is important to you, it may be best to back it all up and recreate the logical volume
â GracefulRestart
May 4 at 5:50
IIRC, using
--activationmode partial is required for a logical volume that is missing physical volumes. If that data is important to you, it may be best to back it all up and recreate the logical volumeâ GracefulRestart
May 4 at 5:50
IIRC, using
--activationmode partial is required for a logical volume that is missing physical volumes. If that data is important to you, it may be best to back it all up and recreate the logical volumeâ GracefulRestart
May 4 at 5:50
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f441686%2fwrite-fstab-file-the-right-way%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
IIRC, using
--activationmode partialis required for a logical volume that is missing physical volumes. If that data is important to you, it may be best to back it all up and recreate the logical volumeâ GracefulRestart
May 4 at 5:50