On Thu, Aug 16, 2018 at 09:23:23AM +0200, Martin Husemann wrote: > Yes. This sounds like a device driver bug - which driver is it?
ahcisata0 at pci0 dev 31 function 2: vendor 8086 product 8c02 (rev. 0x05) ahcisata0: interrupting at ioapic0 pin 19 ahcisata0: AHCI revision 1.30, 4 ports, 32 slots, CAP 0xc730ff43<EMS,PSC,SSC,PMD ,ISS=0x3=Gen3,SCLO,SAL,SALP,SNCQ,S64A> atabus0 at ahcisata0 channel 0 atabus2 at ahcisata0 channel 4 wd0 at atabus0 drive 0 wd0: <ST2000VX000-1CU164> wd0: 1863 GB, 3876021 cyl, 16 head, 63 sec, 512 bytes/sect x 3907029168 sectors wd2 at atabus2 drive 0 wd2: <ST2000VX000-1CU164> wd2: 1863 GB, 3876021 cyl, 16 head, 63 sec, 512 bytes/sect x 3907029168 sectors raid3: RAID Level 1 raid3: Components: /dev/wd2a /dev/wd0a raid3: Total Sectors: 3906766944 (1907601 MB) -- Emmanuel Dreyfus m...@netbsd.org