I have a problem trying to mount a SD card in Ubuntu 12.04. The message what I get from the system is:
mmc0: error -110 whilst initialising SD card
I’m on the 3.5.0-24-generic kernel.
I check previous kernel 3.5.0-15 and card is on the system. I think is some bug in kernel.
I was looking some solution on web. They say my card is dead (but is working)
What I should do?
Some more information on this issue here. If someone have more question about my hardware just ask.
Braiam
66.2k30 gold badges174 silver badges262 bronze badges
asked Feb 16, 2013 at 12:49
5
Basically this error arises only when the SDcard got damaged. But as you mentioned its working, Please try the following steps and share your feedback.
- Please check the output of
dmesgorlsusbto check whether it detects the SD card. - Open the «Disk Utility» application and check whether your SD card is listed. If its listed, just click it -> Unmount Volume -> Format the Volume with suitable filesystem.
- Also, try mounting the SD card on Windows and check whether it is working or not.
Also, you can downgrade your kernel by installing the old kernel / latest stable kernel version with sudo apt-get update && sudo apt-get dist-upgrade && sudo apt-get autoremove.
wget the latest stable kernal from Kernel Website and install it with sudo dpkg -i *.deb && sudo update-grub2
Please select the proper kernel while booting and check whether your SD card mounts well!
Kalle Richter
5,78619 gold badges67 silver badges100 bronze badges
answered Feb 24, 2014 at 11:29
Naga2RajaNaga2Raja
2582 silver badges7 bronze badges
Ceph and Kernel version on client:
root@ceph-admin:/var/log# uname -r 4.2.0-41-generic root@ceph-admin:/var/log# ceph -v ceph version 12.2.0 (32ce2a3ae5239ee33d6150705cdb24d43bab910c) luminous (rc)
Got timeout error when mounting cephfs:
vagrant@ceph-admin:~$ sudo mount -vvvv -t ceph ceph-mon-1,ceph-mon-2,ceph-mon-3:6789:/ /mnt -o name=admin,secret=AQBz/KxZLh1xERAAfVubu6RxePWyZKZNDh1QjQ== mount: fstab path: "/etc/fstab" mount: mtab path: "/etc/mtab" mount: lock path: "/etc/mtab~" mount: temp path: "/etc/mtab.tmp" mount: UID: 0 mount: eUID: 0 mount: spec: "ceph-mon-1,ceph-mon-2,ceph-mon-3:6789:/" mount: node: "/mnt" mount: types: "ceph" mount: opts: "name=admin,secret=AQBz/KxZLh1xERAAfVubu6RxePWyZKZNDh1QjQ==" mount: external mount: argv[0] = "/sbin/mount.ceph" mount: external mount: argv[1] = "ceph-mon-1,ceph-mon-2,ceph-mon-3:6789:/" mount: external mount: argv[2] = "/mnt" mount: external mount: argv[3] = "-v" mount: external mount: argv[4] = "-o" mount: external mount: argv[5] = "rw,name=admin,secret=AQBz/KxZLh1xERAAfVubu6RxePWyZKZNDh1QjQ==" parsing options: rw,name=admin,secret=AQBz/KxZLh1xERAAfVubu6RxePWyZKZNDh1QjQ== mount error 110 = Connection timed out
ceph-fuse client is just fine:
vagrant@ceph-admin:~$ sudo ceph-fuse -m 192.168.15.11,192.168.15.12,192.168.15.13 /mnt --keyring /etc/ceph/ceph.client.admin.keyring --name client.admin ceph-fuse[20117]: starting ceph client 2017-09-04 08:13:27.163183 7f70162ac000 -1 init, newargv = 0x55c88431c540 newargc=9 ceph-fuse[20117]: starting fuse vagrant@ceph-admin:~$ df | grep ceph ceph-fuse 56201216 0 56201216 0% /mnt
missing required protocol features log in /var/log/syslog:
Sep 4 07:45:17 vagrant kernel: [ 3086.769690] libceph: mon1 192.168.15.12:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:45:17 vagrant kernel: [ 3086.769738] libceph: mon1 192.168.15.12:6789 missing required protocol features Sep 4 07:45:27 vagrant kernel: [ 3096.800767] libceph: mon1 192.168.15.12:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:45:27 vagrant kernel: [ 3096.800818] libceph: mon1 192.168.15.12:6789 missing required protocol features Sep 4 07:45:37 vagrant kernel: [ 3106.816588] libceph: mon0 192.168.15.11:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:45:37 vagrant kernel: [ 3106.816639] libceph: mon0 192.168.15.11:6789 missing required protocol features Sep 4 07:45:47 vagrant kernel: [ 3116.832675] libceph: mon2 192.168.15.13:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:45:47 vagrant kernel: [ 3116.832724] libceph: mon2 192.168.15.13:6789 missing required protocol features Sep 4 07:45:57 vagrant kernel: [ 3126.848665] libceph: mon2 192.168.15.13:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:45:57 vagrant kernel: [ 3126.848716] libceph: mon2 192.168.15.13:6789 missing required protocol features Sep 4 07:46:07 vagrant kernel: [ 3136.864960] libceph: mon2 192.168.15.13:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:46:07 vagrant kernel: [ 3136.865038] libceph: mon2 192.168.15.13:6789 missing required protocol features Sep 4 07:48:10 vagrant kernel: [ 3259.952657] libceph: mon0 192.168.15.11:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:48:10 vagrant kernel: [ 3259.952704] libceph: mon0 192.168.15.11:6789 missing required protocol features Sep 4 07:48:20 vagrant kernel: [ 3269.984679] libceph: mon2 192.168.15.13:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:48:20 vagrant kernel: [ 3269.984729] libceph: mon2 192.168.15.13:6789 missing required protocol features Sep 4 07:48:30 vagrant kernel: [ 3280.000791] libceph: mon1 192.168.15.12:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:48:30 vagrant kernel: [ 3280.000841] libceph: mon1 192.168.15.12:6789 missing required protocol features Sep 4 07:48:40 vagrant kernel: [ 3290.016840] libceph: mon1 192.168.15.12:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:48:40 vagrant kernel: [ 3290.016890] libceph: mon1 192.168.15.12:6789 missing required protocol features Sep 4 07:48:50 vagrant kernel: [ 3300.032587] libceph: mon1 192.168.15.12:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:48:50 vagrant kernel: [ 3300.035900] libceph: mon1 192.168.15.12:6789 missing required protocol features Sep 4 07:49:00 vagrant kernel: [ 3310.048834] libceph: mon2 192.168.15.13:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:49:00 vagrant kernel: [ 3310.052296] libceph: mon2 192.168.15.13:6789 missing required protocol features Sep 4 07:49:10 vagrant kernel: [ 3319.953886] libceph: mon1 192.168.15.12:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:49:10 vagrant kernel: [ 3319.957168] libceph: mon1 192.168.15.12:6789 missing required protocol features Sep 4 07:49:20 vagrant kernel: [ 3329.984892] libceph: mon0 192.168.15.11:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:49:20 vagrant kernel: [ 3329.988368] libceph: mon0 192.168.15.11:6789 missing required protocol features Sep 4 07:49:30 vagrant kernel: [ 3340.000906] libceph: mon0 192.168.15.11:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:49:30 vagrant kernel: [ 3340.004269] libceph: mon0 192.168.15.11:6789 missing required protocol features Sep 4 07:49:40 vagrant kernel: [ 3350.016806] libceph: mon2 192.168.15.13:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:49:40 vagrant kernel: [ 3350.020464] libceph: mon2 192.168.15.13:6789 missing required protocol features Sep 4 07:49:50 vagrant kernel: [ 3360.032610] libceph: mon1 192.168.15.12:6789 feature set mismatch, my 103b84a842aca < server's 40103b84a842aca, missing 400000000000000 Sep 4 07:49:50 vagrant kernel: [ 3360.035993] libceph: mon1 192.168.15.12:6789 missing required protocol features
I have a problem trying to mount a SD card in Ubuntu 12.04. The message what I get from the system is:
mmc0: error -110 whilst initialising SD card
I’m on the 3.5.0-24-generic kernel.
I check previous kernel 3.5.0-15 and card is on the system. I think is some bug in kernel.
I was looking some solution on web. They say my card is dead (but is working)
What I should do?
Some more information on this issue here. If someone have more question about my hardware just ask.
Braiam
66.2k30 gold badges174 silver badges262 bronze badges
asked Feb 16, 2013 at 12:49
5
Basically this error arises only when the SDcard got damaged. But as you mentioned its working, Please try the following steps and share your feedback.
- Please check the output of
dmesgorlsusbto check whether it detects the SD card. - Open the «Disk Utility» application and check whether your SD card is listed. If its listed, just click it -> Unmount Volume -> Format the Volume with suitable filesystem.
- Also, try mounting the SD card on Windows and check whether it is working or not.
Also, you can downgrade your kernel by installing the old kernel / latest stable kernel version with sudo apt-get update && sudo apt-get dist-upgrade && sudo apt-get autoremove.
wget the latest stable kernal from Kernel Website and install it with sudo dpkg -i *.deb && sudo update-grub2
Please select the proper kernel while booting and check whether your SD card mounts well!
Kalle Richter
5,78619 gold badges67 silver badges100 bronze badges
answered Feb 24, 2014 at 11:29
Naga2RajaNaga2Raja
2582 silver badges7 bronze badges
- Forum
- The Ubuntu Forum Community
- Ubuntu Official Flavours Support
- Networking & Wireless
- [SOLVED] mounting windows network share: «connection timed out»
-
mounting windows network share: «connection timed out»
I’m trying to mount a windows share network drive (on a university’s server) using Ubuntu 10.04. I’d like to make it a permanent mount, so I’ve added to etc/fstab, but am having problems with the following error:
Code:
mount error(110): Connection timed out Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Here’s what I’ve done so far:
My /etc/fstab has:Code:
//files.school.edu/shared /mnt/shared cifs noauto,user,username=username,uid=user,gid=group,mode=700,filemode=600 0 0
I have smbfs installed. I’ve created mnt/shared. Then from
Code:
sudo mount /mnt/shared
I type in my password, wait awhile, then get the «Connection timed out» error message above.
I’ve solved a couple of problems already to get here, but my ignorance has kept me from getting further. Any ideas? I’ll be more than happy to post some output — let me know what I should be looking at. Thanks.
-
Re: mounting windows network share: «connection timed out»
Have you tried whether you can access the resource by using the Places item on the taskbar, and then follow the dialog for ‘connect to server’ under network?
If you can get that to work, then it’s just down to detail. Otherwise there is a permissions problem to sort out (probably at the server end)Derek
-
Re: mounting windows network share: «connection timed out»
dandnsmith — thanks.
After doing what I describe above, I rebooted my computer, and the share still did not mount. However, I started it up this morning, and everything worked. Great!
If you’re looking to do something like this, try what I’ve done above. It worked for me!
bjorn
-
Re: mounting windows network share: «connection timed out»
Glad to hear it works now.
A couple of quick comments:
— you don’t need (I believe) the full samba stuff if you are not creating shares for Windows machines to access (the default stuff installed with ubuntu is enough to allow you network access to external shares).
— it’s surprising how often re-booting and waiting will ‘solve’ a problem (especially if anywhere it involves Windows servers). I’ve seen it so many times that I tell people ‘just wait, and try again’ if it ought to work, but doesn’t. There can also be questions concerning the number of network connections (and length of life) on Windows sharing.Derek
