Search the Community

Showing results for tags '6.2'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Readers News & Rumours
    • The Noob Lounge
    • Information and Feedback
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN
    • CHINESE
    • HUNGARIAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Found 9 results

  1. jun

    DSM 6.2 Loader

    Hi, everyone, Thanks for you patience. A new ds918 loader support 6.2/6.21 is uploaded. whats new: uefi issue fixed. i915 driver updated. link https://mega.nz/#F!Fgk01YoT!7fN9Uxe4lpzZWPLXPMONMA ---Beginning of addition by polanskiman--- Spoiler [/url] ---End of addition by polanskiman---
  2. Загрузчик 6.2 качаем тут. Пока для 918, будем надеяться, что появятся и для 3615, 3617.
  3. I am in the process of building a kvm host, and will have xpenology running on it. But notice the lack of virtio and sr-iov (ixgbevf) modules. So in the process of building them decided to create some helper functions to facilitate the process. Here is the link to the github page with the script: xdsm-build-utils I was able to create a synoboot image that supports both ixgbevf and virtio_net for bromolow 6.1, I was also able to make one for 6.2 but it only worked for the first boot/initial install once you install the .pat file it would error out. (May need to change the config for make but not sure what am I missing or maybe I am using the wrong source) There are also some helper functions to run inside the NAS to obtain and set MAC the real MAC address to generate and set the serial number (based on https://xpenogen.github.io/serial_generator/index.html) and to get and set the pid/vid for the boot device plus mounting the synoboot partitions. Anyway here is the link for anyone that wants to use it. XDSM-UTILS
  4. I have been able to get my Mac Mini Server 2012 model to boot with Jun's 6.1 3617 loader and it works great. I was able to see the NAS on the network using Synology Assistant and connect just fine. However, I have had no luck getting Jun's 6.2 beta loader to connect to the network. It appears to boot just fine, but I never see it on the network. I tried: Both the 3615 and 3517 loaders Set the PID/VID of the USB Tried 2 different USB drives; all boot, no network Set the mac1 to the actual NIC mac address. I assume the NIC chipset is compatible since it works in 6.1. Is it possible that 6.2 doesn't support my NIC chipset while 6.1? Or, have I failed to cover all my bases on setup/configuration? Thank you.
  5. Подскажите где взять загрузчик для VMWare? Подставлял synoboot.vmdk от загрузчика 6.1, но так и не победил. На аппаратном хосте не помню какая Асус/КореАй5/8Гб ддр3 все 6,2 загрузчики поднялись, DSM встала, всё работает. На более древних матерях, не поддерживающих режим AHCI загрузчики стартуют, в файнд сино и сино ассистент определяются, но винты не видят.
  6. Hello! This is a short guide about how to downgrade from DSM 6.2 to DSM 6.1 after a failed upgrade. I made this mistake myself, so i'm sharing how to fix it! Your going to need a spare HDD or SSD. Make sure there is nothing on it. You've installed DSM before, so you should have your synoboot.img from JunsLoader. Your current bootloader on your USB in now NONFUNCTIONING, you will need to reflash your USB with JunsLoader. Once you have your new, reflashed USB stick, unplug ALL drives from the motherboard. Make sure there are NO SATA interfaces connected. Plug in your new, empty drive to the motherboard and boot from the USB stick. (You will need a keyboard for this step) The first option in the GRUB interface is what you are looking for. Use http://find.synology.com or Synology Web Assistant to find your DSM. Follow the steps and install DSM 6.1 from a PAT file. DO NOT INSTALL 6.2 IF YOU LEFT A DRIVE IN IT WILL SAY RECOVER. GOTO 2. Let Synology do its thing and eventually you will have a working 6.1. While the PC is ON, connect the drives to the motherboard (with you data on it). Under Storage Manager they will pop up and say Unused. You might need to reboot, at this option. It took me some fiddling around, but eventually Synology will prompt you with a Recover Crashed Partition prompt. Click Yes. All of your data will appear, and Synology will automatically perform RAID scrubbing.
  7. Hi Guys, I picked up some old hardware from my work, and I wanted to try out Xpenology on the system. I'm running into a hiccup when trying to install it on an old HP xw8400 system. I'm using a USB to install the DSM and using Rufus to write the .iso or .img file to the USB. When I go to install it I'm greeted with a lovely "no system disk or disk error" message when I go to boot from the USB (The option is available under the boot menu). I've scoured the BIOS settings, but I'm still unsure what the issue could be. Following many attempts of different Rufus settings, and trying both the .iso and .img files created by JUN version 6.2 I'm still unable to get past that point. I then tried a copy of UNRAID to see if it was an issue with the USB boot, but it loaded up just fine. I also took the same .img file and used Rufus on the same exact USB I've been attempting the install with, and it worked without a hiccup on a Supermicro system that is from the same era (within 2 years of the HP workstation). If someone has some knowledge of what has worked for them, or if there is a BIOS setting I'm missing please let me know. I did see that there is a BIOS update, but according the release notes there isn't any changes made to booting or USB. The latest build is 2010, and I have the 2008 version currently. My system is HP xw8400 2x xeon 5150 16GB RAM 12 port LSI RAID Card Quadro Graphics Card 14 Hard drives of various sizes ranging from 3, 2, and 1 TB in size (4 of which are plugged into the motherboard, but I tried with them plugged in and with them not) Dual Redundant power supplies Any help is appreciated!
  8. Hey everyone, Currently playing on an N40L, using Jun's loader 1.02b, and succeeded to use the latest DSM 6.1.4-15217 Update 4. However, i'll replace both my N40L and my genuine DS215J with an HP microserver gen10 next week, and i'm planning to take the latest possible DSM. Updating DSM 6.1.4-15217 Update 4 to DSM_DS3615xs_6.2_23511 or DSM_DS3615xs_6.2-22259 results in failing DSM. I'm not sure if Jun or anyone else is working on this but i wish and really hope it . So basically I'm looking for a tutorial/guide on how to install DSM 6.2 beta (yet) on Hp Microserver (gen10). Alternatively i wish to understand how to do some logging / data collection of the loader to help the guys make a working loader for DSM6.2. Any suggestion is welcome! R/Mark (And thanks goes for Synology for making such a shit product (DS215J) with a great software (DSM) and with the worst customer support who can only say we are sorry for the inconvenience but not helping at all. This really helped me a lot to decide and build a XPEnology lately.) Just found the other topic as well, but not updated in the past 2 months.
  9. I used to run DSM 6.1.4 on an HP Microserver Gen8 using loader 1.02b. a few days ago, I accidentally upgrade the DSM to 6.2 beta (it is stupid, i know), and the box just didn't boot anymore. In Synology Assistant, the Gen8 is not even discoverable (two NICs on Gen8 was configured as Bond connection in 6.1.4). I tried to prepare a fresh USB with 1.02b Loader, and after the box is booted into reinstall mode, I actually can find the both NIC in Synology Assistant, and the status is showing as recoverable. Same thing as if I access the box in the browser, it asks me to recover, but the problem will remain after choosing recover in either way. Please kindly help me on that. Thank you very much.