Jump to content
XPEnology Community

chege

Member
  • Posts

    143
  • Joined

  • Last visited

Posts posted by chege

  1. If you need s/n only to fix problem with random IP then its easier way to do this. Just setup static IP under DSM. If your server works then better dont try to mess with loader that someone else "burned" into it, like you said, you dont even know how server is prepared to work with synology. Only issue you have atm is that you cant migrate to dsm 6.x, and you have to turn off auto update options.

  2. Maybe something is changed lately, but few months ago, when synology released dsm 6.1.1 i could use push notification w/o problems and i didnt need sn/mac other than used in xpeno loader. My setup was on esxi 6.02, and notifications received on android phone. I did nothing more than turn it on.

  3. What you mean? You don't need keyboard other than to select boot option while loader is loading. after that is all thru GUI.

     

    Its not exactly true. On dsm 5.x loader you can login with credentials like thru ssh.

  4. My question. You were running DSM 5.2 on xpenology DS3615XS just fine. Why did you upgraded to Jun's DS3617XS instead of the same Jun's DS3615XS bootloader?

     

     

    I aint Rhubarb so maybe only he can answer exactly. But I am making a guess here that it really doesn't matter if you go for DS3615XS or DS3617XS because you need to create a new usb drive to boot the DSM 6.1 or later iteration anyway. Moreover latest Jun's loader for DS3615XS is v1.02a whereas the latest is v1.02a2 for DS3617XS, which is a later revised version. Although I remember v1.02a2 only contains very minor change, it still make sense to go for the later version if you were to try something new.

     

    Having said all above, neither of the two loader work for my setup with both error 13, which really is a bomber. :-|

     

    1. jun's loader v1.02.a2 is a fixed loader for ds3617xs, v1.02a has "time bomb"

    2. ds3617xs is compiled for new cpu architecture, with new set of instructions, hardware acceleration etc. if you use it on old cpu then it can cause problems on some part of dsm and packages, but users will blame xpeno loaders. for sake of safety and peace of mind its highly recommended to use emulation of ds3615xs

  5. Hello,

     

    Firstly thanks for support here.

    I had ESXi 6.5 and 5.2 version of DSM on HP Microserver Gen8. 1x 120 GB SSD, 4x 3 TB seagate NAS hdd (RDM).

     

    I tried to install loader 1.02a2 (DS3617xs) and DSM 6.1.1_15101. But I get always "error 13".

    But I installed loader 1.02a (DS3615xs) and DSM 6.1_15047. This is working with my all data.

     

    I am using 8 GB SDCard for loader. I tried same SDcard for install. (I switched Bare Metal)

     

    Why did not install loader 1.02a2 (DS3617xs) and DSM 6.1.1_15101 ?

     

    Sincerely,

     

    You cant switch from ds3615xs to ds3617xs without fresh install. Those hardware are not compatible, different architecture.

  6. My "live" system currently runs DSM 6.0.2-8451 update 9 via ESX 6.5. This is with Jun's v1.01 loader for DS3615xs.

    My data drives are connected to my LSI2008 based HBA flashed to IT mode and passed through to this VM.

     

    Yesterday I created another VM but this time based on the DS3617xs using Jun's v1.02a2 and created one virtual disk as a test. It is running DSM 6.1.1-15101 update 2. So far so good. No issues. No time bomb errors. Installed some apps as a test. Will try this for a week or two to make sure there are no issues and then create a new VM with the same settings and pass my drives through.

     

    Currently on my "live" system, volume1 is setup as SHR. should this migrate ok to the new 6.1.1 based VM?

     

    Cheers,

    James

     

     

    Sent from my iPad using Tapatalk Pro

     

    I dont advise to migrate to DSM 6.1.1. There is problem with migration on esxi vm. Before you do that with live system do some tests with migration first. As far as i know all users doing migration on esxi reported brick system, including me.

  7. ok I can get the server to load the network card to GigE if I remove the HDD and let the jun loader run its course, it sees my nic as a 100Mbps Nic then once the loader is done it switches to GigE which is normal, I can ping ip but cannot do anything like ssh. If I leave the HDD in the server bay the nic light stays 100Mbps and the thing is just dead in the water. I dont mind downgrading to 6.00 stock and attempt to just get 6.02 which was my initial intentions.. polanskiman HELPPPP Im seriously out of ideas. I even did the lzma overwrite which made no difference. The IP is pingable but find.synology does not see the server with no drives. thiu really sucks...

     

    Ive got problem to find my dsm 5.2 with find.synology.com, it is up and running for years, but i can find it with synology assistant app.

  8. The last vm I posted is using Jun's alpha loader for 6.1; I'm still using it with no issues, didn't update to 6.1.1. I don't have the time to try and test other loaders :sad:

     

    There is issue when you upgrade DSM 6.x to 6.1.1 on esxi vm. Basically system is bricked.

  9. Sorry I meant SHR not SSH.

     

    I remember we had to install a add a package source to install Nano to edit synoinfo.conf. If I remember correctly, that was the right source http://packages.synocommunity.com. Unfortunately, I can't find Nano or VI anywhere. I also enabled all publishers... I added a bunch of sources and none of them add Nano or VI. Also, most of them don't add any package...

     

    Is it because Nano and Vi don't work with 6.1?

     

    VI is part of DSM, dont need to be installed. There is not many packages yet since they are not prepared for DSM 6.1.

  10.  

    Im not sure this is exactly what you need but good start i think:

    You can't do tunnel without external server with white IP :lol:

     

    Maybe, i dont know. Im using to tunnel from PS's with windows meshcentral.com. There is also client for linux but i never tried it.

  11. Reminder to all:

    For those who are not yet aware, the use of QuickConnect is an abuse of Synology services and servers. Using QuickConnect only brings bad reputation to this project. You are kindly advised to used a customs DDNS which will have the same function as QuickConnect. Any post inciting in using QuickConnect will be deleted without warning.

    You are right, but QC - like a single easy way accsess to storage when ISP do not give white dynamic IP.

     

    QC = tunnel to storage that do not matter about your IP / ISP / Network / Etc problems.

     

    If someone know services or easy way to acsses to storage (without buying wps, wds, hostings) and gives QC functional - pm me please :shock:

     

    Im not sure this is exactly what you need but good start i think:

     

    https://dnstunnel.de/

  12. Just for info. Dont trust web assistant. Today i found out that web assistant find.synology.com didnt found my baremetal xpeno with DSM 5.2. It is strange since this box could be found some time ago and it can be found with synology assistant for windows.

  13. Hi Guys

     

    I have a question on VM.

     

    I have a successful system running with Jun's original Loader in VM (VMware 6.5) with DSM 6.0.2-8451 Update 9

    I initially setup one virtual hdd from my datastore at 300Gig but have a need for more space.

    I have over 700gig free on my datastore and want to increase this drive to 500gig or 600gig.

    Can i do this ?

    Will the synology pick this up and use the additional space ?

    I know i could just add another virtual disk and provision it but id rather have one volume.

    I dont want to lose the data so thought id ask here if anyone has done this, before I attempted it and possibly trash my system and data ?

     

    Many thanks :geek:

     

    Why dont you try to create test VM with, let say, 20GB hard drive. Install some packages, add fake data and then change hdd size. Best lessons comes from practice. It takes about 1 hour or less.

  14. agree to point 2. Have 2 NIC.

    mac1=xxxxxxx86

    mac2=xxxxxxx87

    If I boot, one NIC gets MAC 87 and the other one the real MAC. But both are working

     

    Try both mac to be odd or even last hex, dont remember. But since you said its 87 then i think its odd.

     

    The original MAC from Lun's loader is xxxxx85. I installed a second machine for test and need to change it, because same MAC at same network doesn't work. That was the reason why I count it up. Is there a relationship between MAC and Serial number? I don't want to use quickconnect. Can I use that way?

     

    Then use mac xxxxxx89 instead 86. But IMO best option is to use hardware mac address, just change in grub.cfg to mac1= and mac2=. That should be enough.

     

    You can use same serial on all xpeno you have or just change 1 number in it.

  15. agree to point 2. Have 2 NIC.

    mac1=xxxxxxx86

    mac2=xxxxxxx87

    If I boot, one NIC gets MAC 87 and the other one the real MAC. But both are working

     

    Try both mac to be odd or even last hex, dont remember. But since you said its 87 then i think its odd.

×
×
  • Create New...