Hello SuSE people, Running 10.0, KDE 3.5.1 on an AMD 64 bit system. I have a dvdrecorder which is /dev/hdc, and a cdrecorder which is /dev/hdd. Each of them will play with an audio CD. Ever since I did a new install of 10.0 (from 9.2) a few months ago I've had a problem with automounting data cd's dvd's. I've been able to work around it but is beginning to get annoying. Here is what happens: I put in a data disk and wait for it to mount in media:/ I get this message: Could not mount device. The reported error was: mount: according to mtab, /dev/hdc is already mounted on /media/dvdrecorder mount failed But,it did mount evidently and then shows up in media:/ I can then see it and use it for my purpose. Info: When I look at "My Computer" which is media:/ It shows all of my mounted hard drives and the unmounted floppy drive, but not the cdrecorder nor the dvdrecorder. (Used to see it in 9.2) (both devices are owned by me and the group is disk) I then try to umount it and get this message: umount: only root can unmount /dev/dvdrecorder from /media/dvdrecorder Please check that the disk is entered correctly. I have to "push the button" on the drive to eject the cd. Here is my mtab: (There is nothing in it about the cdrecorder or dvdrecorder that I can see) (The dev mapper entries are because those partitions are mounted as LVM's on my second hard drive hdb) /dev/hdb1 / ext3 rw,acl,user_xattr 0 0 proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 tmpfs /dev/shm tmpfs rw 0 0 devpts /dev/pts devpts rw,mode=0620,gid=5 0 0 /dev/hda2 /workspace ext3 rw,acl,user_xattr 0 0 /dev/hda3 /datastorage ext3 rw,acl,user_xattr 0 0 /dev/hda5 /backup ext3 rw,acl,user_xattr 0 0 /dev/mapper/system-data /data ext3 rw,acl,user_xattr 0 0 /dev/mapper/system-home /home ext3 rw,acl,user_xattr 0 0 /dev/mapper/system-local /local ext3 rw,acl,user_xattr 0 0 /dev/mapper/system-opt /opt ext3 rw,acl,user_xattr 0 0 /dev/mapper/system-usr /usr ext3 rw,acl,user_xattr 0 0 /dev/mapper/system-var /var ext3 rw,acl,user_xattr 0 0 /dev/hda1 /c vfat rw 0 0 usbfs /proc/bus/usb usbfs rw 0 0 /dev/fd0 /media/floppy subfs rw,nosuid,nodev,noatime,fs=floppyfss,procuid 0 0 Here is my fstab: (Sorry about the wrap) /dev/hda2 /workspace ext3 acl,user_xattr 1 2 /dev/hda3 /datastorage ext3 acl,user_xattr 1 2 /dev/hda5 /backup ext3 acl,user_xattr 1 2 /dev/hdb1 / ext3 acl,user_xattr 1 1 LABEL=data /data ext3 acl,user_xattr 1 2 LABEL=home /home ext3 acl,user_xattr 1 2 LABEL=local /local ext3 acl,user_xattr 1 2 LABEL=opt /opt ext3 acl,user_xattr 1 2 LABEL=usr /usr ext3 acl,user_xattr 1 2 LABEL=var /var ext3 acl,user_xattr 1 2 /dev/hda1 /c vfat defaults 0 0 /dev/hdb2 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/hdc /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/hdd /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0 none /subdomain subdomainfs noauto 0 0 About the floppy: If I put a floppy in the drive and try to mount it I get the already mounted message from mtab and am unable to access the drive. I keep hoping that with each new release "everything will just work" sigh !! I have tried every possible configuration I can think of and Yast is completely clueless on configuring these drives. I know that some of you have completely abandoned this automount/hal stuff and reverted to the "old" way of manually mounting. I would be tempted to do that if I knew how. Hope someone can help me solve this. Bob S.
The Monday 2006-03-06 at 02:11 -0500, Bob S wrote:
Ever since I did a new install of 10.0 (from 9.2) a few months ago I've had a problem with automounting data cd's dvd's. I've been able to work around it but is beginning to get annoying. Here is what happens:
I put in a data disk and wait for it to mount in media:/ I get this message:
Could not mount device. The reported error was: mount: according to mtab, /dev/hdc is already mounted on /media/dvdrecorder mount failed
But,it did mount evidently and then shows up in media:/ I can then see it and use it for my purpose.
It is double-mounting. Two "things" are trying to automount it.
Here is my fstab: (Sorry about the wrap)
Remove this two lines:
/dev/hdc /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/hdd /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
This one too:
/dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0
Use traditional lines, no subfs - because subfs is trying to automount, and hald is trying to automount also (so my crystal ball tells me ;-) ). For example: /dev/hdc /media/dvdrecorder auto noauto,ro,nosuid,nodev,exec 0 0 /dev/hdd /media/cdrecorder auto noauto,ro,nosuid,nodev,exec 0 0 /dev/fd0 /media/floppy auto noauto,user 0 0
I keep hoping that with each new release "everything will just work" sigh !!
maybe you inherited the fstab from your older install.
I have tried every possible configuration I can think of and Yast is completely clueless on configuring these drives. I know that some of you have completely abandoned this automount/hal stuff and reverted to the "old" way of manually mounting. I would be tempted to do that if I knew how. Hope someone can help me solve this.
http://lists.suse.com/archive/suse-linux-e/2005-May/1879.html * Re: [SLE] automounting of Floppy 9.3 [solved: NOT automounting] Carlos E. R. (Fri May 13 2005 - 02:30:19 CEST) But first, try as above. Then, if you want fully manual mount, read that thread ;-) -- Cheers, Carlos Robinson
On Monday 06 March 2006 07:34, Carlos E. R. wrote:
The Monday 2006-03-06 at 02:11 -0500, Bob S wrote:
Ever since I did a new install of 10.0 (from 9.2) a few months ago I've had a problem with automounting data cd's dvd's. I've been able to work around it but is beginning to get annoying. Here is what happens:
I put in a data disk and wait for it to mount in media:/ I get this message:
Could not mount device. The reported error was: mount: according to mtab, /dev/hdc is already mounted on /media/dvdrecorder mount failed
But,it did mount evidently and then shows up in media:/ I can then see it and use it for my purpose.
It is double-mounting. Two "things" are trying to automount it.
Here is my fstab: (Sorry about the wrap)
Remove this two lines:
/dev/hdc /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/hdd /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
Hello Carlos, Thanks for replying. OK ... did that
This one too:
/dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0
OK.... did that also.
Use traditional lines, no subfs - because subfs is trying to automount, and hald is trying to automount also (so my crystal ball tells me ;-) ). For example:
/dev/hdc /media/dvdrecorder auto noauto,ro,nosuid,nodev,exec 0 0 /dev/hdd /media/cdrecorder auto noauto,ro,nosuid,nodev,exec 0 0 /dev/fd0 /media/floppy auto noauto,user 0 0
OK.... Cut and pasted those lines into my fstab. Same exact situation as before. Won't work. Now I get this message: Could not mount device. The reported error was: [mntent]: line 18 in /etc/fstab is bad [mntent]: line 19 in /etc/fstab is bad [mntent]: line 20 in /etc/fstab is bad mount: according to mtab, /dev/fd0 is already mounted on /media/floppy mount failed (those are the three lines I pasted into fstab)
I keep hoping that with each new release "everything will just work" sigh !!
maybe you inherited the fstab from your older install.
No, It was a new clean install.
I have tried every possible configuration I can think of and Yast is completely clueless on configuring these drives.
Here are some odd things that I have found: In Yast> Hardware> CD Roms, Yast posts two each of the devices. The NEC dvd device and the LiteOn cd device. They all show as non-configured. I edit them to show the mount point etc. and click "finish" Yast says OK. Reopen the dialogue and they are not configured. The settings do not stick. Now, when I look at /dev it shows 3 devices for each unit. For the cdrecorder it shows cdrom which is linked to /dev/hdc (incorrect - should be /dev/hdd) then cdrecorder, which is correctly linked to hdd, and cdrecorder2 which is linked to /dev/fd0 (really wrong) For the dvdrecorder it shows links from dvd and dvdrecorder to /dev/hdc which is correct. But it also shows a dvdrecorder2 which is linked to /dev/fdo ( again - wrong) cdrecorder 2 and dvdrecorder2 should not even be there. I can manually delete and edit these devices but at the next reboot they are all the same again. Additionally, /dev/hdc and /dev/hdd show me (bob) as the owner and the group as "disk". I can also manually edit those, giving ownership back to root, but again at the next reboot everything reverts to the original configuration.
I know that some of you have completely abandoned this automount/hal stuff and reverted to the "old" way of manually mounting. I would be tempted to do that if I knew how. Hope someone can help me solve this.
http://lists.suse.com/archive/suse-linux-e/2005-May/1879.html
* Re: [SLE] automounting of Floppy 9.3 [solved: NOT automounting] Carlos E. R. (Fri May 13 2005 - 02:30:19 CEST)
But first, try as above. Then, if you want fully manual mount, read that thread ;-)
I would really rather NOT do that, seeing problems "down the road" with upgrades and such. But this is really getting annoying and frustrating and I may just have to, to keep my sanity. Bob S. Ummmmm.....could this have anything to do with not loading some kernel modules?? I noticed a remark about that in my boot.message log.
-- Cheers, Carlos Robinson
On 07/03/06 00:39, Bob S wrote:
<snip>
Here are some odd things that I have found: In Yast> Hardware> CD Roms, Yast posts two each of the devices. The NEC dvd device and the LiteOn cd device. They all show as non-configured. I edit them to show the mount point etc. and click "finish" Yast says OK. Reopen the dialogue and they are not configured. The settings do not stick.
Now, when I look at /dev it shows 3 devices for each unit. For the cdrecorder it shows cdrom which is linked to /dev/hdc (incorrect - should be /dev/hdd) then cdrecorder, which is correctly linked to hdd, and cdrecorder2 which is linked to /dev/fd0 (really wrong)
Same thing happened here; the following isn't necessarily the only way to do it, but it worked for me. Delete all the CD devices in Yast/Hardware, and save; then delete all the soft links in /dev, eg /dev/cdrecorder --> /dev/hdc. It may be a good idea at this point to reboot. I think you can also safely delete (or comment out) the /etc/fstab entries prior to rebooting. On reboot, the devices should be autodetected for you to configure. If not, start Yast and configure them. Verify the links in /dev have been restored as they should be, and make any corrections necessary. When I carried out this procedure, I actually had to recreate all the links. You should also verify the fstab entries. I don't recall if I deleted those. Big PITA, really. A couple of times after a system crash, I had a similar spurious NIC show up -- had to delete the lot of them, reboot, and reconfigure. Fortunately, the rest of the system was left intact, so I was able simply to restart the network, and everything was properly restored. More big PITA.
On Tuesday 07 March 2006 03:09, Darryl Gregorash wrote:
On 07/03/06 00:39, Bob S wrote:
<snip>
Here are some odd things that I have found: In Yast> Hardware> CD Roms, Yast posts two each of the devices. The NEC dvd device and the LiteOn cd device. They all show as non-configured. I edit them to show the mount point etc. and click "finish" Yast says OK. Reopen the dialogue and they are not configured. The settings do not stick.
Now, when I look at /dev it shows 3 devices for each unit. For the cdrecorder it shows cdrom which is linked to /dev/hdc (incorrect - should be /dev/hdd) then cdrecorder, which is correctly linked to hdd, and cdrecorder2 which is linked to /dev/fd0 (really wrong)
Same thing happened here; the following isn't necessarily the only way to do it, but it worked for me.
Delete all the CD devices in Yast/Hardware, and save; then delete all the soft links in /dev, eg /dev/cdrecorder --> /dev/hdc. It may be a good idea at this point to reboot. I think you can also safely delete (or comment out) the /etc/fstab entries prior to rebooting.
On reboot, the devices should be autodetected for you to configure. If not, start Yast and configure them. Verify the links in /dev have been restored as they should be, and make any corrections necessary. When I carried out this procedure, I actually had to recreate all the links. You should also verify the fstab entries. I don't recall if I deleted those.
Big PITA, really. A couple of times after a system crash, I had a similar spurious NIC show up -- had to delete the lot of them, reboot, and reconfigure. Fortunately, the rest of the system was left intact, so I was able simply to restart the network, and everything was properly restored. More big PITA.
Thanks for replying Darryl, much appreciated. I have heard what you said. Maybe that is what I need to do. Tried several ways to delete the duplicate Nec dvdrecorder and the Lite-On cdrecorder but couldn't figure out how to do it. Question: You deleted /dev/cdrecorder. OK not a big deal, just a symlink. But you also deleted /dev/hdc ? That is a block device. Didn't you have to rebuild that? I've been trying to follow Carlos' advice. See my reply to him. Bob S.
On 08/03/06 03:30, Bob S wrote:
<snip> Question: You deleted /dev/cdrecorder. OK not a big deal, just a symlink. But you also deleted /dev/hdc ? That is a block device. Didn't you have to rebuild that?
EEK!! Umm, no -- sorry for the confusion. Just delete the all symlinks for the CDs, such as /dev/cdrecorder. You certainly have to leave the actual devices there.
I've been trying to follow Carlos' advice. See my reply to him.
Try moving that file to some safe place, then go through my procedure. That should be equivalent to a completely clean install, and hopefully will fully resolve the matter.
On Wednesday 08 March 2006 05:22, Darryl Gregorash wrote:
On 08/03/06 03:30, Bob S wrote:
<snip> Question: You deleted /dev/cdrecorder. OK not a big deal, just a symlink. But you also deleted /dev/hdc ? That is a block device. Didn't you have to rebuild that?
EEK!! Umm, no -- sorry for the confusion. Just delete the all symlinks for the CDs, such as /dev/cdrecorder. You certainly have to leave the actual devices there.
I've been trying to follow Carlos' advice. See my reply to him.
Try moving that file to some safe place, then go through my procedure. That should be equivalent to a completely clean install, and hopefully will fully resolve the matter.
OK, I started to do that. Problem is that I cannot delete/remove the cdrecorder and dvdrecorder (The physical devices) in Yast. Yast still shows two instances of both devices. How would I get rid of them? The Add/Remove functions only pertain to their configuration. Following Carlos' advice I can finally get the devices to mount when I insert the CD/DVD but something is still screwed up. Guess I can live with it but rather that it "worked properly". Bob S.
On 08/03/06 23:43, Bob S wrote:
On Wednesday 08 March 2006 05:22, Darryl Gregorash wrote:
On 08/03/06 03:30, Bob S wrote:
<snip> Question: You deleted /dev/cdrecorder. OK not a big deal, just a symlink. But you also deleted /dev/hdc ? That is a block device. Didn't you have to rebuild that?
EEK!! Umm, no -- sorry for the confusion. Just delete the all symlinks for the CDs, such as /dev/cdrecorder. You certainly have to leave the actual devices there.
I've been trying to follow Carlos' advice. See my reply to him.
Try moving that file to some safe place, then go through my procedure. That should be equivalent to a completely clean install, and hopefully will fully resolve the matter.
OK, I started to do that. Problem is that I cannot delete/remove the cdrecorder and dvdrecorder (The physical devices) in Yast. Yast still shows two instances of both devices. How would I get rid of them? The Add/Remove functions only pertain to their configuration.
Following Carlos' advice I can finally get the devices to mount when I insert the CD/DVD but something is still screwed up. Guess I can live with it but rather that it "worked properly". Carlos understands that stuff better than I do, so I can't give you any additional ideas on those lines. You might wish to boot into the rescue system (having first removed the device configurations) to edit or move
Yast will always find the drives, but the system won't do anything with them (or shouldn't) unless they're configured. Just removing the device configurations should suffice. that file. You might also try saving a current copy of /etc/fstab and deleting the relevant lines from that. This should give you a completely clean system when you boot normally, and reconfigure the drives in Yast. This silly problem is really beginning to bother me; today I taught myself 3 new words (the kind you'd never use in a letter to your Mom :) )
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-03-07 at 01:39 -0500, Bob S wrote:
Use traditional lines, no subfs - because subfs is trying to automount, and hald is trying to automount also (so my crystal ball tells me ;-) ). For example:
/dev/hdc /media/dvdrecorder auto noauto,ro,nosuid,nodev,exec 0 0 /dev/hdd /media/cdrecorder auto noauto,ro,nosuid,nodev,exec 0 0 /dev/fd0 /media/floppy auto noauto,user 0 0
OK.... Cut and pasted those lines into my fstab. Same exact situation as before. Won't work. Now I get this message:
Could not mount device. The reported error was: [mntent]: line 18 in /etc/fstab is bad [mntent]: line 19 in /etc/fstab is bad [mntent]: line 20 in /etc/fstab is bad mount: according to mtab, /dev/fd0 is already mounted on /media/floppy mount failed
(those are the three lines I pasted into fstab)
You have inserted extra chars somewhere. The line has to start with /dev... with no white space before, no extra symbols like ">". What I have is: /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 but first correct your symlinks (keep reaing).
Here are some odd things that I have found: In Yast> Hardware> CD Roms, Yast posts two each of the devices. The NEC dvd device and the LiteOn cd device. They all show as non-configured. I edit them to show the mount point etc. and click "finish" Yast says OK. Reopen the dialogue and they are not configured. The settings do not stick.
Could be because the links are wrong. You can try what Darryl said, or (see below)
Now, when I look at /dev it shows 3 devices for each unit. For the cdrecorder it shows cdrom which is linked to /dev/hdc (incorrect - should be /dev/hdd) then cdrecorder, which is correctly linked to hdd, and cdrecorder2 which is linked to /dev/fd0 (really wrong)
Ok, so you have wrong links. The place to modify the links manually in 9.3 and probably in 10.0 is in "/etc/udev/rules.d/20-cdrom.rules". Yast created these two lines for me: BUS="ide", ID="1.0", SYSFS{removable}="1", SYMLINK="dvdram cdrom " BUS="ide", ID="1.1", SYSFS{removable}="1", SYMLINK="dvd" whereas the correct lines for me are: BUS="ide", ID="1.0", SYSFS{removable}="1", SYMLINK="dvdrecorder dvdram dvd" BUS="ide", ID="1.1", SYSFS{removable}="1", SYMLINK="cdrecorder cdrom" If you don't do it there, the changes will not stick. The location may be slightly diferent in 10.0. Take the basis of the lines Yast created, then modify them to suit your situation.
Additionally, /dev/hdc and /dev/hdd show me (bob) as the owner and the group as "disk". I can also manually edit those, giving ownership back to root, but again at the next reboot everything reverts to the original configuration.
Yes, that is so. When you log in, you are given ownership of many devices. If you don't want that, you have to edit "/etc/logindevperm".
But first, try as above. Then, if you want fully manual mount, read that thread ;-)
I would really rather NOT do that, seeing problems "down the road" with upgrades and such.
I will tell you that some months down that road ;-)
But this is really getting annoying and frustrating and I may just have to, to keep my sanity.
I understand...
Ummmmm.....could this have anything to do with not loading some kernel modules?? I noticed a remark about that in my boot.message log.
I don't think so, but perhaps. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEDcxmtTMYHG2NR9URArOKAJ443ne8F4UrwD5geSUB6U2QXeJC5QCfQFUh mI3O/iymKWjzeqyzcf3Az98= =Uddq -----END PGP SIGNATURE-----
On Tuesday 07 March 2006 13:09, Carlos E. R. wrote:
The Tuesday 2006-03-07 at 01:39 -0500, Bob S wrote:
Use traditional lines, no subfs - because subfs is trying to automount, and hald is trying to automount also (so my crystal ball tells me ;-)
Hello Carlos, Back to the beginning. Aren't automount and hal the same thing? More or less? (sorry to interrupt. And you continue)
). For example:
/dev/hdc /media/dvdrecorder auto noauto,ro,nosuid,nodev,exec 0 0 /dev/hdd /media/cdrecorder auto noauto,ro,nosuid,nodev,exec 0 0 /dev/fd0 /media/floppy auto noauto,user 0 0
OK.... Cut and pasted those lines into my fstab. Same exact situation as before. Won't work. Now I get this message:
Could not mount device. The reported error was: [mntent]: line 18 in /etc/fstab is bad [mntent]: line 19 in /etc/fstab is bad [mntent]: line 20 in /etc/fstab is bad mount: according to mtab, /dev/fd0 is already mounted on /media/floppy mount failed
(those are the three lines I pasted into fstab)
You have inserted extra chars somewhere. The line has to start with /dev..with no white space before, no extra symbols like ">". What I have is:
/dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0
OK, but it is not a white space problem. I brought up the fstab and patiently tabbed through all of those lines with the "arrow" key. I note that as long as the line has the "subfs" in it I do not get the error message. If I change it to "auto" I do. I know that is crazy but I have gone back and forth with fstab and that is what happens.
but first correct your symlinks (keep reading).
OK, you too please.
Here are some odd things that I have found: In Yast> Hardware> CD Roms, Yast posts two each of the devices. The NEC dvd device and the LiteOn cd device. They all show as non-configured. I edit them to show the mount point etc. and click "finish" Yast says OK. Reopen the dialogue and they are not configured. The settings do not stick.
Could be because the links are wrong. You can try what Darryl said, or (see below)
Yes, that is correct. The links were wrong, as you point out below but I don't think that is the problem. I will explain. I have determined something though. As I stated when using Yast to configure the cdrecorder and the dvdrecorder the settings did not "stick" because the next time you opened it the mount points....did not appear. Yast does, however make the changes in fstab. (Even though they are incorrect until I changed the links)
Now, when I look at /dev it shows 3 devices for each unit. For the cdrecorder it shows cdrom which is linked to /dev/hdc (incorrect - should be /dev/hdd) then cdrecorder, which is correctly linked to hdd, and cdrecorder2 which is linked to /dev/fd0 (really wrong)
Ok, so you have wrong links. The place to modify the links manually in 9.3 and probably in 10.0 is in "/etc/udev/rules.d/20-cdrom.rules". Yast created these two lines for me:
Same location but called 55-cdrom.rules. Aieeeee !!!!! There are 64 lines in that file!!!! Mostly all the same, but included are the cdrecorder2 and dvdrecorder2. (Most likely created when I was in Yast and configured the duplicate and original devices, the NEC DVD recorder and the Lite-On cdrecorder. Sooooo...I took a deep breath and deleted everything but two lines for both the cdrecorder and the dvdrecorder which I edited, and then saved it. (I guess that file is created everytime you try to configure the cdrecorder/dvdrecorder with Yast) Rebooted and lo & behold the links in /dev were correct. And as you stated, your lines are:
BUS="ide", ID="1.0", SYSFS{removable}="1", SYMLINK="dvdram cdrom " BUS="ide", ID="1.1", SYSFS{removable}="1", SYMLINK="dvd"
whereas the correct lines for me are:
BUS="ide", ID="1.0", SYSFS{removable}="1", SYMLINK="dvdrecorder dvdram dvd" BUS="ide", ID="1.1", SYSFS{removable}="1", SYMLINK="cdrecorder cdrom"
My lines are significantly different from yours but I assume that is because you disabled hal/automount or whatever. Here are mine: (wrapped of course) SUBSYSTEM=="block", ENV{ID_PATH}=="pci-0000:00:0f.0-ide-1:0", SYSFS{removable}=="1", SYMLINK+="dvdrecorder dvd" SUBSYSTEM=="block", ENV{ID_PATH}=="pci-0000:00:0f.0-ide-1:1", SYSFS{removable}=="1", SYMLINK+="cdrecorder cdrom"
If you don't do it there, the changes will not stick. The location may be slightly diferent in 10.0. Take the basis of the lines Yast created, then modify them to suit your situation.
As above.... shown modified and correct. (I think)
But, the problem remains. If I leave the fstab entry as "subfs" I get the message that it can't mount because mtab already has it mounted. If I change it to "auto" I get the fstab message about the incorrect lines and it says it cannot mount it. It will mount though, but only on the dvdrecorder. The data disk will eventually show up in media:/ (My Computer) Or, in the real /media/dvdrecorder directory where I can open either manually and read it. Now, let's muddy the waters even further. (If it doesn't boggle your mind that is - It certainly boggles mine) The Floppy !!! (in relation to the cdrecorder and the dvdrecorder) First, It shows up in fstab in basically the same format as the cdrecorder and the dvdrecorder. It is shown in media:/ (My Computer) (God I hate that name) Yet the cdrecorder and the dvdrecorder do not. Hmmmm...They all appear to have the same format. Why is that one shows up and the others do not?? Here are the pertinent lines from my fstab which illustrate that: (Wrapped again, of course)(and separated by a blank line to see them more easily) /dev/fd0 /media/floppy auto noauto,user 0 0 none /subdomain subdomainfs noauto 0 0 /dev/dvdrecorder /media/dvdrecorder auto noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/cdrecorder /media/cdrecorder auto noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 (PS What is that "none thing anyway??) OK, that explained, let's go on to mtab. Normal operating mtab shows this about the floppy but nothing about cdrecorder and dvdrecorder: (Last few lines shown) usbfs /proc/bus/usb usbfs rw 0 0 /dev/fd0 /media/floppy subfs rw,nosuid,nodev,noatime,fs=floppyfss,procuid 0 0 (Note: that in fstab it shows it as "auto" and in mtab it shows it as "subfs" and the attributes are quite different. (See above fstab) OK, so the floppy is always there. Why aren't cdrecorder and dvdrecorder there also when they belong to the same subset of mountable devices? I can watch mtab as I put a data dvd into the dvdrecorder and see it appear in mtab (with a reload of the file, of course) and I can see it unload when I take the data dvd out. I can see the contents of the floppy when I go to /media/floppy and open it. (although I cannot do it from media:/ (My Computer) because it tells me it is altready mounted in mtab) I can do the same for the data dvd (after it mounts) by going to /media/dvdrecorder and opening it or as opposed to or different from the floppy by going to media:/ (My Computer) when it brings up the mounted directory. None of this makes any sense to me. They should all behave in a similar manner. I am not a trained programmer or even a system administrator, but I am a very experienced logical person. None of this is logical to me unless this behavior can be explained. I really suspect that many others may have this same problem but are either "living with it", "getting around it", or "ignoring it" Sorry if I got into a little bit of a "rant". Didn't mean to. (and this is not directed at you Carlos, or anyone else in particular) Just very frustrating that at this point in development this stuff should "just work properly". Guess we have a long ways to go yet. Bob S.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-03-08 at 04:18 -0500, Bob S wrote:
On Tuesday 07 March 2006 13:09, Carlos E. R. wrote:
The Tuesday 2006-03-07 at 01:39 -0500, Bob S wrote:
Use traditional lines, no subfs - because subfs is trying to automount, and hald is trying to automount also (so my crystal ball tells me ;-)
Hello Carlos, Back to the beginning. Aren't automount and hal the same thing? More or less? (sorry to interrupt. And you continue)
No, not really. I'm using the word "automount" to refer to anything that automatically mounts disks. Both hal and subfs can automount, but hal is more than that.
/dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0
OK, but it is not a white space problem. I brought up the fstab and patiently tabbed through all of those lines with the "arrow" key. I note that as long as the line has the "subfs" in it I do not get the error message. If I change it to "auto" I do. I know that is crazy but I have gone back and forth with fstab and that is what happens.
The problem is that you left this (I'm jumping down text to the point where I found out): /dev/dvdrecorder /media/dvdrecorder auto noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 Simply replacing "subfs" wit "noauto" does not work, and gives incorrect syntax. Use this instead: /dev/dvdrecorder /media/dvdrecorder auto noauto,ro,user 0 0 Nothing more is necessary. Later add things if you need (exec,noexec, etc).
Ok, so you have wrong links. The place to modify the links manually in 9.3 and probably in 10.0 is in "/etc/udev/rules.d/20-cdrom.rules". Yast created these two lines for me:
Same location but called 55-cdrom.rules.
Yeap, that must be version 10. And 10.1 will change again, I think.
Aieeeee !!!!! There are 64 lines in that file!!!!
¡Argh! :-/
Rebooted and lo & behold the links in /dev were correct.
Good!
And as you stated, your lines are:
BUS="ide", ID="1.0", SYSFS{removable}="1", SYMLINK="dvdram cdrom " BUS="ide", ID="1.1", SYSFS{removable}="1", SYMLINK="dvd"
whereas the correct lines for me are:
BUS="ide", ID="1.0", SYSFS{removable}="1", SYMLINK="dvdrecorder dvdram dvd" BUS="ide", ID="1.1", SYSFS{removable}="1", SYMLINK="cdrecorder cdrom"
My lines are significantly different from yours but I assume that is because you disabled hal/automount or whatever. Here are mine: (wrapped of course)
No, it is because SuSE 10 changed things. I didn't disable hal, that's not advisable. I just stopped hal from auto-mounting my disks.
none /subdomain subdomainfs noauto 0 0
(PS What is that "none thing anyway??)
That particular one, I dunno. Leave it alone :-) cer@nimrodel:~> apropos subdomainfs subdomainfs: nothing appropriate. And nothing in the wikipedia.
OK, that explained, let's go on to mtab. Normal operating mtab shows this about the floppy but nothing about cdrecorder and dvdrecorder: (Last few lines shown)
usbfs /proc/bus/usb usbfs rw 0 0 /dev/fd0 /media/floppy subfs rw,nosuid,nodev,noatime,fs=floppyfss,procuid 0 0
(Note: that in fstab it shows it as "auto" and in mtab it shows it as "subfs" and the attributes are quite different. (See above fstab)
mtab shows what is mounted "now". fstab gives "hints" on how they should be mounted, but programs (and users) are not forced to use it. The same thing about subfs applies to the floppy. You can use this for manual mounting: /dev/fd0 /media/floppy auto noauto,user 0 0 This means that "subfs" will not try to mount it, but hal will. We must not have to competing services trying to automount. I don't understand why Yast left "subfs" there. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEDr2KtTMYHG2NR9URAlTfAJ4u+DjYFhTrQwwEKd3zZsKiIaHM8wCePy/p FlRldRDlo/DUYjGoShxX2h4= =WVbg -----END PGP SIGNATURE-----
On Wednesday 08 March 2006 06:18, Carlos E. R. wrote:
The Wednesday 2006-03-08 at 04:18 -0500, Bob S wrote:
On Tuesday 07 March 2006 13:09, Carlos E. R. wrote:
OK, but it is not a white space problem. I brought up the fstab and patiently tabbed through all of those lines with the "arrow" key. I note that as long as the line has the "subfs" in it I do not get the error message. If I change it to "auto" I do. I know that is crazy but I have gone back and forth with fstab and that is what happens.
The problem is that you left this (I'm jumping down text to the point where I found out):
/dev/dvdrecorder /media/dvdrecorder auto noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
Simply replacing "subfs" with "noauto" does not work, and gives incorrect syntax. Use this instead:
/dev/dvdrecorder /media/dvdrecorder auto noauto,ro,user 0 0
Nothing more is necessary. Later add things if you need (exec,noexec, etc).
OK, before we go any further, after having modified the file to what you suggested above, I can now mount the data CD/DVD's. The little KDE daemon thing comes up and I can choose to open it or whatever. Great! (I still get the error message in boot message about the bad lines in fstab). Whatever, at least it works. Now, back to a few days ago. (Just for my sanity and understanding)
The scenario: In fstab /dev/fd0, /dev/cdrecorder, and /dev/dvdrecorder are all identical. (except for the device designation of course) Now, nothing should be mounted (there is no media in any of the drives) If I look in media:/ (My Computer) it shows an unmounted floppy. No unmounted dvdrecorder or cdrecorder. OK ??? Why ?? Now I look in mtab (same conditions existing) It shows the floppy as being mounted. (Still no media inserted) and no mention of cdrecorder or dvdrecorder. Why ?? If I then put media in cdrecorder or dvdrecorder it mounts and I see it come up in mtab and appears similar to the floppy. Why ??? don't these devices act the same ?? Oh well.....If you tire of this and/or cannot help me understand this strange behavior I will certainly understand. I remember that in your last post you explained to me:
mtab shows what is mounted "now". fstab gives "hints" on how they should be mounted, but programs (and users) are not forced to use it.
Well....fstab is more than that, isn't it? That determines stuff from the boot process, or otherwise it wouldn't work, right?
The same thing about subfs applies to the floppy. You can use this for manual mounting:
/dev/fd0 /media/floppy auto noauto,user 0 0
That is exactly what my fstab entry shows. So what is the strange behavior that I have described above?
This means that "subfs" will not try to mount it, but hal will. We must not have to competing services trying to automount. I don't understand why Yast left "subfs" there.
I understand what you have said but I don't understand the behavior either. Yast may need a little more refinement. Oh well......Thanks a million for helping Carlos. You are a regular contributor to this list for many years now and many of us have benefitted from your knowledge and participation. We all thank you for that. Bob S
/dev/dvdrecorder /media/dvdrecorder auto noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
OK! I am no expert, but looking at the above does point out a simple config
On Thursday 09 March 2006 09:09, Bob S wrote: <snipped> problem.. Here is my line for the cd-recorder/dvd rom combo from fstab: /dev/cdrecorder /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid, nosuid,nodev,exec,iocharset=utf8 0 0 Hope this helps Chadley
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-03-09 at 02:09 -0500, Bob S wrote:
(I still get the error message in boot message about the bad lines in fstab). Whatever, at least it works.
It will fail when you try to mount manually whatever is in that wrong line ;-) ... ...
Why ??? don't these devices act the same ??
The floppy behaves somewhat differently, because the kernel or whatever is trying continuously to check whether there is a floppy inside. I think I recollect reading somewhere that cdrom drives will tell the kernel when they have got a new disk inside, or when the door closes. But the floppy drive design is very old (ibm pc original, cheapest hardware possible, more cpu work), it doesn't have any intelligence at all: the system has to interrogate it for changes and everything, in fact. If you check the kernel log, you will see now and then entries when the kernel tries the floppy drive and fails. The other side effect is that it can show as mounted even when empty. The only way to avoid this is to manipulate "hal" so that the floppy is not automounted.
Oh well......Thanks a million for helping Carlos. You are a regular contributor to this list for many years now and many of us have benefitted from your knowledge and participation. We all thank you for that.
Thanks :-) - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEEEdttTMYHG2NR9URAilkAJwPa/xLToIml+HzX1fimzv8uC27NwCdHUhU eeo5Qjnfa5GHlz0KRK/gVRM= =F2Og -----END PGP SIGNATURE-----
On Wed, 2006-03-08 at 04:18 -0500, Bob S wrote:
OK, that explained, let's go on to mtab. Normal operating mtab shows this about the floppy but nothing about cdrecorder and dvdrecorder: (Last few lines shown)
fstab should show what can be mounted and -how- to mount it. mtab should show what -is- mounted and how it -was- mounted. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
participants (5)
-
Bob S -
Carlos E. R. -
Chadley Wilson -
Darryl Gregorash -
Ken Schneider