obermotz

Members
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About obermotz

  • Rank
    Newbie
  1. I just tried my test setup with a VMDK converted from an IMG by V2V and can't see any problems so far - mind you, the test setup is pretty simple and runs only Audiostation.
  2. Just tried this, highly recommended. Way easier to convert the .IMG than manually creating the .VMDK (5 secs instead of half an hour). Be aware that an IDE VMWare pre-allocated VMDK should be created, not the ESX variant. StarWind V2V
  3. Here is a quick and dirty .VMDK (based on the original Gnoboot VMDK) for 5.0.2.4 x64 : http://xpenology.obermotz.org/Nanoboot5024x64.zip It complains about not finding awk and sort but seems to be working alright otherwise. Edit: I have just did a quick install of DSM5-4482 under Virtualbox and it works perfectly.
  4. Hi, I have just tried to download Xpenology Nanoboot-5.0.2.3 DSM 5.0-4482 X64 by Poechi, but the .rar file is only 302 bytes. It seems that the NanoBoot-5023_by_Poechi-flat.vmdk is missing from the archive. Can you please fix it? No problem. I like to do something back for the community so we can all benefit .
  5. I had a look at dmesg and looked for 'sdq' (the HDD which is detected by fdisk but not by Storage Manager) and 'sda' which is the smallish IDE HDD where DSM is installed. I could not find anything peculiar (most likely due to my noobness) but I in case anyone cares here it is: http://drose1.homelinux.com/dmesg.zip
  6. I had a look at dmesg and looked for 'sdq' (the HDD which is detected by fdisk but not by Storage Manager) and 'sda' which is the smallish IDE HDD where DSM is installed. I could not find anything peculiar (most likely due to my noobness) but I in case anyone cares here it is: http://drose1.homelinux.com/dmesg.zip
  7. Being on ESXi console, please do "ls -al //" and show us the output. Vladimir Here you are: /vmfs/volumes/52fabec3-1e8a19f1-8f9e-009c02aa64fd/DSM # ls -al total 52465680 drwxr-xr-x 1 root root 2100 Feb 12 23:18 . drwxr-xr-t 1 root root 1960 Feb 12 21:47 .. -rw------- 1 root root 2000398934016 Feb 12 22:34 2TB_HITA-rdmp.vmdk -rw------- 1 root root 500 Feb 12 22:35 2TB_HITA.vmdk -rw------- 1 root root 53687091200 Feb 12 23:17 DSM-flat.vmdk -rw------- 1 root root 8684 Feb 12 23:17 DSM.nvram -rw------- 1 root root 465 Feb 12 22:58 DSM.vmdk -rw-r--r-- 1 root root 0 Feb 12 21:47 DSM.vmsd -rwxr-xr-x 1 root root 2947 Feb 12 23:18 DSM.vmx -rw-r--r-- 1 root root 258 Feb 12 21:47 DSM.vmxf -rw-r--r-- 1 root root 32440320 Dec 22 18:17 synoboot_trantor_3810_esxi_v1.1-s001.vmdk -rw------- 1 root root 362 Feb 12 21:52 synoboot_trantor_3810_esxi_v1.1.vmdk -rw-r--r-- 1 root root 204443 Feb 12 22:16 vmware-1.log -rw-r--r-- 1 root root 151516 Feb 12 22:48 vmware-2.log -rw-r--r-- 1 root root 151918 Feb 12 23:18 vmware.log
  8. Being on ESXi console, please do "ls -al //" and show us the output. Vladimir Here you are: /vmfs/volumes/52fabec3-1e8a19f1-8f9e-009c02aa64fd/DSM # ls -al total 52465680 drwxr-xr-x 1 root root 2100 Feb 12 23:18 . drwxr-xr-t 1 root root 1960 Feb 12 21:47 .. -rw------- 1 root root 2000398934016 Feb 12 22:34 2TB_HITA-rdmp.vmdk -rw------- 1 root root 500 Feb 12 22:35 2TB_HITA.vmdk -rw------- 1 root root 53687091200 Feb 12 23:17 DSM-flat.vmdk -rw------- 1 root root 8684 Feb 12 23:17 DSM.nvram -rw------- 1 root root 465 Feb 12 22:58 DSM.vmdk -rw-r--r-- 1 root root 0 Feb 12 21:47 DSM.vmsd -rwxr-xr-x 1 root root 2947 Feb 12 23:18 DSM.vmx -rw-r--r-- 1 root root 258 Feb 12 21:47 DSM.vmxf -rw-r--r-- 1 root root 32440320 Dec 22 18:17 synoboot_trantor_3810_esxi_v1.1-s001.vmdk -rw------- 1 root root 362 Feb 12 21:52 synoboot_trantor_3810_esxi_v1.1.vmdk -rw-r--r-- 1 root root 204443 Feb 12 22:16 vmware-1.log -rw-r--r-- 1 root root 151516 Feb 12 22:48 vmware-2.log -rw-r--r-- 1 root root 151918 Feb 12 23:18 vmware.log
  9. obermotz

    [SOLVED] Install on vmware ESXI

    Hi, I have just installed DSM4.3 on my Microserver N40L running ESXi 5.5 . Everything but raw HDD mapping seems to work fine. I followed this guide: http://forza-it.co.uk/esxi-5-1-using-raw-device-mappings-rdm-on-an-hp-microserver/ . Unfortunately the mapped HDD does not appear in Storage Manager, altough I can see it using fdisk -l as /dev/sdq (it's a 2TB Toshiba drive which has data on it / was used before in another XPEnology install). Any advice on this would be greatly appreciated. Disk /dev/sdq: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdq1 1 311 2490240 fd Linux raid autodetect Partition 1 does not end on cylinder boundary /dev/sdq2 311 572 2097152 fd Linux raid autodetect Partition 2 does not end on cylinder boundary /dev/sdq3 588 243201 1948793440+ fd Linux raid autodetect
  10. obermotz

    [SOLVED] Install on vmware ESXI

    Hi, I have just installed DSM4.3 on my Microserver N40L running ESXi 5.5 . Everything but raw HDD mapping seems to work fine. I followed this guide: http://forza-it.co.uk/esxi-5-1-using-raw-device-mappings-rdm-on-an-hp-microserver/ . Unfortunately the mapped HDD does not appear in Storage Manager, altough I can see it using fdisk -l as /dev/sdq (it's a 2TB Toshiba drive which has data on it / was used before in another XPEnology install). Any advice on this would be greatly appreciated. Disk /dev/sdq: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdq1 1 311 2490240 fd Linux raid autodetect Partition 1 does not end on cylinder boundary /dev/sdq2 311 572 2097152 fd Linux raid autodetect Partition 2 does not end on cylinder boundary /dev/sdq3 588 243201 1948793440+ fd Linux raid autodetect
  11. Hi, I have just installed DSM4.3 on my Microserver N40L running ESXi 5.5 . Everything but raw HDD mapping seems to work fine. I followed this guide: http://forza-it.co.uk/esxi-5-1-using-raw-device-mappings-rdm-on-an-hp-microserver/ . Unfortunately the mapped HDD does not appear in Storage Manager, altough I can see it using fdisk -l as /dev/sdq (it's a 2TB Toshiba drive which has data on it / was used before in another XPEnology install). Any advice on this would be greatly appreciated. Disk /dev/sdq: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdq1 1 311 2490240 fd Linux raid autodetect Partition 1 does not end on cylinder boundary /dev/sdq2 311 572 2097152 fd Linux raid autodetect Partition 2 does not end on cylinder boundary /dev/sdq3 588 243201 1948793440+ fd Linux raid autodetect