General :: Mount: Special Device /dev/scd0 Does Not Exist
Jul 3, 2010mount: special device /dev/scd0 does not exist
View 1 Repliesmount: special device /dev/scd0 does not exist
View 1 RepliesThe CD-ROM on this computer, my ubuntu laptop, does not seem to be working properly. It works on and off. I burned a .iso image yesterday but today I can't get it to even read the CD in my drive. I just want to read the CD to see if it is the Ubuntu Live CD I burned a while ago or if it is the Vista Recovery CD.
TL;DR: CD-ROM isn't working properly. When I click on the drive this is the error.
Code:
mount: special device /dev/scd0 does not exist
P.S. I am trying to get Windows Office to install using Wine because I am tired of windows. I know that open office is great. but I have to have excel 2007 and word 2007 for school.
I've just upgraded to the new version of Ubuntu (10.04) and I've got a problem with the mounting configuration.
My PC access to a NAS server which is running samba. Everything worked great before upgrading
In the /etc/fstab, I added the following line :
Code:
//nas/share /mnt/share auto credentials=/root/.smbcredentials,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
and the system always replies :
[Code]....
why I'd be receiving this error. I have created a partition and filesystem and put the label in fstab. Everytime I reboot the server it is unable to mount the filesystem. However I am able to mount it manually.
View 5 Replies View RelatedI seem to have another issue with my raid system
mount -a
mount: special device UUID=fb518c74:2b6bd0f4:66db5ce6:7e004239 does not exist
but when i do mdadm -vv --detail /dev/md5 ... this is what i get --->
/dev/md5:
Version : 1.1
Creation Time : Fri Feb 25 14:07:36 2011
Raid Level : raid1
[code]....
I have created a logical partition (/dev/sda5) and have formatted it with an ext3 filesystem and given it the label PHOTOS.
# mkfs.ext3 -L PHOTOS /dev/sda5
If I mount it to my /PHOTOS directory manually, it does so correctly. However, when I try to automount, it gives me this message:
# mount -a
mount: special device PHOTOS does not exist
I've entered this line in my fstab file:
PHOTOS/dev/sda5ext3defaults0 0
I'm just not sure what's happening; I've never had trouble mounting a filesystem before. Oh and it's a RHEL 5 installation.
Device/Special file Clairification Requested.I'm reading a short article on Device/special files because it is related to VFS. This article has this paragraph that has to many pronouns in it to get an understanding of. URL..."In short, a device file (also called as a special file) is an interface for a device driver that appears in a file system as if it were an ordinary file. This allows software to interact with the device driver using standard input/output system calls, which simplifies many tasks."
What does a Device file have to do with the Application and the Driver communicating? Wouldn't the order of data transfer be , Application to driver and then to Device file?
I've got an LVM2 VG containing 1 LV running on SLES11 SP1.
I have an entry in /etc/fstab to remount them at boot:
Code:
/dev/myVG/ibmLV /opt/IBM ext3 defaults 0 0
Whenever I reboot the whole VG disappears and I find the following in /var/log/boot.msg:
Code:
<notice -- Apr 15 12:35:55.954677000> boot.localfs start
Waiting for /dev/myVG/ibmLV . no more events
[Code]....
I made a duplicate of a Centos 5.5 system disk with dump (dd if=/dev/sda of=/dev/sdb). No device files for sdb were created, but I guess that's not too surprising. I rebooted, and the device files were created. But how would I create them if I wanted to avoid the reboot?
I looked around for info on mknod and MAKEDEV but didn't find a lot.
I'm running mythbuntu 0.21 on a hardy environment. I had a thread under mythbuntu but i think this was the wrong forum. So here it is again
<lameexcuse>
Currently i hesitate to upgrade to lucid because i fear problems coming up which i do not have the time to solve.
The machine works generally fine so why upgrade to lucid?
</lameexcuse>
[Code]...
How can I find which /dev/? device to mount my USB hard drive on redhat 3 taroon, I've been googling a lot and checked log files and still no clue. I'm trying my last chance with you experts, # /sbin/fdisk -lgives nothing about the USB drive
# lsusb -vv
Bus 004 Device 005: ID 059f:0951 LaCie, Ltd
Device Descriptor:
[code]....
I am trying to set up my usb device to be available to mount and umount only for me, not for other users. Using Slackware 12.2Entry in fstab is as follows:
Code:
/dev/disk/by-label/USB /media/usbvfat auto,group,user,noexec,gid=usb,umask=007 0 0
device information:
[code]....
I am dual-bootng Ubuntu 9.10 and Mint 8, both of which use GRUB2. The Mint 8 GRUB sets the initial menu since Mint was loaded after Ubuuntu 9.10. Since both use GRUB2 I was not concerned about this.
Both before the installation of Mint and afterward I see a series of messages fly by on the screen when Ubuntu is booted. These come right after the initial presentation of the Ubuntu logo.
By restarting several times I can read the first several lines. They are:
Mount: Mount Point 0 does not exist
Mount 0 terminated with status 32
Mountall: Filesystem could not be mounted
Further lines follow but I would have to reboot umpteen times to have any chance of copying those.
I have looked in the various Ubuntu GRUB2 files for "Mount Point 0". I do not see any reference to it.
GParted, BKID and etc/fstab all agree on the UUIDs set for my Ubuntu/, Ubuntu Home and Ubuntu swap file.
I see nothing like this when I boot Mint 8.
My questions:
What is the point to error messages (I assume that is what they are) that fly by too quickly to be read? Are they saved to a logfile somewhere?
What is "Mount Point 0"?
What does it mean in this context to say "Filesystem could not be mounted"?
This is all very curious because Ubuntu proceeds to mount and run just fine.
What is Ubuntu trying to do as it starts up that it cannot do?
How do I repair whatever has to be repaired in order to turn off these messages?
I have looked through such GRUB2 dcumentation as I can find without seeing any reference to this.
I have a Corsair R60 ssd disk which is a disk with both sata and usb connectors. But the usb thing seems to be a bit non-standard, or maybe its just my fedora linux.When I insert the disk using a usb cabel to a running Fedora 14 linux system, a device called /dev/sg3 is added but that is all. No new /dev/sd* device is created so I can't mount the disk.
If I look at
cat /proc/scsi/sg/device_strs
I get
ATA Hitachi HTS54321 FB2O
HL-DT-ST DVDRAM GSA-T50N RP05
Seagate Desktop 0130
Corsair CSSD-R60GB2
So the disk is there. (The last entry) but my linux will for some reason not see it as a usb hard disk. When I insert other usb disks they work fine. It is only this specific disk which causes problems. I have tried on 3 different computers with the same result.
A hint to the problem may be that if I add the disk to a windows system(With usb) the disk is called "A fixed disk" and not a portable disk as expected. The disk works fine with linux If i connect it with the sata cabel, but I would really like to have it working with usb too. (To mount it on computers without sata).
Added:I did try to mount /dev/sg3 but mount say that its not a block device. (File say Its a character special device).
Added output from dmesg:
[ 97.454073] usb 7-1: USB disconnect, address 2
[ 105.913055] hub 2-0:1.0: unable to enumerate USB device on port 3
[ 107.048054] usb 2-3: new high speed USB device using ehci_hcd and address 5
[ 107.162900] usb 2-3: New USB device found, idVendor=1b1c, idProduct=1ab8
[code]....
I found an other guy with exactly the same problem [URL] so I think its beginning to look like a bug in the drives firmware or in the linux kernel.
Final update:Corsair have said that the disk design is broken and there does not seem to be any way to make it work.
i can't mount my USB flash disk using GUI... trough normal "mount" command it works fine, but i want to make it automatic. here is error output:
Code:
Rejected send message, 1 matched rules;
type="method_call", sender=":1.13" (uid=1000 pid=2301 comm="exo-mount)
interface="org.freedesktop.Hal.Device.Volume"
member="Mount" error name="(unset)" requested_reply=0
destination="org.freedesktop.Hal" (uid=0 pid=1488 comm="/usr/sbin/hald))
[root@servers guest]# /bin/mount -o -uid=root,gid=root,username=userid,password=user1passwd //172.16.1.212/backup/user1backup /mnt/tmp
retrying with upper case share name
mount error 6 = No such device or address
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
[root@servers guest]#
I also tried:
[root@servers guest]# /bin/mount -t cifs -o -uid=root,gid=root,username=user1,password=user1pass //172.16.1.212/backup/user1backup /mnt/tmp
but no luck!
when i test errors by "sudo mount -a" i got this
mount: mount point swap does not exist
after writing this command "sudo gedit /etc/fstab" ,,,, i got this
UUID=5148630128FE30C4 /media/Collection401 ntfs-3g defaults 0 0
UUID=FE4C11644C1118CB /media/Collection402 ntfs-3g defaults 0 0
UUID=6e73cf26-edcd-42b0-884c-e2686dd70d15 / ext3 defaults 0 1
UUID= swap swap sw 0 0
UUID=7DF3923D63A29C0E /media/Eng ntfs-3g defaults 0 0
UUID=492905577CF6BDDF /media/Software ntfs-3g defaults 0 0
/dev/sr0 swap udf,iso9660 defaults 0 0
After connecting, dmesg shows:
Code:
After that, there are no /dev/sd* entries. the hard drive works as expected on my windows box. how can i mount this drive?
I'm trying to get fstab to auto-mount a removable device when its plugged in? Is this possible and if not what is the easiest way to auto-mount a removable device?
View 3 Replies View RelatedI am developing a device that will run Linux as its operating system.The device is a small form factor X86 device with a flash drive exposed as a SATA-device. So it is not very dissimilar from any other PC running Linux.For several good reasons I am building my own "distribution", instead of using an existing one.What confuses me is how mount/umount of the root file system is handled.I boot my kernel with the commandline "root=/dev/sda1 rw" which works fine. But everytime I do poweroff or reboot Busybox complained about no /etc/fstab, so I decided to build one.Should I have an entry for my root file system? It seems like this is shadowed by the rootfs anyway. I.e. if I have the fstab entry "/dev/sda1 / ext2 1 1" mount still reports rootfs on / type rootfs (rw)/dev/root on / type ext2 (rw,relatime,errors=continue)My questions are:Do I need to worry? Will the drive be correctly unmounted by the kernel on poweroff/reboot?If I want to perform file system checking on boot, can I do that without resorting to an initrd?
View 1 Replies View RelatedI have a program which mounts /dev/sdb1 for which I lack the source code. This device does not exist on my RedHat 9 system and I want to create /dev/sdb1 such that it's an alias for /dev/hdb1 Can I do this? with MAKEDEV?
I need to have an alias which will allow it to mount, not create a symbolic link to an already mounted directory. i.e. 'mount /dev/sdb1 /mnt/harddrive' should actually mount /dev/hdb1
I'm using an external USB drive to perform system backups. The script I'm using has a mount command - mount /dev/sdcx /systembak, it works fine until the external drive is mounted into a different USB port which causes the device path to change and the script needs to be modified to reflect that change. Looking in the /dev/disk/ directory I see ./by-id ./by-label ./by-path ./by-uuid. I've been able to mount the disk using one of the device pointers in those directories; are any of those device pointers static or do they change every time the USB disk is plugged into a different USB port.
OS: RHEL/CentOS
What do I call this device in /etc/fstab. Currently the line I'm using is... code...
Having made a mount directory (/media/ipod) an error message tells me
... mount: special device /dev/sdc0 does not exist...
when I try to mount it.
I cannot see it in 'gparted' or 'disk utility' but I can see it on sys log and kern log when I plug it in and remove it.
I have visited several help forums and loaded several types of recommended software (ifuse-libs and mux's etc) but with no satisfactory result.
I have successfully 'Jail broken' the device using 'Blackra1n' on a windows machine.
It used to appear on the desktop but alas...no more. I've obviously broken something!
How come I can view the contents of the drive using Dolphin before I mount the device? I cannot see the contents using the bash shell until the device is mounted.
View 4 Replies View Relatedwhat now trying to mount partition get this error this is the partition ubuntu 9.10 is installed on and upon reboot error no device with a long string. mount: can't find /dev/sda6/mnt in /etc/fstab or /etc/mtab
so now that I believe I've successfully mounted the partition how do I direct the bootloader to this partition /dev/sda6 on /media/11076e45-e27d-470b-bb6d-6894f7809a0c type ext4 (rw,nosuid,nodev,uhelper=devkit)
How can I mount a device with specific user rights on start up? I still have some problems figuring it out. I would like to mount the divide with uid=1000 and gid=1000. My current entry to the /etc/fstab/ file looks like this:
dev /var/www vboxsf rw, suid, dev, exec, auto, nouser, async, uid=1000
I need a command to display the next info from my hdd:
device name - filesystem - uuid - mount point
I found blkid but the mount point is not displayed, I've already look in man but there is no parameter for that
Found a raw device for my card when reading through the /proc/partition list but got a "no device" message when mounting the card - mount -t vfat /dev/sda1 /var/card though there is sda in the list.How to know if sda1 exists?
View 1 Replies View RelatedI have one hard disk (call her HDA) that contains nothing but a single ext4 partition containing a backup of all my important data. Last night I did a clean install of Ubuntu 10.10 on my primary hard disk (call her HDB) and from there proceeded to upgrade directly to Ubuntu 11.04 upgrade. In 10.10, I was able to read HDA just fine. However after the upgrade, I can no longer mount this drive. When mounting from file browser:
Code:
Error mounting: mount: wrong fs type, bad option, bad superblock on /dev/sda,missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so The end of dmesg said the following:
Code:
dmesg | tail
[ 82.130904] EXT4-fs (sda): bad geometry: block count 122096646 exceeds size of device (122096381 blocks)
my hard disk has a block count greater than the size of my device. I've done my background searching on this and tried a command line utility I've never heard of before:
Code:
# sudo e2fsck /dev/sda
e2fsck 1.41.14 (22-Dec-2010)
The filesystem size (according to the superblock) is 122096646 blocks
The physical size of the device is 122096381 blocks
[code]....
this is as far as I've gotten. This drive holds over a decade's worth of work for me and is extremely valuable. I really didn't think that the Ubuntu upgrade process would mess with this drive, seeing as the Ubuntu install was contained on an entirely different drive. What is it that I need to do to restore my drive to working status?
I'm trying to mount a custom device node for each usb port of my pc. For example: Every pen drive connected to my usb 1-1.2 will be called /dev/usb2 and mounted on /mnt/usb2, on usb 1-1.3 port the device node will be called /dev/usb3 and mounted on /mnt/usb3.
I'm using an embedded linux, the device handler is mdev. Editing mdev.rules I'm able to manage new devices and write special rules for them (on /bin/hotplug.sh I can mount the /dev/udisk device on anywhere I wanna):
Code:
# This will be called after scsi emulation, so the
# new device (sda1, sdb1 ...) will be managed by /bin/hotplug.sh
mmcblk0p10:00600=sdcard */bin/hotplug.sh
sda10:00600=udisk * /bin/hotplug.sh
[Code].....
Is there anyway to change scsi emulation configurations or code? I want to call my pen drive on my way (/dev/usb1 instead of /dev/sd*)!