Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Our RHEL 3.0 u4 server has started displaying these error messages in the system logs and I can't for the life of me figure out what's causing them.
I've dug around google for the past few days with no success.
Has anyone else encountered this message?
Any suggestions as to where I might start looking to try and figure out what's going on?
It doesn't appear to be causing any problems, other than flooding our system logs with junk messages.
Googling on the char-??? comes up with this as the third hit which links to another about a LSI 1030 RAID controller since you say it does not cause any problems I would say you don't have this card installed so comment out the line in the modules.conf that has the alias for it reboot and the problem should go away.
Thanks for the quick response. I did already find that link, but none of the enteries below appear to match what the guy was talking about in the link.
Can I assume that the mptscsih is probably blame?
/etc/modprobe.conf
Code:
alias eth0 tg3
alias eth1 tg3
alias scsi_hostadapter mptbase
alias scsi_hostadapter1 mptscsih
alias scsi_hostadapter2 cciss
alias usb-controller usb-uhci
alias usb-controller1 ehci-hcd
alias block-major-43 off
Thanks for the quick response. I did already find that link, but none of the enteries below appear to match what the guy was talking about in the link.
Can I assume that the mptscsih is probably blame?
/etc/modprobe.conf
Code:
alias eth0 tg3
alias eth1 tg3
alias scsi_hostadapter mptbase
alias scsi_hostadapter1 mptscsih
alias scsi_hostadapter2 cciss
alias usb-controller usb-uhci
alias usb-controller1 ehci-hcd
alias block-major-43 off
I would say so just try an off alias like the block-major-43 then to see if that stops it, worse case move the mptscsih.ko module from your kernel /lib tree.
This is due to the NBD (Network Block Device) driver missing.
No worries, it's just used if you have some kind of software doing disc-things-off-the-net (iSCSI or DRBD for example).
Since the device entries exist in the /dev directory (/dev/nb*), some process tries to find out what's going on these.. for istance the automounter in the GUI or a pvscan (in RHEL3 there's LVM1 which has no filter in the seek for physical volumes like the LVM2 counterpart).
Nothing worry, but it's recommended, as long as you don't use the NBd feature, to disable it either as suggested in the modprobe.conf or deleting the nb* entries in the /dev directory.
Would you need it back, just issue a MAKEDEV or mknod as per documentation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.