Re: kern/58776: RAIDframe panic on I/O error during reconstruction

["Emmanuel Dreyfus via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR kern/58776; it has been noted by GNATS.

From: Emmanuel Dreyfus <manu%netbsd.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/58776: RAIDframe panic on I/O error during reconstruction
Date: Sun, 27 Oct 2024 16:09:24 +0000

 On Sun, Oct 27, 2024 at 04:00:03PM +0000, Greg Oster wrote:
 >  Do you know if the I/O error was on /dev/dk3 or on the other component 
 >  of raid1?  Did you catch anything else printed from the kernel?  What 
 >  does the RAID config look like for this setup?  (In particular, is 
 >  /dev/dk3 component 0 or component 1?)
 
 The I/O error happened on dk3. At some time I tried to swap the
 disks, and the I/O error followed the SATA port, hence the disk
 getting the failure has alwas been wd3 and the RAID component dk3. 
 
 Before the swap, I got the panic because of a write error on dk3. 
 After the swap, it was a read error on dk3.
 
 
 $ raidctl -s raid1
 Components:
             /dev/dk3: optimal
             /dev/dk2: failed
 No spares.
 Component label for /dev/dk3:
    Row: 0, Column: 0, Num Rows: 1, Num Columns: 2
    Version: 2, Serial Number: 20240729, Mod Counter: 25860
    Clean: No, Status: 0
    sectPerSU: 32, SUsPerPU: 1, SUsPerRU: 1
    Queue size: 100, blocksize: 512, numBlocks: 19532873568
    RAID Level: 1
    Autoconfig: Yes
    Root partition: No
    Last configured as: raid1
 /dev/dk2 status is: failed.  Skipping label.
 Parity status: DIRTY
 Reconstruction is 100% complete.
 Parity Re-write is 100% complete.
 Copyback is 100% complete.
 
 I initiated another raid1 reconstruction, I will provide you the
 exact kernel output. 
 
 Note that I plan to move the offending disk to another unused 
 SATA port in 14 hours in order to fix the setup. I hope I will
 not be able to reproduce the problem anymore.
 
 
 -- 
 Emmanuel Dreyfus
 manu%netbsd.org@localhost