[SOLVED] Upgraded to 17.3; disk related issues

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
Post Reply
KirbySmith
Level 4
Level 4
Posts: 281
Joined: Sun Feb 03, 2013 10:25 pm

[SOLVED] Upgraded to 17.3; disk related issues

Post by KirbySmith » Sun Dec 13, 2015 1:10 am

Upgraded to Linux Mint MATE 17.3 64-bit, and to 3.19 kernel in Desktop 2 below; found disk related issues

My first start of gparted since the 17.3 upgrade resulted in it scanning all devices forever and never fully populating its GUI. Killing (evidently just the window) via the window X didn’t remove gparted from the processes. Trying to start it again from the menu again brings up the authentication window, but filling in the root password does not lead to the GUI initializing.

Rebooting and again starting gparted from the menu again resulted in the authentication window, but in this case no GUI. In this test, gparted did not even appear in system monitor as a process. Using synaptic, gparted was reinstalled. Results were the same.

The program “disks” under Menu/Accessories also doesn’t start.

Caja no longer sees the additional hard drives in the PC.

dmesg shows discovery of all of the hard drives during boot.

inxi -d reveals, in part:

Code: Select all

Drives:    HDD Total Size: 1280.3GB (8.0% used)
           ID-1: /dev/sda model: WDC_WD3202ABYS size: 320.1GB
           ID-2: /dev/sdb model: WDC_WD3200YS size: 320.1GB
           ID-3: /dev/sdc model: WDC_WD3202ABYS size: 320.1GB
           ID-4: /dev/sde model: WDC_WD3200YS size: 320.1GB
          
inxi -po shows all the partitions, but notes that sdb, sdc, and sde partitions are all unmounted. Unmounted is expected, but invisibility in Caja is not expected.

Any suggestions are welcome

kirby
Last edited by KirbySmith on Sun Dec 13, 2015 8:28 am, edited 1 time in total.
Desktop 1: DFI Lanparty UT nF4 SLI-D/AMD Athlon 64 San Diego/BFG GeForce 7800 GT/Mint 17.3 MATE
Desktop 2: Gigabyte 770T-USB3/AMD Phenom II X4 965/EVGA GeForce 9800 GT/Mint 17.3 MATE
HTPC: Asus C6H/AMD Ryzen 7 1800X, Asus Geforce 1080 Ti/Mint 18.1 MATE

Monsta
Level 10
Level 10
Posts: 3026
Joined: Fri Aug 19, 2011 3:46 am

Re: Upgraded to 17.3; disk related issues

Post by Monsta » Sun Dec 13, 2015 5:54 am

Try running disk tools from the terminal and see if they show any errors:

Code: Select all

gparted-pkexec

Code: Select all

gnome-disks
Also try 3.16 kernel just in case...

KirbySmith
Level 4
Level 4
Posts: 281
Joined: Sun Feb 03, 2013 10:25 pm

Re: Upgraded to 17.3; disk related issues

Post by KirbySmith » Sun Dec 13, 2015 7:52 am

Thanks, Monsta, for the suggestions. Results below are not too promising.

Code: Select all

kirby@THE-SMITHS2 ~ $ gparted-pkexec
Inhibit all polling failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
kirby@THE-SMITHS2 ~ $ gnome-disks

(gnome-disks:7936): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(gnome-disks:7936): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(gnome-disks:7936): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(gnome-disks:7936): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(gnome-disks:7936): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(gnome-disks:7936): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(gnome-disks:7936): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(gnome-disks:7936): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(gnome-disks:7936): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(gnome-disks:7936): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(gnome-disks:7936): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(gnome-disks:7936): GNOME-Disks-ERROR **: Error getting udisks client: Error calling StartServiceByName for org.freedesktop.UDisks2: Timeout was reached
Trace/breakpoint trap
kirby@THE-SMITHS2 ~ $ 
I'll try moving back to my last kernel using (I think) update manager. [need to confirm this]

kirby
Desktop 1: DFI Lanparty UT nF4 SLI-D/AMD Athlon 64 San Diego/BFG GeForce 7800 GT/Mint 17.3 MATE
Desktop 2: Gigabyte 770T-USB3/AMD Phenom II X4 965/EVGA GeForce 9800 GT/Mint 17.3 MATE
HTPC: Asus C6H/AMD Ryzen 7 1800X, Asus Geforce 1080 Ti/Mint 18.1 MATE

KirbySmith
Level 4
Level 4
Posts: 281
Joined: Sun Feb 03, 2013 10:25 pm

Re: Upgraded to 17.3; disk related issues

Post by KirbySmith » Sun Dec 13, 2015 8:27 am

OK, I booted into my previous kernel 3.16-38 using 'grub menu' and preliminary testing shows all the missing hard drives in Caja's Devices list. Gparted started normally and showed a normal GUI view of partition usage. Evidently, going to 3.19 yesterday as an embellishment on upgrading to Mint 17.3 was over-reaching. Perhaps it only works well when installing 17.3 from scratch. Now to go into Update Manager and uninstall 3.19. I assume (tentatively) that doing so will eliminate any need to manually update grub.

Thanks for the help Monsta.

kirby
Desktop 1: DFI Lanparty UT nF4 SLI-D/AMD Athlon 64 San Diego/BFG GeForce 7800 GT/Mint 17.3 MATE
Desktop 2: Gigabyte 770T-USB3/AMD Phenom II X4 965/EVGA GeForce 9800 GT/Mint 17.3 MATE
HTPC: Asus C6H/AMD Ryzen 7 1800X, Asus Geforce 1080 Ti/Mint 18.1 MATE

Monsta
Level 10
Level 10
Posts: 3026
Joined: Fri Aug 19, 2011 3:46 am

Re: [SOLVED] Upgraded to 17.3; disk related issues

Post by Monsta » Sun Dec 13, 2015 8:31 am

Glad it was just a matter of kernel version. :)

I guess not all the issues in 3.19 have been solved by Ubuntu developers.

Post Reply

Return to “Newbie Questions”