1325894947 Q * nicholi Quit: leaving
1325895383 J * nicholi ~nicholi@rrcs-76-79-196-34.west.biz.rr.com
1325896197 Q * gucki Remote host closed the connection
1325897319 Q * ryker Quit: ryker
1325898985 Q * ghislain Quit: Leaving.
1325902548 Q * clopez Ping timeout: 480 seconds
1325905909 J * Ames ~Adium@63.81.0.20
1325906010 M * Ames anyone have a work around for RAID drivers & vserver kernels?
1325906045 M * Ames on Ubuntu 10.04 lucid?
1325906150 M * hparker Didn't know a work around was needed.. Also don't run Ubuntu
1325906169 M * hparker Maybe describe your problem a bit more
1325906291 M * Ames we recently got some new hardware with an internal RAID controller…discovered that the Ubuntu installation of the latest supported lucid releases require a megaraid_sas driver.  So to see the disk the kernel has to have an Ubuntu 10.04 LTS kernel with kernel mods made.
1325906329 M * hparker Oh... If it were me I'd just compile the kernel as I needed it 
1325906331 M * Ames a very specific kernel.  Comes vserver enabled kernel…if I try to load this kernel as part of the vserver kernel, I won't see the RAIDed disks
1325906376 M * hparker Hopefully someone more familiar with Ubuntu comes along
1325906379 M * Ames well LSI the manufacturer put an updated driver for but only tested it against the latest older kernel release
1325906413 M * hparker Have you tried it with newer just to see?
1325906464 M * Ames I didn't compile the kernel, I believe my co-worker or perhaps someone else found the kernel with the updated megaraid driver already recompiled.
1325906474 M * Ames So I guess my question is, how to get around this.
1325906528 M * Ames Use the vserver kernel and try to recompile with the LSI raid driver….or try to compile in vserver specific kernel with an existing kernel that has the RAID driver.
1325906618 M * Bertl_oO I'm still not sure what your problem is :)
1325906618 M * Ames It's a bit hard to explain as well, as the Ubuntu installation CDs won't even install with the disks RAIDed.
1325906629 N * Bertl_oO Bertl
1325906643 M * Bertl you have a kernel which works for that specific hardware, yes?
1325906653 M * Ames need 2 features (RAID + vserver) compiled into a 10.04 Ubuntu release
1325906663 M * Ames yes
1325906675 M * Bertl what kernel version is that and where does it come from?
1325906686 M * Bertl (uname -a will give some hints)
1325906707 M * Ames from what I can tell it 's from the 10.04 LTS release of Ubuntu with the RAID driver compiled in
1325906730 M * Ames kernel version is 2.6.32-21-server
1325906748 M * Bertl so quite an old kernel, but maybe with additional patches
1325906764 M * Bertl now what kernel did you try/install for Linux-VServer?
1325906780 M * Ames 2.6.32-28-vserver 
1325906817 M * Bertl so that 'looks like' a quite similar kernel, but probably with a different config
1325906832 M * Bertl and that kernel doesn't 'see' your raid controller?
1325906866 M * Ames so default Ubuntu 10.04 LTS release kernel = 2.6.32-21-server (+ raid driver compiled in sees disk)
1325906880 M * Ames without which, the RAIDed disk disappears
1325906893 M * Bertl what do you mean by read driver compiled in?
1325906901 M * Ames RAID
1325906909 M * Ames not READ
1325906911 M * Ames :D
1325906914 M * Bertl sorry, typo
1325906932 M * Bertl so what do you mean by 'raid driver compiled in'?
1325906983 M * Ames without the Hardware RAID driver, I don't see any disks under the control of the HW RAID controller
1325906997 M * Ames OS installation fails
1325907028 M * Bertl I got that, but you added '', which sounds to me like somebody added something?
1325907039 M * Ames we've a crude work around for that which inserts the kernel with the HW RAID driver … during the OS installation.
1325907100 M * Bertl so the 2.6.32-21-server is not the default ubuntu kernel, it is an already modified kernel?
1325907101 M * Ames Ok, what don't you understand? before we play 20 more questions? :)
1325907108 M * Ames yes....
1325907114 M * Bertl who modified it?
1325907124 M * Ames does that matter?
1325907139 M * Bertl well, he can do the same modifications to the Linux-VServer kernel, I guess :)
1325907159 M * Bertl so, for me, it doesn't matter, for you, probably :)
1325907198 M * Ames we can't guarantee the driver will work as LSI is very specific about support for the raid driver
1325907199 M * Bertl I don't think your hardware is that special that it won't work with a recent kernel, let's say 3.1.x or so
1325907218 M * Ames a 3.1 kernel?
1325907237 M * Bertl but maybe I'm wrong there, cold be experimental hardware or so
1325907250 M * Ames I'm not so comfortable with experimental kernels in a production environment
1325907274 M * Ames the problemis the hardware outdates the older software
1325907287 M * Ames new HW, no new drivers in releases
1325907311 M * Ames so I guess we need a vserver kernel with the megaraid driver
1325907311 M * Bertl you are using an 'experimental' kernel (if 3.1.x is experimental for you)
1325907331 M * Ames we're nowhere near 3.0 in production server kernels
1325907348 M * Bertl i.e. 3.1 is a stable, if not more stable than 2.6.32
1325907356 M * Ames production stuff always lags a bit behind the bleeding edge by a while
1325907398 M * Bertl which brings us back to the question, who did the modifications for the original kernel and more importantly, what kind of modifications
1325907419 M * Bertl if you figure that out, you can easily do the same to the equivalent Linux-VServer kernel
1325907442 M * Bertl or you could simply take the source from the modified kernel and apply the Linux-VServer patch
1325907459 M * Ames there are instructions from LSI to use the older kernel to compile in the newer RAID drivers
1325907485 M * Ames I can do that again, but the kernel version of what was supported by LSI is quite specific
1325907504 M * Bertl there you go then, just use the same procedure with the Linux-VServer patched kernel
1325907519 M * Ames I guess my next step would be to take a vserver enabled kernel and try to patch in the LSI driver…but I've my doubts that would work
1325907522 M * Bertl the two kernels you listed look reasonably similar
1325907529 M * Bertl why not?
1325907579 M * Bertl Linux-VServer does not interfere with hardware drivers, so no clashes or changes to an unpatched kernel there
1325907579 M * Ames just because I don't trust the work done against the older kernel release from LSI and there's been NO updates.
1325907607 M * Bertl as I said, personally I wouldn't use 2.6.32 anyways
1325907616 M * Ames 10.04 release came out April 2010, it's been almost 2 years, and we're using newer hardware with a new RAID controller
1325907647 M * Ames So the best bet is to use a newer vserver kernel?
1325907648 M * Bertl an a kernel which is more than a year old ...
1325907669 M * Bertl yeah, I'd go for 2.6.38.x at least, if that supports your hardware
1325907691 M * Bertl if not, feel free to use 3.x, there shouldn't be a problem with those kernels
1325907701 M * Ames The latest most recent release of Ubuntu 11.10 (2011 October) has the RAID driver
1325907732 M * Ames can't recall, but the kernel was at least 3.0+
1325907766 M * Ames we're also trying to match apples with apples…I'm building these for our performance lab
1325907812 M * Ames so perf lab kernel 3.0+, production kernel 2.6.38+, well one issue at a time I suppose
1325911464 Q * Pogs241 Quit: Pogs241
1325911800 J * Pogs241 ~user@cpe-71-72-126-188.insight.res.rr.com
1325912461 J * Mr_Smoke_ ~smokey@layla.lecoyote.org
1325912461 Q * Mr_Smoke Read error: Connection reset by peer
1325921030 M * Bertl off to bed now ... have a good one everyone!
1325921039 N * Bertl Bertl_zZ
1325922090 J * sannes ~ace@cm-84.209.106.118.getinternet.no
1325923125 J * Marbug ~Marbug@83.101.67.3
1325924966 P * Ames 
1325926565 Q * ensc|w Remote host closed the connection
1325926574 J * ensc|w ~ensc@www.sigma-chemnitz.de
1325927538 J * jsg ~chatzilla@87.51.1.143
1325928175 J * Hollow ~Hollow@91-66-255-107-dynip.superkabel.de
1325928572 J * bonbons ~bonbons@2001:960:7ab:0:b587:c0d:6166:391d
1325929439 J * ghislain ~AQUEOS@adsl2.aqueos.com
1325929448 Q * Mr_Smoke_ Read error: No route to host
1325929518 J * Mr_Smoke ~smokey@layla.lecoyote.org
1325931941 J * derjohn_mob ~aj@p4FFD1EBA.dip.t-dialin.net
1325944259 N * Bertl_zZ Bertl_oO
1325944464 Q * Aiken Remote host closed the connection
1325949661 N * ensc Guest23264
1325949671 J * ensc ~irc-ensc@p54ADFA36.dip.t-dialin.net
1325950083 Q * Guest23264 Ping timeout: 480 seconds
1325950208 Q * Pogs241 Remote host closed the connection
1325953334 J * gucki ~gucki@84-72-9-188.dclient.hispeed.ch
1325953846 J * ghislain1 ~AQUEOS@adsl2.aqueos.com
1325954192 Q * ghislain Ping timeout: 480 seconds
1325957039 Q * fisted Quit: leaving
1325960376 J * clopez ~clopez@238.10.117.91.dynamic.mundo-r.com
1325964149 M * Bertl_oO off for a nap ... bbl
1325964154 N * Bertl_oO Bertl_zZ
1325967966 Q * ghislain1 Quit: Leaving.
1325970614 Q * geos_one Ping timeout: 480 seconds
1325971359 J * geos_one ~chatzilla@chello080109195117.4.graz.surfer.at
1325973458 J * BenG ~bengreen@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com
1325973612 Q * Hollow Quit: Hollow
1325974526 Q * Marbug Ping timeout: 480 seconds
1325975630 Q * sannes Remote host closed the connection
1325975701 J * fisted ~fisted@xdsl-87-78-216-122.netcologne.de
1325976707 N * Bertl_zZ Bertl
1325976712 M * Bertl back now ...
1325977688 Q * DoberMann Ping timeout: 480 seconds
1325978017 J * petzsch ~markus@p57B65EE4.dip.t-dialin.net
1325978752 Q * petzsch Quit: Leaving.
1325979975 J * DoberMann ~james@2a01:e35:8b44:84c0::2
1325980376 Q * BenG Remote host closed the connection
1325980592 Q * gucki Remote host closed the connection