Mount: wrong fs type, bad option, bad superblock missing codepage or other error
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Mount: wrong fs type, bad option, bad superblock missing codepage or other error
Hello,
I am running a CentOS vm on a Windows 7 host and I recently installed the latest version of guest additions (3.2.8) when I received the error:
Code:
#mount -t vboxsf ez sequence_data/
mount: wrong fs type, bad option, bad superblock on ez,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
when trying to mount an external hard drive to the guest. I have done this procedure many times with no errors but now for whatever reason I don't know what happened. Please, let me know if you have any suggestions on how to fix this!
Anyway, the cause can also be that the share is not provided to the system or provided with a different method than the vbox shared disk solution... or the path to the share does not exist on the host, causing a bad block being provided... just some grabbing from my high hat ;-) Good luck finding the cause!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.