Solved Linux16 64 and 32 bit Cinnamon

Gigabyte / Ga-78lmt-s2p
March 29, 2014 at 22:31:41
Specs: Windows 7- 64Bit, 1.8 GHz / 4gig
Some time ago I wrote in a post from an OP asking about the wisdom of swapping to Linux and I replied that it was akin to driving a car in the back seat. I resumed experimenting with the OS and now I should add that the car has no steering wheel.

Note that all my installs are in VMWorkstation 10

I downloaded both the 32bit and the 64bit versions and duly installed the 32 bit first. The install went well and I extracted and installed VMware-Tools and then open-vm-dkms so far so good.

I went back to editing the system and added the folders I wanted to share, went back into the system and made the folders in hgfs then I ran: (note: one of my shared folders is "Data")

mount -t vmhgfs .host"/Data /mnt/hgfs//Data

The system advised me that the folder never existed. A post on Linux Mint said forget about mponting the folders like that... edit the fstab, which I did. When I came to reboot the system threw it's hands in the air and gave me 2 options: press S to skip or M to repair. I could not make head nor tail of the M option so I booted in the normal way (pressed S)
This is the fstab as I edited it:
#######################################################

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=a7ee4b6e-c2aa-4279-ac4a-977a4ee33c1f / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=99c9dcfa-1434-4c06-8f59-6686d5ecbc2f none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
.host:/Data /mnt/hgfs/Data vmhgfs defaults 0 0
.host:/Windows /mnt/hgfs/Windows vmhgfs defaults 0 0
.host:/Graphics /mnt/hgfs/Graphics vmhgfs defaults 0 0

####################################################

The last 3 lines are my additions and this is what is causing the hang. Being a comparative newbie at Linux I am at a loss as to what to do next. Interestingly the same circumstance occurs with the 32 bit version.

Does anyone have steering wheel for me?


See More: Linux16 64 and 32 bit Cinnamon

Report •

✔ Best Answer
March 30, 2014 at 23:29:15
There's a long thread here that might help:

https://communities.vmware.com/mess...



#1
March 29, 2014 at 23:26:37
So, do the directories /mnt/hgfs/Data, etc. exist? If not, create them before trying the mount. (I am assuming you used the correct mount command as the one in your post has a couple of typos).

Report •

#2
March 30, 2014 at 02:35:03
The only typo I can find is "mponting" which should be "importing". I can't find any errors in the Mount or mnt command. You say "So do the direcrories /mnt/hgfs/Data" exist... in my post I said this I went back to editing the system and added the folders I wanted to share, went back into the system and made the folders in hgfs then I ran: (note: one of my shared folders is "Data") mount -t vmhgfs .host"/Data /mnt/hgfs/Data

The file that could not be found was this one: hgfs but rest assured it is there complete with sub directories.

Unhappily I am no closer to an answer and I thought my post had been crafted so carefully apart from the typo but I thank you for your interest.

Regards.

message edited by Ewen


Report •

#3
March 30, 2014 at 03:03:10
Sorry, it wasn't clear to me exactly which folders you had added. Assuming that you have permission to all those folders the mount command should work. Don't edit fstab until you are sure that the mount works from the command line; that is bound to lead to difficulties. Your mount command was:

mount -t vmhgfs .host"/Data /mnt/hgfs//Data

It should be

mount -t vmhgfs .host:/Data /mnt/hgfs/Data

The error message you got indicates that either .host:/Data or /mnt/hgfs/Data don't exist (or just possibly that you don't have permission to access them - although I think that you would get a different error message in that case). It shouldn't be too difficult to determine which one. You might also want to check for any messages in the System log.

message edited by ijack


Report •

Related Solutions

#4
March 30, 2014 at 16:16:50
Whoops a typo in my second post, this one: mount -t vmhgfs .host"/Data /mnt/hgfs//Data it should be .host: not .host" I hit the wrong key.

The directories exist and so do the sub directories. Interestingly I have Mint 15 on an older computer with exactly the same lines added to the fstab and the Windows shares work perfectly. After boot-up I can open /mnt/fhgs and all the directories are there complete with contents.

Somewhere along the line I have missed something. This is the sequence of events I followed, all as sudo where needed:

1.) Installed VMware Tools
2.) apt-get install open-vm-dkms

3.) this next step was a problem because I was not sure how to implement it:
/etc/init.d/vmware-tools restart
every time I tried it I got the response that init.d did not exist but when I looked in etc it was there. So how do I run that command and what should the proper syntax be?

4.) mkdir /mnt/hgfs/my_shared_folder
5.) mount -t vmhgfs .host:/my_shared_folder /mnt/hgfs/my_shared_folder

So except for the problem in No.3 what have I missed.

Now having gone the road I have described above an article in the Mint forum suggested that once having created the directories in /mnt/hgfs the mount -t sequence was superfluous and that it was better to alter the fstab as I have shown but no dice and yet it works in Mint 15

I still need the steering wheel - Regards.

message edited by Ewen


Report •

#5
March 30, 2014 at 23:29:15
✔ Best Answer
There's a long thread here that might help:

https://communities.vmware.com/mess...


Report •

#6
March 31, 2014 at 15:51:30
Thanks for the link ijack, the interesting thing is that share folders works perfectly on my Linux 15 install with the fstab I copied above. I had no need for any of the "repair' techniques discussed in the post, and yet the same alterations to the Mint 16 fstab will not work.

"Press on" he said, so I will and thanks for your help.

Regards.


Report •

Ask Question