tcs
Member-
Posts
39 -
Joined
-
Last visited
-
Days Won
1
Everything posted by tcs
-
Physical drive limits of an emulated Synology machine?
tcs replied to SteinerKD's topic in Hardware Modding
If you want to have >26 drives there are really two key things that need to happen. On *INITIAL INSTALL*, you need to have "maxdisks" set to less than 26, I would suggest just doing 12. Once you have gotten through the initial install and first full boot, you then go back and modify maxdisks to a larger number and create your volumes/raid arrays. This is because on first boot, DSM takes a slice off every disk to create a RAID-1 array for DSM itself to live on. Whatever binary they use to create this partition is passed the "maxdisks" variable, and if that variable is >26 the binary will crash. After a system has been installed this script/binary is never called again that I've seen unless you're trying to do a "controller swap" - IE If you went from a 3615 to 3617 it would be called again. -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
I ended up switching to the 3615 image, I could not get the 918 image to properly see the drives. -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
After you do redpill run, you go into redpill-load and edit bundled-exts.json to add whatever extensions you need. If you need more guidance than that, you should probably hold off running this until it's in a more stable state. -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
can you ping github from within the container? What happens when you manually curl the file from inside the container? -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
Do you have a firewall running on the box you have the container on? That’s telling you it can’t make an https connection to GitHub. Can you get to the address from a web browser? Either you’re in a country that is blocking GitHub entirely or something local to your system is doing it. -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
Then they shouldn't be using redpill. It's not considered stable yet, or in any way ready for general consumption. If someone isn't capable of building a bootloader they should wait until the final version is ready for public consumption. -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
Just for giggles I ran this for you, not on an HP box, but a 3615 image 7.0.1-42218 on a supermicro X10SAE with an E3-1225 v3. It ran for an hour before I killed it, no issues other than it complaining about cache after filling up the disk which I expect is normal. -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
What is your maxdisk count set to? How many drives are in the system? And did you double check your USB drive ID? -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
Understand, that's why I @'d you both. I foresee endless requests for help by people adding drivers if those sizes remain the way they are. If the end goal is: usable by everyone, the manual steps listed above probably won't cut it. If the intended audience is the same as the beta: you understand enough coding and linux to unwind problems yourself, then it's not an issue. -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
I think the broader point being that with the size of the current drivers being put out, that volume needs to be larger by default unless there's some reason I'm unaware of that it's stuck at 40MB. Probably wouldn't be a bad idea to make it a flag or part of the config for the docker script @haydibe @ThorGroup. For instance, I can tell you with the mptsas drivers alone that pretty much blows up all the space for drivers by themselves. If you need mptsas and mpt2sas or mpt3sas and the 42218 build you're dead in the water without a larger partition. -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
Definitely an issue with 918+ with SAS adapters on bare metal issue. Switched to 3615 image and it happily reads smart data. The only outstanding issue with 3615 with SAS on bare metal is - I do see this being spammed in scemd.log: scemd[19875]: space_internal_lib.c:1403 Get value of sys_adjust_groups failed space_disk_sys_adjust_select_create.c:600 Failed to generate new system disk list Haven't spent any time to dig further but it otherwise seems happy. -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
It looks like syno is trying to attach a marvell driver to the drives despite them being on an mpt2sas controller: cat /var/log/scemd.log 2021-10-11T16:37:24-05:00 host01 scemd[21169]: disk/disk_is_mv1475_driver.c:71 Can't get sata chip name from pattern /sys/block/sdx/device/../../scsi_host/host*/proc_name Anyone else running bare metal or passthrough LSI with the 918+ and 42218 able to check and see if you have the same errors? -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
Anyone run into this one? For some reason it seems to think a bunch of disks are ineligible for creating a new pool, even though the drives are perfectly healthy. I feel like I've run into this before but don't remember what was causing it. The "disk_reason_template_0" is rather humorous. -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
I would second this. It’s relatively easy to get a 918 build working if you understand json and can read compiler errors. That being said if you can’t, just stop trying and be patient. @Orphée - your 918 repo needed the model changed to 918p and to be pointed at the virtIO build for 4.4.180plus if you care. -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
Also a quick note on this front: it only takes two of the SAS drivers to run out of space with the 918+ build, not sure if @pocopico did something wrong building them or if they're really just that big - they're significantly larger than their 3615 counterparts. The 4.4.180plus mptsas driver alone is 6.76MB: https://github.com/pocopico/rp-ext/blob/main/mptsas/releases/mptsas-4.4.180plus.tgz -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
What he's saying is he upgraded to 6.2.4 without reading the forums first, so I'm sure the system is currently a brick. 6.2.4 does not work with Jun's loader. -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
Presumably there's something in the external SAS connectivity spaghetti code that allows for more than 26 drives - maybe that's a reason to emulate? In theory it'd allow people to use external SAS trays as well (although I'm unclear on whether emulation is actually needed to support that or not). Curious if anyone actually has a functioning native synology system with more than 26 drives to donate to unwinding the mess. -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
https://github.com/pocopico/rp-ext/blob/main/mptsas/rpext-index.json What am I missing? I only see the 42218 for the 3615. "releases": { "ds3615xs_25556": "https://raw.githubusercontent.com/pocopico/rp-ext/master/mptsas/releases/ds3615xs_25556.json", "ds3615xs_41222": "https://raw.githubusercontent.com/pocopico/rp-ext/master/mptsas/releases/ds3615xs_41222.json", "ds3615xs_42218": "https://raw.githubusercontent.com/pocopico/rp-ext/master/mptsas/releases/ds3615xs_42218.json", "ds918p_41890": "https://raw.githubusercontent.com/pocopico/rp-ext/master/mptsas/releases/ds918p_41890.json", "ds918p_25556": "https://raw.githubusercontent.com/pocopico/rp-ext/master/mptsas/releases/ds918p_25556.json" } } -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
Looks like you only added it for the 3615, can you do the 918 as well? -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
I was just doing a poor job of noticing the repo changes, don't mind me -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
Still not following how this properly builds without the proper config folder? That config folder doesn't exist in any of the repo's. [!] There doesn't seem to be a config for DS918+ platform running 7.0.1-42218 (checked /opt/redpill-load/config/DS918+/7.0.1-42218/config.json) -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
master branch handles extensions. -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
How exactly did you get that to build? Neither the redpill or jumkey repo contain the appropriate files for 918 or 3615: [!] There doesn't seem to be a config for DS918+ platform running 7.0.1-42218 (checked /opt/redpill-load/config/DS918+/7.0.1-42218/config.json) -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
@pocopico - any chance you can update the driver repo to support 42218? Appears to be the same kernel so I'd imagine it's just a matter of updating the json files, no? -
RedPill - the new loader for 6.2.4 - Discussion
tcs replied to ThorGroup's topic in Developer Discussion Room
Your branch should be master, not "develop" if you want to be able to add extensions.