Jump to content
XPEnology Community

droiduser22

Member
  • Posts

    20
  • Joined

  • Last visited

Everything posted by droiduser22

  1. I meant a thread on this forum under Loaders. There is one for Redpill.
  2. Is there a thread for each loader here? I looked around but did not see any just Redpill. It would be easier to follow the info for the other loaders such as Arc and M Shell.
  3. A BIG THANKS to dj_nsk for replying to my thread and helping me in 15 minutes. This is a knowledgeable and helpful group. I have learned things and do share them with others who are new.
  4. UPDATE- This is for someone else in the future should they run into this issue. This was EASY. I used the ARC method. I got my system up and running in 10 minutes. It's currently rebuilding my 3rd drive probably because I moved the location of the SATA connection on my motherboard from 3 to 4th. I went to GitHub link, and downloaded the xxx.img.zip. I unzipped and then burned the image to USB3 (16gb drive). Booted the computer/NAS and followed the directions. It was EASY. I picked some options/boxes such as marking the disk check healthy option (don't recall the exact name but you will see it...Synology now gives a warning for Seagate Ironwolf and other drives. That option removes the error from the NAS when you are running). I also picked the Photo station patch option. It did not work the first time, it went to the end of the 10 minutes and then said something went wrong. I reran the ARC/USB stick and picked FORCED REINSTALL and that worked. I'm currently rebuilding my 3rd drive because I originally moved where it was connected to the SATA port from 3rd to 4th position on the motherboard (if that made a difference hence the rebuild). IMPORTANT - WAIT WAIT and WAIT - Arc runs slow, just WAIT...it will eventually get to the end showing the root info saying ARC and telling you to log into your NAS. THANKS! I will try to follow what you said. YOU ARE RIGHT, I forgot what to do, haven't updated in a while. I did save my notes and original manual. I thought Tiny Loader updated itself whenever it reboots. Funny you mentioned ARC as I saw a youtube video few days ago. I'll look more into it.
  5. Hello Everyone, Okay so the situation is this. My NAS shows up in the Synology Assistant. The drives are mapped, I can access in Windows File Explorer. It seems everything is working in the background. BUT I can no longer get into the NAS from my browser. I get this error "Sorry, the page you are looking for is not found." I spent a few hours searching the internet and this forum to see if I can fix it myself. I did not see any info. I've rebooted my router, tried other computers and browsers. I also rebooted the NAS few times. Hardware is bare metal. I am updated on the NAS to DSM 7.2.1-69057 Update 4 This problem came up when I shutdown the NAS and moved a drive from one of the sata ports. I was adding an SSD cache drive. After I rebooted, I can no longer get into the NAS from a web browser. I looked at Tiny loader on boot and it says up to date with 0.0.6 What do I do? I am awaiting your response before I do anything else. I was going to try recreating my Tiny USB boot drive but I will wait for you before I touch anything. THANKS!
  6. I am using HP8300 SFF. I have 3 4tb drives raid 5. I can add a 4th drive or add an ssd drive to boot windows and use it for gaming etc... I only added a sata power splitter for the 4th drive. These are great machines and everything fits neatly. It fits into my tv cabinet and you can't see it or hear it. I am using mine the same way as you are. I find the stock nic card to be fast enough. I have 8gb of ram (can go to 32 if I wanted). The unit is fast and easy to work on. I got a displayport to hdmi cable to connect the desktop to my tv. I am still undecided if I want to add the ssd and turn this into basic gaming and retro gaming machine. I simply shut down then remove the USB boot key .... reboot from ssd with windows to play games. Oh, I added a simple bluetooth dongle so I can use a ps4 or xbox controller. I was trying to understand using windows then a vmware session to run synology but I am still leaning towards my setup for bare metal. Have fun, this is a great setup the team here has created for everyone. * I removed my dvd drive and added a replacement thing that blocks the hole but allows you to add 3.5 drives and 2.5 drives. You will also need those blue screws to add to 3.5 drive or 2.5 drive cage for the spot under the power supply for a drive. *** remove the face from the body and you will see 4 black and 4 silver spare screws already screwed into the front. Use these for the drives that replace the dvd area. They will not fir under the power supply. AliExpress has the hp blue screws for $1 for 4 (they are cheap, buy a few)
  7. If you are referring to me since you were not specific...I think if you read what the problem I encountered actually revealed some minor issues with TCRP to which Peter and Poco have solved and still investigating at the time of this post. If this occurred with me then it can easily happen to others and having this info reduces the future post and most importantly "stress" new or upgrading members might encounter. The mods here are very capable to sort the info. TCRP and Friend are really awesome pieces of tech and it seems they are fine tuning this thing to be that much better. Please remember, not everyone starts as an advanced/expert user. The info shared with me from other senior members here has allowed me to help other new users. My account is new but I am not new to this forum. Happy New Year Everyone!!!
  8. @pocopico @Peter Suh Is it safe to update the loader? Do I just reboot and the loader will auto update? Or should I wait until you guys sort out the version display issue? Thanks Please clarify... It's my understanding that we SHOULD NOT update the nas beyond what the loader supports? e.g. If loader image is DS3622 version 1 then we do NOT install UPDATE 2 from Synology. Even though I was able to do it, does NOT mean we do it. Is my understanding correct? If my understanding is correct, then perhaps you guys can post a warning in the loader or directions in red something such as DO NOT UPDATE DSM beyond what RPL supports (what we see to download when building the loader, the .pat files listed in the loader)
  9. @petersuh I just created another usb key it now says UPDATE 2 (not 3) side note - I used win32diskimager this time. I used RUFUS before I saw errors fly by something about disk characters 2^32 I am using a 32gb usb3 drive. My 4gb usb 2 drive only boots to the grub recovery now. I used that when I posted it was fixed. strange The key note and maybe perhaps you guys can add this to your guides...when it says recovering/migrate and syno assistant says can't recover/failed...Open a browser window and go to the nas ip then do the migrate from there and it will take 10 minutes counting down then get to 0 and says fail...it didn't fail, just reboot everything and wait, then open syno assistant to see the nas then use browser to access the unit. I sure come across strange errors and fixes
  10. @petersuh just a small observation in the tool creator in the serial number menu, you have option 1 as generate and option 2 enter manual BUT in the mac menu, you have them reversed Can you please consider making them the same and default to generate thx
  11. yes, i recall seeing update 0 also. That's why I knew I needed you guys to add update 3 then it would work. I am about to make another usb key (testing my keys). Is it possible to use 2 DIFFERENT usb keys? I would like to keep a spare key ready to go. Or do they same to be identical physical keys (same brand etc...)
  12. @Peter and Poco It's FIXED!!!! Peter, did you apply update 3 to the loader?? This is how I fixed it. 1. remade usb key (did it 3 times with 3 keys, that wasn't the issue) I booted with the key, used syno assistant... IF you click recover here, it will FAIL giving you error and time out. With a fresh key I amde about 15 minutes from posting here and Peter's post... I booted then went to syno assistant THEN I looked at the IP of my nas THEN I went to browser and typed the IP...I picked migrate...it took 10 minutes...It said FAILED at the end BUT...I rebooted the box and started with loader...then used syno assist then it showed me the name of my box with the manual ip I had set. I was able to log in and it is showing DSM 7.1.1-42962 UPDATE 3. I am assuming Peter and Poco did not change anything. The TRICK/BUG is to assume the MIGRATE repair worked even though right at the end says failed. Reboot and all should work for you. THANKS PETER AND POCO!!! I was able to patch together ideas using the info you supplied. It did not make sense that it took all that time, went to the last second then to say fail.
  13. @PeterSuh I made a new usb key using the automated redpill loader - everything went well, no errors I am still getting error from syno assistant: Failed to recover. System has no response. Connection timed out. Just to clarify, I managed to install update 3 on my drives. I am guessing the redpill loader only has update 1 . Is it possible you can add update 3 to the redpill update so my usb key will have the file that matches what's on the drives? Thanks for your help. *** just a thought...perhaps add a sentence at the end of the loader nothing will be displayed here anymore....add use synoassistant on your computer to further manage this new nas setup. It's just an idea to help new users. What you guys are doing here is mind boggling. It makes my head spin knowing how cool what you guys are creating. IMPRESSIVE!!!
  14. Did I miss something? I wrote it EXACTLY how you posted with the "quotes" also.
  15. I am unable to edit my post above. I don't see the option, it was there before. UPDATE: I have to go back and reread this thread or others but if you know, I would appreciate the reply. Does this TRPL setup allow us to download updates from Synology directly using the update feature? I tried to check for updates but my NAS reported no network connection. I have access because the time updated etc... Is this a "bug" or are we only supposed to update manually with this setup? I researched quite a bit last night. There are good Youtube videos showing between old and new synology units. I moved the 3 drives from old to new desktop. Booted up and followed the directions. You will need your .pat file again to manually update from your local machine. In terms of data protection. I don't know so I am asking. Could I have connected 2 drives (not the 3rd) and did the migration to ensure it all worked THEN after a shutdown, connect the 3rd drive, reboot and let it add it to the pool? I am running 3 drives in raid 5 (mirror). If something went wrong, then at least the 3rd drive is safe with all of the data. This was helpful also. https://kb.synology.com/en-us/DSM/tutorial/How_to_migrate_between_Synology_NAS_DSM_6_0_and_later
  16. Assistance please. I am being cautious. I did read the Synology KB article. In short they say to plug in my old drives to the new machine and all works (I guess it runs the migration after boot). I am a bit apprehensive because I don't want to lose my data (backing up my photos). It sounds "easy" as a plug in the old drives to new machine and boot then run migration and viola/done. My setup - I have 2 desktops: 1. HP8200 (sandy lake) DS3615xs DSM 6.2.3-25426 Update 3 I have 3 hard drives mirrored Everything is working I am moving to desktop 2 2. HP8300 (Ivy Bridge) already setup with DSM 7 (redpill loader) and working with a test hard drive DS3622xs+ I am not sure if the migration would work given that I am switching machines and DS models. Do I simply install all of my current drive from desktop 1 into desktop 2 and THEN what do I do? Do I install 1 or 2 drives to get things working THEN add the 3rd drive to the system? Please let me know so I can proceed. I am on pause until further directions from you guys. * I am backing up my files to external usb drive. ** Fly and others, just for the fun of it, I tried to setup using the DS920+. It failed about 40% when trying to install the Synology DSM pat file. The RPLoader allowed me to setup the usb key as a DS920+. I resorted back to redoing the loader and setting up as DS3622xs+. It worked. *** Anyone using the HP8300SFF units, they are great, has 4 sata connectors. Just add 1 more power splitter. You can buy a cool replacment bay for the dvd drive and mount drives in it. I have 3 drives for NAS and 1 laptop drive to boot Windows should I want to use the desktop for other purposes. I simply shutdown the NAS and remove the USB and it reboots into Windows/Linux drive. I updated bios to ver. 2.09 (latest). Turned off UEFI and set boot from USB as well as turned on AHCI per FLY's guide. I did NOT have to format the usb key to hyrid ( pain in the rear, more steps) like I had to with the HP8200. I made was able to follow the directions here and it all worked. I am not sure if this procedure would work for me: The actual migration process is simple: Remove any existing SSD cache configuration (strongly recommended) Shut down the NAS Replace the existing 6.x USB loader with the TCRP 7.x USB loader from the process above Boot the NAS and complete the DSM Migration when prompted Restore SSD cache configuration as desired
  17. First- This is an AMAZING guide. THANKS Fly!!!! I did notice a slight variation when I just setup my unit. The RPloader will list the DS models and not the chipset that you wrote. This section here...suggestion change it to pick your model and build # and add an example as you have in other sections. Finally, choose a DSM release number Each DSM build as provided by Synology has a release number. You can display the combinations of platforms and releases supported by TCRP by just running the script with no arguments
×
×
  • Create New...