Jump to content
XPEnology Community

Tong6998

Member
  • Posts

    36
  • Joined

  • Last visited

Recent Profile Visitors

1,505 profile views

Tong6998's Achievements

Junior Member

Junior Member (2/7)

3

Reputation

  1. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2.1 69057-Update 3 - DS3622xs+ - DSM version AFTER update: DSM 7.2.1 69057-Update 4 - DS3622xs+ - Loader version and model: RR v23.12.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock C2750D4I - Additional comments: Updated from DSM Control Panel
  2. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2-64570 Update 3 - Loader version and model: Tinycore-Redpill v0.9.5.0M - DS3622xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock C2750D4I - Additional comments: Upgraded to DSM 7.2.1-69057 Update 1 via GUI. https://github.com/PeterSuh-Q3/tinycore-redpill TURN OFF 2FA Updated through GUI, RE-booted Used PeterSuh's Tinycore-Redpill with menu (way easier) -- NEW BUILD/NEW METHOD Used Previous SN to not have to change config Built it with Friend, Reboot Asked To Migrate, OK Reboot ALL SET, EVERYTHING WORKS
  3. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1 42962 UPDATE 5 - Loader version and model: TCRP Friend v.0.9.4.9c withfriend - DS3622xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock C2750D4I - Additional comments: * Manually install 7.2 * reboot, wait for "synology is recoverable" * Shutdown * Rebuild usb key with TCRP 0.9.4.6 * ./rploader.sh update now * ./rploader.sh fullupgrade now * ./rploader.sh serialgen DS3622xs+ realmac * ./rploader.sh identifyusb now * ./rploader.sh satamap now * ./rploader.sh backup * ./rploader.sh build DS3622xs+-7.2.0-64570 * ./rploader.sh backup * exitcheck.sh reboot
  4. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42962 Update 3 (Tinycore-Redpill v0.9.4.?) - Loader version and model: Tinycore-Redpill v0.9.4.3 - DS3622xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - AsRock Rack C2750D4I - Additional comments: Upgraded to DSM 7.1.1-42962 Update 5 via GUI & reboot to TinyCore Into TC, run the follow cmds : ./rploader.sh fullupgrade ./rploader.sh update sudo ./rploader.sh postupdate ds3622xsp-7.1.1-42962 exitcheck.sh reboot
  5. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42962 Update 1 - Loader version and model: TCRP v0.9.4.1 Loader DS3622xs - Using custom extra.lzma: No - Installation type: BAREMETAL - ASRock C2750D4I - Additional comments: TCRP Friend v0.0.4.0 couldn't find anything, booted back into TCRP:
  6. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.0-42661 Update 4 (Tinycore-Redpill v0.8.0.5 - DS3622xs+) - Loader version and model: Tinycore-Redpill v0.9.2.2 Loader DS3622xs - Using custom extra.lzma: No - Installation type: BAREMETAL - ASRock C2750D4I - Additional comments: ******TURN OFF 2FA FOR THE LOVE OF GOD******* ******TURN ON SSH IN CASE YOU DIDN'T DO ABOVE****** Upgraded to DSM 7.1.1-42962 via GUI shutdown pull usb, create new one under development branch Plug back in usb Booted into TCRP and run through whole process again of creation/ maybe use mac/sn as before if you care exitcheck.sh reboot enjoy
  7. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.0-42661 Update 3 - Loader version and model: Tinycore-Redpill v0.8.0.5 - DS3622xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock C2750D4I - Additional comments: Upgraded to DSM 7.1.0-42661 Update 4 via GUI. Booted into TCRP and run: ./rploader.sh update sudo ./rploader.sh postupdate broadwellnk-7.1.0-42661 exitcheck.sh reboot Note: It may find in TCRP when doing postupdate step, that it has found update 3. But ignore it and say yes. DSM will be updated to Update 4 anyway.
  8. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.0-42661 Update 2 - Loader version and model: Tinycore-Redpill v0.8.0.3 - DS3622xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock C2750D4I Additional comments: - Upgraded to DSM 7.1.0-42661 Update 3 via GUI - Booted into TCRP and run: ./rploader.sh update sudo ./rploader.sh postupdate broadwellnk-7.1.0-42661 exitcheck.sh reboot
  9. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: Tinycore-Redpill v0.8 - DS3622xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock C2750D4I - Additional comments: Followed Balrog's example to the "T" - step 1: from DSM 6.2.3-25426 Update 3 to DSM 7.1.0-42661 (like described in the tutorial "Tutorial: Install/Migrate to DSM 7.x with TinyCore RedPill (TCRP) Loader") - step 2: Upgraded to DSM 7.1.0-42661u2 via GUI - After Step 2 update, booted into TCRP and run: ./rploader.sh update sudo ./rploader.sh postupdate broadwellnk-7.1.0-42661 exitcheck.sh reboot
  10. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 2 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock C2750D4I - Additional comments: REBOOT REQUIRED -- Manual Update
  11. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock C2750D4I - Additional comments: REBOOT REQUIRED -- Manual Update
  12. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock C2750D4I - Additional comments: REBOOT REQUIRED -- Manual Update
  13. -Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922-4 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock C2750D4I - Additional comment: Manual update, Reboot required.
  14. Update: Never was able to get it to come back online, tried doing a re-install, a data migration but no settings, etc... Was able to get the interface to come up to install the pat file but after reboot it would go back to the same of no web interface, it's like some setting was hanging around and not clearing. Ordered a couple of external USB enclosures, and copied everything off the NAS seeing as i could still see the data and the folders and started all over again. Consider this closed.
  15. Forgive me If I put this in the wrong area. Background: - DSM version : DSM 6.2.2-24922-4 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock C2750D4I Yesterday I logged into the box to check to see if I had any updates(after checking here) or problems (don't log in often). I noticed my ssd cache deteriorated due to one of the drives failing (old 40 gig corsair ssd's). Since the old sata cables used to give me problems with drives I decided to reboot and try to see if i could get it to show up or if the drive was really dead and which one it was. (it was dead). I must of rebooted through web interface like 5 or 6 times in the process of 20 min (kept missing the opportunity to enter bios through BMC). On one of those reboots, i couldn't get to the web interface. and since then haven't been able to. The drives are working and use-able through the network. Assistant finds the box and sees it on the network with the correct IP. But trying to connect through web, "unable to connect" not the typical "connection timed out" if something is not running. Tried 2 different PC's, even from out of network through cell (i have a DNS setup to be able to access external). I'm able to transfer from the folders, to the folders, and obviously use the device as a NAS through basic explorer folders. None of the external services are running (ds audio, ds cloud, etc) I did a re-install of 6.2.2-24922 by selecting the option in the loader, was able to upload the pat file through web (thinking maybe corruption or something), it rebooted, changed to my port numbers, installed the -4 update on it's own and back to same issue. Unfortunately due to all the security issues lately, I turned ssh off (and did 2fa). When I get home, I'm going to put this behind a different router and try again with it being behind a "new" network to see if maybe something is blocking it on my current network. (I'm on a pf-sense box) Other than that, anyone got any ideas on what i could try? Could i go back to a 6.1.something to clear up any web interface settings?
×
×
  • Create New...