WiteWulf
-
Posts
423 -
Joined
-
Last visited
-
Days Won
25
Posts posted by WiteWulf
-
-
17 hours ago, IG-88 said:
just a reminder we are in the section "Developer Discussion Room" - any further questions?
about >80% of the posts are offtopic and i'm not counting myself as "developer" because i'm not committing any code to the git in question so ....
Absolutely! I think it was mentioned at one point that support issues could be dealt with in another thread/section, but the phrase "that ship's already sailed" was mentioned.
I can't speak for them, obviously, but I think TTG's intention was for this thread to be much shorter-lived and lower traffic, with proper support and discussion threads elsewhere on the forum once redpill came out of alpha. Development has maybe been slower than anticipated and this thread has grown way beyond manageable, imho. At 122 pages we can't seriously expect newcomers to read the whole thread and be up to date on procedures and politics (for want of a better word).
We need an updated project FAQ at the bare minimum, and separation of development and support threads. But this isn't my project and I don't want to tread on TTG's toes, wherever they are...-
5
-
-
12 hours ago, seanone said:
Don't agree that, developer also need much more testers to test it, software is useless without users.
Yes, but devs need technically experienced and capable users who can follow detailed instructions and provide good quality feedback and diagnostics beyond "it doesn't work".
If you can't follow the instructions to build redpill-lkm and redpill-load at the moment you're not ready for testing it, sorry.
-
3 hours ago, fly said:
you need to make it by youre self because everyone has own setup.
You need to make it yourself because the boot images contain copyrighted software belonging to Synology.
The whole point of redpill-load is to enable people to build their own custom boot image using the software Synology make publicly available without redistributing that same Synology software with associated legal problems.
Please don't ask for images and please don't provide them if anyone asks. -
-
4 hours ago, Nixion said:
my redpill image get stuck on "booting kernel" and not found on find.synology.com of assistent
some one can help my i don't now how to do
There is no further screen output once the “booting kernel” message appears. This is expected behaviour. All further output is sent to the serial console (if you have a serial port).
Not finding the server with Assistant suggests it hasn’t acquired a DHCP lease, probably due to the network not being brought up. It’s likely your NIC is not supported by the default image.
Exactly what hardware and DSM version are you trying to install on? Please give as much detail as possible.
-
Isn't synoinfo.conf generated dynamically at boot? I don't think there *is* an official one, as it would be different for each installation.
-
56 minutes ago, Aigor said:
Hi, do someone tried to perform in-place upgrade from DSM 6.2 to 7.1 into live system?
Any hint apart backup of data?
Thanks
I didn't do in-place for 6.2.4 to 7.0.1, I booted my 6.2.4 system from a 7.0.1 usb stick and ran through a migration.
I tried in-place for 7.0 to 7.0.1, though, and that didn't work out well. See my post further back in the thread. I think the process may always need to be: boot from target version USB stick, then migrate.
-
3 hours ago, havast said:
Solved the problem, thanks
Could you explain what you did to solve it, please?
Others may come here later looking for a solution to the same problem, and this is one of the most frustrating replies to find
-
1
-
-
56 minutes ago, fly said:
btw according to IG-88 last Github update was on 31th Oct.
NB. GitHub considers additions/updates to "Issues" and pull requests as updates. There have been no commits to redpill-lkm or redpill-load for much longer. redpill-extensions never seems to have had any pull requests accepted (which was meant to be the mechanism by which extension were submitted to the project).
The user "ttg-public" hasn't been active on GitHub since the 3rd of October when they created "RedPill-TTG/redpill-sas-activator", and they haven't been active on this site since October 8th.
I remain hopeful they'll return...but have cloned all the GitHub repos to be safe.
-
3
-
-
TTG have been silent for about a month now. Their last update is the last anyone's heard from them around here. The GitHub repos are still there, though, so it's unlikely to have been anything legal/takedown related. They mentioned some unexpected personal issues at one point, so I guess life has gotten in the way
-
1
-
2
-
-
Has anyone done an in-place update yet, ie. gone from one version to another, downloaded and installed from within the control panel?
Can it be done and do you need to create a new boot image?
My ESXi guest was running apollolake-7.0-41890 and offering to update to 7.0.1-42218. I downloaded and installed it and it seemed to install okay but I had no networking afterwards. I got logged in on the virtual serial console and tried reconfiguring networking but with no success. I eventually rolled it back (I'd taken a snapshot before trying).
-
1 hour ago, Soniccube said:
Why not open source the redpill-helper to github? It would be more convenient for developing and publish.
It's just a script and some config files, everything is there for you to see in the downloaded zip file. No compiled code, no obfuscation, and Haydibe has given his blessing for people to do whatever they want with the code so long as they're (haydibe) not linked with it outside of this site.
-
1
-
-
1 minute ago, titoum said:
ok so i should have kernel panic somewhere because when putting my screen on...i clearly see a reboot. imo, the only change is the usage of photo so it might be culprit with plex... if i rebuild a key with another serial shouldn't see it as a move and propose me to migrate ?
Ah, you didn't mention Plex before! That was one of the applications guaranteed to kernel panic my system. Much more information (and a possible work-around) here:
https://github.com/RedPill-TTG/redpill-lkm/issues/21
I don't know if rebuilding the key with a different serial will trigger a reinstall. Give it a try and let us know!
-
We've seen some instability issues with the bromolow/DS3615xs images when under load, but they usually manifest as reboots on baremetal (following a kernel panic) or lock ups on virtualised platforms. As yours doesn't appear to be rebooting I'm not convinced this is the problem.
Ideally you're going to need to get the console logs to see what's going on when/before it becomes unreachable.
It's possible to format the partition on your HDDs that contains the DSM install (while preserving your data), then reboot off the USB stick and reinstall DSM. Have a search of the forums to find details, it's not a procedure that's specific to redpill or DSM7
-
9 minutes ago, titoum said:
hi there,
NAS was working fine then i let it run during the day...
now, it doesn't work properly anymore as i have half of the icon being displayed.
interface was not reachable so i rebooted it through power button and now it started data scrubbing.
it seems that something doesn't go well (obviously)...
is there a way to refresh the dsm install ? i did an upgrade on the 7.0.1-4x to the latest version so i am wondering if something went off the road.
A few questions:
- please be a lot more specific than "it doesn't work properly anymore". What exactly isn't working? Are you getting any error messages? Are the errors reproducible?
- you say you upgraded: what version were you running previously and what process did you use to upgrade?
- what hardware are you running on? Please give as much detail as possible
- what version of DSM are you running? Please include version number and platform
You'll notice that a lot of forum members include the last two points in their signatures so they're always visible and it saves asking. I'd suggest you take the time to do the same to help yourself and everyone else.
FYI data scrubbing is to be expected if you didn't perform a clean shutdown. It's just DSM doing some background checking on your disks to ensure no data was lost/damaged when you power cycled the server.
-
59 minutes ago, bifferos said:
I'm surprised you think this is in any way comparable. If Synology do something malicious and someone finds out they get their asses handed to them in court. There's no such protection for this closed-source loader. Who is Jun? What is his address? Where would any court papers be served? I've no problem with closed-source software per se since I make a living out of it. I use open and closed-source software as I feel appropriate. I think you have to have a balance.
Thanks for the tip about Redpill. It sounds like I should definitely try it, it came across as a bit Alpha but if you're using it successfully I will give it a go, especially if that's where the dev effort is now.
I have tried FreeNAS but I'm not a fan. Yes, I eventually got it to do what I wanted but nothing like as painlessly as DSM.
As for buying another NAS (Orphee's suggestion), yes I could do that, but I'm running Proxmox 24/7 already, so it would be nice to combine the two boxes, save some space in my house etc... I have 8 disk bays free in the Proxmox server, seems wasted right now.
You're talking about using Synology's code on hardware it was never intended for, and that you haven't paid for or have entered into a EULA for. I get your argument re open/closed source in general, but this project is very unofficial and I doubt you'd have any recourse in law with Synology in this sort of usage if they did "something malicious". To address the concerns you have you'd be much better off paying Synology for their product, imho. You also, of course, have no guaranteed legal recourse when using open source software in general. The person who uploads it to github, or wherever, need not be who they say they are. FWIW, Jun's loader is pretty much dead, development-wise. No one ever really knew who they were or where they were. That's a risk some people are willing to take, I guess, when they want something without paying for it ¯\_(ツ)_/¯
With the above in mind, it's worth pointing out that, although redpill is open source, the developers have gone to some lengths to protect their identity and avoid potential legal entanglements with Synology.
Please don't take my comments re. the stability of redpill as a recommendation in any way of it's stability or readiness for use. I've not suffered data loss, but it's a possibility, ymmv.
Your comments re. FreeNAS strike a chord with me. I consider myself a proficient linux user, but I wanted a system that "just works" out of the box and has managed system updates. Of course I wasn't prepared to pay the premium for the Synology hardware, so that's why I'm here.
Proxmox seems the right approach for you, given your investment in the chassis, and there are a lot of people using it (as well as VMware) on the redpill discussion thread.
-
So you're objecting to a closed-source bootloader that enables you to use a commercial OS distribution that itself has closed-source elements?
Redpill definitely isn't production-ready yet, but it's getting there. I'm using it for day-to-day use on a couple of production servers, but I have read and understood all documentation and open issues on the GitHub repos and am contributing to the development effort.
But yeah, you're correct in the second part: these projects are about getting Synology's software to run on other, generic x86 hardware, and keeping the loader working through Synology OS revisions. There's no effort I'm aware of to allow other software to run on Synology hardware (although, strangely, I've seen a few ppl mention running DSM on QNAP hardware).
From what you're saying I think you'd be better of looking at something like FreeNAS, but another option is to build an x86 system that will take the HDDs from you DS213j and put an xpenology bootloader stick in it (Jun's if you're happy with being stuck on 6.2.3 and closed source, or Redpill if you want newer and open-source but not production-ready (yet)). When it boots it will detect the existing install on the old disks and ask if you want to migrate to a new install. Your data, settings and apps should all be there ready for you when it finishes installing, regardless of that fact that you've moved from an ARM box to x86. That's one of the nice things about DSM.
-
3
-
-
8 hours ago, chrram said:
Hello, maybe someone can give me a template for proxmox dsm7, a finished image or can help me get the DSM7 on proxmox, also via DM, thank you
-
1
-
4
-
-
I think at this point people to need to be quite clear what project they're asking for source for.
I can think of at least the following that have been worked on/used on these forums over the years:
- Synology DSM (some stuff released, some not: https://sourceforge.net/projects/dsgpl/)
- Jun's Loader (source never released, not open source afaik)
- xpenoboot loader (???)
- quicknik's loader (???)
- nanoboot (???)
- redpill (https://github.com/RedPill-TTG)
-
Hi @ThorGroup, not heard from you guys for three weeks now, here or Github. You okay?
Some of us are getting a little worried that Something Bad™ happened. Hope things are good, shout out if there's anything we can do to help (generally, not just regarding RedPill, okay?).
Just say "hi" if you're still around and too busy/have other things on...
-
7
-
-
19 minutes ago, mounsif said:
thx for you help I noticed you are using ESXI can you upload a img of it 🤗
No, sorry. If you read ThorGroup's many posts on the subject, one of the basic ideas of RedPill is to allow users to build their own images easily and not need to share images which include copyrighted Synology material. ThorGroup suggested that an earlier version of this project (from another team of developers) was shut down for exactly that reason.
Please don't share images and please don't ask others to share them. It's risks the future of the project if it's redistributing Synology's software.
From ThorGroup:
QuoteThere are very good reasons why we're not sharing complete images and why we spend many many many hours developing the generator. The RP started in a different thread, its code was shared in different GH repos, the initial work wasn't done by us... and it's now unavailable. Full loader images contain way more than the GPL kernel. They contain syno's proprietary and copyrighted binaries. Distributing them is... problematic at best.
-
2
-
1
-
-
2 hours ago, mounsif said:
SAS disks
As I understand it there is a problem with the Synology kernel not recognising SAS disks >2TB, something to do with it being a very old driver version. I'll see if I can dig up a reference to it.
...
QuoteSo, regarding the SAS issue: the sas-activator may be a flop. We tested it with SSDs and few spare HDDs which obviously weren't >2TB. It seems like the driver syno ships is ancient and while it does work it only runs using SAS2 (limit to 2TB is one of the symptoms). Don't we all love that ancient kernel? Probably on systems with mpt3sas the situation isn't a problem.
As to the native SAS support and how it works: in short it's useless. The SAS support in syno is tied to just a few hardcoded models. Most of them support only external ports (via eboxes). Some, like in a few FS* products support internal ports. Unfortunately, this is completely useless as the OS checks for custom firmware, board names, responses etc. Is it possible to emulate that? Yes. Does it make sense? In our opinion not at all. With the community-provided drivers we can all be fully independent of the syno-provided .ko in the image. As the LKM supports SAS-to-SATA emulation for the purpose of syno APIs thinking it's a "SATA" device further investment into true SAS doesn't really make sense. To be clear here: there's no loss of functionality or anything. Many things in the kernel actually use the "SATA" type. It seems like syno intended it to be a true SATA but down the road changed it to really mean "a normal SCSI-based disk".
The reason why syno separates real SAS controllers is to offer .... hmm, a lot of hacks over their firmware and timing issues with LSI controllers. So in short emulating a true SAS type in syno will give us no benefits. Saying this we also, very cautiously, should probably make a recommendation: for anyone using a standard array of disks of 4-8 it's probably a better choice to go with a Marvell-based chip which works natively without drivers (and which syno uses as well). For bigger installations LSIs are still preferred (as they're cheap, work with low-cost used SAS drives, save on cabling etc etc). -
2 hours ago, NooL said:
English here, otherwise its the French section in the forum
Bit rude!
@Jotouriste merci beaucoup pour votre avis, mais le section française est plus appropriée.
Avez vous le kernel panic avec docker/database concernant https://github.com/RedPill-TTG/redpill-lkm/issues/21 ?
Désolé pour ma pauvre "école d'anglais" français
-
2
-
-
3 minutes ago, titoum said:
yep problem is sloved... apparently saving plex directory is blocking the whole thing...wondering why but ok. 😑
Was PMS running at the time? It's basically a big database, so trying to back it up while running will give you errors re. locked files. You should be able to backup the media library locations with no problems, but the database backend will be problematic.
RedPill - the new loader for 6.2.4 - Discussion
in Developer Discussion Room
Posted · Edited by WiteWulf
Nice, and an interesting write up of how they did it (using IDA Pro), too.
Be sure to read the full article if you consider using this:
- it probably won't survive a DSM update
- it probably won't survive a Photos app update
- use DS3615xs if keeping Face Detection is important to you