Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I'm running CentOS 6.4 in a VMWare Player virtual machine. I was trying to add two partitions to the file system. First I used fdisk to add the partitions, then mke2fs, then I mounted the partitions. Then I manually edited /etc/fstab, I added lines for the new partitions listed by blkid.
When I restarted, the OS is failing to start, it brings me to a terminal. So I tried to undo the changes I made to the /etc/fstab file, but it's saying that everything is read only, even though I am root. It won't let me remove the lines I added before to /etc/fstab.
Does anybody know how I can recover? At least how to get the stupid thing to boot again.
I think you need to remount the filesystem in rw mode:
mount -o rw,remount /
After that you can edit /etc/fstab and revert your changes, save the file and reboot.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
Installed windows 10 on a new SSD but I apparently made the mistake of doing this while the original windows 10 HDD was still connected. Apparently the windows 10 installer edits the EFI of the original drive, which is definitely not wanted. Anyway, this causes the original windows 10 installation, on the original drive, to fail to boot because the EFI now points to a drive that doesn't exist. How can the EFI on the original drive be updated to correct this?
After messing around for a day or two I found out that none of the bootrec commands posted everywhere worked. For example:
bootrec /fixboot
The system cannot find the file specified.
The solution was to use "EasyUEFI" by "Hasleo Software" to edit the EFI to point to the actual windows installation. Took all of 2 seconds to fix after that.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
i had an error at Ubuntu 17.04 before booting. It said: "UNEXPECTED INCONSISTENCY, RUN FSCK MANUALLY" . So i typed after finding the problem's solution in Google: fsck /dev/sda2 . After rebooting my System worked normally without any errors. My question is: what does fsck /dev/sda2 mean?
fsck is the linux file system check command. You can use it to check if there are any errors or attempt to repair errors in the file system. man fsck to learn more about that.
dev/sda2 is the drive which is causing the error. The a part refers to the first disk, so most likely the one you're booting from and the 2 part means the second partition.
Without anymore details it's quite hard to tell what the actual problem is. Possibly it's a corrupted drive or that it is dying. If possible try to back up your data from it.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
Today,I encounter a very tough problem which cost me nearly 6 hours.
When I remove a file called ha_wan.conf using rm -rf ha_wan.conf command under /etc directory,Success.When I use ls -al command to see the result,The file disappear.
But when I reboot the linux system,same file named ha_wan.conf come back,located under /etc/ directory.
I tried to delete it many many times,It is the same result.
What should I do,I want to permanently remove that file.Thanks.
There's no magic. You removed the file. If you still see it after a reboot, it means one of two things:
(very likely) Some service recreates the files on boot, or periodically. You can probably use standard system tools to find out which package contained that file. (for example dpkg -S ha_wan.conf in debian-like systems)
(unlikely) You're running some interesting system which uses a temporary filesystem in /etc. If you're using a standard desktop distribution, that's improbable. But if it's some kind of router / special device, then it could happen.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about programming within the scope defined in the help center.
Improve this question
I want to install two centOS V6.2 on the same Hardidsk but on different partition. After installing on different different partition, at the time of booting it shows only centOS which is installed at last.
Can some help me to install two centOS on the same Harddrive.
I assume that you are using GRUB. Bootup with whatever CentOS that boots up. Open the grub.conf file (normally under /boot/grub). Find the kernel and initramfs of the other installation of CentOS.(usually under /boot)
Copy the title, root, kernel and initrd lines in grub.conf file, and paste those lines after the existing ones. Make changes to the newly pasted lines. Change the title to reflect the text in the new menu. Change root to the / of the other installation partition in GRUB terms. Change the kernel and initrd params to reflect the location of other kernel and initramfs.
Delete the line 'hiddenmenu' and increase the timeout to display GRUB menu properly. Save the changes and reboot.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about programming within the scope defined in the help center.
Improve this question
I recently made the following (i believe important) changes to my system
Actually I was following this tutorial to use something called Linux Containers.
So can you tell me if any of the following stuff is capable enough to crash my system ?
1. Making changes to /etc/fstab or
2. mount /cgroup which will try to mount cgroups automatically or
3 making changes to etc/network/interfaces or
4 making changes to /etc/resolv.conf
A typo in fstab can definitely make a system un-bootable. However, you should be able to boot from CD, mount the HD, and fix it.