Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


How does your KVM VPS CentOS 7 /etc/fstab look like please?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

How does your KVM VPS CentOS 7 /etc/fstab look like please?

The KVM VPS with centos-7.9-x86_64
uname -r
4.19.0-5-amd64

I think that mine is wrong:

# /etc/fstab
# Created by anaconda on Mon May 14 08:32:03 2018
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
LABEL=root /                       ext4    defaults        1 1

How your KVM CentOS7 /etc/fstab look like please?

I am currently in rescue mode:

NAME   MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vdb    254:16   0  60G  0 disk 
└─vdb1 254:17   0  60G  0 part /
vda    254:0    0   2G  0 disk 
└─vda1 254:1    0   2G  0 part

Comments

  • jonathanjonathan Member, LIR
    edited September 2022

    My KVM CentOS 7.9 /etc/fstab:

    # /etc/fstab
    #
    # Accessible filesystems, by reference, are maintained under '/dev/disk'
    # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
    #
    /dev/sda /                       ext4    defaults        1 1
    /dev/sdb none                    swap    defaults        0 0
    
    Thanked by 1postcd
  • postcdpostcd Member
    edited September 2022

    I have tried this, but that not made VPS connectable. I have tried also /dev/vd* with same result. Network configuration /etc/sysconfig/network-scripts/ifcfg-eth0, iptables output looked ok and no iptables rules loaded at boot.
    If anyone have different fstab on KVM CentOS 7 VPS, please share.
    I think i will reinstall VPS now.
    UPDATE: after reinstall i have found that working /etc/fstab and /etc/sysconfig/network-scripts/ifcfg-eth0 are identic as on non working system. So it had to be different issue.

Sign In or Register to comment.