aleXimon wrote:Then, if i do:
I have a fresh installed list of directories
Do you want to say it looks in the directory just about this:
Code: Select all
$ ls -la
total 516
drwxr-xr-x 74 ale users 24576 Dez 10 22:01 ./
drwxr-xr-x 5 root root 4096 Nov 13 2014 ../
-rw------- 1 ale users 8286 Dez 10 22:01 .ICEauthority
-rw------- 1 ale users 121 Dez 10 22:01 .Xauthority
-rw-r--r-- 1 ale users 149 Aug 10 2009 .Xresources
[...]
drwxr-xr-x 14 ale users 4096 Dez 10 12:01 Desktop/
drwxr-xr-x 32 ale users 36864 Dez 1 01:29 Downloads/
drwxr-xr-x 2 ale users 4096 Jan 15 2015 Videos/
$
Can you continue this spelling always further like this:
Code: Select all
ls -li /home
ls -li /home/home
ls -li /home/home/home
ls -li /home/home/home/home
ls -li /home/home/home/home/home
ls -li /home/home/home/home/home/home
and are there always the directories from the root directory to see?
If so, do the directories have content? E.g.
Code: Select all
/home/bin
/home/home/bin
/home/home/home/bin
If they are not empty, who owns e.g. cat
and are then the inode numbers / index numbers
from /home/bin/cat identical to /home/home/bin/cat ?
Code: Select all
ls -li /home/bin/cat
ls -li /home/home/bin/cat
aleXimon wrote:Could I remove this files?
I would say:
no! As long as you do not know how this strangely designed file system was created, operations can lead to further errors.
If the index numbers are not identical, something went wrong when the user was created or at a later time. Then the problem, perhaps, can be corrected by recursive deletion. If directories or files in this faulty tree do not have ownership ale:users, the recursive deletion must be done by the superuser, and it may be dangerous.
If they are identical, the file system on the home partition is defective. Because all directories and files with identical index numbers would be 'hard linked' to each other.
Before that, you should have the file system checked for /dev/sda9 by e2fsck. If this finds errors, which I very strongly assume, then a deletion would not fix the errors.
To check the file system, quit all applications. Unmount all external data carriers. Change to Runlevel 1. Execute
cd / . Execute
sync. Then execute all the following commands as rootuser / superuser or with sudo prefix.
or
then
If e2fsck shows errors, you can try:
or
See the differences for switches '
y' and '
p' in the manual: man e2fsck.
Then
or
In your place, I would give up, however, as soon as errors are displayed, because the effort is not worth for you. Your home directory contains, so shortly after the installation, still no important data. Instead, I would perform a new installation. At the appropriate point during the installation, I would delete the partition and write the partition table immediately (delete command, write command). Then re-create the partition, specifying the correct partition type (probably 8300). Then write the partition table again immediately. I would do this with /dev/sda9 and /dev/sda7. It does not hurt to perform the operation with the swap partition (partition type probably 8200). This ensures that the partition table for these partitions is set correctly. In the further course of the installation, the two partitions (8300) must be assigned to the directory trees '/' and '/home', formatted and provided with the EXT4 file system. I do not know how the SalixLive installation offers that. In the non-live Salix installation, you can format partitions 'extensively' instead of 'quick'. If it is a HDD, a low-level formatting (extensively) gives the S.M.A.R.T firmware the possibility to replace defective sectors with reserve sectors.
There are NTFS-3G partitions on the hard drive. Also, the partition numbering is not continuous. This is generally not a problem, but if Windows is installed, this operating system can also be responsible for a possible damage to the EXT file system. Please do not start Windows until the error is fixed. Also responsible may be a faulty partitioning with overlapping partitions starts and ends.
