Jump to content
XPEnology Community

Badger

Member
  • Posts

    98
  • Joined

  • Last visited

Posts posted by Badger

  1. I'm no software engineer either, but I bet if you have a couple extra disks laying around you could run through the tutorial here:  

    If you can successfully boot from the bootloader and it sees your "test" disks...  you can be pretty confident it will recognize your production disks also (might have to start over and build another loader after installing all your disks.   That said, you will probably have to start over with new Synology volume(s) and restore you backup(s).  Also, I believe the 3622xs+ has a max disk capacity of 12.  I could be wrong.

  2. On 4/3/2023 at 6:19 PM, Dvalin21 said:

    So has anyone experienced after upgrading to TCRP Friend, when booting into it, it shows an IP Address, but your network not registering it as being on the network? I can boot into the regular usb option no problem. Its like when booting into the TCRP Friend, it connects, but then disconnect otherwise why and how would it get an IP Address from the network?  This is an old PC network driver Realtek R8168 AMD Athlon II CPU. Thanks. 

    Exactly same problem for me  (also AMD Athlon and Realtek BTW).  I asked the forum how to set USB boot as default (because that option booted fine), but nobody could (or would) answer that question.  Other advice was to "remove friend"... which hosed the entire loader.  I started from scratch and built a new loader (no friend) for 3622xs+ 7.1.1.  Then updated to v4 via GUI... booted to TCRP and ran the "postupdate" command.  Then I restored a backup of my data.. configured settings... installed apps, etc.  Took a couple days.

     

    Good Luck!

    • Thanks 2
  3. On 3/26/2023 at 10:33 AM, David Rollin said:

    When 3 drives are in, upon rebooting, system is stuck at getting an ethernet connection. 

    I gave up on friend because I never could connect to it.  It appeared to boot fine... and for me, it did report an IP.... but I could never connect.  I could connect if I chose USB boot (instead of friend).  I was unable to set the default to USB, so I finally rebuilt a regular loader (without friend) and all is fine..  FWIW... I have 3 drives also.

  4. Yes... I ran that command and that's kinda where I am now.  The TCRP withfriend did not go away after the remove command.  But now throws the error "must start kernal first".  Still was the default boot though .... strange.  And then even the USB boot option didn't work... so i restored the backup.  Now USB boots but friend (default) doesn't.  I think I'm pretty hosed... unless I  format the disks and start over.  I have a data backup so I can start over, but of course would rather not.  If I could just change the default boot option I'd think I'd be fine.  

  5. I asked this question in another thread, but got no response.  At one point TCRP withfriend appeared to boot successfully (although I could never connect).  Now it always gives an error "you must start the kernal first"... or something to that effect.  USB boot does work and I want it to be the default as I have an automated shutdown and startup task set up.  I tried building a new loader (without friend) but the NAS won't recover.  I believe this is because I'm on 7.1.1 U4... and I guess I can't go backward with a new build.  I know it should be simple to change the boot default, but I can't find where.

  6. 2 hours ago, Trabalhador Anonimo said:

    I create a new usb with "withfriend" and my NIC (all 3) died at the moment it boot. Booting normally, no friend, the NICs works like charmed.

    Yes, I get the same behavior.  I hope someone has an answer on how to set default boot to USB (not "withfriend").  Or how to remove the withfriend option from my loader.

  7. Thanks.  I had tried the platform you suggest... but without sudo.  That said... to my surprise the update appeared to install just fine when I rebooted....  without successfully completing the postupdate command??  I do have the "withfriend" option at Grub.  Perhaps booting to "withfriend" took care of the update automatically?

     

    Here's a question though.... Booting to TCRP withfriend appears to complete.  Last line on monitor says "nothing further will appear here anymore"..  or something like that.  However this boot does not give me an IP on my network (no diskstation appears).  Booting a second time to USB verbose DOES give my an IP.  

     

    How can I set the default boot for my setup to go to USB Verbose???  Thanks.

  8. OK, I successfully built a loader (TCRP 9.4.3 ....  3622xs+ 7.1.1-42962 U1)  MSI MS 6471 V3 AMD Mobo.  I needed a new usb loader because my system wouldn't boot after running for over a year on 7.1.  So now I'm on Update 1, but want to upgrade.  So I manually install U4 via the GUI and then reboot to "TCRP Image".  As there is no tutorial on how to install updates... after much searching I found a post that suggested running these commands:

     

    ./rploader.sh update now

    ./rploader.sh fullupgrade now

    ./rploader.sh backup

    ./rploader.sh postupdate (your platform)

     

    All commands work except the last one.  What do I type as "your platform".  Always comes back with "platform not found"  I've tried: 3622xs+...  broadwellnk-7.1.1-42926...  3622xs+-broadwellnk-7.1.1-42926....  DS3622xsp-7.1.1-42962.  All to no avail.  Please advise if you can.  I hope this is the right place to post this question.

  9. Totally confused re: "withfriend", "bringfriend"....  "Setting TCRP withfriend as default boot option will help me upgrade without postupdate"... but how?

     

    I built a new loader cause my existing 3622xs+ (MSI mobo.. AMD) failed to boot after about a year of operation.  So I added "withfriend" at the end of the build command.  I chose 7.1.1-42962 and if i boot to USB verbose option... everything is fine with 42962 (update 1).  If I chose to boot with TCRP with friend (last option).... the monitor doesn't show any errors but the system never shows on my network.  So it appears I've created a bootloader that has the "friend" boot option, but how do I use it? I'd like to upgrade to U4 if possible.

  10. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 7.1-42661 Update 4
    - Loader version and model: TCRP v0.9... I think?  Loader DS3622xs+ w/ Broadwellnk-7.1.1-42962 update 1
    - Using custom extra.lzma: NO
    - Installation type: Baremetal - MSI  MS 7641 V3 w/old AMD CPU, 4GB ram, 3 2TB disks

    - Additional comments: Lots of trial and fail on this one.  New loader via ARPL did not work (IP showed in router, by couldn't connect).  New loader from fresh TCRP v0.9 download same result (IP showed, but no connect).  Decided to go back to TCRP v0.8, but couldn't find an img download anywhere.  Found an old v8 img on my pc and created new usb stick with TCRP 8.  Proceded with Flyride's tutorial for install/migration to 7.x via TCRP.... then "./rploader update" appeared to upgrade TCRP to v0.9.  Went step by step through the guide (chose 7.1.1-42962).  Had to edit config.json and change build number to 7.1.1-42962... change SN to the previous build's SN.  Booted and it showed as "Migratable".  Dowloaded 42962 .pat file from Synology download center and installed keeping all data and settings.  Whew!

  11. - Outcome of the update: UNSUCCESSFUL
    - DSM version prior update: DSM 7.1-42661 Update 4
    - Loader version and model: ARPL 5.0 alpha 1
    - Using custom extra.lzma: NO
    - Installation type: Baremetal - MSI  MS 7641 V3 w/old AMD CPU

    - Additional comments: Tried to update to 7.1.1 42962, but no luck.  Created new usb flash drive with ARPL...  selected DS3622xs+...  build 42962....  typed in my previous SN... stuck on "booting"...  never completed boot.  

     

  12. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 7.1-42661 Update 1
    - Loader version and model: TCRP per tutorial (V8) Broadwellnk 7.1-42661 (DS3622xs+)
    - Using custom extra.lzma: NO
    - Installation type: Baremetal - MSI  MS 7641 V3 w/old AMD CPU

    - Notes:  After running XPE 7.1 update 1 (DS3622xs+) for many months.  Couldn't update.  always got "corrupted file".  Rebuilt new loader per the TCRP V7 tutorial.  No migration... all data and apps and settings remained intact upon reboot.  Ran GUI update from U1 to U4... rebooted to TCRP and ran the postupdate commands referenced many times herein.  Rebooted to DSM and all is good.

  13. I've been running DSM 7.1 update 1 (DS3622xs+) for many months now.  I was going to attempt (again) to run an update, so I shut down DSM.... entered BIOS to make sure my clock was set correctly...  It was correct so I exit BIOS without changes..... and then this:

     

         GRUB loading.

         Welcome to GRUB!

         error: unknown filesystem

         Entering rescue mode...

         grub rescue> _

     

    Rebooted several times and the above is all I get.  Am I toast?

  14. 14 hours ago, phone guy said:

    If the upgrade is failing inside dsm, maybe you downloaded the wrong update file. THIS LINK is for U4 for the DS3622xs+, I assume you can update directly to u4 from u1? I never tried it so I don't know for sure that would work. If that file fails under dsm, you may have to upgrade to U2, then U3 <run postupdate> and then U4. I know after U3 update you will have to reboot to TC and do backup/update/full upgrade/postupdate commands.  I am not 100% sure if that step is required for U4, as I have personally not done that update yet. but I know it is required for U3.

     

    Good luck

    I have a feeling something is hosed in my system that either corrupts the update files (or causes the update to appear corrupt) because I've tried several downloads of U2, U3 and U4 and I just tried the one from your link above.... also "corrupted".  I think I'm going to have to build a new loader from scratch and test an update from there.  All my data is backed up so its not that big a deal.  Just a bit of a pain to install my apps and settings, SSL, etc.

    • Thanks 1
  15. 7 hours ago, phone guy said:

     

    So you are if your at U3 already, you could update to U4 without running post update. If your on 7.1-u2,after manual update to u3 u4 then yes do the post update... That's what I'm hearing you say 😉

    @phone guyNo, I guess I'm not making myself clear.  I am on 7.1 (U1).  ds3622xs+, MSI Mobo w/AMD CPU.  My problem is I can't complete the manual update from the GUI.  So I've never gotten to the point where I can reboot to TCRP and enter the post update commands.  I go to control panel, update... choose the update file that I've downloaded from Synology... and the file uploads... then either promply says "file probably corrupted", or hangs with "preparing...".  Hopefully this makes my problem clearer.  There is something in my system that makes the update file(s) appear corrupted.

    • Thanks 1
  16. 42 minutes ago, Orphée said:

    If bootloader was not updated, yes.
    Sonoloygy does not always update it with minor patches.

    Wait a minute...  Should i update my TCRP bootloader before I go through the update process for 7.1 (u2, u3 OR u4)?  I believe my TCRP is version 5.  So far I haven't had any success updating my ds3622sx+, 7.1 (U1) to anything newer.  I've tried update 2,3 and now 4... and all I get at the 1st step of the update (manually installing from the GUI) is a "file is probably corrupt" error... or in the case of U4... it just hangs at "preparing".  Please advise as I haven't really got response in the DSM Installation forum.

  17. I would say that if your 6.2 NAS is serving your purpose(s), don't bother upgrading at this point.  I upgraded (actually had to build from scratch) to 7.1 and I'm happy with it... except I am unable to upgrade so I'm kind of stuck as I was with 6.2.  Now others on this forum have been able to upgrade so your setup might also work.  As you search the forum, you'll see the whole gammit... from 1st time success just by following the tutorials...  to trial and error with some success and some failure.   I enyoyed to process of getting to 7.1.. and it is stable for me, but I don't have any confidence on installing any update... Unless I build a new loader each time and migrate.  Any BTW migrating has it's own set of issues (for my setup anyway).  Old MSI 6471 Mobo with older AMD CPU and Realtek NIC.

  18. I have how tried the U2 patch with the same "failed to update file... file is probably corrupted" error.  This happens very quickly.  The first time I got the error.. the update process had been proceeding for maybe 2 or 3 minutes.  Now it's instant.  As if my 1st attempt corrupted something in my system.  As it appears nobody has had this error (at this stage of the udpate process) I'm very open to any troubleshooting ideas.  Should I do a fullupgrade to TCRP before trying the GUI update?  could that possibly make a difference?  Anything else I can explore?  I doubt if these update .pat files are truly corrupted...  thanks in advance.

×
×
  • Create New...