** Changed in: gnome-vfs
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/139748
Title:
poor handling of eSATA drives
To manage notifications about this bug go to:
ht
** Changed in: gnome-vfs
Importance: Unknown => Low
--
poor handling of eSATA drives
https://bugs.launchpad.net/bugs/139748
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Changed in: gnome-vfs
Status: Unknown => New
--
poor handling of eSATA drives
https://bugs.launchpad.net/bugs/139748
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Great, thanks for the quick response, gnome-vfs issue then reassigning.
thanks again.
** Changed in: gnome-vfs2 (Ubuntu)
Sourcepackagename: gnome-volume-manager => gnome-vfs2
Importance: Undecided => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: Incomplete
Definitely. The proposed "solution" would be ideal IMO.
On Jan 4, 2008 1:30 PM, Pedro Villavicencio <[EMAIL PROTECTED]> wrote:
> Thanks for you report, isn't this related to:
> http://bugzilla.gnome.org/show_bug.cgi?id=430024 ?
>
> ** Changed in: gnome-volume-manager (Ubuntu)
> Status: New
Thanks for you report, isn't this related to:
http://bugzilla.gnome.org/show_bug.cgi?id=430024 ?
** Changed in: gnome-volume-manager (Ubuntu)
Status: New => Incomplete
--
poor handling of eSATA drives
https://bugs.launchpad.net/bugs/139748
You received this bug notification because you ar
this problem still exists in gutsy
the worst thing is, that i cannot unplug my eSATA HD safely. if i umount the
partition and unplug it, the system hangs for about one minute and there are
various error messages in dmesg:
Dec 31 03:52:39 x2 kernel: [34550.804000] ata2: timeout waiting for ADMA ID
i found a workaround: the device can be removed using the sysfs:
source: "SCSI - Hot add, remove, rescan of SCSI devices"
http://www-941.ibm.com/collaboration/wiki/pages/viewpage.action?pageId=3625
in short:
1. umount all partitions from the device
2. find the right SCSI ID with "cat /proc/scsi/s
I have similar (but worse) experience:
I use feisty on a laptop, I have a Samsung Sata2 drive formatted as ext3 in an
external usb/esata box. When connected via usb there are no problems. When
connected as esata via Delock Express Card the following happens:
When hotplugging it is not detected at
I can confirm this on 7.04 and 7.10beta (for scenario 2). My drive is in
a SATA caddy (SATA2 controller/AHCI). When pluuged, the event shows up
in hal (using 'lshal -m'), but it seems that gnome-volume-manager simply
ignores it. The drive is listed in fstab (based on UID) and if I type in
"mount /m
10 matches
Mail list logo
