ARC-12x4 support is missing

linum

Renowned Member
Sep 25, 2011
99
3
73
I just tried to install the latest proxmox 3.1 ISO but the kernels fails to detect my ARC-1224 controller. Looking at the source of the proxmox kernel it seems there is arcmsr.1.20.0X.15-110330.zip included but this release is missing support for the ARC-12x4 controller. Any change that the release arcmsr.1.20.0X.15-110330.zip will be included soon?

I will recompile the promox kernel tomorrow but it would be much easier if the current ARECA driver release will be included soon.

And thanks for the great product.
 
pls post a link to your card and the needed driver.
 
Just looking at the kernel sources and found that there's already support to included new areca drivers. I've reenabled the Makefile commands and try to compile a kernel. Maybe this will work right out of the box.

Just looking (a few minutes) at the developer documentation there seems to be no information how to update the promox ISO to allow the newer arcmsr driver to be available at install time. Is this information how to update a driver and create a new ISO image?
 
The kernel already include a driver with version 1.20.00.15.el6u2 2010/08/05.
That is why we removed the other code (arcmsr.1.20.0X.15-110330.zip)
 
I just try to rebuild the proxmox iso but my iso images is much bigger than expected (I removed the old kernel already). What parameters or script do you use to build the ISO image?

I can just install the kernel since I can't see any raid volume with the old iso. Maybe I could try to restore a fresh promox install via a rescue CD.
 
I just try to rebuild the proxmox iso but my iso images is much bigger than expected (I removed the old kernel already). What parameters or script do you use to build the ISO image?

we use mkzftree to compress the content.
 
I tried to recreate the proxmox boot CD since the current sysrecue CD didn't recognize the Areca ARC-12x$ raid controller too. So I can't even clone proxmox from a working setup. To recreate the proxmox ISO I've done this:

mkdir proxmox-old proxmox-new pve-kernel
mount -o loop ../proxmox-ve_3.1-93bf03d4-8.iso proxmox-old
rsync -aPHAX proxmox-old/* proxmox-new/
cd pve-kernel
ar p ../../pve-kernel-2.6.32-27-pve_2.6.32-116_amd64.deb data.tar.gz | tar zx
cd ../proxmox-new/lib/modules
rm -rf 2.6.32-26-pve
mv ../../../pve-kernel/lib/modules/2.6.32-27-pve .
cd ../../boot
rm config-2.6.32-26-pve System.map-2.6.32-26-pve vmlinuz-2.6.32-26-pve
cp ../../pve-kernel/boot/* .
cd isolinux
cp ../vmlinuz-2.6.32-27-pve linux26
cd ../../proxmox/packages
rm pve-kernel-2.6.32-26-pve_2.6.32-114_amd64.deb
cp ../../../../pve-kernel-2.6.32-27-pve_2.6.32-116_amd64.deb .
sed -i 's/pve-kernel-2.6.32-26-pve_2.6.32-114_amd64.deb/pve-kernel-2.6.32-27-pve_2.6.32-116_amd64.deb/' Packages
sed -i 's/pve-kernel-2.6.32-26-pve/pve-kernel-2.6.32-27-pve/' Packages
sed -i 's/^Version: 2.6.32-114/Version: 2.6.32-116/' Packages
sed -i 's/^Size: 33065480/Size: 33071232/' Packages
sed -i 's/^MD5sum: bf1df2436d9dd4ef42b2007c2a81b720/MD5sum: 2ea4c25ad2877fdcd021edd123faa57e/' Packages
sed -i 's/^SHA1: 033ff4ce98a41307176d6867fc774ea8cd8267e6/SHA1: d891dfb80409d4e0318766b1ec6fbfe22ab2c9cd/' Packages
sed -i 's/^SHA256: c79e087aeede2476c96040d527206507b2b6ff3ef9a2eb565e4f205ecd86a399/SHA256: 50ce8fdab1fec132b34559d5a797b58e2eec8c7bb3b505cf12842c6ec846aef3/' Packages
cd ../..
geteltorito ../../proxmox-ve_3.1-93bf03d4-8.iso > proxmox-boot.img
Booting catalog starts at sector: 3359
Manufacturer of CD:
Image architecture: x86
Boot media type is: no emulation
El Torito image starts at sector 3360 and has 4 sector(s) of 512 Bytes
Image has been written to stdout ....
mkzftree -z9 proxmox-new proxmox-new-cmp
cd proxmox-new-cmp
mkisofs -no-emul-boot -boot-load-size 4 -boot-info-table -b proxmox-boot.img -o ../proxmox.iso .
...
Size of boot image is 4 sectors -> No emulation
...
Total translation table size: 2048
Total rockridge attributes bytes: 0
Total directory bytes: 4504780
Path table size(bytes): 27336
Max brk space used d99000
232717 extents written (454 MB)

But till yet I didn't succeed to boot the newly created image. It will stuck right after "ISOLINUX ..." message. Any other things I've missed?
 
But till yet I didn't succeed to boot the newly created image. It will stuck right after "ISOLINUX ..." message. Any other things I've missed?

You must not compress any data used by the boot loader (linux image ...)
 
I must miss something else. I even tried to create an iso without mkzftree and burned that to a dvd-rw but it will stuck at the beginning. Is there any information / script that describes how the proxmox iso image is created?
 
I must miss something else. I even tried to create an iso without mkzftree and burned that to a dvd-rw but it will stuck at the beginning. Is there any information / script that describes how the proxmox iso image is created?

building custom ISO image is a challenging task. I suggest you wait till we publish a new ISO, containing this module.

can´t you test it without ISO? e.g. install the system on single drive directly connected to the mainboard and then update to latest pvetest for testing your controller?
 
Using something else to bootstrap proxmox isn't that easy either since there seems no existing linux distribution that includes a suitable driver. But I just finished to install centos 6.5 with a suitable driver provided by areca. I hope within the next 60 minutes I get proxmox to boot from the areca controller and make use of it.
 
ISO images are updated for releases, so you can expect the new ISO with the release of 3.2, Q1/2014.

If you need service outside the normal release processes contact office@..
 
Just an update for reference. So far the new kernel seems to work fine. I will deploy the new kernel to another system with an older ARC-1231ML controller in 1-2 days to check if the new Areca driver will cause any trouble on these controller. Expect a status report on monday or tuesday.
 
I compiled a new kernel which includes that driver (v1.30.0X.16-20131206) - Please can you test?

# wget ftp://download.proxmox.com/debian/d...pve-kernel-2.6.32-27-pve_2.6.32-116_amd64.deb

@dietmar: To help testing, should I install this kernel (link above) or the 3.10 (as mentioned here: http://forum.proxmox.com/threads/17306-New-3-10-0-Kernel) on an old areca to help testing old/new driver?

Should I try the 3.10 kernel on the new system too (as a standard kernel)?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!