Bug 349575 – sys-apps/gnome-disk-utility has smart status disabled due udisks not recognizing it

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description jeff 2010-12-24 07:57:25 UTC]

Can we have a patch and a use flag for enable smart status in gnome-disk-utility?

[Comment 1 Gilles Dartiguelongue (RETIRED) 2010-12-24 09:53:49 UTC]

how do you think we can do that if it doesn't work out of the box ?

[Comment 2 Pacho Ramos 2010-12-24 10:32:48 UTC]

(In reply to comment #0)
> Can we have a patch and a use flag for enable smart status in
> gnome-disk-utility?
> 

What patch and what configure option is needed?

On my system, I am able to see smart status from palimpsest:
1. Launch it
2. Go to my harddisk
3. Click on "SMART data" -> A window is opened showing the information

[Comment 3 jeff 2010-12-24 10:48:27 UTC]

My hd support smart and smart is active but palimpsest doesn't work.
I have found this searching on google https://bugs.launchpad.net/ubuntu/+source/devicekit-disks/+bug/553282

[Comment 4 Pacho Ramos 2010-12-24 10:51:46 UTC]

What sys-fs/udisks versions do you have? Please try with latest one also

[Comment 5 jeff 2010-12-24 10:58:49 UTC]

sys-fs/udisks-1.0.1-r1
I will try to unmask 1.0.2 version.

[Comment 6 jeff 2010-12-24 15:29:17 UTC]

Same situation with sys-fs/udisks-1.0.2

[Comment 7 Xake 2011-04-16 09:46:18 UTC]

This is probably the same race conditions I have seen.
This is partly fixed in latter udev.

To confirm, try run the following in a terminal as root:
grep dbus /etc/init.d/udev-postmount && killall udisks-daemon && echo OK!

If you are left with an "OK!", then try run palimsest again and check your SMART status. If this does not return "OK!" the try re-emegre udev, reboot and run that command again.


I have had the same behaviour because of two races:
1. udev-postmount (i.e. udevadm trigger --type=failed) being run before dbus is running (creating problems with apps like udisks that needs dbus).
This has been fixed in udev.

2. login before udev-postmount has been launched.
This I am currently hit by. gnome-desktop or gvfs seems to start udisks-daemon before udev-postmount is done, making udisks-daemon use old versions of /udev/.udev/data* which has not been updated with SMART status.
The workaround is "killall udisks-daemon", the long term workaround/fix is probably make xdm depend on udev-postmount. The real fix I guess would be to make udisks-daemon re-read the info from /dev/.udev/data if it has been modified.

[Comment 8 Xake 2011-04-20 11:14:26 UTC]

I found another problem if you have a seperate /usr (needs to enable /dev/.udev/udev.log):

1303304475.565758 [2638] util_run_program: '/lib64/udev/udisks-probe-ata-smart' (stderr) '/lib64/udev/udisks-probe-ata-smart: error while loading shared libraries: libatasmart.so.4: cannot open shared object file: No such file or directory'


For some reason this is not picked up by "udevadm trigger --attr-match=failed" later in udev-postmount, I do not really know why or if it even should.

This is currently the only way for me to get gnome-disk-utilities to recognize SMART support (apart from installing libatasmart into /lib):

udevadm trigger && killall udisks-daemon

This may crash Xorg, and eat other babies, but afterwards you can see your smart status in palimsest without trouble.

[Comment 9 Chris Smith 2011-10-15 05:02:32 UTC]

(In reply to comment #8)
> I found another problem if you have a seperate /usr
> 
> udevadm trigger && killall udisks-daemon

I've run into this as well with a separate user (although it did work previously but stopped recently).

Safer workaround I found posted that works for me (doesn't crash anything) is:

  # echo change > /sys/block/sdx/uevent
  # udisks --ata-smart-refresh /dev/sdx

Substituting sdx for the proper device names (sda, sdb, etc.).

[Comment 10 Chris Smith 2011-10-15 05:07:38 UTC]

(In reply to comment #9)
> I've run into this as well with a separate user 

Should read:
I've run into this as well with a separate /usr

[Comment 11 Samuli Suominen (RETIRED) 2011-10-15 15:07:16 UTC]

Separate /usr or /var is broken configuration without initramfs that mounts them before init. They are not supported.

[Comment 12 Samuli Suominen (RETIRED) 2011-10-15 15:08:58 UTC]

So if the only problems here are caused by invalid partition scheme, propably duplicate of bug 364235.

[Comment 13 Chris Smith 2011-10-15 17:53:53 UTC]

(In reply to comment #11)
> Separate /usr or /var is broken configuration without initramfs that mounts
> them before init. They are not supported.

Been running Gentoo for ages now and this has never been a problem in the past. Is this something new? Where is it documented? Thanks.

[Comment 14 Samuli Suominen (RETIRED) 2011-10-15 17:58:59 UTC]

(In reply to comment #13)
> (In reply to comment #11)
> > Separate /usr or /var is broken configuration without initramfs that mounts
> > them before init. They are not supported.
> 
> Been running Gentoo for ages now and this has never been a problem in the past.
> Is this something new? Where is it documented? Thanks.

udev stopped supporting them, documented nowhere else than in bug 364235 yet, far as I know

[Comment 15 Samuli Suominen (RETIRED) 2011-10-15 18:00:56 UTC]

Also http://archives.gentoo.org/gentoo-dev/ has several threads about it.

[Comment 16 Samuli Suominen (RETIRED) 2011-10-21 20:20:44 UTC]

Closing as per Comment #11.