I have access to a standalone COS box that I got from work, but for unknown reasons I am only able to boot it in emergency mode.
This might be basics for the average developer, but I need to copy a file from it and I have no idea where to start.
I was able to browse to the file locally and I found it, but I could use some help with copying it.
I cannot access this box with WinSCP or PuTTy, because I am unable to boot it up normally and make the changes so I could access it from my home network.
I only have FAT32 USB sticks and NTFS external USB drives.
I would have liked to boot it up normally so I could copy some more settings from it, but I gave up on that.
Sry for the late response, but I decided to make a proper backup and start with a clean install.
Not in the mood to make all sorts of minor changes that will not fix much, because I don't have a clue how to fix problems with the iptables.
Closing this case,
lsmod | grep ipt
Yesterday i tried booting all the kernels I have several times (back to 7.2), but with the same result.
I kept attempting to boot from the latest kernel until it finally worked. Normally I don't reboot my COS box.
I would not know how to look at log files during boot, but I told you that I have no experience with that.
Rebooting is not an option unless absolutely required, but I refuse to reboot 20 or more times for no reason.
I received this error message when I attempted to attach .txt files, so I had to post it here:
The file *.txt, which you are attempting to upload is in an unsupported format.
AFAIK, here is the information you requested:
Thanks in advance.
Isn't there a simpler way too solve this issue ... ?!?
I was thinking about making screenshots of the firewall rules.
Clearing the firewall to factory settings.
Manually add all the rules.
Anyway, I don't know what you mean by having a look at my boot.log, dmesg log and my messages log while booting for errors.
I have no experience with log files and at the moment I refuse to reboot, because it can take a sometimes 20 times before it boots up again.
This problem has always been there, even after I changed HD's and did a full reinstall.
A reinstall is not an option, because it would not solve the boot issues and I would lose a lot of data that I cannot backup on another disk right now.