Well, here's what we've found... TSL 2.2 boots from iso and installs/runs great on the DL385, but will not boot from the DL145 TSL 3.0 boots from iso and installs/runs great on the DL145, but will not work in the DL385 Currently, this leaves us running two versions of the OS on our network, which I'm sure could be resolved, I'm just not sure how to approach the problem.
The major variable seems to be that the DL385 has SCSI hard drives, while our DL145 has SATA drives More importantly (I think), is that the DL385 also has an integrated raid controller, which is not present in the DL145 series. We think the problem likely has to do with the integrated raid controller (Smart Array 6i) and either Viper, or TSL 3.0, my wild guess is Viper. To recap the problem, TSL 2.2 / Anaconda installs fine on the DL385, while any attempt to install TSL 3.0 / Viper on the same machine immediately terminates in a 'no boot device' error -k On Feb 2, 2006, at 6:12 AM, Dominic Maraglia wrote: > Kaliban, > > Yes, you are correct -- at a very minimum, your system should > attempt to boot the CD. Sounds to me like your DL145 is not set to > boot a CD rom -- it looks for a bootable hard drive, does not find > one, and returns a boot failure message. Sounds simplistic, but > have you looked into the bios for configured boot devices? > > Cheers, > Dominic > > Kaliban wrote: >> On Feb 2, 2006, at 12:17 AM, Morten Albrigtsen wrote: >>>> We have several HP Proliant DL145s and a DL385. The v2.20 ISO image >>>> install cd we made boots up and installs fine in the DL385, but the >>>> DL145 gives a 'boot failure' message immediately upon boot >>>> attempt. >>> >>> Have you tried to configure the boot loader manually? >> I'm not sure if I understand you correctly. If I were to >> configure the boot loader manually, wouldn't that be done after >> the computer had booted to the install cd? What happens is, as >> soon as the bios is finished doing it's thing and is now going to >> boot from the cd, the cd light flashes once and the boot failure >> message appears, and that's the end of that. If I understand >> correctly, I'm not even getting to the boot loader, or rather, I >> have not been offered the option of even installing the boot loader. >> Am I incorrect in this? >> Thanks! >> -k >> _______________________________________________ >> tsl-discuss mailing list >> [email protected] >> http://lists.trustix.org/mailman/listinfo/tsl-discuss > _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
