From mboxrd@z Thu Jan 1 00:00:00 1970 From: malahal@us.ibm.com Subject: Re: SLES installation on dual controller subsystem Date: Mon, 4 Feb 2008 18:07:00 -0800 Message-ID: <20080205020700.GA13946@us.ibm.com> References: <110b17190802041558y6b30e000x5a3e530f4c717d4e@mail.gmail.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <110b17190802041558y6b30e000x5a3e530f4c717d4e@mail.gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: dm-devel@redhat.com List-Id: dm-devel.ids Pradipmaya Maharana [pradipmaya@gmail.com] wrote: > Hi All, > > I am trying to install SLES 10.1 on my dual controller subsystem. The > subsystem is ALUA aware and hence shows me 2 LUNs for one while trying > to install SLES on it. > > If my LUN's preferred controller is 1 then everything goes fine, but > if the preferred controller of the LUN I am installing OS on is 2, > then installation goes fine but the boot fails. > > It throws some errors like root (hd1,1) could not found. When I modify > this to too(hd0,1) it boots fine. Looks like a GRUB issue to me. Go into grub's interactive/editing mode while booting and try "root (hd), it will tell you what partitions it sees. My guess is that GRUB can't find your other path and that is why it can't see (hd1,1). (hd0,1) works because it saw that path. If that is indeed right, it is a BIOS feature/problem. -Malahal.