Jump to content
XPEnology Community

xPalito93

Member
  • Posts

    20
  • Joined

  • Last visited

Everything posted by xPalito93

  1. I just got the same error here
  2. So i just tried to migrate from TCRP 918+ on 7.1.0 42661 to ARPL 0.4a6 920+ 7.1.1 42962. The synology won't boot anymore. I created my image, added the i915 (10th gen CPU) module and booted. I was able to go through the installation setup (the one where it asks to upload a PAT file or download it from the web). But after that the synology won't come up. I get the screen where it tells me my IP for about 30 seconds and then the screen goes black. The IP is pingable even after the screen goes black, but the page won't load up. The only driver i had to load manually back when i was using TCRP was the 8125, but i didn't do it with the ARPL since it gets added automatically as far as i understand.
  3. Thanks for your reply, is there a way to convert them?
  4. Hey everyone, how can i manually add this addon? https://raw.githubusercontent.com/pocopico/rp-ext/master/r8125/rpext-index.json I tried pasting this url but it tells me the file format not recognized. I need it for the DS920+
  5. Is this going to be the normal procedure moving forward? Like, if 7.2 comes out will we always have to do a two step update or will there be a way to update manually via the GUI without accessing TC?
  6. Do you have any idea why i keep getting this error after running the postupdate comand? Mounting root to get the latest dsmroot patch in /.syno/patch mount: /mnt/dsmroot: can't find in /etc/fstab. Failed to mount Failed to mount DSM root, cannot continue the postupdate process, returning
  7. I'm having an issue running the postupdate command. I'm trying to update from 7.0.1 -> 7.1 on 3622 This is what i did: Update to 7.1 on the GUI by manually uploading the pat. Boot into TC. ./rploader.sh update now ./rploader.sh backuploader now ./rploader.sh fullupgrade now ./rploader.sh download xxx ./rploader.sh postupdate xxx This is the error i get after running the postupdate comand: Any ideas why it's happening? Edit: xxx is broadwellnk-7.1.0-42661 for me
  8. I've got a similar issue running redpill on esxi 7.0. I always get a message saying that the .pat is corrupted. Does pid/vid matter when using esxi? If yes, which should i enter? Or how do i find out what i should input?
  9. I'll probably have to stop here because i don't even know where to input those commands lol. Do i simply boot any linux OS on it an input those commands? I'm running DSM Baremetal if it's any help
  10. I built 3 different images now. One with TTG SaS activator; one with pocopico mpt2sas and one with mpt2sas+mpt3sas+mptsas. None of them detect any drives. I still get no drives found.
  11. I'm getting really close but i'm missing something and i don't know what. I use ./redpill_tool_chain build xxx ./redpill_tool_chain run xxx then i browse to /opt/redpill-load ./ext-manager.sh add 'https://raw.githubusercontent.com/RedPill-TTG/redpill-sas-activator/master/rpext-index.json' what comes after? if i exit and do ./redpill_tool_chain auto xxx the extension doesn't get added if i stay in the image and do ./build-loader.sh 'DS3615xs' '7.0-41222' i get an error saying "Failed to copy /opt/redpill-load/ext/rp-lkm/redpill-linux-v3.10.108.ko to xxx"
  12. Awesome I figured it out lol, now i just have to find out which extension i have to add for my SAS card. Pocopico has mpt2sas, mpt3sas and mptsas. Is there a list somewhere? And thank you for your input
  13. I'll have to wait then, because i only used haydibe's toolchain and i can't seem to find bundled-exts.json in there. So i guess it doesn't work with his toolchain
  14. Can somebody explain how to insert Drivers? I only played around with the v0.8-0.11 toolchain without using the ext-manager, so I only used the Build & Auto command. I'm trying to learn as much as possible but it's not that easy lol. I have a Fujitsu Server at work which i've been using to play around. It has a Fujitsu D2607-A21 GS2 SAS card in it, which has a LSI SAS 2008 chip on it. What would my steps be to create an image with those drivers in it? Can i do it with the 0.11 toolchain? I hope someone has time to guide me through it 🙂 I forgot to add: I was able to create an image with 3615 on it, but it never finds any drives. That's the issue i'm facing and why i wanted to ask how to add drivers
  15. Thanks for you Input. The first mistake i made, was that i selected USB boot on 1st boot. So I've got to give that a go tomorrow at work. How do you make sure loader is using sata 0:0 and HDD is using sata1:x? In the VM settings, i have two HDDs and they're configured as Sata0:0 and Sata0:1 if i recall correctly. Are those settings done in the grub aswell?
  16. I started playing around with the redpill on two test rigs i have at work the last couple of days. I have a HP AIO PC with a 6th gen I3 on it and two Sata drives. I tried installing 918 on it on baremetal and everything works without any issues for now. But today i started playing with ESXI 7.0 for the first time ever and i followed a tutorial posted a couple pages back. It boots and i can find it on find.synology.com and it even detects two drives because it tells me it will erase the two drives connected. But when i start the installation with the selected PAT file, it always stops at 56% and tells me the file is corrupt. I tried creating the image with 0.9 and 0.10 and i tried DSM 7.0 & 7.0.1. I always get the same error. Am i missing something? I never really worked with ESXI, i'm trying to learn as much as possible The only thing i changed on the image is the Mac Address (i use a random mac adress like 123456abcdef) and i put the same address in the VM settings where you can select the network adapter. If i leave it on auto, it won't show up on the network. PID and VID shouldn't matter right? The other rig is an old fujitsu server which can only run 3615 but it won't detect any drives at all because of the LSI controller which is a known issue afaik.
  17. The redpill is new to me, so two days ago i decided to give it a go and look if i could get a test rig running. I tried the 0.8 and 0.9 tool and both would not work. The USB stick was never bootable. So i downloaded a precompiled image i found a couple pages back and tried it. Everything worked flawlessly after changing Pid, Vid and Mac address. I inspected both images by mounting the first partition with OSFmount ( the one i downloaded and those that i made myself with the tool ) and I noticed there were two folders missing.Both folders were the cause why it wouldn't boot. After copying the missing two folders to my image i build, everything worked without any issues and my test rig is running 7.0 since yesterday So unless I'm doing something wrong, both the 0.8 and 0.9 don't add the UEFI stuff to the image for me All i did was ./redpill_tool_chain.sh build apollolake-xxx and then ./redpill_tool_chain.sh auto apollolake-xxx Am i doing something wrong?
  18. I'm running the same CPU but with a different mainboard and everything works Which NIC are you running? Onboard or a separate one?
  19. Hello, I've been running DSM without any issues for the last couple of weeks. I have a i3-10100F paired with a B460M Steel Legend and a Intel 82574L NIC ( couldn't get the onboard NIC working ) I've been using jun 1.03b loader with DS3617xs with the following version 6.2.3 I have a ds-30104-1/88se9230 SATA PCIe card aswell and it works without any issues whatsoever. Now i tried converting to a 918+ Image, but I couldn't get it to work with a drive plugged to the SATA card The issue i have is the following: 918+ boots without any issues without the SATA card plugged in. 918+ boots without any issues with the SATA card plugged in but no drives connected to it. 918+ doesn't boot with a drive connected to the SATA card. What I've done so far: Tried updating the ds-30104-1 firmware using MS-DOS ( found a very old thread about it ) -> still doesn't work What I haven't tried: Using any extra.lzma files Messing with the grub.config file since I'm kinda new to this whole stuff. Any help would be appreciated
  20. RESULT - SUCCESSFUL Loader version and type: 1.03b & DS3617xs DSM version in use (including critical update): DSM 6.2.3-25426 Update 3 Using custom modules/ramdisk? If yes which one?: No Bare Metal Hardware details: Motherboard - ASROCK b460m Steel Legend CPU - Intel I3 10100f RAM - 2x4GB DDR4 RAM NIC - Intel 82574l (internal Nic wouldn't work, even with extra.lzma)
×
×
  • Create New...