From owner-freebsd-usb@freebsd.org Wed Nov 4 08:41:31 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 582BBA25B42 for ; Wed, 4 Nov 2015 08:41:31 +0000 (UTC) (envelope-from 214748mv@gmail.com) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 214D81975 for ; Wed, 4 Nov 2015 08:41:31 +0000 (UTC) (envelope-from 214748mv@gmail.com) Received: by igbhv6 with SMTP id hv6so30830981igb.0 for ; Wed, 04 Nov 2015 00:41:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sN+q6Z3Aj2DUImSkJt2SVnB12xsILWjmZ+nCtGYDABQ=; b=rs/PVWTcMhaOGwFjt+eaBT9fnt2ig2yDkpR8xF2ehK+VI3KOiAhjCsP2Wr02cPV1Lj loIFFzAtavV4Sd72IT1uY3hzS5qqko0qxkNn7ILWdb9wgIq7YRgnJ6XTXkuUiACG2hoH 7YxIpLSUADWzf50C3bYnhpNtZLwbDs3wQDWiJpuhubWtNxZtLX5J+xq37kTmKHxylOG2 fq5q44okAVyJLqQ1u9mk+UkQgWOeowa/cLa6Ob9WcjCYEQgNlnDqb+kZWUwLmi4N9+w9 CC9pdMX96/D9BLCLdCtqKBk6DF1chkU6OvLRjB0Yfjggay+ww6oiftT/u6B0Oim8dXmW N99A== MIME-Version: 1.0 X-Received: by 10.50.50.139 with SMTP id c11mr1896139igo.10.1446626490641; Wed, 04 Nov 2015 00:41:30 -0800 (PST) Received: by 10.79.70.130 with HTTP; Wed, 4 Nov 2015 00:41:30 -0800 (PST) In-Reply-To: <56375A74.2040704@selasky.org> References: <562FA2E8.1020003@selasky.org> <56375A74.2040704@selasky.org> Date: Wed, 4 Nov 2015 09:41:30 +0100 Message-ID: Subject: Re: Non working USB stick in FreeBSD. From: "Ranjan1018 ." <214748mv@gmail.com> To: Hans Petter Selasky Cc: freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2015 08:41:31 -0000 2015-11-02 13:43 GMT+01:00 Hans Petter Selasky : > On 10/29/15 10:29, Ranjan1018 . wrote: > >> 2015-10-27 17:14 GMT+01:00 Hans Petter Selasky : >> >> On 10/27/15 17:05, Ranjan1018 . wrote: >>> >>> I have a 64GB USB stick that works correctly in Windows and Linux but not >>>> in FreeBSD. The problem is during the write. >>>> >>>> In FreeBSD I have tested the stick with the command: >>>> >>>> # dd if=/dev/zero of=/dev/daX bs=1m >>>> >>>> and, after some time, I received these errors in i386 and amd64: >>>> >>>> >>>> Hi, >>> >>> >> Hi Hans, >> thank you for your answer. >> >> >>> Are you sure the disk is of the size advertised? >>> >>> >> In Linux I obtain: >> >> $ uname -a >> >> Linux phenom2 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux >> >> $ sudo dd if=/dev/zero of=/dev/sdf obs=1M seek=8100 >> >> dd: writing to `/dev/sdf': No space left on device >> >> 114485248+0 records in >> >> 55900+0 records out >> >> 58615398400 bytes (59 GB) copied, 20869.4 s, 2.8 MB/s >> >> >> >> How many 512-byte blocks are successfully written? >>> >>> In FreeBSD : >>> >> >> # uname -a >> >> FreeBSD microserver 10.2-STABLE FreeBSD 10.2-STABLE #4 r289314M: Wed Oct >> 14 >> 15:38:08 CEST 2015 root@microserver:/usr/obj/usr/src/sys/GENERIC >> amd64 >> >> # dd if=/dev/zero of=/dev/da0 bs=1m >> >> dd: /dev/da0: Input/output error >> >> 8140+0 records in >> >> 8139+0 records out >> >> 8534360064 bytes transferred in 3013.528065 secs (2832016 bytes/sec) >> >> # uname -a >> >> FreeBSD qbic 10.1-STABLE FreeBSD 10.1-STABLE #0: Sat May 9 07:53:21 CEST >> 2015 root@ativ >> :/usr/obj/i386.i386/root/TEMP/i386_SRC/src/sys/KSTACK_PAGES_4 >> i386 >> >> [root@qbic ~]# dd if=/dev/zero of=/dev/da2 bs=1m >> >> dd: /dev/da2: Input/output error >> >> 8140+0 records in >> >> 8139+0 records out >> >> 8534360064 bytes transferred in 3011.855356 secs (2833589 bytes/sec) >> >> # uname -a >> >> FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #10 r289378M: Thu Oct 15 >> 21:57:57 CEST 2015 root@ativ:/usr/obj/usr/src/sys/GENERIC amd64 >> >> [root@ativ ~]# dd if=/dev/zero of=/dev/da1 bs=1m >> >> dd: /dev/da1: Input/output error >> >> 8140+0 records in >> >> 8139+0 records out >> >> 8534360064 bytes transferred in 3041.663436 secs (2805820 bytes/sec) >> >> [root@ativ ~/bin]# dd if=/dev/zero of=/dev/da1 bs=1m seek=12140 >> >> dd: /dev/da1: Input/output error >> >> 69+0 records in >> >> 68+0 records out >> >> 71303168 bytes transferred in 35.119861 secs (2030280 bytes/sec) >> >> [root@ativ ~/bin]# dd if=/dev/zero of=/dev/da1 bs=1m seek=12200 >> >> dd: /dev/da1: Input/output error >> >> 9+0 records in >> >> 8+0 records out >> >> 8388608 bytes transferred in 13.562622 secs (618509 bytes/sec) >> >> > Hi, > > What does "dmesg" say after these errors? Maybe you have a bad sector? > > Did you try to add "conv=noerror" to dd ? > > Did you try "bs=65536" or "bs=512" ? > > Hi Hans, I have tested the USB stick with 3 different hardware on 3 different operating systems but is not possible to write, without errors, on it. Sorry for the noise. In FreeBSD 10.2-RELEASE with f3write: # f3write /media/da0s1 Free space: 62.48 GB Creating file 1.h2w ... OK! Creating file 2.h2w ... OK! Creating file 3.h2w ... OK! Creating file 4.h2w ... 6.39% -- 1.00 KB/s -- 14:58:04 6.39% -- 1.00 KB/s -- 17:40:25Assertion failed: (!fdatasync(fd)), function measure, file f3write.c, line 241. Abort trap (core dumped) dmesg output: (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 9d 49 00 00 40 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 9d 49 00 00 40 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 9d 49 00 00 40 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 9d 49 00 00 40 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 9d 49 00 00 40 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Error 5, Retries exhausted g_vfs_done():da0s1[WRITE(offset=17068856320, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17068921856, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17068987392, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069052928, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069118464, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069184000, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069249536, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069315072, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069380608, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069446144, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069511680, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069577216, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069642752, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069708288, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069773824, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069839360, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069904896, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17069970432, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17070035968, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17070101504, length=65536)]error = 5 g_vfs_done():da0s1[WRITE(offset=17087992832, length=32768)]error = 5 g_vfs_done():da0s1[WRITE(offset=20583424, length=32768)]error = 5 On Windows 7 with H2testw: Error writing file 'J:\8.h2w', offset 0x3b700000. It is still possible to verify the test data written up to this point. (Impossibile eseguire la richiesta a causa di un errore di dispositivo I/O. Code 1117) Writing speed: 2.22 MByte/s H2testw v1.4 In Debian Linux 7.5 with f3write: $ ./f3write /media/2AAD-E09F Free space: 62.48 GB Creating file 1.h2w ... OK! Creating file 2.h2w ... OK! Creating file 3.h2w ... OK! Creating file 4.h2w ... 6.17% -- 1.94 MB/s -- 8:55:24f3write: f3write.c:241: measure: Assertion `!fdatasync(fd)' failed. Aborted dmesg output: [ 2311.374327] sd 9:0:0:0: [sdf] Unhandled error code [ 2311.374335] sd 9:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 2311.374345] sd 9:0:0:0: [sdf] CDB: Write(10): 2a 00 01 7d 84 69 00 00 f0 00 [ 2311.374364] end_request: I/O error, dev sdf, sector 25003113 Regards, Maurizio