Re: fsck strange output

2021-01-26 Thread Kirk McKusick
> From: Rozhuk Ivan > Date: Tue, 26 Jan 2021 17:08:41 +0300 > To: Kirk McKusick > Cc: freebsd-current@freebsd.org > Subject: Re: fsck strange output > > On Mon, 25 Jan 2021 15:40:12 -0800 > Kirk McKusick wrote: > > >> Please try this patch to fsck_

Re: fsck strange output

2021-01-26 Thread Rozhuk Ivan
On Mon, 25 Jan 2021 15:40:12 -0800 Kirk McKusick wrote: > Please try this patch to fsck_ffs and see if it fixes your problem. > > Kirk McKusick > > =-=-= > > *** sbin/fsck_ffs/inode.c.orig2021-01-07 15:04:04.969086284 > -0800 --- sbin/fsck_ffs/inode.c 2021-01-25

Re: fsck strange output

2021-01-26 Thread Nilton Jose Rizzo
> > > Rozhuk Ivan writes: > > > Disk is 100% alive, got same on other HW. > > A disk can be alive and still have individually unreadable sectors, > that is, IMO, the most common failure mode. > > Try: > recoverdisk -v /dev/whatever > > That will attempt to read all sectors on

Re: fsck strange output

2021-01-26 Thread Mark Millard via freebsd-current
Rozhuk Ivan rozhuk.im at gmail.com wrote on Tue Jan 26 00:58:07 UTC 2021 : > This happen on 4 different systems, that: > - based on Ryzen zen/zen+ > - FreeBSD 13 > > 2 systems have ECC that works and show no errors. This is just a example-contexts note: I've seen what appears to be the same

Re: fsck strange output

2021-01-25 Thread Rozhuk Ivan
On Mon, 25 Jan 2021 20:51:50 + "Poul-Henning Kamp" wrote: > > Disk is 100% alive, got same on other HW. > > A disk can be alive and still have individually unreadable sectors, > that is, IMO, the most common failure mode. > > Try: > recoverdisk -v /dev/whatever > > That will

Re: fsck strange output

2021-01-25 Thread Kirk McKusick
> From: Rozhuk Ivan > Date: Mon, 25 Jan 2021 23:29:33 +0300 > To: freebsd-current@freebsd.org > Cc: Rozhuk Ivan > Subject: fsck strange output > > Hi! > > I am on fresh 13 and on auto fsck got: > > Jan 25 23:14:13 3des kernel: Starting file system checks: &g

Re: fsck strange output

2021-01-25 Thread Poul-Henning Kamp
Rozhuk Ivan writes: > Disk is 100% alive, got same on other HW. A disk can be alive and still have individually unreadable sectors, that is, IMO, the most common failure mode. Try: recoverdisk -v /dev/whatever That will attempt to read all sectors on the disk. --

fsck strange output

2021-01-25 Thread Rozhuk Ivan
Hi! I am on fresh 13 and on auto fsck got: Jan 25 23:14:13 3des kernel: Starting file system checks: Jan 25 23:14:13 3des kernel: /dev/gptid/81241708-8948-11e9-b1ae-049226c061d6: CANNOT READ BLK: 11072 Jan 25 23:14:13 3des kernel: /dev/gptid/81241708-8948-11e9-b1ae-049226c061d6: UNEXPECTED