From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc3 Firefox/1.0.7 Description of problem: I can't get the i2o raidutil utility to work on the latest Fedora Core 4 kernels. I did a brand new install of FC4, and the i2o raidutils rpm from http://i2o.shadowconnect.com/download.php worked fine (after I created /dev/i2o/ctl). But when I rebooted with all the upgrades, I got the EngineConnect failed compatibility error messages. This is repeatable -- raidutil runs fine with kernel 2.6.11-1.1369_FC4smp but fails with 2.6.14-1.1644_FC4smp or 2.6.14-1.1644_FC4 I have another FC4 machine running 2.6.12-1.1456_FC4 on which raidutil works, so it looks like the problem appeared after 1456. I'll try to do some more tests with different kernel versions. Version-Release number of selected component (if applicable): kernel-2.6.14-1.1644_FC4smp How reproducible: Always Steps to Reproduce: 1. install Fedora Core 4 (with kernel 2.6.11-1.1369), install raidutils-0.0.6-1.i386.rpm (and mknod /dev/i2o/ctl, etc) 2. /usr/bin/raidutil works fine 3. update to kernel 2.6.14-1.1644 4. raidutil doesn't work 5. reboot with either kernel to repeat Actual Results: osdIOrequest : File /dev/dpti17 Could Not Be OpenedEngine connect failed: COMPATIBILITY number Additional info:
I've done some more trials (on a different machine to the one I originally found the problem on) and got the following results: Doesn't work on: 2.6.14-1.1644_FC4smp 2.6.14-1.1637_FC4 2.6.13-1.1532_FC4 2.6.13-1.1526_FC4 Works on: 2.6.12-1.1456_FC4 2.6.11-1.1369_FC4 So it looks like something happened with 2.6.13.
I am also having the same problems. The card in this case is an Adaptec 2100S and I am currently using the following kernel: 2.6.14-1.1637_FC4 I will see if I can give this a test with FC5 test1 asap, at least that might provide a path out of the current situation.
Hello, could you please verify that you have enabled ioctls like mentioned now in the FAQ: http://i2o.shadowconnect.com/faq.php#raidutils_verify Thank you very much. Best regards, Markus Lidel
Yes, I'm running # temporary hack until i2o modules do this automatically mknod /dev/i2o/ctl c 10 166 in /etc/rc.local and I have a /usr/local/sbin/raidutil that does modprobe i2o_proc modprobe i2o_config /usr/bin/raidutil $* And I can reliably demonstrate the problem by rebooting the same machine with different kernels (see above for which ones). I don't build my own kernels so I can't test the "enable ioctls" bit - but is it possible that more recent FC 4 kernels have been built without it?
Hello, yep, it's most likely, because ioctl isn't enabled by default. Best regards, Markus Lidel
Is there some way we can enable ioctls in FC 4 kernels more recent than 2.6.12-1.1456_FC4 (without recompiling a kernel)? Barring that, could we have it included in the next Fedora Core kernel update? Features like that really shouldn't be turned off by upgrades -- it's disconcerting having systems stop working without warning.
Hello, because it's only the i2o_config.ko module, you only have to compile this module on a machine and load it... Nothing else is needed... It's my fault, because the ioctls was not enabled by default when the config option was added... Best regards, Markus Lidel
Thanks, I'll have a go at rebuilding the i2o_config module. Can we make sure this is fixed (ie, ioctls is enabled and raidutil works) in both the next FC 4 kernel update and in FC 5? (I haven't tried FC 5 at all, but Dave said he was going to so I'll leave that to him.)
I've reenabled the ioctls in CVS. They'll be back on in the next kernel update.
While I can't confirm that FC5 works (I have it running, but not on a machine with this controller), I can confirm that raidutils works with the latest FC4 kernel. Thanks to all involved. [root@luggage ~]# uname -a Linux luggage.darkglobe.int 2.6.14-1.1653_FC4 #1 Tue Dec 13 21:32:09 EST 2005 i686 athlon i386 GNU/Linux [root@luggage ~]# mknod /dev/i2o/ctl c 10 166 [root@luggage ~]# modprobe i2o_config [root@luggage ~]# raidutil -L all RAIDUTIL Version: 3.31 Date: 8/12/2002 LINUX CLI Configuration Utility Adaptec ENGINE Version: 3.31 Date: 8/12/2002 Adaptec LINUX SCSI Engine # b0 b1 b2 Controller Cache FW NVRAM Serial Status --------------------------------------------------------------------------- d0 -- ADAP2100S 16MB 370F CHNL 1.1 BF0A337239XOptimal Physical View Address Type Manufacturer/Model Capacity Status --------------------------------------------------------------------------- d0b0t0d0 Disk Drive (DASD) MAXTOR ATLAS10K4_36WLS 35074MB Optimal d0b0t1d0 Disk Drive (DASD) MAXTOR ATLAS10K4_36WLS 35074MB Optimal d0b0t2d0 Disk Drive (DASD) MAXTOR ATLAS10K4_36WLS 35074MB Optimal d0b0t4d0 Disk Drive (DASD) MAXTOR ATLAS10K4_36WLS 35074MB Optimal * REST OF LISTING SNIPPED! *