this is true and i did forget to mention this, however i dont believe it to be directly relevant to my problem. i spoke with their tech support and they would not do much to help me unless i purchased their yearly maintenence contract (which is about 1/3 the cost of the unit). so yes, we learned our lesson as well: never purchase from them again! however, we still have two of these cubes that i would like to use so i'm trying to bring them up-to-date. their tech support told me most of the updates were RH-related, with a few to the firmware and their tools. i'm really less concerned about their tools than i am with kernel and services i'm running, so thanks to the GPL, i was able to get out of them the following email: ---------- Forwarded message ---------- Date: Wed, 11 Dec 2002 15:18:00 -0500 From: Raidzone Technical Support <support@xxxxxxxxxxxx> To: keenanm@xxxxxxxx Subject: OpenNAS kernel 2.4.18 headers & source Please note that these rpm's have no warranty or support associated with them. http://www.opennas.com/NAS24/kernel-headers-2.4.18-12.i386.rpm - 1,132,130 bytes MD5SUM a4926658a6b6810934caec244dfadeb8 kernel-headers-2.4.18-12.i386.rpm http://www.opennas.com/NAS24/kernel-source-2.4.18-12.i386.rpm - 25,443,943 bytes MD5SUM 5b920a6b9f76b3672063ba6cb1eac49b kernel-source-2.4.18-12.i386.rpm Thanks, Ijaaz Ullah Raidzone Technical Support ------- there you can find a kernel that does compile, which i did and have used successfully on one of the cubes. on the other cube, i'd like to not have to spend a weeks time going through all the packages and dendencies to bring it up to RH 8.0 level. that being said, i dont believe the kernel to be the problem in this specific case. i think its the way anaconda is searching for drives. it looks for ide or scsi drives, but the rzX## devices are not considered. i considered trying to hack anaconda myself, but after an hour i was still trying to find all the tools i needed to get it to compile. i'm hoping someone here might have an easier solution. M< ps: what i found most annoying about their tech support was that they didn't know how to build a boot floppy for their own device! i couldnt use the kernel that came with the cube because it was too large for a floppy. after i compiled my own kernel, i did finally make a rescue disk. their reasoning: no one should ever have a need for one. argh!! At 22:22 on Mar 4, Brent M. Clements arranged these symbols: > Michael, You cannot get a stock linux kernel to work with the Raidzone > products. The only way we've found to actually upgrade the raidzone > products is by going through raidzone. > > We have learned our lesson and will NEVER EVER purchased a raidzone > product again. > > -Brent > > > On Tue, 4 Mar 2003, Michael Keenan wrote: > > > I have a Raidzone cube (www.raidzone.com) that is built with a custom > > driver to work with their hardware. I have compiled a new kernel for the > > boot.img disk and added the related devices into the initrd image. > > anaconda will start, however it fails to detect the drive. > > > > the specific error is "No hard drives have been found." > > > > the raid devices are: > > /dev/rza: block special (116/0) > > /dev/rza1: block special (116/1) > > .. > > > > the drive _is_ being detected by the kernel and can be seen with fdisk > > from VT2. > > > > i tried coaxing anaconda into thinking it to be an ide device by changing > > the names of the devices to /dev/hdeXX, but that failed as well (which i > > figured it would after briefly looking at loader.c) > > > > how might i get anaconda to use this device? what i would like to do is > > upgrade the installation already on there. is there another automated way > > other than anaconda to do that? > > > > > > thanks > > > > M< > > > > > > > > > > > > _______________________________________________ > > Anaconda-devel-list mailing list > > Anaconda-devel-list@xxxxxxxxxx > > https://listman.redhat.com/mailman/listinfo/anaconda-devel-list > > > > > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/anaconda-devel-list >
