trouble mounting my dvd-rw - can someone check my fstab?
hello. I am trying to mount my dvd-rw drive but I get this error:
Quote:
here is a copy of my fstab - can someone check it out and see what the problem is? Quote:
|
Welcome to LQ Bigfoot!
How are you trying to mount it? What command are you issuing? It looks like your dvd is being called cdwriter, eh? And you can't quite use noauto and auto - conflicing statements. Plus, you're using ro (read only) rather than rw (read/write). You do want to write with it, don't you? Try this for your dvd entry in fstab Code:
/dev/scd0 /mnt/dvd iso9660 user,umask=1000,rw,noauto 0 0 $ mount /mnt/dvd as a normal user. Works like a charm here. Your system is correct, /dev/scd0 is not a block device. NB: Don't forget to make the directory you wish to mount. |
hello - thanks for the quick response.
I updated my fstab: Quote:
but yet when I $ mount /mnt/dvd, I still get Quote:
|
Please post the output of:
"mount" as normal user Edit: Which distribution are you using? Posted wrong commands. Where is you DVD located in your box? |
Look in /var/log/dmesg
for lines that look like this Code:
hda: Maxtor 6Y060L0, ATA DISK drive IDE drives are listed. |
output from $ mount:
Quote:
/var/log/dmesg does not exist. hmmm... |
Quote:
I mean, what does this mean? Quote:
Quote:
And I'm thinking, how can you run a Linux OS and not have a dmesg file? Try issuing "locate dmesg" to find it. I get this Code:
mingdao@paul:~$ locate dmesg So you should be able to issue "dmesg" or "/bin/dmesg" and get some output. Assuming you can use some type of text editor, try issuing dmesg > boot.messages which will create a file named boot.messages and then open that file with an editor and read it. Post if you find your drives. Or you could issue "/bin/dmesg | less" and scroll up through the output, but I thought reading a file might be easier for you. If you can't find your drives, post the whole dmesg file. If your comp doesn't recognize the drive, you'll never mount it. You might not even have support in your kernel to use it. |
Hi,
To be sure that your CD/DVD is not associated to /dev/hd?, do "cat /proc/ide/hd?/model"... I have no scsi drive but I suppose that there's the same for scsi, so check also /proc/scsi/sc?/model There's also /proc/devices which can give you the major of your drive Oliv' |
Quote:
Quote:
1. $ locate dmesg Quote:
Quote:
Quote:
Quote:
I appreciate your help Chinaman cheers! |
**update***
I spoke too soon! After re-reviewing the dmesg, I see my dvd-rw is listed as hdc. So I can now mount it! Sweet. Now, I have one thing left: when I mount it, I get an error that says Quote:
Quote:
|
Quote:
Edit: Sorry, I've got a new keyboard and hit some key with enter at the same time. Will continue in next post. |
simple but incomplete answer
Sasquatch,
For now I can only give you a little bit of an answer. You are running a 2.6.x series kernel, and everything changed when we went from 2.4 to 2.6, as far as using CD/DVD writers and maybe some SCSI devices are concerned. I see from your dmesg output that you have Seagate 80GB ATA drive, a Maxtor SCSI drive, a Flash disk, a DVD-ROM and a DVD-RW - at least. Is that correct? I just installed a 2.6.7 kernel and I'm having to find out how to use the CD/DVD writers without scsi emulation, which is how we've done it in all the kernels before 2.6. That is on my To Do List for today, but time with my girls is first. I will get back with you. In the meantime, here's some tidbits. (1) you said when you mounted it you were given this: mount: block device /dev/hdc is write-protected, mounting read-only but that's not an error, just an informational message. It says you can read, but not write, to the drive. That comes from the line in /etc/fstab where you have ro rather than rw. (2) you know how to mount it, obviously, but to unmount it you issue "umount /mnt/dvd" if that's the directory where it's mounted. And yes, there is only one n in the umount command. (3) K3b may be all you need to burn CD/DVDs with your present setup, but I can't answer that yet. Once you've changed your /etc/fstab to rw, see if you have a menu where you can find the K3b program. I don't know what apps are available in Yoper. You could also issue locate k3b | grep '/k3b$' in a terminal. Just last night I moved 3 drives from my other computer into this one, and I've not yet read/searched to find out how I'm going to use my writers, flash disk, and usb hard drives with the 2.6.7 kernel. I do know that I can mount my flash disk just by issuing "mingdao@james:~$ mount /mnt/sdb1" Below is my present /etc/fstab, mostly from the other comp. I'll be working on it today, but those last entries are for mounting my flash and usb hard drives. They say /dev/sdb(c, d) and the letter all depends upon which order they're plugged in. My SATA hard drive is /dev/sda and then next thing I plug in (flash disk in my example above) will become /dev/sdb. Therefore, when I issued the above command I mounted it as user, and now user can read/ write to that drive. I'm posting this file in hopes that some of it makes sense to you, and you can use that knowledge to edit your file. Code:
mingdao@james:~$ cat /etc/fstab machine, because I used them with scsi emulation with kernel 2.4.26. |
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
I appreciate your help again chinaman. cheers |
You still have your /etc/fstab file wrong.
Quote:
Just use one or the other, not both, to suit your personal taste. And I'm not sure the purpose of the exec command. What are you "executing?" Issue and read "man exec" for more info. I've learned how to setup /etc/fstab for these drives in 2.6.7 Code:
/dev/hdc /mnt/cdrw iso9660 noauto,user,rw 0 0 a disc into the drive, right-click the icon and choose mount. Then after it mounts you can click that icon and launch the file browser. The other way is to use the command line from a terminal and issue mingdao@james:~$ mount /mnt/dvd mount: block device /dev/hdd is write-protected, mounting read-only mingdao@james:~$ ls -alc /mnt/dvd total 21 dr-xr-xr-x 1 root root 2048 1970-01-01 07:00 ./ drwxr-xr-x 10 root root 240 2004-09-25 22:18 ../ -r-xr-xr-x 1 root root 56 2001-09-26 17:18 AUTORUN.INF* dr-xr-xr-x 1 root root 2048 2003-09-26 14:27 AutoRun/ -r-xr-xr-x 1 root root 10134 2000-03-09 18:34 CyberLink.ico* dr-xr-xr-x 1 root root 2048 2003-09-26 14:26 MediaShow/ dr-xr-xr-x 1 root root 2048 2003-09-26 14:23 PowerDVD/ dr-xr-xr-x 1 root root 2048 2003-09-26 14:24 PowerDirector/ mingdao@james:~$ mount /mnt/cdrw mount: block device /dev/hdc is write-protected, mounting read-only mingdao@james:~$ ls -alc /mnt/cdrw total 839 drwxr-xr-x 7 root root 4096 2004-07-08 03:06 ./ drwxr-xr-x 10 root root 240 2004-09-25 22:18 ../ -rw-r--r-- 1 root root 9681 2004-07-08 03:04 ANNOUNCE.10_0 -rw-r--r-- 1 root root 18606 2004-07-08 03:04 BOOTING.TXT -rw-r--r-- 1 root root 93284 2004-07-08 03:04 CHECKSUMS.md5 -rw-r--r-- 1 root root 189 2004-07-08 03:04 CHECKSUMS.md5.asc -rw-r--r-- 1 root root 17976 2004-07-08 03:04 COPYING -rw-r--r-- 1 root root 15234 2004-07-08 03:04 COPYRIGHT.TXT -rw-r--r-- 1 root root 602 2004-07-08 03:04 CRYPTO_NOTICE.TXT -rw-r--r-- 1 root root 125321 2004-07-08 03:04 ChangeLog.txt -rw-r--r-- 1 root root 32425 2004-07-08 03:04 FAQ.TXT -rw-r--r-- 1 root root 117520 2004-07-08 03:04 FILELIST.TXT -rw-r--r-- 1 root root 1565 2004-07-08 03:04 GPG-KEY -rw-r--r-- 1 root root 275105 2004-07-08 03:04 PACKAGES.TXT -rw-r--r-- 1 root root 12530 2004-07-08 03:04 README.TXT -rw-r--r-- 1 root root 5191 2004-07-08 03:04 RELEASE_NOTES -rw-r--r-- 1 root root 14826 2004-07-08 03:06 SPEAKUP_DOCS.TXT -rw-r--r-- 1 root root 15434 2004-07-08 03:06 SPEAK_INSTALL.TXT -rw-r--r-- 1 root root 70561 2004-07-08 03:06 Slackware-HOWTO -rw-r--r-- 1 root root 5136 2004-07-08 03:06 UPGRADE.TXT drwxr-xr-x 2 root root 4096 2004-07-10 02:32 bootdisks/ drwxr-xr-x 3 root root 2048 2004-07-12 05:35 isolinux/ drwxr-xr-x 20 root root 4096 2004-07-11 23:46 kernels/ drwxr-xr-x 2 root root 4096 2004-07-08 03:04 rootdisks/ drwxr-xr-x 15 root root 4096 2004-07-08 03:06 slackware/ Great! They mount! So I guess it's going to mount it read-only, since I'm using a disc that's already written to and closed. Additionally, there are some filesystems that can't be read unless you compile support into the kernel, such as the cdfs filesystem. To play regular audio CDs, which are .cda files, what I do is install this xmms-cdread-0.11d.tar.gz and then xmms will read the CDs and play them. I don't have K3b on this comp. I'll d/l and compile it tomorrow. Then I can tell you how to burn CDs and DVDs - or maybe you can tell me. I did check the dependencies and I have everything except vcdimager for reading and copying VCDs. But for this issue Quote:
written to as a normal drive, so you will not "mount" them to write to them. Writing will be done by K3b, if you desire. I also believe that cli apps such as cdrecord will write to them, I'm just not sure how now that I've changed to a 2.6.x kernel. After all, K3b is just a gui frontend for cdrecord and other apps, it doesn't do anything without them. If I remember correctly what I read in K3b, the permissions for writing to the drives are given to cdrecord. That being correct, it shouldn't matter whether you give rw or ro in the line in /etc/fstab but maybe with ro you won't get that informational message. So I don't think your fstab is exactly inadequate for writing, but rather, the way it's done in the 2.6.x kernels. I'll check more tomorrow. It's Sunday here, and I'm supposed to be "resting from my work." If you want, you can read about K3b at their website. And don't forget to setup your DVD-ROM similar to the DVD-RW. Just give it the proper device name. So, after you change your /etc/fstab like mine above, where is the problem? Can you mount and read discs? Do you have ISO 9660 CD-ROM filesystem support in your kernel? And you will need to get the latest versions of both Kb3 and cdrecord, because earlier versions did not know how to work with ide-cd and thus you had to load ide-scsi anyway. |
Quote:
If the message comes at no consequence and I am able to burn all disc types, why does it always have to pop up and tell me? how I can prevent it from coming up? as for my trouble umounting: sure, I can mount/umount in the konsole but it would be nice (and easier for the family) to be able to simply click the dvd icon to mount and then right-click "umount" - how can I simply configure this so that non-root can umount? Right now, non-root can mount but root is needed to umount - this doesnt seem very intuitive and surely there must be a way so that all users can mount/umount via kde. here is my current fstab: Quote:
|
All times are GMT -5. The time now is 10:24 AM. |