Posts by sjox

sjox · Other Issues

It works!
Due to a flash of inspiration, I have saved the root partition using fsarchiver, reformatted and played back!
Fsarchiver also secures the UUid and other attributes but apparently the inodes are reassigned!

Result:

root@pchome1:~# touch /usr/lib/cups/backend-available/Hallo_No12.txt
root@pchome1:~# 
root@pchome1:~# ls -li /usr/lib/cups/backend-available/
insgesamt 192
1088658 -rwxr--r-- 3 root root 22760  5. Nov 15:45 dnssd
1101290 -rw-r--r-- 1 root root     0 17. Nov 16:36 Hallo_No12.txt
1088659 -rwxr--r-- 2 root root 51520  5. Nov 15:45 lpd
1088657 -rwxr-xr-x 2 root root 30952  5. Nov 15:45 snmp
1088660 -rwxr-xr-x 2 root root 47424  5. Nov 15:45 socket
1088656 -rwxr--r-- 2 root root 35048  5. Nov 15:45 usb
root@pchome1:~# 
root@pchome1:~# 
root@pchome1:~# find / -xdev -inum 12
/sbin
root@pchome1:~# 
root@pchome1:~# ls -li /sbin
12 lrwxrwxrwx 1 root root 8  3. Nov 19:25 /sbin -> usr/sbin
root@pchome1:~#

There are now completely different inodes and the inode 12 is fixed to "/sbin"!
(now he can't bluff in any other way)
"fsck.ext4" does not return any errors anymore!

Unfortunately, I have no explanation why,when,who...

Thus done
Thanks again

sjox · Other Issues

As it looks, not many should have this problem!
I'm probably the only one...

Thanks to "g4sra" and "stultumanto"!

The result of "find":

find / -xdev -inum 12
/usr/lib/cups/backend-available/Hello_No12.txt

It's the only with Inode 12!

or:

find / -inum 12
/dev/console
/sys/hypervisor
/sys/fs/cgroup/memory.pressure
/usr/lib/cups/backend-available/Hello_No12.txt
/run/user/1000/at-spi/bus_0

Then I rebooted and started immediately from the "Devuan-Excalibur-Live-System" (Ventoy)!
(so it was NOT booted from the built-in SSD)

The result:

fsck.ext4 -n -f /dev/nvme0n1p3
e2fsck 1.47.2 (1-Jan-2025)
Pass 1: Checking inodes, blocks, and sizes
Orphan file inode 12 is not in use, but contains data.  Clear? no

Pass 2: Checking directory structure
Entry 'Hello_No12.txt' in /usr/lib/cups/backend-available (26756) has invalid inode #: 12.
Clear? no

Pass 3: 

and so on...

The SSD was shot down already when driving down!

The result is always the same - no matter what directory - as soon as Inode number 12 is assigned anywhere,
then the file system is shot.

That's why I've also asked the artificial intelligence (https://you.com/?chatMode default)

I have shortened the answer:

Summary:
• Inodes 1–11 are reserved for special purposes in ext4.
• Inode assignment is automatic and based on the first available inode.
• You cannot directly control inode numbers during file creation.
• Consistent problems with inode 12 suggest underlying file system corruption or hardware issues .
• Inode 12 corresponds to one specific file or directory at a time.
• The inode stores metadata, not the filename.
• Filenames are directory entries that point to inode numbers.
• Multiple filenames can share the same inode (hard links).
• When a file is deleted, its inode number (like 12) can be reused for new files.
This explains why your copied file often gets inode 12:
it is the first free inode available after the reserved ones, and inode 12 is assigned to the new
file until it is deleted or the file system changes.
Recommendation:
Consider running a thorough fsck and, if possible, reformatting the file system to ensure there is no
persistent corruption. If the problem persists, it may be a hardware issue or a bug in the file system implementation.

This sounds plausible - so I will format the SSD and reset the system!

sjox · Other Issues

With the new update (Debian 13.2) an updated Cups is also included!
This installs a file "dnssd" in the directory "/usr/lib/cups/backend-available/" and two further hard links
in the directory "/usr/lib/cups/backend"! (dnssd and mdns). The Inode was 12!
Of course you can view these files or directories using "ls -li"!
But that changes after a reboot!
If I try to list this directory on my PC using "ls -l" I get the message: "The structure must be cleaned up"!
(dnssd is only displayed with ? and the file system is shot!!)
Then I get the message for each following command: "input/output error"
A following "fsck.ext4 -y -f /dev/nvme0n1p3" reports "invalid inode 12".

(I noticed this problem due to an AIDE check - after this check the filesystem was shot!)

The question now is how a simple "ls -l" can shoot the whole file system?
(It must be because of the Inode 12!)
I helped myself by simply reinstalling cups using "--reinstall".
This gave the file (and the two hardlinks) another inode!
However, if I install Cups a third time - Inode 12 is active again!
Therefore, 12 is always preferred - except for this inode is already in use!
I was also able to replicate this with other files.
For example, as soon as I copy a normal text file into this directory, this file had the inode 12!
With the command "find / -inum 12" I also found other system files!

Now my questions:
Why is it that Inode 12 is awarded?
Apparently, this is only intended for system-related files!
Also, this behavior occurs in others or I am the only one

sjox · Other Issues

Ah! ntpsec is the package with the daemon!
(I overlooked that...)
Yes, it currently only runs once a day
If you are not an accuracy freak, then it is enough!
(On server, of course, not.)
Thanks

sjox · Other Issues

Hi,

Yes, the problem with "/usr/lib/udev/rules.d/90-alsa-restore.rules" is actually available in all Debian-derived distributions and has been around for a relatively long time! (PCLinuxOS and Artix solved this problem!)
However, these "alsa-utils" are important because you can set "Autodetect" via the Alsamixer.
(Speaker/headphones then switch automatically – but only after a reboot!)
At the end of the rules file, I simply entered the line LABEL-"alsa-restore-std".
Of course, this is not a solution, but it eliminates this annoying message!

I have been experimenting with Excalibur for over a month and am actually very satisfied.
However, there are other peculiarities - also in the RC1 (XFCE4):

a)
First, I had to run the command "xdg-user-dirs-update --force".
Only then were the catalogues created in German.
(user-dirs.dirs and user-dirs.locale)
Under Cinnamon this problem does not exist!

(b)
Then I had to comment out in the file "/etc/default/dbus" the entry "IDTYPE"RANDOM" with a "#".
Thank you for the solution - I found it here in the forum!
Is this a bug or a feature?

c)
Why was mate-polkit installed? There is xfce-polkit!
There are error messages in my ".xsession-errors"!
There are no entries when using xfce-polkit.

d)
Rsyslog has been solved!

e)
There doesn't seem to be an automatic time synchronization with "ntpsec-ntpdate"?
I had to make do with an entry in the “cron.daily”.

f)
Fstrim for SSD maintenance must be activated manually!
(I prefer to me too!)

g)
The computer could not go into broad-based mode!
Remedy: sudo /bin/bash -c "echo GPP0 > /proc/acpi/wakeup"
You have to enter extra in /etc/rc.local. (without sudo)

(h)
A problem with the "speech-dispatcher" in combination with Pulseaudio!
The sound output is strongly distorted - also in Firefox.
(Youtube ist ok - but on X/Twitter the speech-dispatcher is always activated)
Remedy a change in the /etc/speech-dispatcher/speechd.conf file
'AudioOutputMethod "alsa"' helped.
(with pipewire there are no problems)

These were actually only annoying little(?) things that can be solved.

But there is something very important:
I noticed that under XFCE (and only under XFCE) the screen often freezes for several seconds! With me it happened approx. 2-3 times a week!
This problem can also be found in various forums, and is also extensively discussed when looking for "ring gfx_0.0.0 timeout, but soft recovered".

It should be a problem with the AMD graphics driver and you can fix it simply by disabling the composite effects of XFCE4!
(These are now disabled by default in the Devuan RC1)
But I would like to have a composite manager, because, for example, the Firefox edition when leafing back and forth without it jerking! The use of Picom provided a remedy.
(Compiz caused me screen errors).
If you select "egl" as a Picom backend, then the composite manager runs absolutely stable with my AMD card and you are permanently spared from freezing!
I just used the included sample configuration.
The one copied from "/usr/share/doc/picom/examples/picom.sample.conf" to "/.config/picom.conf"! It is complex but well documented and changes are effective immediately - so you have a quick feedback when testing.

Unfortunately, another problem will arise:
Huge number of error messages in the ".xsession-errors" - although you don't notice anything!
This problem is also known: https://bbs.archlinux.org/viewtopic.php?id=306908
If I understand that correctly, XFWM is buggy under 4.20 and therefore there is an improved version on Git: https://gitlab.xfce.org/xfce/xfwm4.
I was able to compile and even install a new xfwm window manager after a few attempts!
First, the necessary DEV packages must be provided:
sudo apt install libwnck-3-dev libxfce4ui-2-dev libgtkd-3-dev libglib2.0-dev pkg-config cmake meson (I hope I haven't forgotten anything)
There is also a good tutorial - I changed it for myself: "meson setup --prefix=/usr build" (Then overwrite the freshly compiled files the old ones.)
In fact, it worked! It runs stable and without error messages in the ".xsession-errors"!

Well, however, this is quite a deep intervention and this should not be necessary!
Now my question:
Is there any chance that this improved Xfwm version will find its way into the Devuan package sources?

Thanks

The officially official Devuan Forum!

#1 Re: Other Issues » [SOLVED] Inode No. 12 » 2025-11-17 16:39:55

#2 Re: Other Issues » [SOLVED] Inode No. 12 » 2025-11-17 09:50:12

#3 Other Issues » [SOLVED] Inode No. 12 » 2025-11-16 19:03:07

#4 Re: Other Issues » Alsa errors during boot of Excalibur » 2025-09-17 16:54:39

#5 Re: Other Issues » Alsa errors during boot of Excalibur » 2025-09-16 18:09:19

Board footer