See my comments in this smartmontools ticket:
https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1810215
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774569
Title:
gsmartcontrol,
FYI I am on a rolling distro (arch) and the same problem has started for me
with my seagate backup drive
It is still present today
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774569
Title:
HDParm/SDParm bug afects me as well with 2 different Seagate usb drives,
I think this one should have a high priority, since it also affects
power management. Further more since the aforementioned drive is also a
sub-hub it would be good to be able to turn on/off the drive portion
without needing
Since this is a physical through to block layer issue and not ZFS per-
se, I'm going to remove ZFS off this bug report.
** No longer affects: zfs-linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also not working for my other external HDDs:
root@desktop:~# sdparm -i /dev/sdd
/dev/sdd: WDMy Book 1140 1019
Device identification VPD page:
Addressed logical unit:
designator type: T10 vendor identification, code set: ASCII
vendor id: WD
vendor
Same here:
root@desktop:~# sdparm -i /dev/sdb
/dev/sdb: Seagate Backup+ Hub BKD781
Device identification VPD page:
Addressed logical unit:
designator type: NAA, code set: Binary
0x5001
root@desktop:~# hdparm -y /dev/sdb
/dev/sdb:
issuing standby command
SG_IO:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gsmartcontrol (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774569
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: hdparm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774569
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774569
Title:
It looks like the drive is replying with an ILLEGAL REQUEST/INVALID
FIELD IN CDB error to all the interesting SCSI commands, and to pretty
much anything hdparm sends it.
I've also tried throwing sdparm at it. The only page sdparm can get out
of it is the basic identification page:
I pulled the hdparm binary from Artful, and it can't spin down the drive
with -y either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774569
Title:
gsmartcontrol, hdparm, and ZFS all refuse to
Even after rebooting with the drive for the zpool physically removed
from the system, I still had a zpool I couldn't destroy, export, or
otherwise remove from the listing.
Using "sudo zpool status -Pv" I worked out that my ZFS was actually
expecting to find the data on partition 1 of the drive:
Nope, my speculation is definitely wrong. The disk shows up in lsscsi:
[anovak@octagon ~]$ lsscsi
...
[9:0:0:0]diskSeagate Backup+ Hub BK D781 /dev/sdb
Also, it shows up in lsusb -t with a "uas" driver.
Maybe the problem is the uas driver itself?
Here's the full description of the
13 matches
Mail list logo
