Hempel

New Members
  • Content count

    1
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Hempel

  • Rank
    Newbie
  1. Moinsen, ich habe seit 4 Wochen Xpenology 5.4482 problemlos als VM in ESXI am laufen. Ich wollte heute updaten. Ich bekomme aber mit Nanoboot 5.0.3.1 kein Bootmenu zu sehen. Ich habe die neue vmdk für ESXI 5.5 genau so erstellt wie damals für 5.0.2.4 : 3. Convert Nanoboot IMG to VMDK and upload to Datastore - Start up Starwind V2V converter - Choose the NanoBoot-5.0.2.4-fat.img file you want to convert - Choose “VMware pre-allocated image”, Choose “IDE” type *Choosing "IDE" type is very important - This will created 2 vmdk files, NanoBoot-5.0.2.4-fat.vmdk and NanoBoot-5.0.2.4-fat-flat.vmdk. - Upload File to ESX Host Datastore (configuration tab -> Storage -> right click drive -> Browse Data Store) - Upload both vmdk file to the folder of your VM Name created in previous step, they will merge to a single vmdk file automatically. 4. Adding Hard Drives to your VM - Edit your virtual machine setting - Add a hard drive - Choose “Use an existing virtual disk” - Choose the vmdk you uploaded in the previous step. - Make sure drive is set as IDE (0:0) and check “Independent -> non-persistent” *IDE (0:0) is important because this is the boot disk that starts up Nanoboot* *non-persistent is important because it prevents the non-booting situation after you do the DSM install. Technically explanation is during DSM install all hard drives gets repartition including the nanoboot drive, the non-persistent setting makes these changes temporary and after reboot the original nanoboot boot partition is returned. danach die alte 5.0.2.4.vmdk in ESXI entfernt und die neue 5.0.3.1 als IDE 0:0 wieder angelegt. Ich habe das Gefühl, das er direkt die 4482 von Volume1 (SSD) startet. Warum sehe ich kein Bootmenu? Dank Euch schon mal für die Mühe !!