Bad SSD drive - what happens with unreadable data

[peter.blok at bsd4all.org]

Hi Jan,

Yes, I noticed the “clone” wasn’t 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 <janm at transactionware.com> wrote:
> 
> Hi,
> 
> You need to add “sync" to get the unreadable areas filled with zeros. Something like "dd conv=sync,noerror bs=4k” is probably good.
> 
> Regards,
> 
> Jan.
> 
>> On 13 Jun 2019, at 13:02, peter.blok at 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?
>> 
>> Peter
>> 
>> 
>> 
>> 
>> _______________________________________________
>> freebsd-scsi at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-scsi
>> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe at freebsd.org"
>