utopic has seen the end of its life and is no longer receiving any
updates. Marking the utopic task for this ticket as "Won't Fix".
** Changed in: linux (Ubuntu Utopic)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I have also experienced this problem with a USB connected Seagate
ST3300601CB-RK 300 GB external hard drive. The issue is still present in
Ubuntu Server 13.10 with kernel level 4.2.0-30-generic. Using the
command suggested by Brad in #37 above fixed the problem. I have not
rebooted to see if the fi
To verify if quirks parameter is in place inspect `dmesg` _after_ plugging in
the device.
You should have a line indicating "quirks match" for your device - e.g. (in my
case)
[ 2266.284812] usb-storage 8-4:1.0: USB Mass Storage device detected
[ 2266.284979] usb-storage 8-4:1.0: Quirks match for
Thanks, I tried that & there was no change. I got it working with
sudo -s
echo 'temporary write through' > /sys/block/sdb/device/scsi_disk/*/cache_type
It seems to be permanent :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
I have used this workaround for a LaCie DVD RW (being used as a USB hard
drive adapter): 059f:0363 (I obtain the usb id for my particular
enclosure using `lsusb`).
- For temporarily adding the quirks, I stop the kernel module:
`modprobe -r usb-storage` (I may also need to stop dependent kernel
mo
Can someone outline for a noob how to use usb-storage quirks. I'd like
to get my Maxtor working. thx
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366538
Title:
Synchronisation/close /dev/sdX: i/
jkampe: I tried your workaround of adding usb-storage quirks 'uw' with
my Maxtor OneTouch 250GB, same kernel as yours (3.16.0-31-generic
#43~14.04.1-Ubuntu - x86_64). So far,
IT WORKS.
I'll have to test it further: I'm still running a (lengthy as in hours
long) fsck caused by the previous test _
I can confirm same with old LACIE 250GB
However adding usb-storage quirks 'uw' for it _may_ work around the issue;
e.g. add (just substitute vendor and product id for yours)
options usb-storage quirks=059f:0651:uw
dmesg with above quirks / kernel 3.16.0-31-generic
[ 57.952732] usb 2-4: new hi
I use a Maxtor OneTouch 250GB, and can confirm the previous reports:
even an fsck that returns "clean" (ext3 partition inside) is followed by 2
errors like:
end_request: critical target error, dev sdX, sector 0
Any subsequent fsck turns off the journal and finds many previously non
existent err
These are consecutive cmds, wirte cach goes from on, to not supported,
to off . Further tries for this show that it seems random.
~
dt1:sudo hdparm -W /dev/sdc
/dev/sdc:
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Can't seem to turn off write caching.
~
dt1:sudo hdparm -I /dev/sdc1
/dev/sdc1:
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ATA device, with non-removable media
Model Number: ��+@�Z#��C`@
Can you post the output of:
sudo hdparm -I /dev/sdb
or what ever sdN is if it changes?
Also, can you see if setting the cache off makes the bug go away? It can be
done with:
sudo hdparm -W0 /dev/sdc
To confirm it is off, you can run:
sudo hdparm -W /dev/sdc
--
You received this bug notific
syslog:
Feb 1 19:21:12 dt1 kernel: [ 5378.841282] usb 1-1.4: new high-speed USB device
number 4 using ehci-pci
Feb 1 19:21:12 dt1 kernel: [ 5378.934784] usb 1-1.4: New USB device found,
idVendor=0d49, idProduct=7110
Feb 1 19:21:12 dt1 kernel: [ 5378.934788] usb 1-1.4: New USB device strings:
I'm trying to reproduce this issue to gather addition data. Can folks
affected by this bug attach the section of syslog that is generated
after attaching the external USB drive.
Specifically, I'm looking to see if the Write cache is enabled or
disabled.
For example, my syslog shows the cache is
Is installing the jsalisbury test kernel the recommended fix for a user
at this time?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366538
Title:
Synchronisation/close /dev/sdX: i/o error on target
manually installing all the deb packages from
http://kernel.ubuntu.com/~jsalisbury/lp1366538/
fixes the issue for me on linux mint 17.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366538
Title:
Is this patch going to be incorporated soon? I have 2 USB drive that
are useless until this is fixed. 'Importance' is more than medium for
me!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366538
T
Hello! I found the original bug and proposed the original patch to the
kernel SCSI guys. Here's some context:
The SCSI flush command was being treated by a zero-byte write, which
means that if an error was returned, you wouldn't catch it until a
subsequent write (or flush). The way writes work is
The patch James shipped fixes this bug by special-casing the flush error
path. Before flush wouldn't return errors; now it does.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366538
Title:
Synchron
** Also affects: linux (Ubuntu Vivid)
Importance: Medium
Status: Triaged
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Sta
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366538
Title:
Synchronisation/close /dev/sdX: i/o error on target host
To manage notifications about this bug go to:
http
Joseph, your kernel works for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366538
Title:
Synchronisation/close /dev/sdX: i/o error on target host
To manage notifications about this bug go to:
I built a Trusty test kernel with a revert of the commit mentioned in
comment #18. Can you test this kernel and confirm it fixes this bug?
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1366538/
This is commit d215f91 in the Trusty repo.
--
You received this bu
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366538
Title:
Synchronisation/close /dev/sdX: i/o error on target host
To manage not
Great gianluca, far better than peremtory autistic "hardware error" that didn't
even take into account circumstances (trusty 64 KO vs precise 32 OK).
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Summary changed:
- Synchronisation/close /dev/sdi: i/o error on target host
+ Synchronisation/close /dev/sdX: i/o error on target host
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366538
Title:
26 matches
Mail list logo
