I'm lost the ability to mount my cdrom drive in either my host or guest OS. I installed VMware Player within my Kubuntu 12.04 LTS OS. After which I installed WinXP as a virtual OS . I was originally able to use the cdrom in either WinXP or Kubuntu, switching between the two by means of a toggle built into VMware Player (via CD icon in bottom-right corner or File Menu > Virtual Machine > Removable Devices > CD/DVD (IDE) > /dev/sr0 or /dev/cdrom)
Unfortunately I think one of the two below instances may have broken my cdrom mount point when a media cd is inserted:
1) I lost power/rebooted while I was using the virtual WinXP OS, and it had the cdrom drive mounted.
2) When I plugged in an additional internal 1TB HDD it mounted, but I could not write to the disk. Hence, I determined it was because root took ownership of it. I then input these commands to retake control of it
It resolved the issue and now I can write to the 1TB HDD. I'm trying to see if I can't re-mount my cdrom drive so I can use within the host and guest OS. Any assistance is greatly appreciated! Thanks in advance.
My relevant hardware is as follows:
1x cdrom drive ==>
1x SSD (host OS & all mount flags?) - formatted to ext4 ==> /dev/sda1
1x HDD - formatted to ext4 w/ no boot flags(?) ==> /media/sdb1
Here's my mount output
Here's my /etc/fstab (I'm not sure it's even helpful...)
Any suggestions?
Unfortunately I think one of the two below instances may have broken my cdrom mount point when a media cd is inserted:
1) I lost power/rebooted while I was using the virtual WinXP OS, and it had the cdrom drive mounted.
2) When I plugged in an additional internal 1TB HDD it mounted, but I could not write to the disk. Hence, I determined it was because root took ownership of it. I then input these commands to retake control of it
Code:
chown -R user * chown -R user .
My relevant hardware is as follows:
1x cdrom drive ==>
1x SSD (host OS & all mount flags?) - formatted to ext4 ==> /dev/sda1
1x HDD - formatted to ext4 w/ no boot flags(?) ==> /media/sdb1
Here's my mount output
Code:
/dev/sda1 on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) /dev/sdb1 on /media/sdb1 type ext4 (rw,noexec,nosuid,nodev) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) /home/paul/.Private on /home/paul type ecryptfs (ecryptfs_check_dev_ruid,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs,ecryptfs_sig=682470319a02235e,ecryptfs_fnek_sig=3498e8be2c92771c) vmware-vmblock on /run/vmblock-fuse type fuse.vmware-vmblock (rw,nosuid,nodev,default_permissions,allow_other)
Code:
# /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> proc /proc proc nodev,noexec,nosuid 0 0 # / was on /dev/sda1 during installation UUID=cc62e445-3e5d-4bce-a2fd-04372b061e03 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation #UUID=8fd889bd-e3fa-40b0-a813-714a5b188c89 none swap sw 0 0 /dev/mapper/cryptswap1 none swap sw 0 0 /dev/sdb1 /media/sdb1 ext4 user 0 0
Comment