Eject disk error

Every time when i eject some disk from DVD drive i get errors about unmounting volume…bla bla bla. It’s some kind of a bug? Because in Ubuntu it was not there…

It’s possible to somehow turn this silly message off? Please don’t tell me that i or my family members must allways right-click and set Unmount/Eject disk…

ImageShack - Hosting :: obrazovkaaa0.png

It would be nice if somebody could find a fix for this…

It would also be nice if you would post your /etc/fstab and to let us know what version of linux you’re using.

You always have to unmount devices before removing them, only this is now an automated process unless your FSTAB in configured not to mount and unmount automatically.

If you remove a usb disk or stick like that you will start loosing data.

Post your fstab and we’ll see.

Here’s my fstab :slight_smile:

/dev/disk/by-id/scsi-SATA_ST3500630AS_9QG1GXQJ-part5 swap                 swap       defaults              0 0
/dev/disk/by-id/scsi-SATA_ST3500630AS_9QG1GXQJ-part6 /                    ext3       acl,user_xattr        1 1
/dev/disk/by-id/scsi-SATA_ST3500630AS_9QG1GXQJ-part7 /home                ext3       acl,user_xattr        1 2
/dev/disk/by-id/scsi-SATA_ST3500630AS_9QG1GXQJ-part2 /windows/C           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_GB.UTF-8 0 0
/dev/disk/by-id/scsi-SATA_SAMSUNG_HD501LJS0MUJ1FP976637-part1 /windows/D           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_GB.UTF-8 0 0
/dev/disk/by-id/scsi-SATA_WDC_WD1600AAJS-_WD-WCAP93439563-part1 /windows/E           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_GB.UTF-8 0 0
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0

How did you mount the disc ?
Just put it in the drive and opened it or did you do something else before ?

Just put it in the drive and opened it :slight_smile:
I got this error on my both PC’s :confused:

The error seems to be related to those using GNOME (2.22) & openSUSE 11.0. At first sight it seems to be a bug in the media automount/dismount sequence.

@rozbarwinek (and others here) : It might speed up things if you open a bug report for this - or join an existing one, like https://bugzilla.novell.com/show_bug.cgi?id=406528

There is not enough feedback for the devs to do anything with it, so adding your input would be worth much!

Cheers,
Wj

ok, I have voted (5) :smiley:

Same fun here :wink:
When I “eject” the tray opens, but within a second, it closes… trying to take my finger with it…
So I have learned to wait and ‘eject again’ this time the tray will sty open… :smiley:

PC’s are just like houses, cars & people. Each has its own peticularities…
Examples: no-one can ever start my car during winter, yet I get it going first time, that tap upstairs ? push while turing… wife #3 ? never ever tell her that she has a big a** … like that :slight_smile:
Just autopilot, you live longer that way !

Cinq-Marquis wrote:

> Same fun here :wink:
> When I “eject” the tray opens, but within a second, it closes…
> trying to take my finger with it…
> So I have learned to wait and ‘eject again’ this time the tray will sty
> open… :smiley:

The tray behaving like Arkwright’s till (grand old TV series “Open All
Hours” in UK) has been around for a while - 10.3 at the latest. I usually
managed to avoid it by selecting “eject” from the desktop CD/DVD icon.

I’ve had the error messages in 11.0 reported by the OP but they’ve now
vanished. Disappearance may have coincided with switching from 64-bit to
32.


Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy

I cannot eject a CD/DVD in Suse 11.0 as a normal user. I have to drop to command line, su root, and umount manually.

I have this problem on two different installations. Suse 11.0/KDE 4.0

Seems to be a ‘rights’ problem. What has changed since 10.3?

So… did anyone found a solution for this? :slight_smile: