From owner-freebsd-scsi@freebsd.org Sun Jun 9 21:01:31 2019 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3499715AB77A for ; Sun, 9 Jun 2019 21:01:31 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B7EDD8681F for ; Sun, 9 Jun 2019 21:01:30 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7B6C715AB767; Sun, 9 Jun 2019 21:01:30 +0000 (UTC) Delivered-To: scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68C8915AB766 for ; Sun, 9 Jun 2019 21:01:30 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 016E586810 for ; Sun, 9 Jun 2019 21:01:30 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id F140125B8 for ; Sun, 9 Jun 2019 21:01:28 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x59L1SAM011460 for ; Sun, 9 Jun 2019 21:01:28 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x59L1SRu011459 for scsi@FreeBSD.org; Sun, 9 Jun 2019 21:01:28 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201906092101.x59L1SRu011459@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: scsi@FreeBSD.org Subject: Problem reports for scsi@FreeBSD.org that need special attention Date: Sun, 9 Jun 2019 21:01:28 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jun 2019 21:01:31 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 221952 | cam iosched: Fix trim statistics 1 problems total for which you should take action. From owner-freebsd-scsi@freebsd.org Thu Jun 13 11:03:01 2019 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A898315AE04D for ; Thu, 13 Jun 2019 11:03:01 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from smtpq6.tb.mail.iss.as9143.net (smtpq6.tb.mail.iss.as9143.net [212.54.42.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F09C08010D for ; Thu, 13 Jun 2019 11:02:59 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from [212.54.42.136] (helo=smtp12.tb.mail.iss.as9143.net) by smtpq6.tb.mail.iss.as9143.net with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1hbNVJ-0006tv-Nt for freebsd-scsi@freebsd.org; Thu, 13 Jun 2019 13:02:49 +0200 Received: from 94-209-122-217.cable.dynamic.v4.ziggo.nl ([94.209.122.217] helo=wan0.bsd4all.org) by smtp12.tb.mail.iss.as9143.net with esmtp (Exim 4.90_1) (envelope-from ) id 1hbNVJ-0006Dz-KN for freebsd-scsi@freebsd.org; Thu, 13 Jun 2019 13:02:49 +0200 Received: from newnas (localhost [127.0.0.1]) by wan0.bsd4all.org (Postfix) with ESMTP id 3D4C2188 for ; Thu, 13 Jun 2019 13:02:49 +0200 (CEST) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from wan0.bsd4all.org ([127.0.0.1]) by newnas (newnas.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qz0Brtu5QdVk for ; Thu, 13 Jun 2019 13:02:48 +0200 (CEST) Received: from [192.168.1.65] (unknown [192.168.1.65]) by wan0.bsd4all.org (Postfix) with ESMTPSA id D3B19181 for ; Thu, 13 Jun 2019 13:02:48 +0200 (CEST) From: peter.blok@bsd4all.org Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Bad SSD drive - what happens with unreadable data Message-Id: Date: Thu, 13 Jun 2019 13:02:48 +0200 To: freebsd-scsi@freebsd.org X-Mailer: Apple Mail (2.3445.104.11) X-SourceIP: 94.209.122.217 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.3 cv=Zo2T1OzG c=1 sm=1 tr=0 a=0XONDDbZk2SpjknwKA3Xxg==:17 a=IkcTkHD0fZMA:10 a=dq6fvYVFJ5YA:10 a=ASqCesjh3PPKGcoGyAIA:9 a=QEXdDO2ut3YA:10 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-Rspamd-Queue-Id: F09C08010D X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of peter.blok@bsd4all.org designates 212.54.42.169 as permitted sender) smtp.mailfrom=peter.blok@bsd4all.org X-Spamd-Result: default: False [-3.36 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[6]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; MIME_TRACE(0.00)[0:+]; R_SPF_ALLOW(-0.20)[+a:smtp.ziggo.nl/16]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-scsi@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MX_GOOD(-0.01)[smtp.bsd4all.org]; NEURAL_HAM_SHORT(-0.67)[-0.671,0]; FROM_NO_DN(0.00)[]; IP_SCORE(-0.78)[ipnet: 212.54.32.0/20(-3.10), asn: 33915(-0.81), country: NL(0.01)]; DMARC_NA(0.00)[bsd4all.org]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[169.42.54.212.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:33915, ipnet:212.54.32.0/20, country:NL]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[217.122.209.94.zen.spamhaus.org : 127.0.0.11] X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jun 2019 11:03:01 -0000 Hi, I have a bad SSD drive. If I read it with dd and conv=3Dnoerror, what = happens with the unreadable areas? Does it fill with zeroes, or does the = driver still copy what it was able to read? I=E2=80=99m getting ATA status 51 back, many blocks in a row. Followed = by chunks of readable data, followed by unreadable data. Is there a modepage or something else to tell the drive to pass on the = bad data? Any other ideas? Peter From owner-freebsd-scsi@freebsd.org Thu Jun 13 13:34:51 2019 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E38315B233F for ; Thu, 13 Jun 2019 13:34:51 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mithlond.kdm.org (mithlond.kdm.org [96.89.93.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mithlond.kdm.org", Issuer "mithlond.kdm.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0906184EEE for ; Thu, 13 Jun 2019 13:34:49 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mithlond.kdm.org (localhost [127.0.0.1]) by mithlond.kdm.org (8.15.2/8.14.9) with ESMTPS id x5DDYe5Y014993 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 13 Jun 2019 09:34:40 -0400 (EDT) (envelope-from ken@mithlond.kdm.org) Received: (from ken@localhost) by mithlond.kdm.org (8.15.2/8.14.9/Submit) id x5DDYehw014992; Thu, 13 Jun 2019 09:34:40 -0400 (EDT) (envelope-from ken) Date: Thu, 13 Jun 2019 09:34:39 -0400 From: "Kenneth D. Merry" To: peter.blok@bsd4all.org Cc: freebsd-scsi@freebsd.org Subject: Re: Bad SSD drive - what happens with unreadable data Message-ID: <20190613133439.GE66314@mithlond.kdm.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mithlond.kdm.org [127.0.0.1]); Thu, 13 Jun 2019 09:34:40 -0400 (EDT) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mithlond.kdm.org X-Rspamd-Queue-Id: 0906184EEE X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of ken@kdm.org designates 96.89.93.250 as permitted sender) smtp.mailfrom=ken@kdm.org X-Spamd-Result: default: False [-4.77 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mithlond.kdm.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[kdm.org]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[mail.scsiguy.com,mithlond.kdm.org]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.98)[-0.981,0]; IP_SCORE(-1.48)[ip: (-3.77), ipnet: 96.64.0.0/11(-3.64), asn: 7922(0.05), country: US(-0.06)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7922, ipnet:96.64.0.0/11, country:US]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jun 2019 13:34:51 -0000 On Thu, Jun 13, 2019 at 13:02:48 +0200, peter.blok@bsd4all.org wrote: > Hi, > > I have a bad SSD drive. If I read it with dd and conv=noerror, what happens with the unreadable areas? Does it fill with zeroes, or does the driver still copy what it was able to read? > > I???m getting ATA status 51 back, many blocks in a row. Followed by chunks of readable data, followed by unreadable data. > > Is there a modepage or something else to tell the drive to pass on the bad data? > > Any other ideas? You might try the recoverdisk(1) utility. It is designed for that sort of situation. One of the recommendations in the recoverdisk(1) man page is to lower the retry count for the disk driver you're using, so you don't wind up retrying a lot in situations where the drive itself has tried and failed to read the data. In looking at the source, it appears tht it will only write out the blocks it is able to read successfully. IMO, it would be good to have at least an option to write zeros in output file in the areas where the reads failed. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@freebsd.org Fri Jun 14 10:03:16 2019 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F19615CC260 for ; Fri, 14 Jun 2019 10:03:16 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from hermod.tmst.com.au (hermod.tmst.com.au [203.14.245.41]) by mx1.freebsd.org (Postfix) with SMTP id B5A988C146 for ; Fri, 14 Jun 2019 10:03:07 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 45842 invoked by uid 907); 14 Jun 2019 09:56:23 -0000 Received: from p5DD77B6B.dip0.t-ipconnect.de (HELO [192.168.7.2]) (93.215.123.107) by hermod.tmst.com.au (qpsmtpd/0.96) with ESMTPSA (ECDHE-RSA-AES256-GCM-SHA384 encrypted); Fri, 14 Jun 2019 19:56:23 +1000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Bad SSD drive - what happens with unreadable data From: Jan Martin Mikkelsen In-Reply-To: Date: Fri, 14 Jun 2019 11:56:15 +0200 Cc: freebsd-scsi@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: peter.blok@bsd4all.org X-Mailer: Apple Mail (2.3445.9.1) X-Rspamd-Queue-Id: B5A988C146 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [2.31 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[transactionware.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.40)[0.398,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[a.mx.transactionware.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.46)[0.459,0]; NEURAL_HAM_SHORT(-0.04)[-0.042,0]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:17559, ipnet:203.14.245.0/24, country:AU]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.00)[country: AU(0.01)] X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jun 2019 10:03:16 -0000 Hi, You need to add =E2=80=9Csync" to get the unreadable areas filled with = zeros. Something like "dd conv=3Dsync,noerror bs=3D4k=E2=80=9D is = probably good. Regards, Jan. > On 13 Jun 2019, at 13:02, peter.blok@bsd4all.org wrote: >=20 > Hi, >=20 > I have a bad SSD drive. If I read it with dd and conv=3Dnoerror, what = happens with the unreadable areas? Does it fill with zeroes, or does the = driver still copy what it was able to read? >=20 > I=E2=80=99m getting ATA status 51 back, many blocks in a row. Followed = by chunks of readable data, followed by unreadable data. >=20 > Is there a modepage or something else to tell the drive to pass on the = bad data? >=20 > Any other ideas? >=20 > Peter >=20 >=20 >=20 >=20 > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to = "freebsd-scsi-unsubscribe@freebsd.org" From owner-freebsd-scsi@freebsd.org Fri Jun 14 10:25:34 2019 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1919515CC6D9 for ; Fri, 14 Jun 2019 10:25:34 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from smtpq6.tb.mail.iss.as9143.net (smtpq6.tb.mail.iss.as9143.net [212.54.42.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5B34C8C8EC for ; Fri, 14 Jun 2019 10:25:32 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from [212.54.42.136] (helo=smtp12.tb.mail.iss.as9143.net) by smtpq6.tb.mail.iss.as9143.net with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1hbjOi-00033L-Lc; Fri, 14 Jun 2019 12:25:28 +0200 Received: from 94-209-122-217.cable.dynamic.v4.ziggo.nl ([94.209.122.217] helo=wan0.bsd4all.org) by smtp12.tb.mail.iss.as9143.net with esmtp (Exim 4.90_1) (envelope-from ) id 1hbjOi-0006T3-Gq; Fri, 14 Jun 2019 12:25:28 +0200 Received: from newnas (localhost [127.0.0.1]) by wan0.bsd4all.org (Postfix) with ESMTP id 944D91F2; Fri, 14 Jun 2019 12:25:27 +0200 (CEST) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from wan0.bsd4all.org ([127.0.0.1]) by newnas (newnas.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5sKSx_LYIaLq; Fri, 14 Jun 2019 12:25:26 +0200 (CEST) Received: from [192.168.1.65] (unknown [192.168.1.65]) by wan0.bsd4all.org (Postfix) with ESMTPSA id 6E85A1EE; Fri, 14 Jun 2019 12:25:26 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Bad SSD drive - what happens with unreadable data From: peter.blok@bsd4all.org In-Reply-To: <20190613133439.GE66314@mithlond.kdm.org> Date: Fri, 14 Jun 2019 12:25:25 +0200 Cc: freebsd-scsi@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20190613133439.GE66314@mithlond.kdm.org> To: "Kenneth D. Merry" X-Mailer: Apple Mail (2.3445.104.11) X-SourceIP: 94.209.122.217 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.3 cv=Zo2T1OzG c=1 sm=1 tr=0 a=0XONDDbZk2SpjknwKA3Xxg==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=kj9zAlcOel0A:10 a=dq6fvYVFJ5YA:10 a=Gw1ouQRIAAAA:8 a=6Q3WNqvRAAAA:8 a=TlfEPOs9qqefzcL246AA:9 a=CjuIK1q_8ugA:10 a=K9VNa7-dmgn0gKMGrBPS:22 a=I8PBwKCn76L9oNdl0isp:22 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-Rspamd-Queue-Id: 5B34C8C8EC X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of peter.blok@bsd4all.org designates 212.54.42.169 as permitted sender) smtp.mailfrom=peter.blok@bsd4all.org X-Spamd-Result: default: False [-3.49 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[6]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:smtp.ziggo.nl/16]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bsd4all.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: smtp.bsd4all.org]; RCPT_COUNT_TWO(0.00)[2]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-0.83)[-0.834,0]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; IP_SCORE(-0.74)[ipnet: 212.54.32.0/20(-2.95), asn: 33915(-0.78), country: NL(0.01)]; RCVD_IN_DNSWL_LOW(-0.10)[169.42.54.212.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:33915, ipnet:212.54.32.0/20, country:NL]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[217.122.209.94.zen.spamhaus.org : 127.0.0.11] X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jun 2019 10:25:34 -0000 Hi Ken, Yes I already had changed the time-outs and retries. I ended up using = ddrescue out of the ports collection. Despite the amount of read errors = I was able to recover the important stuff. SSD drive is going back under warranty (hopefully). It is less than a = year old and hardly used. Peter > On 13 Jun 2019, at 15:34, Kenneth D. Merry wrote: >=20 > On Thu, Jun 13, 2019 at 13:02:48 +0200, peter.blok@bsd4all.org wrote: >> Hi, >>=20 >> I have a bad SSD drive. If I read it with dd and conv=3Dnoerror, what = happens with the unreadable areas? Does it fill with zeroes, or does the = driver still copy what it was able to read? >>=20 >> I???m getting ATA status 51 back, many blocks in a row. Followed by = chunks of readable data, followed by unreadable data. >>=20 >> Is there a modepage or something else to tell the drive to pass on = the bad data? >>=20 >> Any other ideas? >=20 > You might try the recoverdisk(1) utility. It is designed for that = sort of > situation. >=20 > One of the recommendations in the recoverdisk(1) man page is to lower = the > retry count for the disk driver you're using, so you don't wind up = retrying > a lot in situations where the drive itself has tried and failed to = read the > data. >=20 > In looking at the source, it appears tht it will only write out the = blocks > it is able to read successfully. IMO, it would be good to have at = least an > option to write zeros in output file in the areas where the reads = failed. >=20 > Ken > --=20 > Kenneth Merry > ken@kdm.org From owner-freebsd-scsi@freebsd.org Fri Jun 14 10:27:12 2019 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0757315CC74D for ; Fri, 14 Jun 2019 10:27:12 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from smtpq2.mnd.mail.iss.as9143.net (smtpq2.mnd.mail.iss.as9143.net [212.54.34.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E784A8C965 for ; Fri, 14 Jun 2019 10:27:10 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from [212.54.34.119] (helo=smtp11.mnd.mail.iss.as9143.net) by smtpq2.mnd.mail.iss.as9143.net with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1hbjQD-0002ja-M2; Fri, 14 Jun 2019 12:27:01 +0200 Received: from 94-209-122-217.cable.dynamic.v4.ziggo.nl ([94.209.122.217] helo=wan0.bsd4all.org) by smtp11.mnd.mail.iss.as9143.net with esmtp (Exim 4.90_1) (envelope-from ) id 1hbjQD-0007Ww-HW; Fri, 14 Jun 2019 12:27:01 +0200 Received: from newnas (localhost [127.0.0.1]) by wan0.bsd4all.org (Postfix) with ESMTP id 7789B1F9; Fri, 14 Jun 2019 12:26:59 +0200 (CEST) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from wan0.bsd4all.org ([127.0.0.1]) by newnas (newnas.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PbkazfFyFQ0w; Fri, 14 Jun 2019 12:26:57 +0200 (CEST) Received: from [192.168.1.65] (unknown [192.168.1.65]) by wan0.bsd4all.org (Postfix) with ESMTPSA id 3F8B71F3; Fri, 14 Jun 2019 12:26:57 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Bad SSD drive - what happens with unreadable data From: peter.blok@bsd4all.org In-Reply-To: Date: Fri, 14 Jun 2019 12:26:56 +0200 Cc: freebsd-scsi@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Jan Martin Mikkelsen X-Mailer: Apple Mail (2.3445.104.11) X-SourceIP: 94.209.122.217 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.3 cv=euyhMbhX c=1 sm=1 tr=0 a=0XONDDbZk2SpjknwKA3Xxg==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=dq6fvYVFJ5YA:10 a=xx_wHFljAAAA:8 a=6Q3WNqvRAAAA:8 a=6I5d2MoRAAAA:8 a=SpGXxCBClp5b3tWxNDIA:9 a=QEXdDO2ut3YA:10 a=wiPnYZwWLcOViUC1u154:22 a=I8PBwKCn76L9oNdl0isp:22 a=IjZwj45LgO3ly-622nXo:22 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-Rspamd-Queue-Id: E784A8C965 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of peter.blok@bsd4all.org designates 212.54.34.165 as permitted sender) smtp.mailfrom=peter.blok@bsd4all.org X-Spamd-Result: default: False [-3.40 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[6]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:smtp.ziggo.nl/16]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bsd4all.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: smtp.bsd4all.org]; RCPT_COUNT_TWO(0.00)[2]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-0.78)[-0.783,0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-0.71)[ipnet: 212.54.32.0/20(-2.82), asn: 33915(-0.75), country: NL(0.01)]; RECEIVED_SPAMHAUS_PBL(0.00)[217.122.209.94.zen.spamhaus.org : 127.0.0.11]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:33915, ipnet:212.54.32.0/20, country:NL]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[165.34.54.212.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jun 2019 10:27:12 -0000 Hi Jan, Yes, I noticed the =E2=80=9Cclone=E2=80=9D wasn=E2=80=99t growing during = the read errors and read the manual page.But I ended up using ddrescue. Peter > On 14 Jun 2019, at 11:56, Jan Martin Mikkelsen = wrote: >=20 > Hi, >=20 > You need to add =E2=80=9Csync" to get the unreadable areas filled with = zeros. Something like "dd conv=3Dsync,noerror bs=3D4k=E2=80=9D is = probably good. >=20 > Regards, >=20 > Jan. >=20 >> On 13 Jun 2019, at 13:02, peter.blok@bsd4all.org wrote: >>=20 >> Hi, >>=20 >> I have a bad SSD drive. If I read it with dd and conv=3Dnoerror, what = happens with the unreadable areas? Does it fill with zeroes, or does the = driver still copy what it was able to read? >>=20 >> I=E2=80=99m getting ATA status 51 back, many blocks in a row. = Followed by chunks of readable data, followed by unreadable data. >>=20 >> Is there a modepage or something else to tell the drive to pass on = the bad data? >>=20 >> Any other ideas? >>=20 >> Peter >>=20 >>=20 >>=20 >>=20 >> _______________________________________________ >> freebsd-scsi@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-scsi >> To unsubscribe, send any mail to = "freebsd-scsi-unsubscribe@freebsd.org" >=20 From owner-freebsd-scsi@freebsd.org Sat Jun 15 08:11:03 2019 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A85815C00C1 for ; Sat, 15 Jun 2019 08:11:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 058E26C42D for ; Sat, 15 Jun 2019 08:11:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B7EA315C00BF; Sat, 15 Jun 2019 08:11:02 +0000 (UTC) Delivered-To: scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A552F15C00BE for ; Sat, 15 Jun 2019 08:11:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F3706C427 for ; Sat, 15 Jun 2019 08:11:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7D8759053 for ; Sat, 15 Jun 2019 08:11:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x5F8B1CB027097 for ; Sat, 15 Jun 2019 08:11:01 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x5F8B1DC027095 for scsi@FreeBSD.org; Sat, 15 Jun 2019 08:11:01 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: scsi@FreeBSD.org Subject: [Bug 219857] panic in scsi_cd code Date: Sat, 15 Jun 2019 08:11:00 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bugzilla.freebsd@omnilan.de X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ken@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jun 2019 08:11:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219857 --- Comment #24 from Harald Schmalzbauer --- Kenneth's patch successfully prevented my machines from panicing for almost= one year. I don't use ODD regularly, so the fact that I don't see any other side effect nor regression isn't counting much, but I remember staring at console while hypervisor reboots after ejecting (removing USB-) OD(D)... Unfortunately it seems that 11.3 again ships with this trip-wire/trip-mine. I'd vote for commiting it as soon as possible. Thanks, -harry --=20 You are receiving this mail because: You are on the CC list for the bug.=