Jump to content
XPEnology Community

Netizen1

Transition Member
  • Posts

    15
  • Joined

  • Last visited

Posts posted by Netizen1

  1. 1 hour ago, gericb said:

    TBH, I am more concerned why it blew up on me, a USB, loader working perfectly fine for many previous updates, as evident by the numerous archived user.config files.  This is a 16GB USB, so more than enough free space on the device itself, but with the partitions created, obviously not.  I think it would be relevant to know why, since it wasn't anything weird or unusual on my part, just followed the normal sequence of things in your 4 screens menu/build system to upgrade to 7.2.1-69057.  

     

    The other project, ARPL I believe, increases the third partition to use more of the free space on the USB, but I don't think TCRP or Mshell have that function built in.

     

    You could modify the third partition of your USB using some partitioning software before you try again. However, it would be cool if pocopico and Peter Suh adopted the repartition step in their respective projects 😇

    • Thanks 1
  2. 10 hours ago, Peter Suh said:

     

     

    Older AMD CPUs are not supported by ARPL's default GNU kernel and TCRP FRIEND (also the GNU kernel).
    So, ARPL supports an option called Direct Boot.
    In the case of TCRP, it is called Jot.


    Pocopico's TCRP already exists alongside the FRIEND boot menu.
    However, every time a SmallUpdate such as U1~ occurs, you must manually PostUpdate.
    In the case of Mshell (TCRP), postupdate in Jot has been improved to be slightly more convenient.
    ARPL will probably work better with direct boot and ramdisk patch without postupdate.

     

    Try this method.

     

    I found the Direct Boot setting in ARPL while doing my research this weekend. I finally saw that pocopico exposed that setting in their HTML builder, and was able to get around some of my earlier issues. However, it appears that most of my problems were with TCRP's deployment of 42218 on my hardware.

     

    When trying out Mshell, I expressly recall that I couldn't use JOT and 42218. When I tried to use 42218, it stayed as Friend, while the 7.1 and 7.2 showed JOT. There was also an issue during the loader build where I was running out of space on sdb3 and after so many days of trying to get it to work,  I reverted to the TCRP to test the HTML builder, and that's what ended up working for me.

     

    For now, it appears to be working with 42962 Update 6. Also, TCRP Friend worked as it should after I applied the patch to my install.

     

    I honestly don't remember why I was so insistent on loading 42218 😅

    • Like 1
  3. One more update from me. I retried the build with TCRP and ds920p-7.1.1-42962, and it works now. 🤯

     

    Not sure what the problem with 42218 was, but at this point I don't care...

     

    Just waiting for the repo to have 7.2.x support for r8168/r8169 before I attempt another upgrade.

     

    Thanks for the help!

  4. 11 hours ago, Netizen1 said:

    Greetings, a returning user here. First off congrats on the work with TCRP, secondly, I hope I'm not posting in the wrong place 😅.

     

    As a small project, I've been trying to put together the following using the latest TCRP loader (0.9.4.9)

    • Gigabyte GA-F2A68HM-H
    • AMD A6-7400K
    • 8GB DDR3 memory
    • 160GB disk for initial testing

    After a couple of days scouring the forum and watching the process get streamlined, I've gotten to the point where I got ds920p-7.0.1-42218 loaded using ARPL, and ds920p-7.1.1-42962 using TCRP (not with M Shell). However, when I tried to update the DSM to update 6, I ended up in a recovery loop. Long story short, I've started over quite a few times and still can't seem to get TCRP to install a stable loader.

     

    The last attempt, using the latest HTML feature added by pocopico, gave me the following error when I chose the USB boot.

    Loading Linux:
    error: kernel doesn't support EFI handover.

     

    Note that I had to use "staticboot": "true" or else TCRP Friend freezes.

     

    Any guidance would be appreciated.

     

    Update:
    I went ahead and tried a couple of different models today, like the DS1029+, and DS918+, and I got the same error mentioned in my earlier post.

     

    Makes me wonder how I managed to get the ds920p-7.0.1-42218 loaded in an earlier build, as well as with ARPL 🤔

  5. Greetings, a returning user here. First off congrats on the work with TCRP, secondly, I hope I'm not posting in the wrong place 😅.

     

    As a small project, I've been trying to put together the following using the latest TCRP loader (0.9.4.9)

    • Gigabyte GA-F2A68HM-H
    • AMD A6-7400K
    • 8GB DDR3 memory
    • 160GB disk for initial testing

    After a couple of days scouring the forum and watching the process get streamlined, I've gotten to the point where I got ds920p-7.0.1-42218 loaded using ARPL, and ds920p-7.1.1-42962 using TCRP (not with M Shell). However, when I tried to update the DSM to update 6, I ended up in a recovery loop. Long story short, I've started over quite a few times and still can't seem to get TCRP to install a stable loader.

     

    The last attempt, using the latest HTML feature added by pocopico, gave me the following error when I chose the USB boot.

    Loading Linux:
    error: kernel doesn't support EFI handover.

     

    Note that I had to use "staticboot": "true" or else TCRP Friend freezes.

     

    Any guidance would be appreciated.

  6. @IG-88 Thanks for the response.

     

    I've tried another flash and got the same error. I'm now going over the process of retrying with each on the syno/std/recovery mods once more with the 2nd flash drive.

     

    If this fails, I'm going to try going over my BIOS/EUFI settings to see if I missed anything.

  7. It's been a few days of trying, and retrying. Still no dice. I keep getting error 13 in the Web Assistant.

     

    I've tried extra918plus_v0.8_syno.zip, extra918plus_v0.8_std.zip and extra918plus_v0.8_recovery.zip

    I've even tried the extra.lzma file from 

     

     

     

     

    So I switched the the Synology Assistant, and I get a different error:

     

    image.thumb.png.040cc66e2232e4fa46e3b6ab4b46ecd1.png

     

    I'm really struggling here. I'll go back and do some more research tomorrow, but if anyone wants to offer any suggestions I would be grateful.

     

     

  8. Sorry for the lack of updates. It's been a hectic time with this virus!

     

    I've been hitting my head against the desk wondering why I keep getting error 13 for every .pat file I tried. Just came across some info that basically said I wasn't using a good serial number.

     

    My question now is, do I just use the S/N that comes in the synoboot.img I downloaded? Or is there another serial number generator for the 918+ lurking around somewhere?

  9. Hello fellow enthusiasts, I'm new to the forum, but not to XPenolgy. In this topic, I'd like to propose/discuss the repurposing of my old HTPC parts in an XPenology build.

     

    The parts I'm planning to use are here on PCPartPicker: https://pcpartpicker.com/user/Netizen1/saved/#view=bFhmkL

     

    (I'll list it out here, in case the link doesn't work)

     

    • ASRock AM1B-ITX Mini ITX AM1 Motherboard

    • AMD 5350 2.05 GHz Quad-Core Processor

    • Crucial Ballistix Sport 8 GB (2 x 4 GB) DDR3-1600 Memory

    • Various hard disks ♻️

     

    I've read that people have had success with AMD builds before, so I'm going to try to start with the latest bootloader and see how that works.

     

    Wish me luck!

  10. Hello folks, just decided to join the forum after lurking for a while here and on Reddit in r/Xpenology.

     

    I've worked in IT for over 20 years, and have experience in building PC's and servers but mostly I'm a Windows Server guy.

     

    I came across XPenology a few years ago when I first started with Synology hardware. At the time I couldn't afford to buy my own NAS, so I was thrilled to discover the project. I managed to get it to work on an old Dell PC as 'proof of concept' to myself, and afterwards had an instance running in VirtualBox for Plex.

     

    With the global pandemic, I've decided to repurpose my now idle HTPC to serve as a media server running Plex. So, look forward to my thread on that.

    • Like 1
×
×
  • Create New...