Hey ho again-- I don't *think* this is a major issue, as everything works, but since my system is reasonably stable atm, I'm working on my 'orange flag' items (disturbing things that are not an emergency).
During boot, when devices are being set up, services loaded, and drives mounted, I get a whole lotta the following: nbd110: Request when not-ready end_request: I/O error, dev nbd110, sector 0 nbd111: Request when not-ready end_request: I/O error, dev nbd111, sector 0 nbd112: Request when not-ready end_request: I/O error, dev nbd112, sector 0 nbd113: Request when not-ready end_request: I/O error, dev nbd113, sector 0 nbd114: Request when not-ready end_request: I/O error, dev nbd114, sector 0 nbd115: Request when not-ready end_request: I/O error, dev nbd115, sector 0 nbd116: Request when not-ready end_request: I/O error, dev nbd116, sector 0 nbd117: Request when not-ready end_request: I/O error, dev nbd117, sector 0 nbd118: Request when not-ready end_request: I/O error, dev nbd118, sector 0 nbd119: Request when not-ready end_request: I/O error, dev nbd119, sector 0 nbd120: Request when not-ready end_request: I/O error, dev nbd120, sector 0 nbd121: Request when not-ready end_request: I/O error, dev nbd121, sector 0 nbd122: Request when not-ready end_request: I/O error, dev nbd122, sector 0 nbd123: Request when not-ready end_request: I/O error, dev nbd123, sector 0 nbd124: Request when not-ready end_request: I/O error, dev nbd124, sector 0 nbd125: Request when not-ready end_request: I/O error, dev nbd125, sector 0 nbd126: Request when not-ready end_request: I/O error, dev nbd126, sector 0 nbd127: Request when not-ready end_request: I/O error, dev nbd127, sector 0 device-mapper: dm-linear: Device lookup failed device-mapper: error adding target to table This is just the end of the list; the listed nbd devices start from 0. I've checked Google, and now I know that nbd stands for 'network block device". I also know that I have enabled network block devices in my kernel (currently gentoo-sources 2.6.11-r6), because I thought it might be useful when setting up Samba to share to and receive shares from my bf's Windows computer. But even though I have not yet configured Samba (it is, however, installed and running; it just doesn't work because I haven't configured it), and even if nbd has nothing to do for or against it, I don't see that I should be getting 127 unusable devices. Why has udev not removed them, for example (no, I'm not using the tarball; I checked /etc/conf.d/rc)? Can I (as root) remove them without issue? I've just downloaded a new kernel; if I disable ndb, will that get rid of them? Should I actually disable nbd in the kernel (or is it useful for something like Samba)? Or do I just need to configure Samba (client and server) so that *something* knows what to do with these devices, and that will do it? I don't have a clue (obviously), so any suggestions apreciated. In case it's relevant, I will also mention that this installation is 'converted' to real Gentoo from an installation of "that Gentoo-based OS with an installer" (I was just out of patience, but whether it was worth it is offically questionable), so if it's possible that this device creation/persistence is caused by a holdover system utility from that OS which I'm unaware of and which was not removed during the conversion process, please let me know-- that's another aspect of the "orange flag" cleanup that I'd like to handle as well. Thanks, Holly -- gentoo-user@gentoo.org mailing list
