Hi,

> hi Stephen,
> Maybe my idea is a bad one but does it work ?

ok, I got your discussion like you agreed, that it wouldn't work. My mistake!
> 
> On Wed, May 28, 2008 at 5:17 PM,  <gildo.rex@gmx.de> wrote:
> >> > Hi,
> >> > Im not a openvz expert, but your problem probably lies elsewhere.
> >> > Instead of using root=/dev/disk/...... use something
> >> > like /dev/sdb1 ...
> >> Bad idea.
> >> /dev/disk is better anyway.

I checked my harddisk using fdisk -l:

test1:~ # fdisk -l

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000f2454

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1         262     2104483+  82  Linux swap / Solaris
/dev/sda2   *         263       38913   310464157+  83  Linux

Disk /dev/sdb: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x6d8cf30e

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       38913   312568641    7  HPFS/NTFS


so I created a new entry in menu.lst referring /dev/sda2:

###Don't change this comment - YaST2 identifier: Original name: linux###
title Ovztry
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.16.43-027test002-24.1-ovzpae root=/dev/sda2 vga=0x31a  acpi=off resume=/dev/sda1  showopts
    initrd /boot/initrd-2.6.16.43-027test002-24.1-ovzpae

The bootprocess didn't find the disk again and tried once more with

/dev/disk/by-id/scsi-SATA_MAXTOR_STM33208_9QF9K35F-part2

but that didn't work either like before.

Is there any possibility to let you see the boot messages?

Do you have any more hints?

Kind regards

Stephan
-- 
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/?mc=sv_ext_mf@gmx