Unable to see a SD Card Drive in Ubuntu 1010 in VM Ware Player

Asked by Stephan Cadisch

Looking for help for a problem which keeps me busy a couple of days already. I'm using Ubuntu 1010 (installed from ubuntu-10.10-desktop-i386.iso) in a VM Ware Player 3.1.2 build-301548, after installing a new virtual machine with this Ubuntu Build, I was able to see my SD Card Drive which I use as my data store and could access all the data properly. After running the Update Manager in Ubuntu, to be updated on the most recent released updates, and restarting Ubuntu, I couldn't find my SD Card anymore in Filesystem/mnt/hgfs. Hope to find a solution for this problem, thanks in advance.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu util-linux Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

If you boot and login without the SD card inserted then once the OS settles, insert a card and run:

dmesg | tail; sudo fdisk -l; mount

What is output?

Revision history for this message
Stephan Cadisch (stephan-cadisch) said :
#2

shorty@ubuntu:~$ dmesg | tail; sudo fdisk -l; mount
[ 5.313334] vmhgfs: disagrees about version of symbol sock_recvmsg
[ 5.313336] vmhgfs: Unknown symbol sock_recvmsg (err -22)
[ 5.313365] vmhgfs: disagrees about version of symbol sock_release
[ 5.313367] vmhgfs: Unknown symbol sock_release (err -22)
[ 5.347659] vmci: disagrees about version of symbol contig_page_data
[ 5.347694] vmci: Unknown symbol contig_page_data (err -22)
[ 5.347738] vmci: disagrees about version of symbol __alloc_pages_nodemask
[ 5.347740] vmci: Unknown symbol __alloc_pages_nodemask (err -22)
[ 5.414275] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
[ 9.089095] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
[sudo] password for shorty:

Disk /dev/sda: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 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: 0x0005b182

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 1244 9990144 83 Linux
/dev/sda2 1244 1306 492545 5 Extended
/dev/sda5 1244 1306 492544 82 Linux swap / Solaris
/dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0)
proc on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev type devtmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /var/lib/ureadahead/debugfs type debugfs (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/shorty/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=shorty)
shorty@ubuntu:~$

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

Sda sounds like it is not healthy. I suggest you boot to live CD and check all partitions for errors with fsck.

Can you help with this problem?

Provide an answer of your own, or ask Stephan Cadisch for more information if necessary.

To post a message you must log in.