> I created it with bioctl, but my version is from a September 1 snapshot > so it is before your fix.
There is a good chance that the hotspare does not work prior to that fix. I'd say this explains what you see. > The server ran flawlessly for 2 years now, and I'll bet it's been a year > since I've even slid it forward enough in the rack to get the cover off. > Do cables go bad with use? No but they might have been dislodged when you moved the server. > I may try to replace the safte0 enclosure this weekend then. It could be that it is simply hung (GEM chips tend to do that). Power cycle the whole thing to see what happens. If the GEM is hung there is a chance that the SCSI bus is hung too. This can easily lead to the issues you have been seeing (I have seen this in the past on other enclosures with a GEM chip). > So the last combination combination I tried is the correct one? It > still fails here: > [EMAIL PROTECTED]:/usr/src $ sudo bioctl -q sd0 > bioctl: DIOCINQ: Invalid argument I should have said "not raided disks". I guess I could add that functionality to RAID disks as well even though it is mostly bogus it is nice if it all works the same. > Thanks for your input and expertise, Marco. If you get a moment, I > posted a follow-up as a reply to Dieter's response. There are more > anomalies afoot I fear, especially with drives just not showing up, even > in the crtl-m bios. If drives are missing and other weird things are happening you can assure yourself of bad hardware somewhere in the chain. Again check cables (maybe they were under tension and something snapped when you moved it), drives, the enclosure itself etc. A bad device can hang the bus and only limited IO will make it through (if any); this causes all kinds of mayhem on SCSI busses and is the primary reason why SCSI went SAS (point to point instead of bus). Figuring this out can be tedious and painful so be prepared to spend enough time on it.
