Hi all, I have a 500Gb Maxtor external USB HD. It has 2 FAT32 partitions.
I was experiencing the same problem and I tried the suggested workaround:
sudo mv /usr/share/hal/fdi/policy/10osvendor/10-storage-policy.fdi
/usr/share/hal/fdi/policy/10osvendor/10-storage-policy.fdi.orig
My question now
This has been fixed a while ago. I suppose to close this in order to
reduce the amount of open issues.
I do this for this incident (#63090). If anyone objects, please reopen.
Thanks,
Wolf
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug
This was fixed a while ago. Why carry it with us?
** Changed in: hal (Ubuntu Feisty)
Status: Confirmed = Fix Released
** Changed in: gnome-volume-manager (Ubuntu Feisty)
Assignee: (unassigned) = Wolf Rogner (war-rsb)
Status: New = Fix Released
** Changed in:
I don't know if hal in feisty backports is solving; I'm not /don't want to use
backports (stability reason on professional laptop).
In feisty (official ports) fully updated, this is not solved (see attachement)
** Attachment added: Capture-gnome-umount.png
It's a shame that eject has gone in Gutsy. I have keys with multiple
partitions and using eject meant I knew the key could be pulled out
because all partitions had been unmounted.
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification
Sitsofe,
If I may quote my comment on bug #36252,
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/36252/comments/40
, perhaps if my suggestion (last part) was implemented, it would solve
your problem?
[quote]
How Kubuntu does it:
I ejected (allthough it's called 'safely unmount' in
Confirming, the feisty-backports package solves the problem by
suggesting to unmount a partition instead of ejecting the whole drive.
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which
This has been fixed a while ago in version 0.5.9-1ubuntu1 in gutsy.
This version is in feisty-backports, too, so feel free to install this
on feisty if it causes problems for you in feisty.
** Changed in: hal (Ubuntu)
Status: Confirmed = Fix Released
--
do not eject all USB/Firewire
Adding Feisty task since the demand for fixing this in Feisty is quite
high. However, we have ejected all devices since Hoary. It is not such a
big problem, after all, and is more convenient if your hard disk has
several partitions. With eject, all of them are unmounted at the same
time, so that
I believe eject is the expected functionality of an external USB drive.
The solution should be to make eject work well with all USB hard drives,
and to make gnome-volume-manager aware of ejects, instead of disabling
eject.
Based on the observation that eject works well with those Cyrpress-based
the feisty-backports package of hal correct this bug
but with a MacBook2 Feisty64 after upgrading hal
the gnome-power-manager and key F1 F2 for light don't works
Under MacBook it's better change /usr/share/hal/fdi/policy/10osvendor/10
-storage-policy.fdi
--
do not eject all USB/Firewire
Linux hb 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686
GNU/Linux
On my machine the problem is solved. I can unmount devices (USB, ext.
IDE) no problem.
Wolf
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you
This is still an issue, and there are numerous bug reports and
complaints in the forums. This is a pretty major bug, and yes it is a
regression. It has been 8 months with still no fix in place.
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug
Bug is solved upstream. So wait for a backport of hal
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
After installing the hal update (0.5.9-1ubuntu2~feisty1) released
several days ago, eject becomes unmount on the context menu for USB hard
drives. I think It is a workaround for this problem, but it's not a nice
solution.
--
do not eject all USB/Firewire devices
Is it possible that part of the problem is because the value in
/sys/block/sdb/removable is 0 not 1?
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I've also got the same prob when I've upgrade to Feisty
Some work around with nautilus-scripts.
$ gedit .gnome2/nautilus-scripts/Eject
-Paste
for uri in $NAUTILUS_SCRIPT_SELECTED_URIS; do
device=`echo $uri | sed 's/file:\/\///g'`
Just for the record: among the three external hard drives I have access
to, feisty can eject two Cypress CY7C68300C-56PVXC based external hard
drives smoothly; it cannot eject the one based on Initio INIC-1530L.
Perhaps it is a bug in the usb_storage driver?
I hope the problem will be fixed soon.
This is *very* probably a HAL bug, if you can mount/unmont the thing, it
means the kernel driver and udev is working properly, as the device node
is created. Can you please try with the above (
https://bugs.launchpad.net/ubuntu/+source/gnome-volume-
manager/+bug/63090/comments/33 ) workaround?
--
J wrote:
This is *very* probably a HAL bug, if you can mount/unmont the thing, it
means the kernel driver and udev is working properly, as the device node
is created. Can you please try with the above (
https://bugs.launchpad.net/ubuntu/+source/gnome-volume-
manager/+bug/63090/comments/33 )
Please, if you want to shout, do it in a forum. A bug report is meant to
be just that: a report. Comments should be adding new information or
discussing a fix. It bites me too, but please relax and let the
developers do their job. It's far easier for them if they don't have to
filter the comments
dmesg output when inserting and ejecting an USB external harddrive. It
is a Zynet Monster 3 IN 1 Data Center, which is a USB 2.0 Hub + Flash
Card Readers + USB hard drive combo. The USB/Firewire - IDE adapter
included in this device is produced by Initio. Ejecting the external
hard drive used to
** Attachment added: lsusb output of Zynet Monster 3 IN 1 Data Center
http://librarian.launchpad.net/7411094/lsusb.log
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Feisty can eject this external hard drive well.
** Attachment added: lsusb output of Zynet HD-D13-U2 hard drive enclosure
http://librarian.launchpad.net/743/Zynet-HD-D13-U2.lsusb.log
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug
Okay, I found some working policy files in the opensuse HAL package, I'm
not sure how clean this is, or whether it'll blow up something (I'd
think not as they use the same version of HAL), so here are the files,
if someone's brave enough to test them, please do, check ubuntuforums
post
** Attachment added: fdi file from opensuse HAL package
http://librarian.launchpad.net/7411242/99-storage-policy-fixed-drives.fdi
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which
I guess the 99-storage-policy-fixed-drives.fdi policy file is not
needed.
** Attachment removed: fdi file from opensuse HAL package
http://librarian.launchpad.net/7411242/99-storage-policy-fixed-
drives.fdi
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You
I agree that this is an extremely serious bug, which should be fixed as
soon as possible. Ubuntu is supposed to be the user-friendly Linux
dist, right? Well, one of the most common things the average user does
is attach external USB devices (ie. pen drives and hard drives). If a
user gets an
Whoops- I should add that I DO use Ubuntu and have for some time, and in
general I love it. :-) But this bug definitely feels like regression
to me.
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of
I wonder if a shout to someone would do, or where could one drop it?
ubuntu forums? something?
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I think the problem is that the fix is a deeper one and this wouldn't
fit with the freeze version. But I think that's what we have the rep
feisty-updates for. Btw Kubuntu had a similar problem in Dapper or
Breezy, don't know anymore, but they had fixed it after release.
--
do not eject all
I think this is a major bug that should've been eliminated right away, this is
plain amazing, people not being able to unmount their external usb hdds is a
very important bug!
Some people are saying this worked a few weeks ago, why not just roll back this
even using the /usr/share/hal/fdi/policy/10osvendor/10-storage-
policy.fdi file from the edgy version of hal helps, although it does
print out errors about not being able to eject the medium, it does
unmount it after all.
--
do not eject all USB/Firewire devices
** Changed in: hal (Ubuntu)
Status: Unconfirmed = Confirmed
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
@Sander50: What workaround??
@pitti: In general I think it *doesn't* work fine to eject all usb
devices - especially external USB hard drives - flash drives seem to
work okay - except they can't be remounted afterwards and need to be
physically removed and reinserted first - but I have an
I disagree that it is a regression that is critical for Feisty; after
all, we have ejected all removable devices since Breezy or so. However,
I do acknowledge that it causes trouble, so I'll fix it in Gutsy.
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You
But it seems like this (not being able to eject devices using nautilus /
drive-mount applet) is definitely a new problem - at least for me I
never had problems like this before, and thus this a regression for me -
has anything else changed such as the method used to eject the devices
which could
I don't understand why this is delayed so long, 6 months is a pretty
long time imho, and this would be a usability enhancement, which would I
think ease the transision from other OSes for people. This just mixes
people up, can I or can I not remove my hdd, because they can't check in
syslog if the
Interestingly, while I can't eject my external usb harddrive, I can
still eject my usb thumb drive, so I have attached the output from
DebuggingRemovableDevices from the wiki with first the usb flash (thumb)
drive which can be correctly ejected, and then the external usb
harddrive which can't be
udev.log with thumb drive
** Attachment added: udev.log with thumb drive
http://librarian.launchpad.net/7336300/udev.log
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: lshal with thumb drive
http://librarian.launchpad.net/7336301/lshal.txt
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
dmesg with thumb drive - note before running these debugging steps I had
previously inserted and ejected the drives a couple times so only the
last bit is probably relevant
** Attachment added: dmesg with thumb drive
http://librarian.launchpad.net/7336304/dmesg.txt
--
do not eject all
devices.txt listing sd* devices in /dev
** Attachment added: devices.txt
http://librarian.launchpad.net/7336305/devices.txt
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
other outputs requested - ie id etc
[EMAIL PROTECTED]:~$ id
uid=1000(alex) gid=1000(alex)
groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),110(netdev),111(lpadmin),113(powerdev),114(scanner),116(admin),1000(alex)
[EMAIL PROTECTED]:~$ id hal
id: hal: No such
Now is attached the same but when the external usb harddrive is attached
- I also tried ejecting it so the output in gvm from trying to do that
is there too
** Attachment added: gvm.log with external usb harddrive
http://librarian.launchpad.net/7336311/gvm.log
--
do not eject all
** Attachment added: lshal with external usb harddrive
http://librarian.launchpad.net/7336312/lshal.txt
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
dmesg output for external usb harddrive which cannot be ejected - Since
I did this after the thumbdrive stuff above it also includes that as
well...
** Attachment added: dmesg with external usb harddrive
http://librarian.launchpad.net/7336317/dmesg.txt
--
do not eject all USB/Firewire
ls of /dev/sd* with external usb harddrive connected
** Attachment added: devices.txt
http://librarian.launchpad.net/7336319/devices.txt
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs,
Martin:
Your workaround works for me! Thanks.
I hope an update will be released soon.
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
49 matches
Mail list logo
