On Fri, Apr 13, 2012 at 2:25 PM, Paul A <razor@xxxxxxxxxxx> wrote:
> Dale, I disabled it and the server came up but im seeing all sorts of kernel
> errors when its disabled ( see below ). If this can't be fixed I would
> really like to boot the previous kernel however the network script won't
> start. Im not really sure how upgrading the kernel caused the network to
> stop working on the previous kernel.
Nor do I know how upgrading could do that. What other changes have
you made?
Two questions:
1. Is the previous kernel (with iscsi and iscsid enabled) giving any error
messages in the log when you attempt to boot it.
2. Is your RAID using local disks or disks on an iscsi target device?
If local, iscsi shouldn't have anything to do with RAID. If on an iscsi
target device, then you need iscsi and iscsid enabled.
I'd suggest re-enabling iscsi and iscsid and try to solve the network problem
with the old kernel.
> -----Original Message-----
> From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On Behalf
> Of Dale Dellutri
> Sent: Friday, April 13, 2012 3:07 PM
> To: CentOS mailing list
> Subject: Re: upgrade issue
>
> On Fri, Apr 13, 2012 at 2:02 PM, Paul A <razor@xxxxxxxxxxx> 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@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On
>> Behalf Of Dale Dellutri
>> Sent: Friday, April 13, 2012 1:32 PM
>> To: CentOS mailing list
>> Subject: Re: upgrade issue
>>
>> On Fri, Apr 13, 2012 at 12:19 PM, Paul A <razor@xxxxxxxxxxx> 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@xxxxxxxxxx
>> http://lists.centos.org/mailman/listinfo/centos
>>
>> _______________________________________________
>> CentOS mailing list
>> CentOS@xxxxxxxxxx
>> http://lists.centos.org/mailman/listinfo/centos
>
>
>
> --
> Dale Dellutri
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
--
Dale Dellutri
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
