gadreel
-
Posts
317 -
Joined
-
Last visited
-
Days Won
5
Posts posted by gadreel
-
-
Hi @pocopico. I have Unraid and I boot the img as a virtual USB. When trying to identify the usb to enter the correct VID and PID I get the below error.
tc@box:~$ ./rploader.sh identifyusb now Found QEMU QEMU QEMU QEMU SerialNumber: 1-0000:00:07.7-2 28754-0000:00:07.7-1 Vendor ID : 0x46f4 0x0627 Product ID : 0x0001 0x0001 Should i update the user_config.json with these values ? [Yy/Nn] y sed: -e expression #1, char 33: invalid usage of line address 0 sed: -e expression #1, char 33: invalid usage of line address 0
In the VM I created additional 2 hard disks (20G). First time the interface was Virtio and the other time was SATA and both times when I am on the DSM installation it reports that no drives were detected...
The qx1 is the video driver for VNC we can ignore that one...
tc@box:~$ ./rploader.sh listmods now Testing modules.alias.json -> File OK ------------------------------------------------------------------------------------------------ It looks that you will need the following modules : ./rploader.sh: line 982: ./redpill-load/ext-manager.sh: No such file or directory Found VGA Controller : pciid 1b36d00000100 Required Extension : qxl qxl Searching for matching extension for qxl Found matching extension : ./rploader.sh: line 982: ./redpill-load/ext-manager.sh: No such file or directory Found SATA Controller : pciid 8086d00002922 Required Extension : ahci Searching for matching extension for ahci Found matching extension : Found Ethernet Interface : pciid 1af4d00001041 Required Extension : No matching extension ------------------------------------------------------------------------------------------------
UPDATE: Removing the SataPortMap from the user_config.json found the drives but the installation failed. Will investigate further...
-
4 hours ago, pocopico said:
Hi ! Thanks, Care for some documentation
Documentation or maybe a YouTube Video?
-
@Hemin, if by early you mean the loader, the answer will always be yes. The loader is functional for most users, but still, before ThorGroup going AWOL the loader was still in alpha stage. If you use it on a production server it will be at your own risk. The same applies for Jun's loader...
At some point the community here we have to decide whether we should start using ThorGroup's loader or not and start creating tutorials and easy way for inexperienced users to create the loader, like what pocopico is trying to do here.
-
12 minutes ago, IG-88 said:
all speculation and guessing
i have one more, maybe its just one person and he/she had invested some time to make a working loader for 6.2.4/7.0 and as its working, all is documented and source is available there is no need to do more, drivers and other things can be delivered through other channels
and if there is need for more coding, all the documentation, source and forks can help to go on
i guess we are fine atm, working loader, source, documentation and next thing might be a pre-build loader or a (cloud/hosted) click and build solution to make it more accessible - either way the one doing this would be the one sticking his neck out
@IG-88 I would not agree more to your assumption...
In addition I know a lot of posts they mention that the loader is still under development, still on alpha stage etc... and you should not use this loader with the data that matter most to you. IMHO it does not matter if it's Red Pill or Jun's loader, the risk is always there, if you worry much about your data then it's better to buy an actual Synology...
-
1 hour ago, NeoID said:
I've build RedPill and everything it running as intended, but I can't get any other vNIC to work except e1000e.Both virtio and virtio-net aren't recognized. Anyone else tried this on UnRAID and gotten them to work? Would be nice to test higher speeds then 1Gbps.
As far as I remember... Unraid Virtio were working fine. I doubt they changed anything to caused such issue.
-
-
28 minutes ago, Aigor said:
A question, when "official release" will be available, we should to make a new bootloader every time when a update will be available?
Correct, but I believe on the last post by ThorGroup they gave me the impression that they will try to automate the bootloader procedure to make it easier and quicker for everyone, something like Haydibe's toolchain...
-
20 minutes ago, mcdull said:
A noob question. For every new loader image to test with, is it mandatory to migrate the entire system again?
Look at the first batch of today's answers from ThorGroup. I asked the same question look at the answer...
-
@ThorGroup as always thank you so much for all your work and your time that you spent to reply to all those pages. I even went to sleep and woke up and you guys kept replying...amazing.
May I suggest the following if you do not mind... Can you guys share a roadmap? Where are we, whats needs to be done from your perspective before an official release. In that way it might help a little bit with all that hacking that is going on lately.
- 1
-
It's highly recommended that you do not. That way is easier for Synology to ban you if they care. ThroGroup said that all telemetry and stuff were removed etc... but as always you rather not.
- 1
-
On 8/29/2021 at 10:52 AM, ThorGroup said:On 8/26/2021 at 2:19 PM, ghtester said:
I have succesfully compiled the image using docker, unfortunately the baremetal devices I can use for testing have just Broadcom ethernet adapters. Is there an easy way to modify the script(s) to get compiled & included tg3 module driver please? Where should I start looking?
Currently - no. We will have a sane method of adding drivers in the future.
@pocopico I think they will implement it at a later stage not during alpha stages.
-
1 hour ago, titoum said:
Can you explain why going virtual is better than baremetal?
everything is already so picky about hw difference so throwing in even more software layers to virtualize...how can this make thing easier?
so if you have an intel + supported nic by syno...what is the added value of virtual ?This is what is said before, as I mentioned into other posts, virtualisation has a lot less hassle. On my first XPEnology build I bought a MB with the I-219v ethernet chipset which was not supported...my bad. I had to throw that board away and buy a new one with 2 ethernets I-211 and I-219 to make it work...
As I expressed my opinion in another post and ThorGroup also commented on that, recent AMD leaks suggest that soon we will have 96cores/192treads CPU. With such a CPU as @taiziccf expressed in his own way you can build a lot more stuff than just a DSM. That 96 cores CPU can run a university lab with virtual machines.
Virtualisation has evolved a lot with Passing-through GPUs, ethernets, USB Controllers, Sata Controllers etc... The performance difference between baremetal and virtualisation is not really noticable.
Now if you have a BareMetal that is fully compatible it's not a problem at all, but not everybody has compatible hardware... other users would like to run XPEnology on an AMD CPU with higher clock speeds, or the latest Intel CPUs that might not be supported by Synology.
At the end virtualisation is a choice...but is the solution with less hassle in terms of compatibility for most users...
- 3
-
26 minutes ago, WiteWulf said:
To be honest, I think it's time I bit the bullet and went virtual. I've been running xpenology for years now and have lost count of the number of problems I've had caused by running baremetal
It's really just the time involved in backing everything up, rebuilding the machine, then restoring data that's holding me back. It's just so much simpler to do an in-place upgrade when it works, and not have to reconfigure all the services (mainly Plex) that are running on it.
IMHO you will make yourself a big favor if you do that...
-
1 hour ago, WiteWulf said:
Is RedPill intending to support baremetal, or just virtualisation platforms?
Yes, it will support baremetal too, as ThorGroup said before virtualisation has a lot less hassle!
- 1
- 1
-
12 minutes ago, jforts said:
2nd USB (newly formatted), manually edit the PID and VID during boot command <- will this work?
No idea. Never read something similar.
12 minutes ago, jforts said:I am using RedPill official git to generate the loader.
Can you try with Haydibe's docker container and see if you get similar results?
-
11 minutes ago, jforts said:
I formatted another USB facing the same result. May I know how to make sure the USB is loaded correctly?
I also notice another error:
Jan 1 00:00:35 raidtool: disk/disk_port_to_container.c:38 Unknown diskType Jan 1 00:00:35 raidtool: partition_path_enum.c:29 Failed to parsing device: name Jan 1 00:00:35 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type Jan 1 00:00:35 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Is it my USB does not mapped??
I am not sure to be honest. All I can tell you is that from previous posts when /dev/synoboot2 was not present in the OS it meant that the USB was not mounted.
Are you 100% you used the correct PID and VID for your flash drive? Did you use Haydibe's docker container to create the bootloader image?
-
8 minutes ago, jforts said:
The stuck at error 55% is due to there is no /dev/synoboot2. Anyone face this problem before?
This was happening when the USB was not loaded correctly...
-
If it was not clear what jumkey said, if you look into red-pill loader repo you will find inside the config folder that bsp file.
Currently the bsp file for 7.0.1 is not there. Either ThorGroup has to update the repo or build it yourself if you know how to...
As Jumkey mentioned in his post, everything it's in the ThorGroup repos how to do all that.
-
Just now, Orphée said:
From my understanding, can't be updated from DSM GUI. Loader block it, and crash the install.
Yes, this was my original question. So ThorGroup disabled the functionality to update from DSM? For the time being when there is update we need to create a new loader...?
I updated from the DSM and it goes to recovery mode and does nothing... is a test machine and I am just curious...
-
@jumkey do you know why the loader does not work if you update to 7.0.1 from DSM? It requires re-patching or something?
-
37 minutes ago, WowaDriver said:
Many thanks to the development to all involved!
Has anyone managed to create a useful VM with DSM 7 under Unraid?
In my case I would have to pass an LSI 9211-8i HBA and an intel NIC for native ethernet?
Would anyone share their configuration?
I did. If you go pages back you will find one of my posts that I shared my XML. I think ThorGroup replied back that for ethernet I slould use virtio.
Edit: Of course if you want to try to pass through your intel nic go ahead...
-
Tried to update DS918+ to this 7.0.1 release candidate. Things did not work out after the update... 🤣
-
43 minutes ago, hoangminh88 said:
Mais-MacBook-Pro:redpill-tool-chain_x86_64_v0.6 kevin$ ./redpill_tool_chain.sh build apollolake-7.0-41890 Downloading Kernel ######################################################################### 100.0%######################################################################### 100.0%######################################################################### 100.0% Downloading Toolkit Dev ######################################################################### 100.0%######################################################################### 100.0%######################################################################### 100.0% ./redpill_tool_chain.sh: line 16: docker: command not found
Make sure you have docker installed and run the command with sudo... e.g. sudo ./redpill_tool_chain.sh build apollolake-7.0-41890
- 1
-
8 minutes ago, haydibe said:
Since the raid/shr information is stored in the meta-data superblock it should not matter if the drives are in the same order.
Actualy I have never seen a QEEN XML. Haven't sumbled accross it on Proxmox so far, no such fiels are location in /etc or /lib.
I have yet to understand it Proxmox allows that level of configuration for storage.
Thanks for replying. I will leave it as is if it will not cause any issues...
Because if I remember correct maybe I read something somewhere (I could be very wrong) that DS918+ cannot take more than 12 drives, but maybe that has nothing to do with those numbers.
TinyCore RedPill Loader (TCRP)
in Loaders
Posted
I do not have multiple USBs, but I will give it a go.