You are right, i will try follow your advice.
But tomorrow, I’m so tired that I destroy more than repair.
But, I promise, I must do mount -l to get any output and i remeber
it always was.
Maybe tomorrow it behave different.
For now thank you, hope you will listen again tomorrow.
Before checking other stuff I would like to check the process which starts the problems.
What exactly happens when a CD/DVD is inserted to drive ?
If this is a hotplug/ Udev process how can I find out which rule is applied ?
Is there a way to rebuild udevrules after removing all udevrules from the /usr/lib/udev/rules.d/
folder ?
I have actually a lot udevrules and do not know where all this rules come from. Other
Suseversion in the past did not hold so much rules.
Which of them are candidates for removal and or involved in the actual problems ?
10-dm.rules
10-usrp-uhd.rules
11-dm-lvm.rules
13-dm-disk.rules
40-usb-media-players.rules
42-usb-hid-pm.rules
50-avrdude.rules
50-firmware.rules
50-udev-default.rules
60-cdrom_id.rules
60-fprint-autosuspend.rules
60-heimdall.rules
60-keyboard.rules
60-persistent-alsa.rules
60-persistent-input.rules
60-persistent-serial.rules
60-persistent-storage.rules
60-persistent-storage-tape.rules
60-persistent-v4l.rules
60-vboxdrv.rules
60-vboxguest.rules
61-accelerometer.rules
61-msft.rules
63-md-raid-arrays.rules
64-btrfs.rules
64-md-raid-assembly.rules
65-xorg-wacom.rules
69-dm-lvm-metad.rules
69-libmtp.rules
70-infrared.rules
70-power-switch.rules
70-uaccess.rules
71-seat.rules
73-seat-late.rules
73-seat-numlock.rules
75-net-description.rules
75-probe_mtd.rules
75-tty-description.rules
77-network.rules
77-nm-olpc-mesh.rules
78-sound-card.rules
80-drivers.rules
80-hotplug-cpu-mem.rules
80-kvm.rules
80-net-name-slot.rules
80-udisks2.rules
81-mount.rules
90-alsa-restore.rules
95-dm-notify.rules
95-udev-late.rules
95-upower-battery-recall-dell.rules
95-upower-battery-recall-fujitsu.rules
95-upower-battery-recall-gateway.rules
95-upower-battery-recall-ibm.rules
95-upower-battery-recall-lenovo.rules
95-upower-battery-recall-toshiba.rules
95-upower-csr.rules
95-upower-hid.rules
95-upower-wup.rules
99-systemd.rules
thanks for patience 
It’s not udev that’s responsible for your problem, it’s almost certainly a controller, disk, cable issue. The udev rules don’t mount the device either. That’s done by the desktop environment.
Ok, hardware problem. I might check this with another free harddisk later.
On the other hand it’s not easy to believe a cable or whatever decide to remount a device as readonly
when during boot it is mounted read write.
Whats about tACL ?
I would check dmesg for errors, mounting etc
The message are above in a post. And my conclusion, as I said, is : Hardware.
No need whatsoever to go for things lilke udev rules, etc. Nobody else has this. There are complaints in dmesg about the ATI bus. Do we need more?
I’m in complete agreement Henk. My real point (to the OP) was that the kernel messages tell the story, not what udev is doing.