tc3.4 mount tool not working (SOLVED)

[JohnJS]

Unable to mount hds . Tried from wbar, cpanel and aterm. TOP shows multiple mnttool entries.
(Ran as base norestore).
Checked md5sum.

Edit: See post Dec 29 2010 for my solution.

[gerald_clark]

You need to be more specific.
Can you mount your partitions manually?
If you can't mount them as root, the mount tool will not be able to either.

[JohnJS]

Cannot mount them as root.
On hda1 with ls -a I get ". .. Xdefaults .ash_history .profile"
Tried hda2 I get "failed: Device or resource busy".
My harddrive : hda1 hda2 both ext2 and swap.
Grub has 3.3 standard and 3.4 with "base norestore"

[tinypoodle]

1. You can't get any output of ls from an unmounted partition.
2. You can't mount a swap partition.
3. "hda1" is not a full path and therefore makes no sense to be mentioned like above.

[JohnJS]

sudo mount /mnt/hda1
sudo mount /mnt/hda2
Now drives mounted okay.
Is this the new way to mount harddrives? (changed from 3.3?)
What is the mount icon in wbar for?

tinypoodle: Thought info on harddrive and grub would help. Did not try to mount swap.

[thane]

I'm running into the same problem (mount tool not working) when trying to upgrade to 3.4. Will try JohnJS solution.

edit: On second thought I'm hesitant to upgrade if this is a bug. I normally burn the ISO to CD and then upgrade on the USB stick using the terminal usbinstall. Part of this process is using the mount tool to mount/unmount the CD. Like JohnJS I'd like to know if the mount tool has changed since 3.3.

[curaga]

In a quick test in Qemu, the mount tool worked fine for mounting the TC-3.4 cdrom.

[thane]

Thanks. I'll try downloading and burning the ISO again and see what happens.

edit: Urrgh, wonder if this is my problem (and maybe JohnJS's). From roberts final release 3.4 post:

Note: .profile has been changed to add FILEMGR=fluff for use by mnttool and MANPAGER env variable.
Update your .profile as deemed necessary, e.g.,

cp /etc/skel/.profile /home/tc/.profile

Didn't do that, but then I was booting from CD (base norestore noswap waitusb=5) so that should already have been set, right? Hmmm. Also there's this (same post):

* Updated mnttool to show all drives and mount launch filemgr via FILEMGR env.
* Updated mnttool to support labels and 10+ partitions.

Got a feeling I'm overlooking something...

[thane]

OK, I upgraded to 3.4 and can confirm what JohnJS reported. After installing 3.4 and following roberts' advice in the 3.4 release post, I backed up and rebooted. Clicking the mount tool icon in wbar (or on the control panel) starts a process, but the mount panel that lets you cycle through the devices does not display. It doesn't work when booting from CD either (I tried two separate ISO downloads).

Since it works for Curaga I'm at a loss to explain it. I haven't had any problem in prior releases of TC.

edit: Interesting. Several minutes after I clicked the icon, what looks like the mount tool panel has appeared on the desktop. Maybe there's some weird interaction with FLWM or a timing thing that keeps it from showing up right away?

[JohnJS]

Hi thane,
Found out what was wrong with mounttool.
My computer is a custom assembled AMD with card readers instead of floppy. I changed the Bios to read "not installed" for the floppy.
Now the mounttool works perfectly.
I noticed on shutdown/reboot at the end of the process some error message  flashed by about the floppy.
Hope this solves your problem too.

[thane]

I'm running a barebones AMD box too! Just CD and USB though; no floppy, hard disk, or card reader.

I'll check the BIOS. I had to fiddle with it some when I got the box so maybe it needs more tweaking. Didn't think of it at all. Interesting that it didn't cause a problem before though.

I'm a little hesitant to call this solved, but it's your thread. I'll start a new one if I can't fix my problem.

Thanks for the help!

[JohnJS]

Hi thane,
I too did not have this problem with 3.3 and earlier versions.
Will remove SOLVED from the heading to keep this thread open.

[curaga]

Hm, so it's a nonexistent floppy drive causing a long timeout when mountables.sh tries to read its label. In 3.3 the mount tool did not try to read device labels.

JohnJS, could you verify that this is the case?

Turn it back on from the bios, post if it appears in /etc/fstab, and what happens when you try to "getdisklabel /dev/fd0".

[JohnJS]

Hi curaga, reset bios to include floppy.
# /etc/fstab
proc            /proc        proc    defaults          0       0
sysfs           /sys         sysfs   defaults          0       0
devpts          /dev/pts     devpts  defaults          0       0
tmpfs           /dev/shm     tmpfs   defaults          0       0
/dev/ramzswap0  swap         swap    defaults,noauto   0       0
/dev/fd0        /mnt/fd0        auto     noauto,users,exec    0 0 # Added by TC
/dev/hda1       /mnt/hda1       ext2     noauto,users,exec,relatime 0 0 # Added by TC
/dev/hda2       /mnt/hda2       ext2     noauto,users,exec,relatime 0 0 # Added by TC
/dev/hda3       none            swap     defaults             0 0 # Added by TC
/dev/hdc        /mnt/hdc        auto     noauto,users,exec    0 0 # Added by TC

getdisklabel /dev/fd0 results in green cursor and nothing happening.

edit: while checking this post the red mounttool appeared showing fd0 hda1 hda2 and hdc

[curaga]

OK, I guess just skipping the label for floppies would be a good solution. People rarely have several floppy drives these days, needing to recognize them by label.