Re: [Xen-devel] xenclient : grub-install problem

[Jean Guyader <jean.guyader@xxxxxxxxx>]

2009/3/27 Vaghasia, Vinu <Vinu.Vaghasia@xxxxxxx>:
> Hi Ian,
>
>
>
> I have checked out  sources from
> http://xenbits.xen.org/git-http/xenclient/build.git ,  and build it.  Build
> went through and  the I started  xenclient installation.   I followed the
> steps given in the  HOWTO document embedded with source code.    But the
> grub-install fails.  Please look at the  command and output it returns.
>
>
>
> [root@vinxen binaries]# fdisk -l
>
>
>
> Disk /dev/sda: 160.0 GB, 160041885696 bytes
>
> 255 heads, 63 sectors/track, 19457 cylinders
>
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Disk identifier: 0xcd02b4d0
>
>
>
>    Device Boot      Start         End      Blocks   Id  System
>
> /dev/sda1   *           1         131     1052226   83  Linux
>
> /dev/sda2             132        6664    52476322+  8e  Linux LVM
>
> /dev/sda3            6665       13197    52476322+  83  Linux
>
> /dev/sda4           13198       19457    50283450    5  Extended
>
> /dev/sda5           13198       13850     5245191   82  Linux swap / Solaris
>
> /dev/sda6           13851       19428    44805253+  8e  Linux LVM
>
> /dev/sda7           19429       19457      232911   8e  Linux LVM
>
>
>
> Disk /dev/sdb: 160.0 GB, 160041885696 bytes
>
> 255 heads, 63 sectors/track, 19457 cylinders
>
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Disk identifier: 0x0001736b
>
>
>
>    Device Boot      Start         End      Blocks   Id  System
>
> /dev/sdb1   *           1          25      200781   83  Linux
>
> /dev/sdb2              26       19457   156087540   8e  Linux LVM
>
> [root@vinxen binaries]#
>
>
>
> //---------------------- Grub Installation -----------------------------
>
>
>
> Step :1
>
> [root@vinxen binaries]# pvcreate /dev/sda6
>
>   Physical volume "/dev/sda6" successfully created
>
>
>
> Step :2
>
> [root@vinxen binaries]# vgcreate xenclient /dev/sda6
>
>   Volume group "xenclient" successfully created
>
>
>
> Step :3
>
> [root@vinxen binaries]# lvcreate --name config --size 12M /dev/xenclient
>
>   Logical volume "config" created
>
>
>
> [root@vinxen binaries]# lvcreate --name root --size 200M /dev/xenclient
>
>   Logical volume "root" created
>
>
>
> [root@vinxen xenclient]# ll
>
> total 54792
>
> -rw-rw-r-- 1 vinxen vinxen 42885120 2009-03-24 12:18 rootfs.i686.ext2
>
> -rw-rw-r-- 1 vinxen vinxen 13151711 2009-03-24 12:19 rootfs.i686.ext2.bz2
>
>
>
> Step :4
>
> [root@vinxen xenclient]# dd if=rootfs.i686.ext2 of=/dev/xenclient/root
>
> 83760+0 records in
>
> 83760+0 records out
>
> 42885120 bytes (43 MB) copied, 3.93264 s, 10.9 MB/s
>
>
>
> Step :5
>
> [root@vinxen xenclient]# fsck -f /dev/xenclient/root
>
> fsck 1.41.4 (27-Jan-2009)
>
> e2fsck 1.41.4 (27-Jan-2009)
>
> Filesystem did not have a UUID; generating one.
>
>
>
> Pass 1: Checking inodes, blocks, and sizes
>
> Pass 2: Checking directory structure
>
> Pass 3: Checking directory connectivity
>
> /lost+found not found.  Create<y>? yes
>
>
>
> Pass 4: Checking reference counts
>
> Pass 5: Checking group summary information
>
>
>
> /dev/xenclient/root: ***** FILE SYSTEM WAS MODIFIED *****
>
> /dev/xenclient/root: 791/1200 files (0.6% non-contiguous), 24773/41880
> blocks
>
>
>
> Step :6
>
> [root@vinxen xenclient]# resize2fs /dev/xenclient/root
>
> resize2fs 1.41.4 (27-Jan-2009)
>
> Resizing the filesystem on /dev/xenclient/root to 204800 (1k) blocks.
>
> The filesystem on /dev/xenclient/root is now 204800 blocks long.
>
>
>
> Step :7
>
> [root@vinxen xenclient]# mkfs -t ext2 /dev/xenclient/config
>
> mke2fs 1.41.4 (27-Jan-2009)
>
> Filesystem label=
>
> OS type: Linux
>
> Block size=1024 (log=0)
>
> Fragment size=1024 (log=0)
>
> 3072 inodes, 12288 blocks
>
> 614 blocks (5.00%) reserved for the super user
>
> First data block=1
>
> Maximum filesystem blocks=12582912
>
> 2 block groups
>
> 8192 blocks per group, 8192 fragments per group
>
> 1536 inodes per group
>
> Superblock backups stored on blocks:
>
>         8193
>
>
>
> Writing inode tables: done
>
> Writing superblocks and filesystem accounting information: done
>
>
>
> This filesystem will be automatically checked every 25 mounts or
>
> 180 days, whichever comes first.  Use tune2fs -c or -i to override.
>
>
>
> Step :8
>
> [root@vinxen xenclient]# mount /dev/xenclient/root /mnt
>
> [root@vinxen xenclient]# mount /dev/xenclient/config /mnt/config/
>
> [root@vinxen xenclient]# mount --bind /dev /mnt/dev/
>
> [root@vinxen xenclient]# mount --bind /proc /mnt/proc
>
>
>
> Step :9
>
> [root@vinxen xenclient]# chroot /mnt /bin/sh
>
> / #
>
>
>
> Step :10
>
> / # cd /config && ln -fs . config
>
> /config #
>
>
>
> Step :11
>
> /config # grub-install  --root-directory=/config --modules="ext2 pc gpt
> biosdisk lvm" /dev/sda
>
> error: cannot seek `/dev/sda'
>
> error: cannot seek `/dev/sda'
>
> error: no signature
>
> error: cannot seek `/dev/sda'
>
> error: cannot seek `/dev/sda'
>
> error: no signature
>
> grub-probe: error: no mapping exists for `xenclient-config'
>
> error: cannot seek `/dev/sda'
>
> error: cannot seek `/dev/sda'
>
> error: no signature
>
> error: cannot seek `/dev/sda'
>
> error: cannot seek `/dev/sda'
>
> error: no signature
>
> stat: invalid option -- c
>
> BusyBox v1.13.1 (2009-03-24 11:29:58 CDT) multi-call binary
>
>
>
> Usage: stat [OPTION] FILE...
>
>
>
> Display file (default) or filesystem status
>
>
>
> Options:
>
>         -f      Display filesystem status
>
>         -L      Dereference links
>
>         -t      Display info in terse form
>
>
>
> stat: invalid option -- c
>
> BusyBox v1.13.1 (2009-03-24 11:29:58 CDT) multi-call binary
>
>
>
> Usage: stat [OPTION] FILE...
>
>
>
> Display file (default) or filesystem status
>
>
>
> Options:
>
>         -f      Display filesystem status
>
>         -L      Dereference links
>
>         -t      Display info in terse form
>
>
>
> stat: invalid option -- c
>
> BusyBox v1.13.1 (2009-03-24 11:29:58 CDT) multi-call binary
>
>
>
> Usage: stat [OPTION] FILE...
>
>
>
> Display file (default) or filesystem status
>
>
>
> Options:
>
>         -f      Display filesystem status
>
>         -L      Dereference links
>
>         -t      Display info in terse form
>
>
>
> stat: invalid option -- c
>
> BusyBox v1.13.1 (2009-03-24 11:29:58 CDT) multi-call binary
>
>
>
> Usage: stat [OPTION] FILE...
>
>
>
> Display file (default) or filesystem status
>
>
>
> Options:
>
>         -f      Display filesystem status
>
>         -L      Dereference links
>
>         -t      Display info in terse form
>
>
>
> stat: invalid option -- c
>
> BusyBox v1.13.1 (2009-03-24 11:29:58 CDT) multi-call binary
>
>
>
> Usage: stat [OPTION] FILE...
>
>
>
> Display file (default) or filesystem status
>
>
>
> Options:
>
>         -f      Display filesystem status
>
>         -L      Dereference links
>
>         -t      Display info in terse form
>
>
>
> error: cannot seek `/dev/sda'
>
> error: cannot seek `/dev/sda'
>
> error: no signature
>
> grub-setup: error: no mapping exists for `xenclient-config'
>
>
>
> /config #
>
>
>
>
>
>
>
> Please let me know what could be the reason for the failure.
>
>

Hi Vinu,

Sometime those things happen we don't really know why.

If you add those line to the /config/boot/grub/device.map you should
be all right:

(xenclient-config)      /dev/sda6
(xenclient-root)        /dev/sda6

Thanks,

-- 
Jean Guyader

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel