On Fri, Apr 13, 2012 at 2:02 PM, Paul A <razor at meganet.net> wrote: > I'm running Raid with scsi disks so I'm assuming it's needed correct? iSCSI is for carrying SCSI command s and data over IP networks. I don't know how your RAID is set up, but it isn't normally done with iSCSI. See, for example: http://en.wikipedia.org/wiki/ISCSI versus http://en.wikipedia.org/wiki/RAID > -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf > Of Dale Dellutri > Sent: Friday, April 13, 2012 1:32 PM > To: CentOS mailing list > Subject: Re: [CentOS] upgrade issue > > On Fri, Apr 13, 2012 at 12:19 PM, Paul A <razor at meganet.net> wrote: >> I have an old dell 2450 that was running kernel 2.6.18-308.1.1.el5 I >> then upgraded it via yum to 2.6.18-308.1.1.el5. Now when the server >> boots to the new kernel, 2.6.18-308.1.1.el5 it hangs on "starting >> iSCSI" and the weird thing is when I tried to switch back to the older >> 2.6.18-308.1.1.el5 kernel it works fine but the network script fails >> to start. I'm not really sure what I should do, if someone can give me >> an idea on what I need to do to fix the iSCSId issue on the new kernel >> or revert back to the old kernel and fix the network issue. The odd >> thing is both kernel load the e100 network driver but on the older kernel > I can get the network script to start. >> >> I would appreciate some help. > > Do you need iscsi? If not, boot with the old kernel, and disable iscsi > > # chkconfig --list | grep iscsi > (will probably show iscsi and iscsid) > > Then > # chkconfig iscsi off > # chkconfig iscsid off > > Then reboot with the new kernel. > > -- > Dale Dellutri > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos -- Dale Dellutri