Jump to content
XPEnology Community

CtrlAltDel

Member
  • Posts

    344
  • Joined

  • Last visited

Everything posted by CtrlAltDel

  1. What mtu rate did you have set for the nic? If it was above 2k you may have hit a known issue. Try a live linux boot and edit the file where the mtu value is declared and reboot. The default of 1500 is a safe value.
  2. The two nic's will show a independent devices in Syno Assistant because they are acting as single lan connections with unique macs, and they will get an IP address assigned my dhcp accordingly. If you go into DSM > Network > Network Interface and both nic's are showing as connected then they should both move data on the lan. You can click on > Create > Create Bond to make them work together in link aggregation and then Syno Assistant will only see one connection to the server. It works for me on a Gen8 bear metal, with no value set in grub for mac2= and both nic's move data whether used as singles or aggregated.
  3. When you added the mac2= did you also try editing the synoinfo.conf file to manually set it as active? It should then show under Hardware and Power with a check box for WOL. Maybe you can use that to see if the card is accessible on the network?
  4. @y333, The processor is reported as an i3 because it's a hard coded value. Past Xpenology builds have reported the processor which is installed in the real Synology device. For example an AMD chip will be reported as an i3 but the functionality will be based on you physical chip features, whether they are better or worse than the i3.
  5. Power button info is here > https://xpenology.com/forum/topic/6253-dsm-6xx-loader/?do=findComment&comment=55463 afaik that's still current but things are moving so fast things my have changed. Don't extract the zip in the root copy the files up individually and set executable for scripts. Power Save seems to work out of the box. On my system the governor is set to performance rather than power save/conservative. I used the old method to set power save. That's because I couldn't find the file to set the governor state in the default build. WOL works once you add the shutdown fix and make it executable. Note rc.d has moved in DSM 6 it's now in /usr/local/etc/rc.d. Edit: You need to use the MAC that you used in the grub config. You can get SHR functionality back and use btrfs. This post gives some detail but it's now out of date in some respects > https://xpenology.com/forum/topic/6253-dsm-6xx-loader/?do=findComment&comment=55037 .
  6. It maybe that Windows is detecting the uefi stuff? You could try the drive in a different machine or use a linux boot disk.
  7. The governor works out of the box but it seems to be in "performance" mode. Is there a way to tell it to use "conservative" or "powersave" etc. without applying the old fix we used in DSM 5.X? I greped the usr folder but couldn't find the string with my searches.
  8. The improper shutdown is a known issue if your machine has no console. You need to edit /usr/share/init/syno_poweroff_task.conf and change console "output" to "none" and if you want to stop spam in some of the logs you need to do the same in a few other files. See Jun's original post #1 of this thread for more details. Without the quotes.
  9. This info was provided by Setsunakawa earlier in this thread... You could try SataPortMap=51 assuming you have the four bays and the onboard sata port populated and the esata is classed as a separate controller. I'm only using three bays so I can't test the theory.
  10. That's good to know. I don't use QC either but here's my thinking...our machines connect to Synology servers for a few reasons, and if their systems log serial numbers and macs for any reason it seems wise to me to pass them a valid pair. I have no idea if they do track them but it seems prudent to assume they do and it takes no real effort. @lewis666, useful link thanks and your English is fine. @macleaned, glad you got it working.
  11. You need a valid serial # and mac # pair that's what the spreadsheet gives you. Did you prefix your vid/pid with the 0x? The general consensus is that error 13 is caused by one or more of these values being invalid.
  12. Big thanks to Jun and Arcao for making it happen! Gen7 N40L success using Arcao's new img linked above. There goes my weekend.
  13. You can find the answer here > https://xpenology.com/forum/topic/6253-dsm-6xx-loader/?do=findComment&comment=55037
  14. No not that I'm aware of. My first install was a migration from 5.2 to with shr and the shr was recognised in DSM 6 no problem. After that I did a fresh install on the same box and by default shr isn't an option under DSM 6. You can edit the config file to re-enable shr which works perfectly. I have drives using shr with btrfs on the new DSM 6 build. I can't say for sure about shr 2 as I have no first hand knowledge, but my guess would be that it should be fine. I'm not sure if a migrated system would allow a new disk group/volume to use shr by default, but editing the config file should soon fix that problem.
  15. The new loader doesn't work with AMD based mother boards at the moment. It would require the kernel to be recompiled from the source. That can't be done because the source isn't available. The new system is a Dynamic patch and it can only work based on the core of the kernel which is Intel based. That's my understanding of how things stand at present using Jun's method and the associated derivatives. AMD is now supported.
  16. Someone on the forum (probably in this thread) mentioned an expansion limit exists using SHR and that's why it's being phased out of the high end devices. Seems a bit daft to me because there will be lots of users who will never reach the limit and SHR would be far more useful. Besides if Synology are concerned about the limit all they needed to do was to put a warning comment next to the option, and then the user could decide which is best for them based on their real world use case. It's a big and unique selling point they're giving up on those devices for no good reason imho.
  17. See the SHR section of this post > viewtopic.php?f=2&t=20216&start=420#p74492
  18. CtrlAltDel

    DSM 6.1 Beta

    Looking at the packages that are in Beta seems to indicate a push towards a more corporate centric development cycle. The rumours about Synology opening their own data centre in Europe also suggests they're gearing up for the business market. There is a level of mistrust in using third party cloud services as well as using any software and servers with any connection to American companies with good reason imho. It looks like Synology are planning to offer private server hosting or some form of collocation solutions. They are building the tools to bring mission critical and sensitive data back in house, while reducing the requirement for expensive IT departments to manage the systems. This is probably aimed directly at the small and medium business sector where IT budgets don't tend to extend to in house IT departments. It also seems like Synology are looking to attract M$ small business users, which is a smart move given the cloud based model that M$ is busy steering people into. Synology could set themselves up as a cost effective solution to M$ with systems that don't rely on any M$ operating systems and expensive licensing etc. The downside will be for the smaller businesses and domestic users who will get caught up in the new licensing models, which are probably being created right now, going by the new licensing for Virtual DSM and MailPlus. Current users are beta testers who can expect to pay for what's to come in the new Synology office suit and other business solutions. No doubt there will be trivial levels of free entry by way of limited numbers of free users for each package. I guess users can always install thirdparty packages in many cases at the expense of ease of use and Synology support. Maybe I'm just an over sceptical pessimist? My storage always seems to be half full if that's any indication. Currently under development: BETA Backup *Cloud station Server, *Sharesync and *Cloud Sync. Media Audio Station, Photo Station and Video Station Business *Office *Surveillance Station Security *Intrusion Prevention Utilities *Virtual DSM Manager Productivity *Calendar *Chat * These packages are classed as business and productivity.
  19. The WOL tool is a quick 'n dirty custom autoit script which a friend of mine knocked up one night. But other scripts that send a magic packet should work just the same. Yes DSM Finder wakes the server up no problem. Yes I did add the powerdown script but it needs to be put in root/user/local/etc/rc.d in DSM6.
  20. One thing to check is the ntp service is setup and that the DSM has the correct time. When you reboot go into bios and check the time/date if it's set to a default/incorrect time fix it manually, save bios and reboot. Then see if your machine can complete a reboot cycle without the bios error? Afaik the regional and ntp settings need to be active to help prevent some bios corruption issues.
  21. For clarity Jun's dynamic patch works for some popular VM's with UEFI support and Bare Metal on machines with UEFI, systems must be Intel based at this point in time. Setsunakawa created a modified img using Jun's dynamic patch and it works on bare metal Intel machines which don't support UEFI. Jun and Setsunakawa both added some additional driver support for some of the more common hardware used by the Xpenology community. My post is Gen8 Intel Baremetal Non-UEFI centric because I have first hand knowledge of that method. That said, I think there should be enough info to help others get to the relevant information in the thread that's needed to get up and running, on other hardware.
  22. I misunderstood your question and even now that I get it I don't know the answer, sorry.
  23. Yes. See here > viewtopic.php?f=2&t=20216&p=74492#p74492 Thanks, I found that after posting this. The problem is that if I buy a Gen8 I would also like to have a Windows 10 VM on it, so I would also need to run XPenology on a VM. I understand that DSM6 is still work-in-progress for a VM on Gen8? I can't give any first hand info on VM's and their many flavours because I use baremetal, sorry. If you read the first post by Jun he covers the VM's currently working with his dynamic patch here > viewtopic.php?f=2&t=20216 . I'm not up to speed on the latest developments in the "Working DSM 6" thread here > viewtopic.php?f=2&t=16114 . Afaik those two threads cover all currently available options for getting DSM 6 running using Xpenology.
  24. My 3rd party WOL tools are working fine...I had been busy pasting in a MAC address that had a typo in it. Once I spotted my error and corrected it the tools worked. Also remember to use the same mac as used in the grub config file.
×
×
  • Create New...