well i guess i don't have to worry about it. the servers were so defective that im just shippin em back.
gonna get the right stuff this time, no more OS on a raid array. nate > i thought that the debian rescue disk didnt include support > course i havent tested this yet. > > and no the systems have no cdrom. > > and yes i do not like the idea of having the OS on the > raid controller. > > thanks for the info, tomorrow i should recieve the floppy > cable that the company forgot to install in the system > and i will try to install 2.2r3. > > hope it goes well. > > nate > > >> >> Why are you trying to rebuild your rescue floppy? The Linux kernel >> already includes excellent 3Ware drivers so IIANM your rescue floppy >> should already be able to access the RAID array. If you are using >> such an old version of Debian that it predates the 3Ware products... >> you might want to consider upgrading your distro instead of sending >> back your hardware. >> >> All of the drives are supposed to be on the RAID controller. That's >> good design. RAID boots fast, especially 3Ware RAID 0. >> >> Also, if these are new systems they probably include a CD-ROM reader, >> correct? You should be able to boot directly from the Debian CD if you >> set the correct option in the BIOS. Booting from CD is much faster >> and MUCH more reliable than booting from a floppy. >> >> Shawn Yarbrough >>[EMAIL PROTECTED] >> >> >> >> [EMAIL PROTECTED] wrote: >> >>> hi >>> >>> i recieved 3 new systems today ..i was unaware of their >>> (lack) of design until i opened the case. they are >>> 1U IDE raid systems from some company called 'pogolinux'. >>> the problem is there is 4 drives, and ALL of them are on >>> the raid controller(3ware). since i am not gonna >>> be using redhat on these systems, i need to figure out >>> the best way to replace the kernel on the rescue >>> disk for debian so it will recognize the drives. either >>> that or i return the systems. I can take care of the >>> compiling kernel and stuff no problem just would like to >>> know if there is a way to replace the kernel image. >>> last time i checked, when i mounted the rescue disk >>> all it was was a bunch of files, so could i just copy >>> my new kernel on top of the old one?(don't need to >>> worry about modules i won't be using any at first, everything >>> will be statically built). or is there something more >>> to it. last time i created a boot disk with kernel-package >>> it seemed to be a rather inflexable boot disk(didn't have >>> lilo, or at least didn't have it configured so i could do >>> other things with it, it would just boot without prompting) >>> i really don't like the idea of having the OS on raid >>> especially because we will be running them in raid0, >>> that would indeed suck to have the OS itself go down >>> because of a storage drive dieing. >>> >>> any help would be appreciated. >>> >>> thanks! >>> >>> nate >>> >>> -- >>> To UNSUBSCRIBE, email to [EMAIL PROTECTED] >>> with a subject of "unsubscribe". Trouble? Contact >>> [EMAIL PROTECTED] >> >> >> -- >> To UNSUBSCRIBE, email to [EMAIL PROTECTED] >> with a subject of "unsubscribe". Trouble? Contact >> [EMAIL PROTECTED] > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED]
