Sure, I made a mistake with the tarball, here it is.
Device: jmicron:/dev/sdb
ize: 953869 MiB
Model: [WDC WD10EAVS-00D7B0]
Serial: [WD-WCAU42028877]
Firmware: [01.01A01]
SMART Available: yes
Quirks:
Awake: No such device
SMART Disk Health Good: No such device
Failed to dump disk data: No such devi
I forwarded your comments upstream. For those of you who want to bypass
me as a bug data relay and talk to upstream directly, please feel free
to post/subscribe directly to
https://bugzilla.redhat.com/show_bug.cgi?id=515881 .
** Changed in: libatasmart (Ubuntu)
Status: Incomplete => Confirm
@Scott Zawalski:
> I wasn't able to get the skdump jmicron output
You should be able to do that right after pluggin in the drive. After an
skdump invocation you need to unplug/replug the drive to reinitialize
it.
@Wesley: Can you please also provide the skdump outputs, as described in
comment 42?
Removing the udev file helps, I'm able to use the disk, when either
skdump command is run the resets happen and i need to reconnect the
drives.
I've also noticed, but maybe unrelated, that the device notifier of KDE sees:
* Both partition on my disk (FAT/ext3)
* Only FAT partition
* Only ext3 pa
I reported a duplicate bug: https://bugs.launchpad.net/ubuntu/+source
/linux-meta/+bug/417508
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Even with the rules removed I still need to be quick to do the skdump outputs
because my drive still gives the error -71
I wasn't able to get the skdump jmicron output but for sudo skdump /dev/sdf
Device: jmicron:/dev/sdf
Type: JMicron SCSI ATA Passthru
Size: 715404 MiB
Model: [ST3750640NS]
Seri
I have the same problem here.
After renaming the udev rules file the disk will show up.
If I then rename the udev file to its old name and invoke one of the skdump
commands the disk is unmounted.
The attached file contains both trace dumps and the output of the udevadm
command together with some
Stefan Ebner [2009-08-25 11:24 -]:
> a) sudo skdump /dev/sdb ejects the harddrive and tells me: Failed to open
> disk /dev/sdb: Invalid argument
Hm, it seems you have a very different problem than other people, the
symtoms are so much different. Can you please open a new bug against
libatasm
Ok, moving away the rules files leads the Harddrive to show up.
It appears in /media under the name "407B117F74F2".
Running
a) sudo skdump /dev/sdb ejects the harddrive and tells me: Failed to open disk
/dev/sdb: Invalid argument
b) sudo skdump jmicron:/dev/sdb ejects the harddrive and tell
If you still have the issue with version 0.14, please move the udev
rules away again with
sudo mv /lib/udev/rules.d/95-devkit-disks.rules{,.disabled}
devkit-disks --dump # this will make sure that the daemon is running
and supply the information requested in comment 42.
--
External SATA->US
so there is no fix ...
i thought that i was crazy, but in fact you were wrong :( (i'm up to date with
new versions and bug is still present)
any news about this bug ?
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
You received t
As I said upgrading libatasmart fixed the issue for me and of course
I also upgraded devicekit-disks and moved back the rules files and unfortunately
the bug is still present. The USB-harddisk is not recognized and dmesg shows me
again all this -71 errors.
I also can't these commands since my hard
Oh! thought the problem was similiar! sorry, I will do it!
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Andrix [2009-08-07 13:37 -]:
> I'm using Ubuntu 9.04 up-to-date and I have this problem
No, I'm afraid you have an entirely different problem. Can you please
open a new bug against the kernel? (with "ubuntu-bug linux"). Thanks!
--
External SATA->USB Drive gives lots of USB resets on ATA sma
Hi ,
I'm using Ubuntu 9.04 up-to-date and I have this problem when I'm resuming
from a previous suspension from RAM.
I've attach the kernel log that happens after the resume.
I've read all the thread and I can say that I don't have installed:
* devicekit-disk (isn't in the repo)
* libata
libatasmart 0.14 uploaded and accepted through NEW. I also uploaded a
new devicekit-disks which uses the new libatasmart.
Can you please upgrade to devicekit-disks version 005-0ubuntu6 (will be
available in some two hours), move back the rules (well, the package
upgrade will reinstate them automat
The latest upload of libatasmart fixes the issue for me.
Currently it's in the NEW queue and after it entered the archive you have
to install it manually because of the new library soname libatasmart0 ->
libatasmart4
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
http
Everyone else who is affected by this, please also give the output of
sudo skdump /dev/sd...
and
sudo skdump jmicron:/dev/sd...
** Bug watch added: Red Hat Bugzilla #515881
https://bugzilla.redhat.com/show_bug.cgi?id=515881
** Also affects: libatasmart via
https://bugzilla.redhat.co
** Changed in: libatasmart
Status: Unknown => Confirmed
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
i can't do what you told me in comment 36
r...@ubuntu:/home/alain# apt-get install libatasmart-bin
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
libatasmart-bin est déjà la plus récente version disponible.
0 mis à jour,
here the output of udevadm info --attribute-walk --name=/dev/sdb
** Attachment added: "udevadm info"
http://launchpadlibrarian.net/29951175/udevadm_info
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
You received this bug notif
Please copy&paste the skdump output here in any case.
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
Sorry, the previous comment was wrong. Please just do
sudo skdump jmicron:/dev/sdb
and check if that triggers the reset as well? (No probe-ata-smart
afterwards).
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
You received this
Also, can you please install libatasmart-bin, then do
sudo skdump jmicron:/dev/sdb
and then check if
sudo /lib/udev/devkit-disks-probe-ata-smart /dev/sdb
still fails?
** Package changed: devicekit-disks (Ubuntu) => libatasmart (Ubuntu)
--
External SATA->USB Drive gives lots of USB resets
So these devices need to be blacklisted in /lib//udev/rules.d/95-devkit-
disks.rules . Can you please give me the output of
udevadm info --attribute-walk --name=/dev/sdb
?
** Package changed: libatasmart (Ubuntu) => devicekit-disks (Ubuntu)
--
External SATA->USB Drive gives lots of USB rese
Not a kernel bug
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu)
Assignee: Stefan Bader (stefan-bader-canonical) => (unassigned)
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
Yo
So, I discussed this with upstream:
if we encounter an USB disk we try to find out if it speaks SAT
we do that the hard way:
by sending it some commands
some shitty bridges tend to hang themselves up due to that
or reset themselves
there is not much we can do about that
we had similar repor
here the version with the good debug2 deb
** Attachment added: "the real debug2"
http://launchpadlibrarian.net/29878746/debug2.tar.bz2
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
You received this bug notification because y
holly crap ... i downloaded the wrong deb, please ignore the last submitted
file ...
I will do the test again
sorry
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
You received this bug notification because you are a member of Ub
here is the output from debug2 version
** Attachment added: "debug2"
http://launchpadlibrarian.net/29878596/debug2.tar.bz2
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
You received this bug notification because you are a memb
Unfortunately klogd seems to lag badly, and the timestamps didn't match
up at all. So I uploaded an improved version to my PPA which drops the 2
seconds of sleep and does the logging to the kernel directly.
Can you please do the same exercise again, with 0.13-1debug2 from my
PPA? Thanks!
--
Exte
** Attachment added: "the kern.log"
http://launchpadlibrarian.net/29817481/kern.log
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
ok here they are
** Attachment added: "the trace file"
http://launchpadlibrarian.net/29817478/trace
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Sorry, the last command should read
sudo apt-get install libatasmart0/karmic
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
OK, let's do the good old print/sleep method then. I prepared a
debugging version of libatasmart in my PPA which should help us track
down the operation which causes trouble. Please go to
http://ppa.launchpad.net/pitti/ppa/ubuntu/pool/main/liba/libatasmart/
and click on libatasmart0_0.13-1debug
sorry i can not help :(
my gdb knowlegdes are basics
i mean
adding ddebs.ubuntu... to source list
running a programm with gdb
and taking backtrace
obviously this won't help here, because devkit-disks-probe-ata-smart shut down
without errors :(
i really wisch i could help more
--
External SATA-
If not, another possible test would be to add lots of sleep() statements
to the sk_disk_open() function in a PPA version of libatasmart and
compare kernel logs against strace logs to check where the problem
happens.
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https:/
devkit-disks-probe-ata-smart just calls sk_disk_open() and
sk_disk_smart_is_available(), so something in those will most probably
trigger the problem. It's not clear to me yet whether libatasmart does
an invalid operation, or whether a valid operation triggers a kernel
bug, so I keep both tasks ope
** Summary changed:
- External SATA->USB Drive gives lots of USB resets
+ External SATA->USB Drive gives lots of USB resets on ATA smart probing
--
External SATA->USB Drive gives lots of USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
You received this bug notification bec
i did as you asked (as root i did)
reinstall devicekit :
apt-get install --reinstall devicekit-disks
mv /lib/udev/rules.d/95-devkit-disks.rules{,.disabled}
pluged in the drive, and it worked ^^
/lib/udev/devkit-disks-part-id /dev/sdb
DKD_MEDIA_AVAILABLE=1
Entering MS-DOS parser (offset=0, size=
If it turns out that moving away the udev rules file helps, please keep
the drive plugged in, then do the following commands, and check dmesg
after each one for the USB resets. Please note down which command
triggers this error.
sudo /lib/udev/devkit-disks-part-id /dev/sdb
sudo /lib/udev/devki
Thanks! I looked at the strace and found some oddities:
1274 11:37:08.712674
readlink("/sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda1",
0xbfdd92cc, 1024) = -1 EINVAL (Invalid argument)
(lots of those); this is probably because the device disappears
underneath.
hi i also have the same problem
i bought an SATA to USB case and put my old sata disk in.
and it don't work on karmic ...
i did
sudo killall devkit-disks-daemon
sudo strace -vftt -s 1024 -o /tmp/dk-disks.trace
/usr/lib/devicekit-disks/devkit-disks-daemon
saw some text on screen
put the usb dri
I can confirm the bug and the workaround:
Made a fresh install of Alpha 3: USB PATA drives work, but USB SATA does
not.
Workaround:
dpkg -r --force-all devicekit-disks
Then USB SATA works fine.
--
External SATA->USB Drive gives lots of USB resets
https://bugs.launchpad.net/bugs/387161
You rece
Hello,
I think that the problem is not caused by the executable /usr/lib
/devicekit-disks/devkit-disks-daemon. Here is why:
I am now using jaunty, but I tried to generate the trace like Martin Pitt
suggested. So I temporarily added the karmic repositories to sources.list and
installed these pac
Sorry, please ignore the blacklisting exercise. All the USB drivers are
built in now.
--
External SATA->USB Drive gives lots of USB resets
https://bugs.launchpad.net/bugs/387161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
46 matches
Mail list logo
