warren3
May 3rd, 2015, 04:59 PM
Hi.
My system is a Brix with a mSata drive for OS etc. and a 2.5" 500GB drive for my music files.
I upgraded to 15.04 (previously on 14.04) and I am getting a lot of "no object for d-bus interface" errors when I try to access my 500GB drive. At first a reboot seemed to fix it but today I rebooted about 3 times and error persisted. So I took the drive out of APR 127 spin down mode and rebooted and I could access it again. Now I would rather have the drive spin down due to noise.
Is this a bug in 15.04 or is it fixable someway?
I am also getting the odd sbin/plymouthd error when I start Ubuntu as well.
Cheers.
My system is a Brix with a mSata drive for OS etc. and a 2.5" 500GB drive for my music files.
I upgraded to 15.04 (previously on 14.04) and I am getting a lot of "no object for d-bus interface" errors when I try to access my 500GB drive. At first a reboot seemed to fix it but today I rebooted about 3 times and error persisted. So I took the drive out of APR 127 spin down mode and rebooted and I could access it again. Now I would rather have the drive spin down due to noise.
Is this a bug in 15.04 or is it fixable someway?
I am also getting the odd sbin/plymouthd error when I start Ubuntu as well.
Cheers.