Fixes for 'cd/dvd mounting problem' in Mepis repo

[ko]

Hi,

The long awaited fixes (for 32bit and for 64bit) for the 'cd/dvd mounting problem' have been released in the Mepis repo. Consists of two updated Mepis .deb packages:

Mepis-auto-6.0 version 6.5
Mepis-init-6.0 version 6.5

(note: I could only find mepis-init for 32bit, but that may be caused by the fact that I already had it installed yesterday........)

These fixes work best on a "non-fixed' static portion of /etc/fstab.
Meaning please remove any cd/dvd-drive related lines that you (may) have copied there.

....and please reboot after updating to notice changes!

Excerpts from Warrens emails:
======================

It should work as follows:

Early during boot, the kernel and udev should detect each cdrom drive that is
present. None should be "lost." At the end of the udev actions, the cdrom
symbolic links should exist in /dev but I no longer create the dvd, cdrw, etc
symbolic links. They served no official purpose. At this point the created
links may be in a random order.

Later in boot when mepis-init runs, it will sort the cdrom links to the
traditional order, that is cdrom->hdc, cdrom1->hdd, or whatever.

Subsequently adding and removing plugable cdrom devices should work normally, that is they should be added as the next available device and with a symbolic cdrom link but not with an automatic fstab entry.

If you have two drives and you want a desktop icon for the second drive, you
will have to create it manually. Or you could try to have kde media
notification create the desktop entries, but that only works with some
hardware.

If your drives were detected during boot, they should have fstab entries,
therefore you should be able to use them via kwikdisk.

Install mepis-init and mepis-auto.
If they ask if a file should be updated, allow the update.
Then reboot and look at your fstab file.
In all cases it should contain a line that says
"# Dynamic entries below, identified by 'users' option"

Static/permanant fstab entries should be above this line and dynamic/automatic entries should appear below this line.

If any dynamic entries are above the line, erase them and reboot. For proper
operation, cd and fd entries should be below the line.

This is probably a problem for any machine where MEPIS was installed to use
the entire disk. This probably fixes a lot of old bug reports.

Warren.
===================

Regards, Ko

[Saist]

It has worked on the Gateway and the Mutt system that I posted about on Mepis.org

http://www.mepis.org/node/13416

I haven't restarted my dual drive system yet, so I don't know if it has worked there.

[mcrofutt]

Yipppppeeeeeeeeeeeeeeee!!!!!!
Works 100% on my box! I added an icon to point to /dev/cdrom1 and presto! Eject and everything works! THANKS Warren!
Mark

[Roadblock]

FAN-DANG-TASTIC!!! I had gotten so used to adding those entries, it had become Mepis-install second nature to me.

Kudos to Warren and the team.

[soundtech]

This is great news, because the cdrom issue has been a pain, especially when running virtual machines.

I just did the updates.
Synaptic reported that all went well, but when I closed the terminal window, there was an error message waiting for me:

E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

Is this anything to be concerned about?

Also, fstab now has double entries for my two devices - e.g one as /dev/cdrom, and one as /dev/hdc.
Is this the way it is supposed to be?

My fstab:

# Pluggable devices are handled by uDev, they are not in fstab
/dev/hda2 / ext3 defaults,noatime 1 1
none /proc proc defaults 0 0
none /proc/bus/usb usbfs devmode=0666 0 0
none /dev/pts devpts mode=0622 0 0
none /sys sysfs defaults 0 0
/dev/hda4 /home auto defaults,noatime 1 2
# Dynamic entries below
/dev/hda1 /mnt/hda1 ext3 noauto,users,exec 0 0
/dev/hda3 swap swap sw,pri=1 0 0
/dev/sda1 /mnt/sda1 ext2 noauto,users,exec 0 0
/dev/cdrom /media/cdrom udf,iso9660 noauto,users,exec,ro 0 0
/dev/hdc /media/cdrom udf,iso9660 noauto,users,exec,ro 0 0
/dev/cdrom1 /media/cdrom1 udf,iso9660 noauto,users,exec,ro 0 0
/dev/hdd /media/cdrom1 udf,iso9660 noauto,users,exec,ro 0 0
/dev/fd0 /media/floppy vfat,ext2 noauto,users,exec,rw 0 0


Thanks.

[carlops]

yes, it should be like that. Some apps use the hdx nomenclature, others the cdrom.

Hope it works OK for you now.

[nlyric]

Mepis6.5 64
I need some input here. I upgraded Mepis-auto-6.0 version 6.5 and Mepis-init-6.0 version 6.5. I have 2 drives. Doing so seems to have caused some problems. I first noticed it after the upgrade. When I go into system "settings" anything I click on presents me with a warning "KDEinit could not launch *". I close the warning and whatever I clicked on launces anyway. I also have 2 entries for each device in fstab and I may be wrong on this but it doesn't look right to me.
# Dynamic entries below
/dev/sda1 /mnt/sda1 ntfs-3g noauto,users 0 0
/dev/sda3 /mnt/sda3 vfat,ext3,ext2,reiserfs noauto,users,exec 0 0
/dev/sda6 /mnt/sda6 ext3 noauto,users,exec 0 0
/dev/sda7 swap swap sw,pri=1 0 0
/dev/cdrom /media/cdrom udf,iso9660 noauto,users,exec,ro 0 0
/dev/hda /media/cdrom udf,iso9660 noauto,users,exec,ro 0 0
/dev/cdrom1 /media/cdrom1 udf,iso9660 noauto,users,exec,ro 0 0
/dev/hdb /media/cdrom1 udf,iso9660 noauto,users,exec,ro 0 0
/dev/fd0 /media/floppy vfat,ext2 noauto,users,exec,rw 0 0
I noticed this last night. Tonight when I booted settings would not even start and konqueror wouldn't either. I rebooted and settings and konqueror opened but still had the same issue in settings with the KDEinit
I am not 100% the upgrade caused this issue. But it seems that way.
Thoughts ?????

[nlyric]

I saw your post carlops fstab is good then. I just logged in as root and don't have these issues so maybe I am wrong about what caused this. No other changes though.
Edit created another user and no problems. Then I used kcontrol to access the same apps and no KDEinit error message, Very strange issue. Only seems to be a problem with konqueror --profile mepissettings settings:/ with one user (me). involking any of the commands (example> mxconfig)from anywhere except settings:/ does not produce the error message.

[dekalbave]

Whew... finally! Had to make a Create New->Link To Device->DVD-ROM and choose /dev/cdrom1 from the drop-down menu to get the right desktop icon for my second optical drive, a DVDRW.

But at least now when I insert a music CD into this drive, an "Audio CD" icon pops up consistently. Even though under properties, it says the mount point is media:/hdb. What the....? However, bottom line, both drives actually work. Hooray!

[lucky9]

No problems here with the upgrade and my 64bit install.