Re: kern/54289: wd1 fails to be identified properly

[jdbaker%consolidated.net@localhost]

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

From: jdbaker%consolidated.net@localhost
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/54289: wd1 fails to be identified properly
Date: Wed, 14 Aug 2019 23:44:54 -0500

 I've discovered another device which appears to be affected by
 this problem:
 
 [...]
 [   1.0201435] pci5: i/o space, memory space enabled, rd/line, wr/inv ok
 [   1.0201435] siisata0 at pci5 dev 4 function 0: CMD Technology SiI3124 
 SATALink (rev. 0x02)
 [   1.0201435] siisata0: interrupting at msi1 vec 0
 [   1.0201435] siisata0: SiI3124, 3.0Gb/s
 [   1.0201435] siisata0: 32-bit 66MHz PCI
 [   1.0201435] atabus0 at siisata0 channel 0
 [   1.0201435] atabus1 at siisata0 channel 1
 [   1.0201435] atabus2 at siisata0 channel 2
 [   1.0201435] atabus3 at siisata0 channel 3
 [...]
 [   1.7933982] siisata0 port 0: device present, speed: 3.0Gb/s
 [   1.7933982] siisata0 port 1: device present, speed: 3.0Gb/s
 [   1.7933982] siisata0 port 2: device present, speed: 3.0Gb/s
 [   1.7933982] siisata0 port 3: device present, speed: 3.0Gb/s
 [...]
 [   1.8034036] wd0 at atabus0 drive 0
 [   1.8034036] wd0: <Hitachi HDS721010CLA332>
 [   1.8034036] wd0: drive supports 16-sector PIO transfers, LBA48 
 addressing
 [   1.8034036] wd0: 931 GB, 1938021 cyl, 16 head, 63 sec, 512 bytes/sect 
 x 1953525168 sectors
 [...]
 [   7.8264245] wd0: autoconfiguration error: IDENTIFY failed
 [   7.8264245] autoconfiguration error: wd0: unable to open device, 
 error = 5
 [  10.8338789] wd0(siisata0:0:0): using PIO mode 0
 [  10.8338789] wd1 at atabus1 drive 0
 [  16.8588129] wd1: autoconfiguration error: IDENTIFY failed
 [  16.8588129] wd1: fixing 0 sector size
 [  16.8588129] wd1: secperunit and ncylinders are zero
 [  19.8662676] wd1(siisata0:1:0): using PIO mode 0
 [  19.8662676] wd2 at atabus2 drive 0
 [  25.8912017] wd2: autoconfiguration error: IDENTIFY failed
 [  25.8912017] wd2: fixing 0 sector size
 [  25.8912017] wd2: secperunit and ncylinders are zero
 [  28.8986561] wd2(siisata0:2:0): using PIO mode 0
 [  28.8986561] wd3 at atabus3 drive 0
 [  34.9235903] wd3: autoconfiguration error: IDENTIFY failed
 [  34.9235903] wd3: fixing 0 sector size
 [  34.9235903] wd3: secperunit and ncylinders are zero
 [  37.9310448] wd3(siisata0:3:0): using PIO mode 0
 [...]
 
 Unfortunately, these devices form half of my file server's RAID
 and they all got marked as FAILED.  Even if I reboot netbsd-8 where
 the disks are properly identified, they are considered FAILED and the
 RAID won't initialize.
 
 [  44.3777787] wd0: autoconfiguration error: IDENTIFY failed
 [  44.3777787] opendisk: can't open dev wd0 (5)
 [  50.4529393] wd0: autoconfiguration error: IDENTIFY failed
 [  50.4529393] opendisk: can't open dev wd0 (5)
 [  56.5682603] wd0: autoconfiguration error: IDENTIFY failed
 [  56.5682603] raid0: RAID Level 5 rotated sparing
 [  56.5682603] raid0: Components: component0[**FAILED**] 
 component1[**FAILED**] component2[**FAILED**] component3[**FAILED**] 
 /dev/wd5a /dev/wd6a /dev/wd7a /dev/wd8a
 [  56.5682603] raid0: Total Sectors: 11721149952 (5723217 MB)
 [  56.5682603] raid0: failed to create a dag. Too many component 
 failures.
 [  56.5682603] raid0d: error reading fsbn 0 (raid0 bn 0; cn 0 tn 0 sn 0)
 [  56.5682603] raid0: dos partition I/O error
 [  56.5682603] raid0: failed to create a dag. Too many component 
 failures.
 [  56.5682603] raid0d: error reading fsbn 0 of 0-31 (raid0 bn 0; cn 0 tn 
 0 sn 0)
 [  56.5682603] raid0: failed to create a dag. Too many component 
 failures.
 [  56.5682603] raid0d: error reading fsbn 1 (raid0 bn 1; cn 0 tn 0 sn 1)
 [  56.5682603] WARNING: 9 errors while detecting hardware; check system 
 log.
 [  56.5682603] boot device: wd4
 [  56.5682603] root on wd4a dumps on wd4b
 [  56.6688152] root file system type: ffs
 [  56.6789022] kern.module.path=/stand/amd64/9.0/modules
 [  73.7538756] wsdisplay0: screen 1 added (80x25, vt100 emulation)
 [  73.7538756] wsdisplay0: screen 2 added (80x25, vt100 emulation)
 [  73.7538756] wsdisplay0: screen 3 added (80x25, vt100 emulation)
 [  73.7639110] wsdisplay0: screen 4 added (80x25, vt100 emulation)
 [ 120.9231258] raid0: failed to create a dag. Too many component 
 failures.
 [ 120.9231258] raid0d: error reading fsbn 0 (raid0 bn 0; cn 0 tn 0 sn 0)
 [ 120.9231258] raid0: dos partition I/O error
 
 Sorry for the poor (or lack of) formatting.  I'm having to use my ISP's
 web-mail until I can get things straightened out here.
 
 John D. Baker