[SOLVED] Cannot modify /etc/fstab because it is read-only mode
by slac from LinuxQuestions.org on (#52YJ1)
I have made a new-fresh Slackware's installation and it has been successfully except for one thing and it is that, I cannot modify the file /etc/fstab because it is read-only. Let me explain what happens.
After the Slackware installation, I cannot boot up because the file /etc/fstab has a wrong configuration. The root partition is trying to be mounted using the following line:
Code:/dev/sdb2 / ext4 defaults 1 1That is just wrong, because my root device/partition is: /dev/sda2. I think the setup of the Slackware installation made such wrong configuration because I used an USB to install slackware and during the installation the usb was /dev/sda and the HDD was /dev/sdb.
IT IS NOT a grub problem, even if the grub configuration file is using /dev/sdb just like /etc/fstab, because grub ultimately uses UUID to look up for the right partitions.
IT IS only a problem related to /etc/fstab for using /dev/sdX syntax instead of using UUID.
Just as I said, I cannot boot up because of /etc/fstab having the wrong configuration. After trying to boot up, an error prompt gives me an opportunity to go in single-user/maintenance mode, a introduce the root password and try to modify the /etc/fstab with correct configuration but it just doesn't let me because the file is supposedly in read-only mode even if I am supposedly logged-in as root user.
So, my questions are:
After the Slackware installation, I cannot boot up because the file /etc/fstab has a wrong configuration. The root partition is trying to be mounted using the following line:
Code:/dev/sdb2 / ext4 defaults 1 1That is just wrong, because my root device/partition is: /dev/sda2. I think the setup of the Slackware installation made such wrong configuration because I used an USB to install slackware and during the installation the usb was /dev/sda and the HDD was /dev/sdb.
IT IS NOT a grub problem, even if the grub configuration file is using /dev/sdb just like /etc/fstab, because grub ultimately uses UUID to look up for the right partitions.
IT IS only a problem related to /etc/fstab for using /dev/sdX syntax instead of using UUID.
Just as I said, I cannot boot up because of /etc/fstab having the wrong configuration. After trying to boot up, an error prompt gives me an opportunity to go in single-user/maintenance mode, a introduce the root password and try to modify the /etc/fstab with correct configuration but it just doesn't let me because the file is supposedly in read-only mode even if I am supposedly logged-in as root user.
So, my questions are:
- How to modify the /etc/fstab file, using maintenance mode, if even using such mode and logged-in as root, it doesn't let modify the file?
- Why doesn't the Slackware installation setup use UUID by default for /etc/fstab instead of /dev/sdX?