Jump to content
XPEnology Community

gericb

Member
  • Posts

    145
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by gericb

  1. You're most welcome! I'll always help the best I can! BTW, when I mentioned me being lazy, impatient...none of that was directed towards you or your goals, just talking about me getting at platform I could get up and running ASAP with as little grief as possible. 🤣 I'd enjoy to hear how your adventures ultimately go! 😎 Cheers!
  2. Your unit is using the Intel Atom® Processor 230 (Diamondville), released in 2008 and was the 1st Generation of Atom and does support x86/x64. It does only have 1 Core and 2 Threads.... supports Max 2GB RAM, 4 Drives. What I don't know, is if the motherboard itself can be configured to boot from an attached USB, instead of it's default method, and even if DSM 5.x/6.x would support the rest of the integrated hardware (chipset, ethernet, etc.), I am not as well versed like some of the other long time experienced senior users/contributors to the DSM DIY would know. I'm lazy, impatient and don't really have a lot of time to fight with a litany of possible technical issues, so I followed K.I.S.S. (Keep It Super Simple). 🤠 I would say, IF it would work, your most likely best choice would the the DS3615xs... Ultimately, not to be Mr. Downer, it probably would be a better use of your time/effort, to find a newer, 2013 or better Intel system, that you can stuff several drives into and take the plunge with DSM 7.x instead. There are if I am not mistaken, several packages that are now also not supporting updates for DSM 6.x which might be limiting, depending on your use case. Here is the software tool you were looking for, I still had it buried in some archived folders on my NAS. Once you unzip it, you have all of the separate software tools that the XPENology Tool would download for you. I am sure several of them have been updated since that tool was created. I did update the version of Rufus in it's folder, to the latest and greatest. https://drive.google.com/file/d/1KSPvs8EZ3E3E6I6ZaljG9XRKfP7McVUj/view?usp=sharing Since DSM 5.x/6.x have been retired, their respective installers have been archived, so you'll also need this link to get all of that older stuff... https://web.archive.org/web/20230117045449/https://archive.synology.com/download/Os/DSM This is the best I can do for you!
  3. Hey there! It's basically deprecated, since it was the tool du jour for DSM 6, and the circus hoops process to create JUN's loader. All of the newer DSM 7.x loader methodologies are much more straightforward, easy-peezy,(mostly) wham-bam-done type of thing. I might have a copy of it somewhere if you really need it. You're not trying to do a DSM 6.x build are you? 🤠
  4. Nothing at all, this is really outside of my knowledge of this process of booting and installing DSM. I thinking....hoping...that maybe something got corrupted within DSM, that we can fix. I think there might be an option to re-intall DSM, but I have to check on that, hopefully without effecting the other softwares installed and their respective configuration. All I did was re-boot and let it do it's thing, and it was a series of loader failures and glitches, and given nothing changed on my platform and not even a DSM incremental update, I'd venture to say it's all loader/friend generated glitches, and they were numerous. I'm sure the root cause will be determined and we'll get it resolved! 🤠
  5. Yes me too. I am on a 920+ using TCRP w/Friend. Since I have a real SN/MAC's it's not a worry and in fact has been working perfectly (AME) since first release of DSM 7.1. I was able to login via "External Access" and "Synology Account" @ Control Panel until just recently, thinking about 3 weeks ago, something changed in the loader. It accepts my credentials, spins for a bit like it's going to login, but never successfully does in either sub-section. Prior to this stop working, there were a couple of glitches with the loader and it's reliability, both with the SN and MAC addresses, and though visually it appears to be resolved, there is this last glitch, which has me thinking something might be embedded still in the DSM on the HDD.
  6. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2.1 69057-Update 3 - DSM version AFTER update: DSM 7.2.1 69057-Update 4 - Loader version and model: TCRP w-Friend v1.0.1.0 / v0.1.0g DS920+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Additional Comments: Download PAT file. Updated Manually, Reboot Required. Required “Recover” via Synology Assistance. Didn’t accept valid account password for 15min, after update.
  7. I would venture to say something unusual is going on... Yesterday, when I decided to restart my 920+, and "build loader" so it would pull any updates that you might have released, I noticed a glitch. When all 4 of the status windows opened, the windows which would show the SN / MAC, the SN field was blank, but in a fast glance, the rest looked fine. I have a real SN / MAC. I built and restarted, it all came back as expected, correct SN / MAC @ Info Center, as I was able to sign-in to the static IP assigned to that machine, I assume the SN came from DSM, not the loader. There's more...but I'll share that in a bit. FYI
  8. So far, so good! I can report that SA6400 with your current Loader w/Friend, it was effortless and largely flawless on the test XPS 8950. The only thing I could report at this time, was the screen resolution when booting into Friend, was lower than optimal, so I needed to resize and arrange the 4 windows a bit, but that's trivial. It recognized all 4 SSD installed, as well at the 2 x 256GB NVMe SSD installed for possible R/W cache options testing. Created a RAID F1 smoothly. Singular network connection, recognized as predicted and performing well thus far.
  9. So is the general notion that ESXI is more stable, reliable, robust, functional, easier setup with lessor issues than Proxmox?
  10. Personally, I would not even use win32diskimager. It's only v1.0.0, no updates since 1/2023 might as well be a deprecated product. Rufus on the other hand, I've never had a problem with regarding the various loaders here, or others like Windows, Linux, ISO's etc. It's updated regular, always being improved, enhanced. BalenaEtcher was basically filling that void for macOS of a general USB creation tool, but it's more of a side product to the rest of what the company offers, though at least they are constantly trying to improve it with new releases, it's often has some quirky issues. https://rufus.ie/en/
  11. "The device management of the company acquired by Intel is really a mess." Very much so, yes! Thanks for your attention to detail and application of scripts as it relates to this part/driver. Good to know that the SA6400 already has OEM support for the E3100G. I'll definitely try a SA6400 build, and testing the HW transcoding as well.
  12. Funny, I ran across this article too. There was another one somewhere else, can't find it at the moment, creating the same driver confusions due to it's "self-reported" info. 🤣
  13. Sure, based on the 10EC, I would agree that it's obvious. Given the whole merger path and development partnerships that Rivet had, it then begs the question, who's maintaining the driver development, Intel or Realtek. Is Intel really relying on Realtek to regularly release driver updates, for a product line they own...messy to be sure. Latest release combo driver pack from Intel, which includes the E3100G is 10.10.2023 Realtek on the other hand is 11.28.23 Sadly, the package was no help either. Thanks for your detective feedback!
  14. Really? This is surprising to hear, given that Rivet Networks/Killer was acquired by Intel back in 2020. It started out as Bigfoot Networks, then was acquired by Qualcomm in 2011, the got spun out to form Rivet Networks. Qualcomm provided some great ASIC building capabilities, to the product line while they had it. Rivet then later was known to be partnering with Intel and Realtek on various parts offering a standard version under the normal brand or the Killer version with additional network detection and shaping capabilities. I could be missing something, but it would appear all the modern drivers come from Intel. I'm wondering if my previous provided Hardware/Compatible ID (not captured real-time from a running OS) might therefore, be incorrect. In a couple of references, I am reading this might be based on the I225v chipset. Given the acquisition path Rivet Networks went though, I shouldn't be surprised if somehow Intel acquired a Realtek designed part. Are you able to glean any info from the current driver download from Intel? https://www.intel.com/content/www/us/en/download/19779/intel-killer-performance-suite.html Thank You
  15. That being said... I've a great machine to test out this whole thing, a Dell XPS 8950 w/12th Generation Intel Core i7-12700K. Throw in a couple of SATA drives, there are even 2 - M.2 2230/2280 slots for solid-state drives that could likely be used for testing caching. It's got a Killer E3100G Ethernet controller (10/100/1000/2500 Mbps) which may/may not be supported even though it's "Intel". Do you know @Peter Suh if this controller is currently supported? e3xw10x64.inf PCI\VEN_10EC&DEV_3000&REV_03 PCI\VEN_10EC&DEV_3000&REV_06 PCI\VEN_10EC&DEV_3000&SUBSYS_30001A56&REV_06 PCI\VEN_10EC&DEV_3000&SUBSYS_384C17AA&REV_06 PCI\VEN_10EC&DEV_3000&SUBSYS_387817AA&REV_06
  16. Well it's definitely been mentioned here by several people, that the DSM Kernel is hardcoded for the numbers of supported cores/threads, based on model. Of course, maybe that is just. visual thing, in the Info Center, maybe in reality, it uses all there is available, this, I can't remember for sure. I'm on a 920+ which is also build on a 6 Cores / 12 Threads CPU. The 920+ officially is stated to support 4 Cores / 4 Threads, per the link. So if I am remembering the hardcoded support issue right, then we'd like both benefit to the SA6400. Interestingly, my Info Center is showing 6 Cores / 8 Threads. 🤔 I too also already have perfectly running HW Transcoding. Assuming there are no draw-backs from this model. 🤠
  17. I think I can see, aside from the great news @Peter Suh regarding the "Fast Transcoding" which at the moment, I assume to be HW, even though the system is built with an AMD by default, is that it's kernel should support 12 Cores and 24 Threads. So depending on your chosen hardware platform to build your NAS, your 918+ might support less than what processor is actually capable of. 🤞🏼 It also supports up to 32GB of ECC (don't know if required) RAM. https://kb.synology.com/en-nz/DSM/tutorial/What_kind_of_CPU_does_my_NAS_have
  18. For your follow-up....I just rebuilt the loader on my 8th Gen Intel Core i7-8700, 920+ to see your newly updated FRIEND was pulled down and integrated. Also upgraded to Update 3 as well. I'm using a system with a real SN/MAC, have native activation (so I assume) of the AME. I could happily HW Transcode before, and after all of these updates, I STILL can, which is a good thing. 🤠. Thank you for your continually amazing support!
  19. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2.1 69057-Update 1 - DSM version AFTER update: DSM 7.2.1 69057-Update 2 - Loader version and model: TCRP M-Shell w/Friend v1.0.0.0, DS920+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - additional Comments: Updated Manually, Reboot Required. Downloaded .pat file from: https://archive.synology.com/download/Os/DSM/7.2.1-69057-2
  20. Safe to assume that we don't have to create an all new USB/Re-configure the Loader to get all your changes and benefits. Just restart the computer with the existing USB, it will download and re-configure/update things as needed. Possibly only requiring "build the loader" with the current DSM to get all changes implemented.... 🥳 Thanks
  21. I just finished test building a new loader usb, as I did before: 7.2.0-64570 then 7.2.1-69057 and it went smoothly, no showstopper issues and decent free space on /sdb3 once it was completed. For an additional test, I restarted and repeated the 7.2.1-69057 build as it would typically bring down any new additions/changes you might implement later, where to rebuild is required to pull them down. The additional step also ran smooth and decent free space left on all partitions. 👍🏼 Might I suggest that you copy the zlastbuild.log file automatically over to say the /dev/sdb2 partition at the end of each build cycle. As it's a small file and would not pose any issues being copied there, so you have a saved snapshot in a safe, accessible location...until the next loader build and can easily be pulled in between as needed. I performed this additional step with a simple "cp" as a test with success. Interesting side note, though I have not done testing with several machines to fully confirm, at the moment, the USB isn't natively viewable/accessible in macOS Sonoma or Windows 11...but IS fully on Windows 10. I'm intrigued given they are indicated as FAT/FAT32 partitions. 🤔
  22. Hey there @Peter Suh, sorry just getting back online here, "life" has been keeping me away and busy for a bit, I fully intended to provide you the requested logs, wasn't ignoring you or your request. It seems like in my absence, that OCD part of any respectable IT/Tech persons brain to resolve a problem, got ahold of you due to the quirky challenges I was running into. EXCELLENT FIND! I reiterate my DM! Thanks You 🥳
  23. It was ME, @Peter Suh I just assumed that this log file (not lost in the process) would be saved somewhere on the USB itself, so at any point later, someone could go back to the appropriate partition on the USB, and find this log file, if it needed to be referenced for diagnostics (maybe a good idea?). It may was my failure to understand it was only viewable / found while still in the whole build / configuration process....accessible in the green terminal windows BEFORE rebooting to start the loader - now I know. My apologies! 🤠
  24. Guilty as charged! I was thinking and hoping the log file might actually be saved for later viewing as needed to one of the 3 USB partitions (maybe a good idea to implement), so I was looking all over the usb using my Mac/Windows/Linux and could not find anything, now I know why - "This process should be done in the TCRP Loader build phase, where you will see four windows." Since the USB process I did yesterday, completely filled partition 3, 100% ... I'll erase and rebuild again, later and get that log, before rebooting. Is the log file lost at reboot, if not saved first? Thanks
×
×
  • Create New...