Jump to content
XPEnology Community

Dfds

Moderator
  • Posts

    598
  • Joined

  • Last visited

  • Days Won

    16

Posts posted by Dfds

  1. Just now, bajwha said:

    which bois version do you have? I think this is the issue with the Network card. I have installed win 10 just for testing and not getting ip from DHCP.

    It was "theBay's" bios, do a google search & you should find it.

  2. 3 minutes ago, bajwha said:

    Did you make any special changes in BIOS? and which usb port did you used to boot?

    I'd already disabled C1E support & didn't make any other bios changes. I used the internal USB port.

  3. 3 minutes ago, bajwha said:

    Can you please share how you did that. I have followed everything. also changed the MAC and VID,PID but not cannot found xpnology with Assistant.

    please help

    For a test of DSM 6.2 I removed all of my existing disks & USB stick, created a new one with jun's 1.03b loader, setting the vid & pid as normal, then just went through a clean install. It should work as a migration from 6.1 but as I don't need 6.2 at present I haven't tested that.

  4. 38 minutes ago, Pagi said:

    Hello. I have a problem with upgrade from 6.1 to 6.2.

    I have working 6.1 DSM on bare metal PC.

    Now I build new USB stick with 1.03b loader using proper VID/PID, serial and MAC of physical NIC.

     

    Grub is starting but nothing else, xpenology don't acquiring IP from DHCP.

     

    I did everything the same as for 1.02b, but without success.

     

    How is the proper way to upgrade from 6.1 to 6.2?

     

    In order for people to assist you please state what hardware you're using. Also you might want to try 6.2 with a spare HDD just to make sure that your hardware is compatible.

  5. On ‎8‎/‎13‎/‎2018 at 2:46 PM, ZerOneX said:

    Guys, anyone here tried to update to DSM 6.2 using JUN's LOADER 1.03? Tks

    As very few people are likely to have that hardware I would suggest that you test it yourself with a spare HDD.

  6. @gold8009 I have translated your post this time but please ensure that future posts are in English

    39 minutes ago, gold8009 said:

    Loader: Jun's loader 1.03B.

    Network: RTL8111

    CPU: Core i7 8700T

    Memory: 16GB

    ESXI6.7

    DS3615 1.03b

    SATA Drive: ASM1062 Passthrough   

     

    Problem: Find the "NAS" host and can't find the hard drive on "ASM1062". 1.02b ds3615 is good. Doubt 1.03b "extra.lzma" does not have "ASM1062" driver

     

  7. The N54L will run 6.1 quite happily, you will however have to disable C1E support in the bios. As you're running below 5.1 it is advisable to upgrade to 5.2 before attempting to upgrade to 6.1 UNLESS you do a clean install. As for VM's, inless you aphave a real need I'd stick with bare metal. See this guide to upgrade.

     

  8. 2 hours ago, necoalex said:

    After boot from Jun's 1.03b, http://find.synology.com/ can show my nas ip and get to the setup webpage. However the NAS webpage shows nodisk, the harddisk cannot detected, tried 3615xs and 3617xs bootimg but not working.

    Use xpebootloader back to 5.x DSM, it can show the harddisk works well.

     

    is the bootloader missing the sata controller of my motherboard's model?

    it is a Lenovo A55 Desktop, has 2 IDE port and 2 SATA, in bios IDE 0 1 is the IDE and IDE 2 3 is SATA (the harddisk is running at IDE 2 the sata port)

    Intel NM10/ICH7 Family SATA Controller

     

    Can I put the controller into the boot.img or any config need to edit?

     

    Thanks!

    Your Sata disks need to be running in AHCI mode in the bios, not IDE.

  9. 2 minutes ago, Cr4z33 said:

    Test on an empty spare hard drive was succesfull with hardware in signature!

     

    Now how should I upgrade by using the normal system without loosing personal data and config?

    Only you can decide that. If the test was successful everything should be fine, however there is always a risk that something can go wrong when performing an upgrade & it is advisable to have a backup of any data that you aren't willing to risk loosing.

    • Like 1
  10. 1 hour ago, traianstc said:

    I never modified anything when i installed xpenology to microserver gen8, i don't use quickconnect. And it worked everytime.

    I repeat, the same usb stick with bootloader 1.02b who is working perfect in microserver gen8, i doesn't work with fujitsu server..

    I thought modifying vin/pid is only a requirement for functionality of quickconnect.

    Setting the correct vid/pid of the USB stick has nothing to do with quickconnect. It will however resolve the error 13 issue you're having.

×
×
  • Create New...