Re: WDCTL_RST failed for drive 0 / wd0: IDENTIFY failed (SATA autodetection issue after installation)

[Matthias Petermann <mp%petermann-it.de@localhost>]

Hi Rin,

thank you for your quick response. I can first confirm that the 
controller installed in the system is ahcisata(4). I have two different 
model variants where the problem occurs - on one very reliably at every 
boot, and on the other almost after every cold start (and only two of 
four disks affected on the latter). I will build and test the kernel 
with AHCISATA_EXTRA_DELAY and give feedback in a timely manner.

Many greetings
Matthias

Am 24.05.2022 um 18:23 schrieb Rin Okuyama:
> Hi,
>
> The recent change for probe timing should only affect ahcisata(4).
> Is your SATA controller ahcisata(4)? If so,
>
> (1) please try kernel built with:
>
> ---
> options AHCISATA_EXTRA_DELAY
> ---
>
> If it works around the problem,
>
> (2) please send us full dmesg of your machine.
>
> Then, we can add your controller to the quirk list. At once it is
> registered to the list, AHCISATA_EXTRA_DELAY option is no longer
> required.
>
> Thanks,
> rin
>
> On 2022/05/25 0:49, Matthias Petermann wrote:
> > A small addendum: disabling the Intel Platform Trust technology in the 
> > BIOS did not help me (had read this in another post of the linked 
> > thread).
> >
> > However, by plugging in additional USB devices (a mouse) I apparently 
> > caused the necessary delay, which the disk would have needed in the 
> > first case to execute the WDCTL_RST without errors. This "workaround" 
> > is a shaky one though, an extremely close call. I don't even want to 
> > think about what I would do to a production server if this happened to 
> > me on a reboot.
> >
> > Kind regards
> > Matthias
> >
> >
> > Am 24.05.2022 um 17:31 schrieb Matthias Petermann:
> > > Hello all,
> > >
> > > with one of the newer builds of 9.99 (unfortunately I can't narrow it 
> > > down more) I have a problem on a NUC5 with a Seagate Firecuda SATA 
> > > hard drive (hybrid HDD/SSD).
> > >
> > > As long as I boot from the USB stick (for installation, as well as 
> > > later for booting the kernel with root redirected to the wd0) the 
> > > hard drive wd0 is recognized correctly and works without problems.
> > >
> > > When I boot directly from the wd0 hard drive, I get through the boot 
> > > loader fine, which also still loads the kernel correctly into memory. 
> > > However, when running the initialization or hardware detection, there 
> > > is then a problem with the initialization of wd0:
> > >
> > > ```
> > > WDCTL_RST failed for drive 0
> > > wd0: IDENTIFY failed
> > > ```
> > >
> > > The error pattern seems to be not quite rare and probably the closest 
> > > to it is this post:
> > >
> > > http://mail-index.netbsd.org/current-users/2022/03/01/msg042073.html
> > >
> > > Recent changes to the SATA autodetection timing are mentioned there. 
> > > This would fit my experience, since I had the problem neither with 
> > > 9.1 (build from 02/16/2021) nor with older 9.99 versions. Does anyone 
> > > know more specifics about this timing thing, as well as known 
> > > workarounds if there are any? I have several NUC5s with exactly this 
> > > model of hard drive running stably for several years - it would be a 
> > > shame if I now have to replace them for such a reason.
> > >
> > > Many greetings
> > > Matthias