Franks4fingers

Members
  • Content Count

    44
  • Joined

  • Last visited

Community Reputation

6 Neutral

About Franks4fingers

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. 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 followi
  4. 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.
  5. @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.
  6. 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.
  7. 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?
  8. Anyone seen this issue before since migrating to DSM7 and any guidance on what I can try to do to resolve it?
  9. I have upgraded today and am now running Apollolake 7.0.1-42218. I have got Plex MS up and running and have repaired other packages that needed it. Python fails to update but I believe Python is an issue anyway in DSM7. One thing that has happened is that I have lost the ability to connect to Sonarr, Radarr or NZBGet which I run via Docker. (EDIT - I actually see these packages are available via the SynoCommunity repo so would I be better off just to stop the Docker containers and instead install the packages from SC? I used to them ages ago but they weren't being regularyl u
  10. Do you need to be running 6.2.4 to be able to go to 7 or can you be on 6.2.3 and then still make that jump?
  11. Curious if anyone can provide some guidance if this is possible: Currently running 6.2.3-25426 Update 3 via Jun's loader on baremetal. I would like to get to V7 but would like to try and do that by converting to Proxmox in ther process. I have a second PC that is identical in terms of mobo / processor that I could use if required as part of this conversion (assuming it's possible of course). The eventual aim is to have this virtual instance running on the original source system because that is running in a tower case (the target I could use is a SFF PC which
  12. I think this is where it would be ideal if some sort of tutorial could be drafted for the masses. I know that RP is still classed as Alpha and in theory for people with some experience, but I think that if there was a guide that could be followed then people who are willing to give it a go can do so. This would reduce the potential of image sharing. Of course any guide would be up to the end user to follow and if they didn't get it right then there could be no comeback. We should all be adult enough to run with the consequences in the event something went awry. Just my