Cannot mount othe internal hard drives

[deadlyhydra]

Can someone help please bring up the other internal hard drives present in my computer. Tried looking in Dolphin's left hand column but they are not showing up in there. They were there before, i unmounted them, thinking i didn't need them, and now unable to bring them back up. I am a total nOOb with linux.

[dibl]

Re: Cannot mount othe internal hard drives

#15 in the FAQs in my signature has information and links that should help.

[deadlyhydra]

Re: Cannot mount othe internal hard drives

sorry but that didn't make any sense to me. What faq? signature? #15?

[deadlyhydra]

Re: Cannot mount othe internal hard drives

found the link you mentioned but for me it's total jibberish. Any chance it could be put in plain english simple terms?

[Rog131]

Re: Cannot mount othe internal hard drives

With the Dolphin (If you have clicked the hide option on)

1) Reboot your computer
- Sometimes the KDE don't show all partions, reboot usually brings them back.

2) Right click the Dolphin's "Places" panel.
- There should be small pop up with the "Show All Entries" option



3) After you have clicked the "Show All Entries" option on - take the hide option off by right clicking the partition and clearing the marking

[dibl]

Re: Cannot mount othe internal hard drives

Any chance it could be put in plain english simple terms?

Welcome to Kubuntu and Linux!

OK, here's the first thing you need to understand. There is no one on this forum or any other Linux forum who is being paid anything to help you. Therefore, there is an expectation that you will learn to use the forum search capability, and the help provided by Mr. Google, to help yourself through commonly-encountered problems for new users. Your "can't see/set up my other internal drives" issue is a very common scenario for new users, and there are thousands of posts in Ubuntu Forums and elsewhere on the Internet on this topic.

Having said that, I'll get you started. You have a "console window" called "Konsole", found in the KMenu > System menu. You can run it with Alt-F2 and enter "konsole" with no quote marks. Once it is open on your desktop, and you see the Command Line Interface (CLI), which is often referred to as a DOS-like prompt, you will enter the following three commands:

cat /etc/fstab

sudo fdisk -lu

sudo blkid

The first one will list out your existing File System Table (fstab). The second one will list the physical drives and partitions. The third one will list the partitions and drives by both their "/dev" physical device ID, and also their Universally Unique Identifier (UUID). With these bits of information about your system, it will be possible to edit your /etc/fstab file (as described in the FAQ #15 link) and have your other partitions mounted automatically when you boot your computer (assuming that is what you want to have happen).



EDIT : -- whoops, sorry Rog!

[Rog131]

Re: Cannot mount othe internal hard drives

The "dibl's" FAQ #15 is telling how you permanetly add partition to the fstab /1/.

If the partition is in the fstab - then you (as default) can't unmount it from the Dolphin (I can't). there will be warning/information: "Not mounted by HAL - can't unmount"





/1/ > Fstab wiki

The fstab (/etc/fstab) (or file systems table) file is commonly found on Unix systems as part of the system configuration. The fstab file typically lists all available disks and disk partitions, and indicates how they are to be initialized or otherwise integrated into the overall system's file system.

The fstab file is most commonly used by the mount command, which reads the fstab file to determine which options should be used when mounting the specified device...

[dibl]

Re: Cannot mount othe internal hard drives

If the partition is in the fstab - then you (as default) can't unmount it from the Dolphin

Correct.

The expected setup for typical use of the personal computer is:

-- internal hard drives and partitions are mounted with /etc/fstab

-- external drives are mounted with HAL (i.e. they are "plugged in" or "hot-pluggable")

This means the internal drives and partitions are owned by root, mounted at boot time and remain available "permanently" unless they are deliberately unmounted, using root privileges. The external "hot-pluggable" devices are user owned, and can be plugged in and unplugged by users.

Some of the pros and cons of these distinctions will not necessarily be obvious to the new user, and some of them may not be applicable to individual situations. Of course, Linux is very flexible and can be adjusted to fit pretty much any usage situation that you have.

[deadlyhydra]

Re: Cannot mount othe internal hard drives

thank you very much for your help but i have done research on Mr google and other Linux forums, however being a total NOOOOB at linux, whatever i seemed to read did not mean a thing and being scared of bodging stuff up. If i was savvy then i wouldn't of posted in " Help the New Guy " section of the forum, don't you think? I appreciate that you don't get paid for giving support and i admire that, and it's one of the reasons why i would like to move away completely from Windows dominion and pass knowledge on. And then maybe i could also pass on the knowledge learnt on. But first i have to learn.

[vinnywright]

Re: Cannot mount othe internal hard drives

Mr. dibl gave you 3 comand's a few post's back please post the output of those comand's!!

VINNY

[ohb1knewbie]

Re: Cannot mount othe internal hard drives

I am having a similar problem but have been unable to locate the FAQ you reference in this post. (A link or nudge in the right direction would be greatly appreciated).

Changing the settings re auto mounting removable devices results in the crash referenced in the bug report included below. The "Show All Entries" in the Places context menu (if that's what it's called in Linux) is not listed when I right click the Places panel; only the "Add Entry" option is available. If I try to use the "Add Entry" option, navigation seems to stop at the /dev/disk sub folders - clicking the (+) of any one the sub folders does not result in the expansion of the folder to allow the selection of the partition. I have booted off of several live CD's - Kubuntu, Ubuntu and OpenSuse - and in each case the partition (/dev/sda12: LABEL="Linux") is listed in the file manager run from the live CD session.

I would like to have the /dev/sda12 auto mounted on login and perhaps figure out how to have the "Places" panel sorted by volume label if possible. (Any recommendations on a good reference book to keep me out of the forums until I know more of what I'm doing?)

The Linux partitions are as follows:
/dev/sda9-linux swap; /dev/sda10-root; /dev/sda11-home; /dev/sda12-data (hopefully for virturalizing my windows install after I get comfortable enough with Linux to punt the dual boot).

contents of /etc/fstab is listed the the related bugzilla report included below.

Thank you for your time and assistance.

\\
sudo fdisk -l output:

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0cb70cb6

Device Boot Start End Blocks Id System
/dev/sda1 1 765 6144831 12 Compaq diagnostics
/dev/sda2 * 766 5021 34186320 7 HPFS/NTFS
/dev/sda3 5022 32382 219777232+ c W95 FAT32 (LBA)
/dev/sda4 32383 57899 204964706+ f W95 Ext'd (LBA)
/dev/sda5 32383 35423 24426801 b W95 FAT32
/dev/sda6 35424 41504 48845601 b W95 FAT32
/dev/sda7 41505 47585 48845601 b W95 FAT32
/dev/sda8 47586 53666 48845601 b W95 FAT32
/dev/sda9 53667 54164 3999744 82 Linux swap / Solaris
/dev/sda10 54165 55409 9999360 83 Linux
/dev/sda11 55410 56654 9999360 83 Linux
/dev/sda12 56655 57899 9999360 83 Linux

\\
sudo blkid output:

/dev/sda1: LABEL="PQSERVICE" UUID="16D9-B5D2" TYPE="vfat"
/dev/sda2: LABEL="ACER" UUID="3CD8DBF2D8DBA882" TYPE="ntfs"
/dev/sda3: LABEL="ACERDATA" UUID="3904-0FF6" TYPE="vfat"
/dev/sda5: LABEL="ACER-02" UUID="2112-1DF2" TYPE="vfat"
/dev/sda6: LABEL="ACER-03" UUID="4508-08E2" TYPE="vfat"
/dev/sda7: LABEL="ACER-04" UUID="3E08-08EC" TYPE="vfat"
/dev/sda8: LABEL="ACER-05" UUID="2A08-08F4" TYPE="vfat"
/dev/sda9: UUID="3d59f466-1e85-46ad-822d-db32fafab170" TYPE="swap"
/dev/sda10: UUID="c7f84e9d-a260-4951-8a30-2fe9db8fc169" TYPE="ext4"
/dev/sda11: UUID="a202047a-a311-46c9-9779-0ed9cade99db" TYPE="ext4"
/dev/sda12: LABEL="Linux" UUID="2cdbc2da-86bc-46a8-bfaf-9f1ee09ae1b5" TYPE="ext4"

\\
related bugzilla report:

100904:1052-
/
Bug 250178 -
KCMInit (kdeinit4), signal: Segmentation fault
/
Application: kcminit_startup ()
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-24-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
I created four logical partitions when I installed Kubuntu 10.04 as a dual boot with WinXP.

fstab -
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda10 during installation
UUID=c7f84e9d-a260-4951-8a30-2fe9db8fc169 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda11 during installation
UUID=a202047a-a311-46c9-9779-0ed9cade99db /home ext4 defaults 0 2
# /usr/local was on /dev/sda12 during installation
UUID=2cdbc2da-86bc-46a8-bfaf-9f1ee09ae1b5 /usr/local ext4 defaults 0 2
# swap was on /dev/sda9 during installation
UUID=3d59f466-1e85-46ad-822d-db32fafab170 none swap sw 0 0

I have been trying to manually mount the "/usr/local" partition without much success. I created a folder named "Linux" in the /dev/disk folder to match the "/usr/local" partition's volume label and then manually mounted the partition from the terminal, however once I logged out and then logged back in not only was the partition not mounted (I expexted this but...) the "Linux" folder that I had created for the mount point was no longer in the /dev/disk folder.

I stumbled upon the System Settings/Advanced/Removable Devices page. I had not previously looked in this settings page because the "/usr/local" partition is not a removable device but a partition on the local HDD in my laptop. I was surprised to see the "/usr/local" partition listed under its volume label "Linux" in the list along with all the other partitions on the fixed HDD. I checked the box to "Automount on Login".

I then logged out and back in to see if the partition would be automounted. It was NOT automounted but that's when I began to get the "KCMInit (kdeinit4), signal: Segmentation fault" crash popup. I then when back and also checked the "Automount on Attach" check box for the "/usr/local" partition and then repeated the log out/log in - again no automount and again the same crash error.

I have now unchecked both boxes of the "/usr/local" partition and again logged out/logged in with the same resulting error msg. I have never had this error msg before the above change to the automount settings and have still not managed to resolve the automount of the partition.

Please let me know if there is additional information you require.

Thank you for your time and assistance,


The crash can be reproduced every time.

-- Backtrace:
Application: KCMInit (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5 0x00007f3eb0e7a6b3 in ?? () from /usr/lib/kde4/kcm_touchpad.so
#6 0x00007f3eb0e7de74 in ?? () from /usr/lib/kde4/kcm_touchpad.so
#7 0x00007f3eb6d83889 in KCMInit::runModule (this=<value optimized out>, libName=..., loader=0x15623e0, service=<value optimized out>) at ../../kcminit/main.cpp:92
#8 0x00007f3eb6d84054 in KCMInit::runModules (this=0x7fff0f464d50, phase=<value optimized out>) at ../../kcminit/main.cpp:135
#9 0x00007f3eb6d8442e in KCMInit::runPhase1 (this=0x7f3ec09e2e40) at ../../kcminit/main.cpp:232
#10 0x00007f3eb6d844b4 in KCMInit::qt_metacall (this=0x7fff0f464d50, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=<value optimized out>) at ./main.moc:84
#11 0x00007f3ec00e1486 in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=..., slotIdx=<value optimized out>)
at qdbusintegrator.cpp:904
#12 0x00007f3ec00e26ef in QDBusConnectionPrivate::activateCall (this=<value optimized out>, object=0x7fff0f464d50, flags=48, msg=...) at qdbusintegrator.cpp:809
#13 0x00007f3ec00e2f0e in QDBusConnectionPrivate::activateObject (this=<value optimized out>, node=<value optimized out>, msg=..., pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1383
#14 0x00007f3ec00e3468 in QDBusActivateObjectEvent:laceMetaCall (this=0x14e7100) at qdbusintegrator.cpp:1477
#15 0x00007f3ec1d2cd49 in QObject::event (this=0x7fff0f464d50, e=0x14e7100) at kernel/qobject.cpp:1248
#16 0x00007f3ec0eb922c in QApplicationPrivate::notify_helper (this=0x143b7e0, receiver=0x7fff0f464d50, e=0x14e7100) at kernel/qapplication.cpp:4300
#17 0x00007f3ec0ebf6fb in QApplication::notify (this=0x7fff0f464d70, receiver=0x7fff0f464d50, e=0x14e7100) at kernel/qapplication.cpp:4183
#18 0x00007f3ec2264526 in KApplication::notify (this=0x7fff0f464d70, receiver=0x7fff0f464d50, event=0x14e7100) at ../../kdeui/kernel/kapplication.cpp:302
#19 0x00007f3ec1d1d06c in QCoreApplication::notifyInternal (this=0x7fff0f464d70, receiver=0x7fff0f464d50, event=0x14e7100) at kernel/qcoreapplication.cpp:704
#20 0x00007f3ec1d1f7e7 in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x13f1c30) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x13f1c30) at kernel/qcoreapplication.cpp:1345
#22 0x00007f3ec1d469d3 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#23 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276
#24 0x00007f3ebd0fe8c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x00007f3ebd102748 in ?? () from /lib/libglib-2.0.so.0
#26 0x00007f3ebd1028fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x00007f3ec1d46513 in QEventDispatcherGlib:rocessEvents (this=0x13f3140, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#28 0x00007f3ec0f6946e in QGuiEventDispatcherGlib:rocessEvents (this=0x7f3ec09e2e40, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007f3ec1d1b992 in QEventLoop:rocessEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#30 0x00007f3ec1d1bd6c in QEventLoop::exec (this=0x7fff0f464890, flags=) at kernel/qeventloop.cpp:201
#31 0x00007f3ec1d1faab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#32 0x00007f3eb6d84c4f in KCMInit (this=<value optimized out>, args=<value optimized out>) at ../../kcminit/main.cpp:219
#33 0x00007f3eb6d85801 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../kcminit/main.cpp:272
#34 0x00000000004070f3 in launch (argc=1, _name=<value optimized out>, args=<value optimized out>, cwd=<value optimized out>, envc=0, envs=<value optimized out>, reset_env=false, tty=0x0,
avoid_loops=false, startup_id_str=0x40a4f9 "0") at ../../kinit/kinit.cpp:717
#35 0x0000000000408e91 in main (argc=4, argv=<value optimized out>, envp=<value optimized out>) at ../../kinit/kinit.cpp:1800

Possible duplicates by query: bug 247586, bug 247239, bug 246139, bug 245413, bug 245072.

Reported using DrKonqi

\\

[oshunluvr]

Re: Cannot mount othe internal hard drives

I am having a similar problem but have been unable to locate the FAQ you reference in this post. (A link or nudge in the right direction would be greatly appreciated).

FAQ = Frequently Asked Question

sig = forum shorthand for "Signature" which is the information included at the bottom of each post.

Scroll to dibl's last post and click on the highlighted text near the bottom that says "TOP 20 KUBUNTU FAQ'S HERE"

[oshunluvr]

Re: Cannot mount othe internal hard drives

ohb1knewbie (great name BTW):

I see about 3 or 4 different issues in your post. It is better both for your response rate and for others to reference your topics to start a new thread for each question after you've done some research on your own.

To have a partition mounted automatically at every startup, the usual steps are:

1. Create a target directory
2. Edit /etc/fstab to include your new mount
3. Mount it

If you want to have /usr/local on a separate partition - it appears that has been done correctly in your fstab. Reboot, open a terminal and type df and you will see all mounted partitions, mount locations, and their sizes.

In your case it appears you want to re-mount /usr/local to a different mount location. IMO this is a bad idea. I suspect your problem is you're confusing the windows way of doing things with the linux way. No matter where you mount it, it will be addressed as a subdirectory. Changing it from /usr/local to another directory would only make the space more difficult to address.

/dev is a system folder and you really shouldn't be messing about there without advanced knowledge. In fact your partition is already listed there, but as /dev/sda12 as it should be. You also attempted to mount a fixed device as a removable one and one that was already mounted at that - I'm not surprised you were able to generate a crash.

If you insist on accessing this partition in a non-standard way, you could mount it twice using a correct method (not attempting to create a faux device), but I'm against it.

I don't know if there's a way to force dolphin places panel to alphabetize, but you can drag and drop the places (labels or device names) into whatever order you like and it should be persistent.