Jump to content
XPEnology Community

cableguy

Member
  • Posts

    14
  • Joined

  • Last visited

Everything posted by cableguy

  1. I did the same upgrade and created 4 videos on how to get from 6.2.3 to 7.1.1 Update 4. They are long, but that is because I was doing an upgrade on my prod system and wanted to make sure everything was correct so the first video is a test run ("prep") on the same system but with a new SSD to test the upgrade process. Good luck! Here is the first: https://www.youtube.com/watch?v=SL91KIzNM_4&pp=ygUUdXBncmFkZSBkc20gNi4yIHRvIDc%3D
  2. After taking a break, letting my brain process the code and taking another look with fresh eyes, I got it. Thanks for the help.
  3. Sorry - it was late and my brain was scattered. I think I asked the wrong question. Where is the ultimate source for synoinfo.conf after the build? In other words, what file location is overwriting /etc/synoinfo and /etc.default/synoinfo on boot? The directory (ies) above are used during the TC build process, with the first link being the unpacked RAM disk (synoboot1) which I've discovered and understand. However, it doesnt help with my question, unless I didnt something wrong as I've unpacked rd.gz on synoboot1, updated it and then repacked it and the synoinfo.conf was still the old file/settings. Thanks
  4. To the smart people... Poco, Peter, Flyride, etc... Where in the heck is synoinfo.conf written to during the "BUILD" process which then overwrites the local /etc and /etc.defaults synoinfo.conf? I feel like I'm missing something. Yes I know I can update some (all?) fields with user_config, however, I'm way past that as I've sunk about 10 hours into this and I'm bashing my head against at wall at 1AM over here... I've went deep into your scripts (pretty good stuff Poco, BTW, little spaghettieie, but hey, it works) and I've pulled /synoboot1/2/3 and I thought for sure it was synoboot1/rd.gz but I've pulled that apart and recompressed it and still it is getting over written somewhere. I then looked at synoboot2 contents and pulled apart those files but those look like defaults, so no luck there and then went to synoboot3 and changing those file did nothing. Coming here was a last resort as I like to figure this stuff out myself but man, I'm really struggling. Truth me told, I dont need to be down in my office for another day with my wife thinking "what the heck is he doing down there?!" FWIW, I'm going all of this work/editing in TCRP env, just didnt know what to call the synology mount points (sda1 vs synoboot1, etc.) TYIA!
  5. Anyone have experience with this? I couldn't find much but the VAAI clone is failing and then it copies it across the network and back as it would without VAAI. You can see in the image that hardware acceleration is supported but you can see at the bottom that the clone fails.
  6. Worked on my Custom Ryzen build. No reboot required.
  7. Worked fine on my AMD Ryzen build. Broke a couple custom items with my synoinfo.conf file but other than that it worked great.
  8. Trying to add a share via command line and running into issues. root@CABLABNAS:/etc.defaults# /usr/syno/sbin/synoshare --add private "dasasd" /volume2/plexMedia "" "" "" 1 0 Error: Share path is invalid. root@CABLABNAS:/etc.defaults# /usr/syno/sbin/synoshare --add private dasasd /volume2/plexMedia "" "" "" 1 0 Error: Share path is invalid. root@CABLABNAS:/etc.defaults# /usr/syno/sbin/synoshare --add "private" dasasd /volume2/plexMedia "" "" "" 1 0 Error: Share path is invalid. root@CABLABNAS:/etc.defaults# /usr/syno/sbin/synoshare --add "private" dasasd /volume2/plexMediza "" "" "" 1 0 Error: Share path is invalid. I tried just about every combination - with and without quotes, changing the path 50+ times, changing the 1 and 0 at the end... always errors. Any ideas?
  9. It could, but it has to do with more than the CPU. Usually the main bottleneck is the storage controller.
  10. Either. I just did the automated upgrade and it worked fine.
  11. Running a Ryzen and just updated -- 6.1.3 Update 8 seems to be working fine.
  12. Just updated to 6.1.3 Update 8 and all seems good and well. Also lower m voltage some more - Running 1.025 vCore voltate and .8875 vcore SOC (whatever that is). Both are lower than stock. Still running 20x100mhz = 2000mhz.
  13. I haven't been home in a few days but I just VPN'd into my box and everything looks good. Almost 3 days of uptime and communication to another box running VM's looks good. I havent had time to work with the C1E but will keep this thread up to date with issues and updates.
  14. There seems to be a lot of questions around Ryzen, Intel's i211's and other AMD related posts but not a ton of answers to those questions. I spent about 8 hours getting this to work and wanted to share some tips. I originally used the 1.01 (6.0.2) JUNS loader guide and that DID NOT work. I tired the extra.lzma and also tried it with both NICs plugged in, booting to both the Intel and AMD grub... Nothing worked. It would Post, load the GRUB loader and then find.synology.com couldn't find anything. I then used the 1.02B (6.1.3) JUNS loader guide and that worked like a charm. Make sure to the use Intel NIC port. Also, a couple notes of my own that I couldn't find any answer to but would have like to have known when I was having issues with the 6.0.2 loader. The VID and PID must be correct. The guide states this and this is because after you install DSM, DSM uses the USB drive and will look for the VID and PID. The SN as far as I can tell could be anything. This is used for Synology services such as QuickConnect. DO NOT USE Quickconnect (I'll be honest here, I'm new to this and Quickconnect is a Synology service and based on what everyone including mods on here say, dont use it!) The MAC address: I used my actual MAC address of my NIC... not the auto-generated one. I got this when I enabled PXE Boot because I didnt have an OS prior to install (I used https://jsfiddle.net/7Lorpu77/ to generate a SN, FYI, again it could be anything...) JUN stated some issues around "C1E function". I did run into a weird issue during my initial install and disabled this as a knee-jerk reaction. I will do more testing and see if I notice any issues. This will turn the multiplier down to 6x in an "unloaded" state to save on power which is a good thing most of the time for a NAS. Not even sure if this will work while I manually set the multiplier. The last thing I will note is my system specs: GA-AX370-Gaming K7 (rev. 1.0) Ryzen 1600 with Stock Cooler 8GB DDR4 3000 8GB SanDisk USB Drive Corsair 500W 80+ PSU **I bought a Ryzen for future growth as this is for my Homelab. I can use this as a HomePC, HTPC, or my gaming PC in the future and the Mobo/CPU will be plenty speedy. With that said, it is OVERKILL. I undervolted the Ryzen and slowed it down to 1.1V VCore (from 1.22500 IIRC) and also set the Multiplier and FSB to 20x100MHZ for a total for 2000mhz. This dropped the idle temp about 3* Celcius and also the running Wattage by about 10W. I plan to continue to test with this and drop it some more. With a cheap video card and one 1TB HDD, this setup is pulling around 58W idle. As you can see in the image it shows up as an i3 and only 2 core are showing as working but when I SSH into the DSM, 8 of the 12 cores are working.
×
×
  • Create New...