I have a few questions I sincerely hope you'll help me with. I had a hard disk crash on one of my servers running ISPConfig. I can't boot it. But having attached this hard disk to another computer I saw that most of the files are intact. So I did a fresh install of ISPConfig 2.2.37 on a new hard disk drive (debian 5.0.7, perfect setup) and tried to manually restore some sites I didn't have fresh backups for. Of course it went well with the files inside web/ but when it came to MySQL... Well, that's what I did. I made a new db via the panel, and then copied the contents of /var/lib/mysql/old_db from the crashed disk to the corresponding /var/lib/mysql/new_db on the freshly installed server. Then I changed permissions of all these .frm .myd .myi files to 660 (I didn't touch the directory) and changed ownership to mysql:mysql (which are the default permissions - as I can see looking at the other "naturally" created databases). Then I rebooted and tried to load the site. Well, it didn't load, with MySQL error 1017, ER_FILE_NOT_FOUND This made this thinking that something is still wrong with the permissions. And indeed, when I chmodded the contents of /var/lib/mysql/new_db to 755, the site was finally up and running, seemingly without any problems. So, my questions are: 1. Are 755 permissions inside /var/lib/mysql/ somehow compromising the server's security? 2. What is keeping MySQL from seeing the copied files, taking into account the fact that they have ABSOLUTELY the same permissions (user, group, read-write-execute rights)? Is there some other "subtle" permission layer?