Jump to content
XPEnology Community

neotronic

Member
  • Posts

    21
  • Joined

  • Last visited

Posts posted by neotronic

  1. Hi,
    I have a N54L with DSM 6.1.3, but WOL doesn't work anymore.
     I have problems with the Mac and Serial.
     
    Schould I use the Mac from my N54L networkcard?
    But how can I generate a serial, which fits?
     
    Or can I choose any Mac an Serial by the generator?
    Schould i flash my Networkcard after that ?
     
    I only want to start the NAS by Magic Packet, over the fritzbox.

    Did you upgrade or clean install?
  2. Hi!
     
    I probably didn't do anything I had to. Please help me find out what I've forgot.
     
    Hardware: HP Microserver N40L
     
    These are the steps I took:
    * Download jun 1.02b loader
    * Edit grub.conf - VID+PID, SN, MAC edited
    * C1E disabled in BIOS
    * Copied the img to USB
    * Booted from USB
     
    I can reach my "Web service", nothing was found with find.synology.com, the 22 and 5000 ports are not accessable.
     
    I've installed the Synology Assistant, which was also unable to find the NAS.

    Can you just enter the IP into your browser and you should see the initial page. If that's not working check your router DHCP table or scan the subnet for addresses of your NAS. Not sure if your N40L has a different NIC to a N54L.
  3. On 7/28/2017 at 7:31 PM, mar1boro said:

     

    so did you check if that miracle really happened?

    Hi @mar1boro and sorry for the delay it's been a busy week at work. I did get to check and it looks like I did build a VM with DSM 6 but in VMWare Workstation not Hyper-V. Sorry for raising your hopes on this this issue - I'm in need of a Hyper-V solution too. Like many I keep trying different bootloaders in Hyper-V and from memory the issue is always lack of a working NIC. I did have a DSM 6 img file that I thought was working with Hyper-V but dispite a working NIC - the IMG has that 'failed to create a volume' issue so I must have given up. Hope a solution arrives soon and sorry for my mistake again.

  4. I try to install Xpenology on baremetal and failed. During the DSM installation, I was forced to manual install but  then it keep saying "Failed to install the file. The file is probably corrupted.(13)"
     
    I try to use DS3617xs so I downloaded DSM_DS3617xs_15152.pat. I checked the MD5 and it's ok.
     
    Is there anything I missed? 

    That happens if your pid and vid are not set correctly.
  5.  
    I tried to use DS3615xs 6.1 Jun's Mod V1.02b.iso in Hyper-V (Gen1) with no luck. The virtual machine doesn't boot with it. Still no chance to use dsm6.1 in Hyper-V?

    I have it working in Hyper-V. Not sure if It's 1.02b though. I converted the img to vhd and set it as the 1st drive. Hope it helps.
  6. Hi, thx for the reply.
    How do u read the USB after u format and burn img file in it? which software i need to read it?
    Thanks.

    Just your own PC. If you wish to edit the image directly use OSF mount to mount the image/partition. Make your changes, save and write the boot image again.
  7. I have succesfully updated my n54l from 6.0.2 to 6.1.3 update 1 with ejt01´s guide. I can confirm that this works fine.

    The only issue I´m having right now is that unfortunately WOL has stoppped working since I updated. I got the same MAC as before and inbefore it worked flawlessly. If someone has a suggestion as how I could get it to work again, it would be much appreciated [emoji4]

    I think WOL is broken with 1.02b - at least mine is. Other posts I found today also suggest GEN8 servers also won't WOL.

  8. Hi, I also have problem to locate the grub_ver file... how do you check the USB after you burn the img in it??? thanks.

    I found the grub file was created on the USB boot media after installation of the latest update. The trick is to power off after the update restart and look for the file on the USB media (plug it into your PC), edit the file and update with the version of the update you just applied. Reinsert the boot media in your server and boot up. You should be ok then.
  9. On 20/07/2017 at 11:24 PM, davdi1982 said:

    I have used the 1.2b i think (please find the file attached :smile: )

     

    The only problem remaining since the dsm 6.0, it is the fact that i cant reboot it. I need to power off an power on manually, i dont know why.

     

    edit: Previously i had updated to 6.1.315132 and not this one. I did the last one and all seems ok.

    HP proliant gen7 (reboot seems ok now)
    Loader JUN v1.02b DS3617xs
    Misse avec succès . DSM 6.1.3-15152
     

    The boot loader works well for me too. The only issue I can find is WOL isn't working. I've seen other posts by GEN8 users having the same issue. My server is GEN7 - so both models may be affected. Is your WOL working ok?

  10. 3 hours ago, milo said:

    Hi, what is the difference between 1.02b and the one provided on 1st page? Is it simplify the way of the installation? Is it suitable for the upgrade from dsm 6.0 to 6.1? 

    Can I have one? Many thx.

    I'm not sure what the differences are other than this shows 1.02b on the boot menu and it seems to support the latest DSM Update 1. Hopefully you can also test and find good results. I've attached the file. I'll be doing some upgrade testing today from DSM 5 and and will feedback asap.

    synoboot.img

  11. I have a new 1.02b boot image that works for bare metal fresh installs - just tested this today and now running the latest DSM with Update 1 applied. If anyone would like this please let me know. I take no credit for it - I received it from a user in another thread.

    Tested on an N54L only on internal NIC.

  12. Hi,
    I have successfully migrated my HP N54L from version 6.0.2 to 6.1.3 15152 and created a step by step guide below which worked for me.
     
    First Please read the upgrade tutorial by Polanskiman and this thread!
     
    Use this guide at your own risk. I won’t be held responsible for any loss of data or failures that may result in the use of this step by step guide!
     
    1.      Backup your data and system configs! You have the full responsibility!!!
    2.      Disable C1E setting in bios!!!
    3.      Start with the workaround script to copy network drivers at boot to prevent the HP micro server from not getting a network connection and become un-accessible
    a.      Create a shared folder called Scripts in volume1
    b.      Download the script update_patch.sh by Eduardo
    c.      Enable SSH port 22 in Control Panel / Terminal & SNMP
    d.      Use Putty to connect to your server log in with your admin account and password. Check that admin password is set.
    e.      In Putty to become super user type Sudo –i
    f.        Change permissions of your update file, type chmod 0744 /volume1/Scripts/update_patch.sh
    g.      Log out, exit putty, disable SSH access
    h.      Go to Control Panel / Tasks Scheduler and create a triggered task, select user root and select event boot up and then go to task settings and type in /volume1/Scripts/update_patch.sh and finally enable the task!
    4.      Go to Control Panel /Update & Restore and update to DSM 6.1.3-15152
    5.      When the server reboots turn it off and unplug your usb stick
    6.      Make a backup of your usb stick with image writer
    7.      Note VID, PID, mac address and serial of your grub config file of your usb stick
    8.      Write with Image writer the loader image file JunsMod102a-test-NICadd.img by Khile to your usb stick
    9.      Update the grub config file of your usb stick with VID, PID, serial number and mac address
    10.   Update the GRUB_VER file of your usb stick with DSM Version to 15152
    11.   Put back the updated USB stick to your server and start the server
    12.   Start Synology assistant to check when the server comes online, if it does not come online wait about 15 minutes for the update_patch script to run and to copy the network files to the right folder after that is done it will reboot. Mine rebooted twice however my server always needs to be turned off at boot as it does not reboot the usb stick for some reason.
     
    If your migration does not work out for some reason you can reinstall by pulling out all the hard disks from the server and select forced install, when the server appears in the Synology assistant insert the hard disks and install fresh.

    Thanks for the tutorial. Do we always leave the scheduled task enabled - so it runs every boot or can it be disabled once 15152 is working? Thanks.
  13. I updated from 5.2-5967 update 2 to update 3 via control panel and everything seems to be working fine.
     
    I am running a bare metal build based on the ASRock C2550D4I.
     
    I am using XPEnoboot_DS3615xs_5.2-5967.1.
     
    Thanks again to everyone here.

    Thanks for the info. Do you have a link to the boot loader you are using please.


    Sent from my iPhone using Tapatalk
  14. can this bootloaer updated to 1.02b ?
     
    i'll try it this weekend : JunsMod102a-test-NICadd
     
    Thanks

    It would be great to have an N54L 1.02b boot loader.


    Sent from my iPhone using Tapatalk
  15. N36L working, but not migrate from 6.0.2!
    Clean install with DSM 6.1.2!!! [emoji4]
     

    Can anyone running the latest pat on bare metal comment on how uptime has been going. Are you seeing any crashes or issues when your server is on 24/7? Thanks.


    Sent from my iPhone using Tapatalk
  16. A few people have said they only got it to work as a new/clean install im looking into it but that may be an option 

    I see what you mean now. So I need to use your loader and install the latest pat and see how it goes. Thanks for the feedback. I'll be able to test that on bare metal soon and report back.


    Sent from my iPhone using Tapatalk
  17.  
    Have you disabled c1 support as DSM_DS3615xs_15132 is supported if you follow my guide it has been tested on n36l alway up to the n54l and all work.
     
    1) Make sure c1 is disabled in bios.
    2) Select force install (install pat)
    3) one reboot select top option (dont select amd)
    4) give it time 5-10 mins to come up (mine took around 10 mins first time)
     
    any issues please post back 

    I did disable C1 in the BIOS but the latest pat didn't work for me and the server was unable to obtain and IP address after a restart. Maybe I should of fixed the IP to manual before the restart when applying the latest pat. I still have the test disk and USB for further testing. Other than that I did follow your install guidelines and everything worked apart from the latest pat.


    Sent from my iPhone using Tapatalk
  18. I did some bare metal testing over the weekend and and found the loader and 15047 pat file worked great on an N54L, and thanks to those who have made that possible. That was a clean install using 'force install' to begin with then just booting with default choices after that. I thought I'd then test updating to the latest DSM_DS3615xs_15132.pat file but despite installing ok and restarting - the updated server couldn't find the N54L's NIC so no further connectivity was possible. Would it be possible for someone to add N54L support to Jun's 1.02b loader? I'm assuming that Jun's 1.02b with N54L support would be able to support upgrading to DSM_DS3615xs_15132.pat which I believe is the latest available from Synology?

×
×
  • Create New...