[Info-vax] recognizing SCSI disks
Hans Bachner
hans at bachner.priv.at
Thu Oct 3 19:35:19 EDT 2019
Phillip Helbig (undress to reply) schrieb am 03.10.2019 um 23:56:
> [snip]
>
> Perhaps unrelated to the shutdown and power-off, or perhaps not, a BA356
> was making some loud noises. It didn't sound like a bad disk, but you
> never know. I removed them one by one, but the noise didn't go away. I
> figured it was the fan or something. So, I swapped the disks into
> another box. This solved the problem, and the node is back in the
> cluster now. Nice to have spare hardware sitting around; thanks to all
> who have given me stuff over the years (or, by now, decades).
>
> [snip]
>
> As the model was identical, I though that I could just connect it up and
> boot, but the console couldn't see the disks.
How did you determine that the "console couldn't see the disks"?
Using just >>> SHOW DEV isn't necessarily sufficient; IIRC it takes
a >>> SHOW CONFIG to rescan the SCSI bus and detect what's out there.
Hans.
> I power-cycled the
> machine (a PWS), and then everything is OK.
>
> Why was it necessary to power-cycle the machine so that it could see the
> disks? I remember once when I pulled a SCSI cable by accident; the
> disks (including the system disk )went into mount verification, then
> came back when I plugged the cable back in. That seems much more
> dangerous than unplugging the cable at the console prompt. Of course,
> it is a different box (but same connector at the top of the box, the
> removable one where the cable plugs in), but surely the SCSI controller
> doesn't need the ID of the box (assuming that there is one).
>
More information about the Info-vax
mailing list