Updating suse kernel

Rated 4.3/5 based on 661 customer reviews

The Attachmate Group acquired Novell and split Novell and SUSE into two autonomous subsidiary companies.

After The Attachmate Group merged with Micro Focus in November 2014, SUSE became its own business unit.

The changes to the boot loader can then be applied as above, and then the system will boot/reboot using the CCISS driver and the newer kernel.

The initial release of the community project was a beta version of SUSE Linux 10.0. The community project offers a rolling release version called open SUSE Tumbleweed, which is continuously updated with tested, stable packages.

The difference between the two drivers can be summarized as follows: CCISS is a block storage driver, that serve the disks directly, not using SCSI transport.

The disks appear with device names like "/dev/cciss/c0d0p1", (First partition on first disk on first controller). It uses the same naming conventions that most disks use today.

The scsi naming convention "/dev/sda1" can cause lots of confusion regarding multipath i SCSI, DMRAID and MDRAID disks. Not the CCISS disks, which have a fixed order naming.

Personally i like the CCISS naming convention, since it makes it easier to keep separate the i SCSI disks et cetera from the system disk.

The system has one HP Smartarray P400 RAID controller with 512 MB battery backed cache, and four 2TB WB RE4 disks split up in two RAID5 logical disks - One small for the system "/dev/cciss/c0d0", and one large work disk "/dev/cciss/c0d1".

Before updating, the system was running linux kernel version 3.11.10-34 and everything was working 100%.

In case the system got updated with the new kernel before the above mentioned patch of the boot parameters, and did not succed in booting.

Then the system can be booted to the previous kernel version by selecting it in the GRUB2 boot menu.

Leave a Reply