Fedora with external USB disk vs. mediaclient with systemdcheck

[jpkrohling]

Hello,

I think I might have hit a case that wasn't perhaps expected by the driver. I have a Fedora 19 installed on a machine, and my data files are mounted at boot on /var/media. This is an external USB 3.0 disk. After installing the Sundtek driver, I'm unable to boot. After a timeout during boot, I'm in emergency mode, where I can choose to proceed (Ctrl+D) or enter in the maintenance mode. Neither means that the mount points will be available upon booting. But I'm able to mount them once boot is completed.

After some hours debugging (and of reinstalling fedora, piece by piece), I've found out that if I remove the "--systemdcheck" from /etc/udev/rules.d/80-mediasrv-eeti.rules , I'm able to boot just fine, but the Sundtek driver won't start. And it seems that starting the mediaclient doesn't just work. As I didn't have time to debug this particular problem, I've decided to just reinstall the driver, and it worked.

So, currently, I have two choices:
a) Leave the system in the state that the installer left, but as a price to pay, the boot will be extremelly long and the devices won't be mounted (but hey, mediaclient will be working)
b) Remote "systemdcheck" from the rules directory, and reinstall the driver after each reboot.

Is this a known bug? Is there a workaround for this? For debugging purposes, what concrete things can I do to help you? Send the boot.log? dmesg?

[Sundtek]

We'll check it immediately.

[Sundtek]

Did you try to remove following files:

/lib/udev/rules.d/80-mediasrv-eeti.rules
/etc/udev/rules.d/80-mediasrv-eeti.rules

We updated the netinst installer to remove those files automatically on Fedora (just download it again and run it).

[jpkrohling]

Unfortunately, it didn't seem to work. I removed the udevd files, installed the driver again based on the latest version (24. September 2013) and the exact same behavior remains. Even the udev files look the same. So, perhaps something on the Fedora check didn't work. By looking at the diff, I see this:

Code: [Auswählen]

9c9
< _SIZE=49455
---
> _SIZE=49305
277c277
<            sed '1,1370d' ${app} > /tmp/.sundtek/installer.tar.gz
---
>            sed '1,1366d' ${app} > /tmp/.sundtek/installer.tar.gz
1074,1077d1073
<           if [ -e /usr/sbin/systemctl ]; then
<               rm -rf /etc/udev/rules.d/80-mediasrv-eeti.rules
<               rm -rf /lib/udev/rules.d/80-mediasrv-eeti.rules
<           fi

It seems strange to me, because on Fedora 19 this doesn't exists. It does exist, however, on "bin" (not "sbin"):

Code: [Auswählen]

$ which systemctl
/usr/bin/systemctl
$ uname -a
Linux acai 3.11.1-200.fc19.x86_64 #1 SMP Sat Sep 14 15:04:51 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/redhat-release
Fedora release 19 (Schrödinger’s Cat)

Removing the "s" (and changing the SIZE parameter) seems to make it work.

[Sundtek]

We have no problem with it, the only side-effect we noticed is that without the udev rules the system boots faster.

Do you still get some timeout during the boot even without the udev files?

Please try to provide some log files or screenshots so we can see what problem you have, obviously it just works as it should on our side.
We tested Fedora 19 x86-64

You might also contact us via Skype "sundtek" to check your issue directly with you.

[jpkrohling]

With the change I mentioned (from /usr/sbin/systemctl to /usr/bin/systemctl) made it work, so, it's all fine now. I can safely reboot the machine and everything works. Thanks for your support!

[Sundtek]

I think the installer got updated again for that in the meanwhile.