Jump to content
XPEnology Community

extenue

Member
 View Profile  See their activity

  • Posts

    70

  • Joined

  • Last visited

 Content Type 

Posts posted by extenue

    Trial of Nanoboot (4493) - 5.0.3.1

    in DSM 5.2 and earlier (Legacy)

    Posted

    for those who have migrated to update 5 , can you enable web station ?

     

    i face this "the operation failed. Please log in DSM again and retry" if i want to enable it , put R/O or R/W access to web folder for group http (permission which was gone same as the others i guess) does not help)

     

    webstation was not enabled before the update so not sure if there is a relation

     

    also , i would like to downgrade , my only path is return to PAT stock so 4493 , is anyone knows how i could manually update to update 4 ?

     

    Thanks,

    XT

     

    EDIT : downgraded successfully to 4493 "update 0" , i could immediatly enable web station , so now any guidance to migrate to update 4 would be appreciate :smile:

    Trial of Nanoboot (4493) - 5.0.3.1

    in DSM 5.2 and earlier (Legacy)

    Posted

    for those who have migrated to update 5 , can you enable web station ?

     

    i face this "the operation failed. Please log in DSM again and retry" if i want to enable it , put R/O or R/W access to web folder for group http (permission which was gone same as the others i guess) does not help)

     

    webstation was not enabled before the update so not sure if there is a relation

     

    also , i would like to downgrade , my only path is return to PAT stock so 4493 , is anyone knows how i could manually update to update 4 ?

     

    Thanks,

    XT

    Trial of Nanoboot (4493) - 5.0.3.1

    in DSM 5.2 and earlier (Legacy)

    Posted

    something went wrong with that upgrade (native on proliant N54L) ,i believe i lost everything after second reboot post upgrade : all disks were shown as initialized ... a reboot has fixed that but i lost permissions for my account (so fixed on reapply them) , got a message saying that USB has been not properly ejected ...

     

    i DO NOT recommend that upgrade until experts give their insights

     

    i fear to try to downgrade to earlier version :sad:

    Trial of Nanoboot (4493) - 5.0.3.1

    in DSM 5.2 and earlier (Legacy)

    Posted · Edited by Guest

    hi,

     

    Gnoboot does not support NIC in ESXi right ?

     

    works fine on hyper-v but no luck with ESXi 5.1 , is there a plan to add VMWare NIC drivers ?

     

    Thanks

    XT

     

    EDIT : please disregard this message , NIC is well recognized , just i was misleaded as IP does not appears in console mode as with Hyper-V (it show 169.254.x.x in ESX .... instead of 192.168.x.x in Hyper-V)

    Trial of Nanoboot (4493) - 5.0.3.1

    in DSM 5.2 and earlier (Legacy)

    Posted

    Are there any performance improvements with using the x64 nanoboot or not really is it more hardware compatibility..?

    gnoboot and trantor have always been x64, nanoboot x64 wud be the best to use, x86 was added to support older/slower hardware :smile:

     

    x86 is just magic for those like me who rent a VPS with a cpu which don't have VT enabled , you can setup your Xpen VM easily with virtualbox

    XPEnology DS3612xs DSM 4.3 build 3827 (ESXi v1.2)

    in DSM 5.2 and earlier (Legacy)

    Posted

    Merci Trantor !!!!

     

    Que du bonheur , migré sans pertes depuis ta version précédente en update 4 , les opentools c'est que du bonheur

     

    par contre sur mon premier proliant l'update me propose de télécharger la V5 alors que sur mon 2 eme proliant l'update me propose la build 3827 update 1 , strange n'est ce pas !

     

    Thank you Trantor !!!!

     

    what a big pleasure , migrated with no loss since your previous release (update 4) , the opentools are just magic

     

    however for my first proliant the update manager gives update to V5 whereas on the second proliant he gives update to build 3827 update 1 , weird isn't ?

    [SOLVED] DS3612xs_4.2-3211_x64

    in DSM 5.2 and earlier (Legacy)

    Posted

    :'(

     

    i have my two ESX 5.1 installed with the version from the dedicated thread http://xpenology.com/forum/viewtopic.php?f=2&t=558 based on odie82544's DS3612xs_3202-Repack images

     

    i tested successfully upgrade to this DS3612xs_4.2-3211_x64 version on a test VM with a 16 Go vmdk file , however unlike with the odie82544's DS3612xs_3202-Repack , my RDM disks are not seen :'(

     

    i tried all the possible controller (normally paravirtual is the good one) but my RDM disks are not seen , i thought i could finally upgrade to 3211 with that version but it miss something

     

    is anyone could run ESXi 5 with RDM disks with that version ?

     

    what can i attempt to make that happen ?

     

    Thanks,

    XT

    XPEnology DS3612xs DSM 4.2 build 3211++ (repack v1.2)

    in DSM 5.2 and earlier (Legacy)

    Posted

     

    Does two VM disks, are they IDE or SCSI?

     

    Does spindown work for you?

     

    For me installation is working, but when i shutdown the VM, attach my LSi raidcontroller, turn it on, it will auto power off the vm after 1 minute.

     

    yes both disk are IDE and spin down works, auto power off happened to me when there was no support for the card.

     

    Hi,

    is a solution has been found for that problem ?

    i run ESXi 5.1 on a proliant N40L , i got Xpenology working like a charm with the release from the ESX post since months , however with that release which i really want to have (newer version and VPN is working) , i am stuck , as soon as i start the VM with my 4 * RDM disks then the VM shutdown same as you

     

    any clue will be very appreciated

     

    Thanks!

    XT

    XPEnology DS3612xs DSM 4.2 build 3211++ (repack v1.2)

    in DSM 5.2 and earlier (Legacy)

    Posted

    Final got this repack installed on my esx 5.1, added an extra disk as IDE 0:1, removed floppy and cd drive, reuploaded boot image after grub error 22.

     

     

    Please help , i am loosing my nerves and become really crazy

     

    i don't see at all what i am missing , i spent hours to get this repack working , i am in a loop , each time i reupload vmdk i get the configuration lost so install begin from scratch again and again !

     

    i am on ESX 5.1 , i tested vmdk converted in vmware mode (ide) and ESX mode (SCSI) but that does not make any difference

     

    what make me crazy is if we reupload initial vmdk how to not rebegin from scratch ?

     

    i feel desperate , please advise

     

    thx

    XT

     

    solved , i had to create a second IDE disk using vmware workstation then upload the full VM to my ESX , i can't add an IDE drive to the VM when created from ESX

    XPEnology DS3612xs DSM 4.2 build 3211++ (repack v1.2)

    in DSM 5.2 and earlier (Legacy)

    Posted

    Final got this repack installed on my esx 5.1, added an extra disk as IDE 0:1, removed floppy and cd drive, reuploaded boot image after grub error 22.

     

     

    Please help , i am loosing my nerves and become really crazy

     

    i don't see at all what i am missing , i spent hours to get this repack working , i am in a loop , each time i reupload vmdk i get the configuration lost so install begin from scratch again and again !

     

    i am on ESX 5.1 , i tested vmdk converted in vmware mode (ide) and ESX mode (SCSI) but that does not make any difference

     

    what make me crazy is if we reupload initial vmdk how to not rebegin from scratch ?

     

    i feel desperate , please advise

     

    thx

    XT

×
×
  • Create New...