[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: DL360 G3 FC3 boot problem
- From: Brian Long <brilong cisco com>
- To: "Red Hat Enterprise Linux 4 (Nahant) Discussion List" <nahant-list redhat com>
- Cc: For users of Fedora Core releases <fedora-list redhat com>, Brad Clemmons Jr <brad clemmons gmail com>
- Subject: Re: DL360 G3 FC3 boot problem
- Date: Tue, 08 Mar 2005 14:27:14 -0500
On Tue, 2005-03-08 at 12:14, Axel Thimm wrote:
> On Mon, Mar 07, 2005 at 07:43:18PM -0500, Brad Clemmons Jr wrote:
> > Well, I think i have what happened. It looks like the boot loader
> > never got installed properly even though I did get a Install finished
> > page on the gui (did the graphical install). I used the Fedora Rescue
> > CD to get to a shell then:
> > chroot /mnt/sysimage
> > grub-install /dev/cciss/c0d0
> > rebooted
> >
> > It works now.
>
> Yes, I saw that with RHEL4, too. sda and hda get ordered before
> /dev/cciss/c0d0 and anaconda installs the bootloader on these. Since
> FC connected SANs appear as /dev/sdN you often get stuck.
>
> I solved this by disabling the port on the FC switch the box was
> connected to during installation. Would be nice if anaconda (and thus
> kickstart) had an explicit setting to where to place the bootloader.
In ks.cfg:
bootloader --driveorder=cciss/c0d0,sda,hda
/Brian/
--
Brian Long | | |
IT Data Center Systems | .|||. .|||.
Cisco Linux Developer | ..:|||||||:...:|||||||:..
Phone: (919) 392-7363 | C i s c o S y s t e m s
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]