Jump to content
XPEnology Community

Mincemeat

Member
  • Posts

    27
  • Joined

  • Last visited

Recent Profile Visitors

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

Mincemeat's Achievements

Junior Member

Junior Member (2/7)

1

Reputation

  1. Thanks for bringing that to out attention. We will get right on it, making loaders harder to work and whatever Why u in their dms, you got a legit unit?
  2. Well next day it reported 32 pending sectors and today finished scrub. Doing a disk repair scan in hdsentinel now because smart extended can apparently hang. It already reported this and smart is now clear of bad sectors. Only got 2 of these tosiba MG05ACA800E that are maybe a bad batch because both reported io error. Was thinking of also doing a ram test and replacing the very old psu that i probably still should before this test.
  3. Got this while scrubbing and once before but no bad sectors anywhere. The 202 crc error is from before it was in nas. Both connected to motherboard intel controller on 6.2.2u6. Did a quick smart test after maybe need to do extended but dunno works still
  4. Well VPN is mostly a scam anyway. https://gist.github.com/joepie91/5a9909939e6ce7d09e29
  5. Why u no gpedit the shity windows so it never forces updates? Did u manage to recover?
  6. Ah I see, something about it being disabled in ui for enterprise units. Never ran into this problem on 918+ 1.04 loader. DS1821+ new unit and has shr.
  7. Pretty sure SHR is one of the main features of Synology. Hopefully it doesnt go away
  8. The weird errors in dmesg? You using ssd to test transfer to? Mine goes around 270mb but I have 7 disks in shr2 right now, no idea how fast shr is with 4. edit: hmm my mtu is 1500, guess thats the jumbo frame thing thats needs to be the same on all eths.
  9. I mean the conflict between jun driver and 6.2.3 i915 driver disables transcoding? No idea what those errors were, transfers didnt seem to be interrupted if i remember. Still didnt want that happening, thats why i went back to 6.2.2. Probably should have tried 2.12.0 before downgrade.
  10. Its a RTL8156 usb eth. Found one log but its still not fully complete. Does i915 conflict disable transcoding? Sure I can try 2.14.0 driver, currently using 2.12.0.
  11. 6.2.3 was working, those errors were when transferring data over usb eth. Then i downgraded to 6.2.2 and using r8152-apollolake-2.12.0-2.spk bb-qq driver currently. edit: Did the upgrade, seen the i915 conflict, uninstalled spk and replaced extra with v0.13.3 but it was couple of months ago.
  12. Would it be possible to get 1.04b juns extra with just i915 driver removed? Had some problems with v0.13.3 r8125 driver back then when trying 6.2.3 i think.
  13. found this cool little greasyfork script that lets you run media directly in VLC player from a Videostation. https://www.reddit.com/r/synology/comments/7kymgw/integrating_video_station_and_vlc_in_a_different/ once logged in to nas by //ip/ it works great, for a couple of months now. would prefer mpch, but not a big deal.
  14. Got a 6.2.2-24922u6 connected over ics in win10 and it seems ports 5k and 22 are closed from outside so it should be ok? Thats pretty bad, out of the blue multiple remote vulnerabilities.
  15. Uh, fail. Ordered with paypal&mailboxde and got this now: Your order unfortunately did not meet one of the test criteria and therefore had to be automatically rejected for security reasons.
×
×
  • Create New...