Domenico, (and everyone else thanks) Thank you for your input. This seems to be a deeper rabbit hole than I expected.
I tried (echo "1" > /sys/bus/scsi/drivers/sd/<SCSI-ID>/delete) and sure enough it cleanly wiped out the /dev/sdc and the /sys/block/ device etc. Upon reboot, it was back and had the same old Buffer I/O errors and block errors on reboot and recreated the same /dev/sdc etc. So I started digging through the udev / udevinfo commands and comparing with lspci to find that yes the ghost /dev/sdc was hanging (supposedly) off my Qlogic Fiber Card, I then launched my Navisphere to make sure it only had one LUN being handed out (and it is). So I got even more confused. I've not got much SAN experince and I was handed this with my servers. I then took a look at the SANSurfer Cli tool (sfcli), I was able to see that the HBA does see (looks like it) 2 LUNS of exaclty the same size (I.E. it's really just the one I guess). The LUN that is being presented to the machine is being mounted as sdd. (the offender I'm hunting down is sdc). Do you think it's possible that when I delete the sdc with the above "echo 1" you suggested and reboot, that the kernel is trying to assign the presented LUN as the next device in line sdc? (since sda, sdb and sdd are taken). I don't know anything about the persistent binding (yet) but I'll be going through all the docs from the Qlogic and EMC products tomorrow (now that I know what to start looking at). Thanks for any other advice (if you can suggest any). Thanks again for responding the first time. On Jan 31, 2008 2:39 AM, Domenico Viggiani <[EMAIL PROTECTED]> wrote: > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > > On Behalf Of dbcooper > > Sent: Thursday, January 31, 2008 12:46 AM > > > > I got a handful of servers handed over to me and I noticed one > > of them (on boot up) was complaining about /dev/sdc having bad > > blocks and other various errors. > If kernel finds it during bootstrap, then this device is detected and thus > it exists! > But it could be also a passive path to an active-passive array (like EMC > Clariion): in this case, you can safely ignore it. > > BTW, you can remove a no more existing SCSI drive: > - rebooting > - or running: > echo 1 > /sys/bus/scsi/drivers/sd/<SCSI-ID>/delete > > -- > Domenico Viggiani > > > > _______________________________________________ > rhelv5-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/rhelv5-list >
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
