Franks4fingers
-
Posts
59 -
Joined
-
Last visited
Everything posted by Franks4fingers
-
Hi all I recently followed this guide to install the Mega Sync tool - https://mariushosting.com/how-to-install-mega-on-your-synology-nas/ All went well and I was able to log in to my Mega account, set up the sync and it happily ran in the background and downloaded all the files that I wanted it to. The problem is now I can't find them on my device. I am not an expert in Linux and so aren't sure about where I can go or what commands I can run to try and find them. I think the problem partly lies in the fact that the guide advises to install the package as root. Is there anyone in the community who could point me in the right direction on how I locate the files I have downloaded so I can move them elsewhere. Also, is there anyone who can give me a pointer on the best way to have created this container so I can redo it to avoid this problem again. Hoping someone can help. Cheers
-
Hi all I am looking to purchase an external camera or maybe two that I can use with Surveillance Station. I quite like the look of Reolink but am not necessarily tied to that if there are other good alternatives. Keen to understand if anyone is using Surveillance Station and what the experience is like. The key question though relates to decent, reasonably priced camera options that work with Xpenology. Any info would be great. Cheers
-
Hi all Currently using ARPL as the loader with DS918+ as the model and using the latest pat file. Everything is working fine so this question to the masses is me just being curious. I see a lot of comments around the use of one of the later models for the pat files with a number of them referring to DS3622xs+. Can anyone advise why people would change their installation to use 3622 over DS918+? I am running my server on a repurposed Dell Optiplex 9020 SFF with a core i5 CPU. Software wise, the only thing I think of significance would be that I run Plex Media Server and believe the CPU has enough grunt to do hardware transcoding. Any views or thoughts on this one? Cheers
-
Thanks.
-
Thanks pocopico.
-
With regards backing up of the loader disk before doing this. How do most people perform this? Looking for the simplest way as Linux skills aren't the greatest.......be even better if it could be done using the USB inserted into a W11 device.
-
Baremetal Hp microserver Gen8 migration to VM ( promox/esxi)
Franks4fingers replied to erimotte's topic in DSM 6.x
Thanks phone guy. I will get into it and see how I go. Appreciate all the detail -
Baremetal Hp microserver Gen8 migration to VM ( promox/esxi)
Franks4fingers replied to erimotte's topic in DSM 6.x
Thanks for the info @phone guy I presume by this I would have to remove the 3 drives that make up my SHR drive array today then........ Install a spare drive and then get Proxmox followed by TCRP followed by a generic Synology instance installed and running via your guide then..... Start the process to install one new drive and complete the migration piece? Just trying to get it clear in my head as to the high level steps as that makes it easier when doing the lower level steps. Cheers -
Baremetal Hp microserver Gen8 migration to VM ( promox/esxi)
Franks4fingers replied to erimotte's topic in DSM 6.x
I was hoping to click in to this thread and see that someone had said, "Yeah it can be done, and this is how you do it". I have the same question although I am running 7.1 via TCRP on my Dell 9020 repurposed desktop. I was thinking that I would like to convert to Proxmox via the guide that was written by @phone guy . The only thing I could think of is to backup your current instance of Xpenology to an external drive using HyperBackup. Follow the guide to get Proxmox up and running and then do a restore from the new instance. Sounds logical but as always you never know the gotcha's until you get into it. -
Thanks @gadreel
-
Ok so...... Update from the GUI within Synology from 7.1-42661 U1 to U3 Then reboot, drop into TCRP and go with the following: ./rploader.sh update ./rploader.sh fullupgrade ./rploader.sh postupdate apollolake-7.1-42661 Is that last command right?
-
That simple, thought there was more to it. Many thanks @gadreel
-
What version was this updating from? I am running 7.1-42661 as my base. Can I go straight to Update 3 with certain commands?
-
Solved the issue. I didn't realise Docker wasn't installed as part of the new update. Once I did then my containers were already there and voila.
-
Hi all I had a few issues in being able to migrate my original install from 7.0.1 to 7.1-42216 U1 but eventually I created a new TCRP loader which allowed me to get the update back up and running just now. Although I migrated to this update for some reason I do not get to see any of my prior packages that were installed via docker. These were NZBGet, Sonarr, Radarr, Transmission and Docker itself. I also don't see Hyper Backup or some other key packages installed that were there in the earlier version I was running. I took a Hyper Backup before migrating so can I install the package and then use that to restore the status of my Xpenology install back to where it was before upgrading......although with the 7.1-42661 OS. Or if not, how do I get my installs and config of Plex, Sonarr, Radarr, NZBGet etc back without having to go through the whole setup process again???
-
Hi all I have DSM7 running via the Tinycore loader and it is working fine. I was just wondering of the process for performing upgrades when Synology release minor updates. Do you have to do a complete rebuild using the latest .pat file or is there another way? The original thread is already huge so I thought maybe a separate topic would be easier for others to find. Any pointers would be great.
-
Thanks for the reply. I have jumped into the Storage Manager and found the link and having clicked on it the problem looks to be resolved. Cheers for the guidance.
-
Hi all I posted this initially in the main TinyCore thread but thought it better to have a separate post to allow the main thread to focus on support for those trying to get TC functional. I am successfully running DSM7 via @pocopico TinyCore Loader having migrated from 6.2.3. Since migrating I get the following error: I was asked to verify the status by running the following commands which gave the output below : mdadm --detail /dev/md0 mdadm --detail /dev/md1 @pocopico asked if I could run the following command to identify how many disks I had - mdadm —detail /dev/md2 which I did and the detail I got back was This is as far as I got before thinking it would be better to start a new thread so I am hoping that someone can assist with whatever I may need to do to try and resolve the issue about the System Partition Failed error in the first image. Anything that you may need me to provide then please let me know and I will get onto it. Thanks.....and great work to both Thor Group and @pocopico for their efforts in getting a loader that allows for DSM7 functionality.
-
Hey all Anyone heard from @pocopico lately? He / she has always been very active but not of late. Hoping its not another disappearance similar to TTG.
-
Hi @pocopico Four disks in total
-
@pocopico - Took me a while to get back to this as life got in the way. I have checked the disks and get the following detail. Based on this detail, they don't seem to match what my disk config shows, should / can I use the command you provided or should I look to do something different? Any pointers from you or the community would be great. Other than this one issue, everything else is running great and stable.
-
I got the same error as you when used the satamap script to try and determine what I had. In the end I had to manually change the satamap to =1 and left the other value (diskidxmap) I think it was to 00. Once I did that then the install went as planned. pocopico has advised a few people to try that and it appears to have got a lot of them going.
-
Sorry but can you clarify further....do you drop into TinyCore loader GUI and then do a backup from there and then just run the command sudo ./rploader.sh update now Or is there another step that is required?
-
Anyone seen this issue before since migrating to DSM7 and any guidance on what I can try to do to resolve it?
