by Tomo » Sep 3rd, '08, 01:29
I'm logged into Linux as root, as it happens...
I'm at the point of having to admit defeat. This never happened before. I can usually figure out anything in Linux, especially under pressure of a deadline, but this part of this operating system simply doesn't bloody work. I've recompiled the kernel, and it now reports a recoverable error condition that I can't find out about because the message that appears simply says that "an internal error has occurred", and that it's in an unrelated module. Installing from scratch and starting again shows cause and effect. The YaST2 system configuration tool crashes when it tries to save any modifications to an initial iSCSI target configuration. The boot log says the iSCSI daemon is running perfectly but querying its status with the relevant init.d control script says it's unused. It won't restart, choosing instead to refuse to stop. So, any changes that do get written before YaST2 crashes (believe me, it happens about one in ten tries) can only be applied by rebooting the whole operating system. The whole iSCSI subsystem is mostly undocumented, and the online community guides are either about connecting to an iSCSI target, out of date, or actually wrong. Something is very badly broken here and there is no fix for it. And yet, I have a feeling that I'm missing something simple, something other than sleep, something that makes it all go. Something interesting.
More coffee and one last re-installation, methinks.
