naasking

Members
  • Content Count

    30
  • Joined

  • Last visited

Community Reputation

0 Neutral

About naasking

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. No, never found a solution. Strange that it still seemed to work running ordinary Linux, just not under DSM.
  2. Well, a fresh install seems to have done the trick. My previous configuration had been updated since DSM 5.1ish, so some errors had to have crept in over time.
  3. I'm running into exactly this error. Had DSM 6.2 running fine on this exact same hardware to backup my old server, then swapped the old server disks into this machine and migrated. Everything seemed fine except accessing DSM and ssh simultaneously kills the network and all network services, and I see these syslog errors everywhere. I've tried a reinstall with a different USB drive and the same flash image, same problem. I just tried a brand new flash drive with a freshly constructed flash image, as I thought perhaps the image itself got corrupted, but the problem remains. I think at this point whatever the problem is, it must be on the system partitions and it must somehow persist across reinstalls. Unless anyone has any other suggestions, I might have to do a completely fresh reinstall instead of trying to preserve all of my settings.
  4. The guides lately have been pretty helpful, but I have to say I'm still confused at how this works, or why certain apparent inconsistencies happen. For instance, I'm setting up a new machine with the 1.03b loader and the 6.2 series for the 3615. Jun's loader runs fine and I can load the installation page (http://find.synology.com) and setup the machine, but on reboot after installing the .pat file, it's no longer reachable on the network. Why would the installation load with the correct network driver, but the later step fail to load? Edit: I figured it out, on reboot the system was booting from the USB using UEFI. I had to disable all UEFI booting in the firmware to use 3615 with 6.2. One real bummer though is that hybrid raid/shr no longer seems available in 6.2 for the xs series.
  5. I have a working DSM 6.1 installation using jun's 1.02b on an AMD E-350 system, and I'm trying to see if DSM 6.2 with the new new jun 1.04b and 1.03b loaders are compatible. I've followed the typical instructions but upon selecting the right option from the grub menu, the machine immediately restarts. I assume this is because they aren't compatible, or is it perhaps only because there's a driver missing. Is there an extra.lzma with more drivers for these loaders?
  6. Is it possible to move a DSM volume to a new machine by moving over all of the disks? If so, what are the steps? For instance, does the new motherboard need the same number of SATA ports and I have to plug in the drives in the exact same slots on the new board?
  7. Just an update, the drops still happen but are much less frequent with the bandwidth limiter.
  8. So here's my partial solution: I noticed that the drops seemed related to burst traffic, so I used the DSM control panel's traffic shaping tab to limit the bandwidth of the problematic network card to less than 95MB/s (you may have to play around with this number). That seems to have eliminated the drops, but I'll keep you posted.
  9. That's a bummer. I was seriously considering replacing the board with something like this, but it too has a Realtek 8111 chipset. It's the H revision though, ie. RTL8111H. I'm gunshy on the 8111 chipset now, but since this problem seems to only have been reported in the E revisions in this thread, maybe it's a hardware bug in that edition alone.
  10. DSM 5.2 was great for over a year. But I need DSM 6.
  11. Machine boots fine, but network drops still occur. I have the same AuthenticAMD unknown vendor error: [ 0.000000] CPU: vendor_id 'AuthenticAMD' unknown, using generic init. CPU: Your system may be unstable. So perhaps it's all related to the spotty AMD support in Jun's current loader. Strange that everything mostly works though, and it's rock solid otherwise.
  12. Machine boots fine, but network drops still occur. I have the same AuthenticAMD unknown vendor error: [ 0.000000] CPU: vendor_id 'AuthenticAMD' unknown, using generic init. CPU: Your system may be unstable. So perhaps it's all related to the spotty AMD support in Jun's current loader. Strange that everything mostly works though, and it's rock solid otherwise.
  13. I also tried swapping the modules and the memory slots, still no dice. It's strange because the ethernet statistics (netstat -i) don't show any packet drops or errors, it just stops responding for a period of time, then starts up again. Some online posts on Windows with this same issue have disabled "energy efficient ethernet" to fix it, but "ethtool --set-eee eth0 eee off" fails as not supported. I wish I could simply install a new ethernet card, but the one slot I have available is taken by an SATA card I use for my storage. Looking into other embedded motherboards, they all seem to have RTL8111 chipsets of various editions (mostly H or G, I have RTL8111E), so just replacing the board might not actually fix this issue. I have no idea what to do now.
  14. I've tried removing a memory module so I only have 2GB of physical memory, but it hasn't improved the situation. However, the BIOS reports 2GB but Synology's info center says the NAS has 4GB of physical memory. Perhaps it's displaying a cached value? Is there some way to refresh this information?
  15. Hmm, a module r8168 is installed and running. The version says 8.044.02, which seems to only be one minor version behind the up to date one on the Realtek site which is 8.045.08. If someone could point me in the right direction to update this module, I could play around with this and hopefully get it working.