From owner-freebsd-questions@FreeBSD.ORG Sun Nov 22 03:46:25 2009 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96DC5106566C; Sun, 22 Nov 2009 03:46:25 +0000 (UTC) (envelope-from gjin@ubicom.com) Received: from server70.appriver.com (server70.appriver.com [69.20.119.203]) by mx1.freebsd.org (Postfix) with ESMTP id 00B358FC0A; Sun, 22 Nov 2009 03:46:24 +0000 (UTC) X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Primary: gjin@ubicom.com X-Note: This Email was scanned by AppRiver SecureTide X-Virus-Scan: V- X-Note: TCH-CT/SI:0-5/SG:5 11/21/2009 10:46:18 PM X-GBUdb-Analysis: 0, 216.112.109.98, Ugly c=0.733847 p=-0.903069 Source Normal X-Signature-Violations: 0-0-0-28178-c X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES X-Note-Sending-IP: 216.112.109.98 X-Note-Reverse-DNS: 216.112.109.98.ptr.us.xo.net X-Note-WHTLIST: gjin@ubicom.com X-Note: User Rule Hits: X-Note: Global Rule Hits: 115 116 117 118 122 123 221 X-Note: Mail Class: VALID X-Note: Headers Injected Received: from [216.112.109.98] (HELO stork.scenix.com) by server70.appriver.com (CommuniGate Pro SMTP 5.3c2) with ESMTP id 107744208; Sat, 21 Nov 2009 22:46:29 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sat, 21 Nov 2009 19:40:27 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 8.0-RC USB problem -- how to recover a damaged USB stick Thread-Index: AcpoP3z6JZv+wKUaR6W88hemmQS/OQC4iGNc References: <200911181213.34112.hselasky@c2i.net> From: "Guojun Jin" To: "Hans Petter Selasky" , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: questions@freebsd.org, freebsd-stable@freebsd.org Subject: 8.0-RC USB problem -- how to recover a damaged USB stick X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Nov 2009 03:46:25 -0000 It seems this is more serious problem in 8.0, and I hope it could be = resolved before a formal release. I can help to diagnose this if people = need more information (this is destructive). I have picked a USB stick (DataTraveler 2GB), that has two partitions s0 = for DOS and s1 for FreeBSD. Both USB hard drive and the USB stick have worked under FreeBSD 6.2, = 6.3, 6.4 and 7.2 for a few years without any problem. Plugged USB stick in 8.0-RC and mounted it on /mnt; then untar a file, tarred one day ago from FreeBSD 6.3 machine onto stick,to = a IDE drive then tar it back to the USB stick. During tar writting from IDE to USB stick, did "ls /mnt", and "tar" = paused and "ls" hangs. A couple of minutes later, ls comes back, but tar still pauses. Hit ^C on tar process around 14:30, it took another minutes to stop the = process. Tried tar again, and system disallowed to write on the USB stick. "ls" shows all file = still there (probably cached inods). Went out for a few hours, and came back found /var/log/message are = flooded with following message: -rw-r--r-- 1 root wheel 167181 Nov 21 19:02 messages -rw-r--r-- 1 root wheel 7390 Nov 21 18:00 messages.0.bz2 -rw-r--r-- 1 root wheel 7509 Nov 21 17:00 messages.1.bz2 -rw-r--r-- 1 root wheel 9365 Nov 21 16:00 messages.2.bz2 -rw-r--r-- 1 root wheel 20598 Nov 21 15:00 messages.3.bz2 Nov 21 18:00:00 wolf newsyslog[2635]: logfile turned over due to = size>384K Nov 21 18:00:27 wolf kernel: = g_vfs_done():da0s2[WRITE(offset=3D625688576, length=3D1 31072)]error =3D 5 Nov 21 18:00:27 wolf kernel: = g_vfs_done():da0s2[WRITE(offset=3D625819648, length=3D1 31072)]error =3D 5 ..... Nov 21 18:19:03 wolf kernel: = g_vfs_done():da0s2[WRITE(offset=3D524451840, length=3D1 6384)]error =3D 5 Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=3D5586944, = length=3D204 8)]error =3D 5 Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=3D65536, = length=3D2048) ]error =3D 5 Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=3D114688, = length=3D1638 4)]error =3D 5 Nov 21 18:20:05 wolf kernel: = g_vfs_done():da0s2[WRITE(offset=3D349700096, length=3D1 and has to reboot the system, and reboot was not able to umount = everything (boot up message): Nov 21 18:24:03 wolf kernel: da0: = Removable Dir ect Access SCSI-2 device Nov 21 18:24:03 wolf kernel: da0: 40.000MB/s transfers Nov 21 18:24:03 wolf kernel: da0: 1947MB (3987456 512 byte sectors: 255H = 63S/T 2 48C) Nov 21 18:24:03 wolf kernel: WARNING: / was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /data was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /home was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /tmp was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /usr was not properly dismounted ... # mount /dev/da0s2 /mnt mount: /dev/da0s2 : Operation not permitted The USB stick cannot be mount under any FreeBSD OS now, and everything = on the drive has lost. Does anyone know if it is possible to revocer such damaged USB stick? -----Original Message----- From: Hans Petter Selasky [mailto:hselasky@c2i.net] Sent: Wed 11/18/2009 3:13 AM To: freebsd-usb@freebsd.org Cc: Guojun Jin; freebsd-stable@freebsd.org; questions@freebsd.org Subject: Re: 8.0-RC3 USB lock up on mounting two partitions from one USB = drive =20 Hi, I'm not sure if this is an USB issue or not. If you get READ/WRITE = errors and=20 the drive simply dies then it might be the case. Else it is a system = issue. There are quirks for mass storage which you can add to=20 sys/dev/usb/storage/umass.c . --HPS On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote: > Did newfs on those partition and made things worsen -- restore = completely > fails: (I had experienced another similar problem on an IDE, which = works > well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD = 6.4. > > Is something new in 8.0 making disk partition schema changed? > > g_vfs_done():da0s3d[READ(offset=3D98304, length=3D16384)]error =3D 6 > g_vfs_done():da0s3d[WRITE(offset=3D192806912, length=3D16384)]error = =3D 6 > fopen: Device not configured > cannot create save file ./restoresymtable for symbol table > abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status = =3D=3D > 0xa, scs i status =3D=3D 0x0 > (da0:umass-sim0:0:0:0): removing device entry > ugen1.2: at usbus1 > umass0: on usbus1 > umass0: SCSI over Bulk-Only; quirks =3D 0x0000 > umass0:0:0:-1: Attached to scbus0 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) > Device da0s3d went missing before all of the data could be written to = it; > expect data loss. > > 99 23:19 sysinstall > 100 23:20 newfs /dev/da0s3d > 101 23:20 newfs /dev/da0s3e > 102 23:21 mount /dev/da0s3d /mnt > 103 23:21 cd /mnt > 104 23:21 dump -0f - /home | restore -rf - > 105 23:27 history 15 > > > > -----Original Message----- > From: Guojun Jin > Sent: Tue 11/17/2009 11:05 PM > To: freebsd-stable@freebsd.org > Cc: questions@freebsd.org; freebsd-usb@freebsd.org > Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB = drive > > When mounting two partitions from a USB dirve, it can cause the drive > access lock up for a long time. Details: > > Terminal 1 -- > term1# mount /dev/da0s3d /mnt > term1# cd /mnt ; rm -fr * > > when rm starts, go to terminal 2 and do: > > term2# mount /dev/da0s3e /dist ### this will hanging for a long time = and > USB hard drive activity light is off. After more than 1-2 minutes, = mount > returns, and the drive activity light is blinking, thus removing is = going > on. > > term2# ls /dist ### this will cause dUSB dirve hanging again -- no > avtivity. Similarly, ls will finish in a couple of miniutes or longer, = the > rm command continues; but for a while, the drive activity will stop = again. > > Reboot machine, repeat the above steps, and result will be the same. = Reboot > machine again, and just mount one partition, then doing "rm -rf *" = without > involve the second partition, rm will finish quickly. > > Has anyone obseved this behave on 8.0-RC? > > -Jin