First post here. I have been using OpenSuse 11.x for almost a year now, exclusively as my main machine.
I recently had a problem of some significance that I need help with to diagnose exactly what happened.
I recently was doing some development (via ethernet) (SSH, SFTP, HTTP, apache, mysql) and updating my machine. At the time I didn’t have “disable root login” in the SSH config file set correctly but I do have a complex password. But during the time frame, I also added the update aaa_base bugzilla #642289#674192 and kdelibs4 #686652 via YAST. Within the hour KDE crashes when attempting to run fsarchiver. I reboot.
Grub console appears. Never seen this before. (Googling and troubleshooting later…)
I mount /dev/sda1 (root sys) in the Systemrescue CD wizard and only the directories:
…appeared…(with a filesize of 4096, see pic)… How can this be?
Grub couldn’t find a filesystem nor could the Install DVD recognize it. So it seems as if parts of the system were taken down…but by what? I ran the check filesystem via gpart (on the repair CD) and the disk is okay.
Lastly, I was able to restore an earlier version of my sys via a fsarchiver image and am up and running with minimal discomfort.
Has anyone seen anything like this??? This is very troubling for me as I try to be as security-conscious as possible and had significant problems upgrading from 11.3 to 11.4. I have a hardware and software firewall, etc…
This is the way ls works (nothing to worry about). This is an output from my openSUSE and basically any linux I have used :
> ls -l
drwxr-xr-x 2 test users 4096 03-12 14:10 bin
drwxr-xr-x 2 test users 4096 03-12 14:10 Dokumenty
drwxr-xr-x 2 test users 4096 03-12 14:10 Muzyka
drwxr-xr-x 2 test users 4096 03-12 14:10 Obrazy
drwxr-xr-x 2 test users 4096 03-12 14:10 Pobrane
drwxr-xr-x 2 test users 4096 03-12 14:10 public_html
drwxr-xr-x 2 test users 4096 03-12 14:10 Publiczny
drwxr-xr-x 2 test users 4096 03-12 14:11 Pulpit
drwxr-xr-x 2 test users 4096 03-12 14:10 Szablony
drwxr-xr-x 2 test users 4096 03-12 14:10 Wideo
I’ve never used fsarchiver so I don’t know anything about it (could You tell us something more about this application) but maybe it’s an fsarchiver bug ? Did You check the logs before restoring an eariler version of your system ?
Thanks for responding. I didn’t check my logs after KDE crashed because I didn’t think there was something significantly wrong with my system. Boy, was I was wrong. :shame: Where I did ls was on my root sys, after the crash. My home is on a different partition. On the root sys, several important directories were missing…that’s why Grub couldn’t fix or OpenSuse couldn’t repair…
Could someone of hacked my system with the “enable root login” in SSH config on and deleted directories on my root partition (even with an extremely strong password)?
When using fsarchiver, an imaging program, I did this command to save an image of the root sys:
It’s possible but very unlikely. A strong password is very important but even more effective way to secure ssh is to set it up to listen on a port different than 22. There is a log for checking who logged into your system and when ("/var/log/secure" as far as I can remember) IMHO without the logs we can just speculate what happened untill it happens again but I hope it won’t and we will not have anything to talk about.
Thanks for your insight. Does it seem more likely that the updates crashed my system, or Fsarchiver (which was running as root) crashed it than a SSH hack? The symptom being missing critical directories?
Yes, I hope it doesn’t happen again. Now I know to make it a habit when something abnormal happens to check my logs immediately rather than just reboot.
So you did have a damaged file system. If so it is sometimes not possible to reconstruct all the pieces. Did you look in the Lost & found directory and see if some of the missing stuff is there? Note that if this is root then it is almost impossible to re-piece things back together. You must either restore from backup or reinstall.
As to why, I suggest that you may have mis-configured the Fsarchiver program which started to overwrite the root partition and caused the damage. But that is speculation.