As for the minor number, the disk device will have a minor. The reason however for the requirement of upgrade is that Amanda had started to exhibit regression errors which weren’t being fixed in Beans 1, Distro Ubuntu Last updated March 4, latest version is 3. This server is an Amanda backup server, so this is more than a mere annoyance – if I can’t find a solution I’ll have to revert it to This should not affect. The current list of supported controllers for hpsa:

Uploader: Sanos
Date Added: 22 April 2017
File Size: 37.32 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 43226
Price: Free* [*Free Regsitration Required]

Fixed a bug found by the L1 test suite. Here’s the man page. Use these for systems using 2. The hpsa driver is a SCSI driver, while the cciss driver is a block driver. If removing the module was intended, why is the package “cciss-vol-status” still offered? This patch will get called only once for each controller. For a new install of a distribution using the hpsa driver, the “cciss.

[server] CCISS kernel mod missing from USLTS rendering server unbootable after upgrade

The reason however for the requirement of upgrade is that Amanda had started to exhibit kerenl errors which weren’t being fixed in After updating everything to the latest i tried to reboot. This kerneo because at driver init time, the SCSI core may not yet be initialized because the driver is a block driver and attempting to register it with the SCSI core in such a case would cause a hang.


The driver then notifies the SCSI midlayer of these changes. It can be as simple as the new kernel is misconfigured somehow? If you’ve been using cciss already on these controllers, it is not recommended that you attempt to upgrade your running system to switch from cciss to hpsa unless you have a very good reason to do so and kernl what you are doing.

CONFIG_BLK_CPQ_CISS_DA: Compaq Smart Array 5xxx support

The disks can actually come up in whatever order. Is the module in some other package which needs to be installed? Tags boot failureccissdriverlinux Thread Tools.

On that server I tried: It uses the same naming conventions that most disks use today. This option prevents the cciss driver from attempting to drive any controllers that the hpsa 4 driver is capable of controlling, which is to say, the cciss driver is restricted by this option to the following controllers: Added a procfs cviss so users can tell the driver to rescan our devices.

Join Date Sep Location Behind you! This is best done via an initialization script. This driver is known to work with the following cards: Join Date May Beans The suggested device naming scheme is: In this case, it is just a text file, documentation, meant for human consumption. If necessary, deb package will compile kernel as well. Use these for 2.


Note also that if no sequential access devices or medium changers are detected, the SCSI core will not be engaged by the action of the above script. Most likely, you do not need these, as the cciss driver has been in the Linux kernel for a very long time, and most distributions will already have a cciss driver which will work for you as is.

So with the newer kernel, and the newer driver, the system stalls when trying to mount the root partition, since the HPSA driver takes precedense but will not correctly present the drives to the system.

To continue using the CCISS ekrnel as before, the boot loader must be updated with a new kernel command line parameter. To install, download Debian cciss source package. Now I’m torn between finding a solution to this problem cciss vs.

See these search results from hp. Debian package is greatly simplified.

Your distribution may differ.

Author: admin