Jump to content
XPEnology Community

gadreel

Members
  • Posts

    285
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by gadreel

  1. @Kyar incase you have any issues with 440fx another way to make the ports to start from 1 it's to change the SataMap and IDMap to something like this: SataPortMap: 16 SataIdxMap: 00 I do not know what that combination means but basically it will make the 1st SATA controller disappear and the 1st Sata Drive will start from position 1 but from the 2nd Sata Controller...
  2. I have an LSI SAS 9207-8i and I tried to install ARPL with DS2422+ (AMD 3900X) and no drives were detected. Looking at the modules, geminilake and v1000 do not contain the mpt3sas.ko therefore you cannot use LSI on these 2?
  3. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1-42661 - Loader version and model: Automated Redpill Loader 0.4 alpha 6 DS918+ - Using custom extra.lzma: NO - Installation type: VM - Unraid, AMD 5950X - Additional comments: Migrated from TC to ARPL 0.4 alpha 6
  4. @fbelavenuto Now it works I see eth0 in the logs. Found it also in the Synology Assistant. Any idea what happened so I do not do it again? Edit: Migrated from TC to ARPL 7.0.1 42661 and then updated successfully to DSM 7.1.1-42962
  5. OK. All these are from the latest build/image. Shall I select the 9p or it does not matter if I select it or not in the menu?
  6. @fbelavenuto it does not work on my Unraid KVM. It's not detected in synology assistant. I tried also the e1000, also does not work. I think I need the virtio drivers. I believe the virtio-net drivers are not loaded therefore it does not work. That v9p drivers does not work for my case. Unless I am doing something wrong...
  7. @fbelavenutothanks for the reply. Modules already exist you mean they are already inside the image I downloaded from the repo? Then ARPL is smart enough to detect what I need? So, the one I see in "Add an addon" or in "Show user addons" it's what it's already detected? And last question if you can kindly answer if I want to migrate from TinyCore to ARPL is there a specific procedure or I just build a new loader and it should work.
  8. Hi everyone, I have been using TinyCore before and I want to try ARPL but everything is very confusing. I select DS918+ and if I want to add additional addons like virtio or ixgbe etc... when I enter the url I get "File format not recognized!"... what is going on?
  9. There is but you do not want to take that road. You have to play with the disk mapping which most of the time is trial and error moving the disks around. I recommend you to leave it as is...
  10. In DSM 7.1 the error was caused because Hper Backup for LUN Drives (not sure if it's the same for DATA) does NOT like spaces on the name of the destination shared folder. I had it like this "LUN Backups" and changing it to this "LUNBackups" it worked.
  11. @pistachio No, it's not a problem and there is nothing to worry about it. I have the same "issue". I have 6 drives in total.
  12. Hello everyone, I have a 3 Hyper Back tasks. 2 for backing up my LUN drives and 1 for backing up my Shared Folders. I do not know since when, but the LUN Backup tasks stopped working a long time ago without even a warning. I just realised it yesterday. When I am trying to back them up from Red Pill DS918+ to a Genuine Synology DS720+ I am getting an error message (after completing the backup) "Unknown Error 220". It completes the task but nothing is written in the destination server (720+). I tried permissions, deleting the task etc... and nothing works. The task for backing up the shared folders has no issue but the 2 LUN tasks do not work no matter what I try. What is left is delete the package and reinstall it... Any ideas what might causing this issue?
  13. @pocopico I updated my DS918+ to update-4 but when I ran the postupdate command instead of "The new smallupdate version will be : 7.1-42661-4" I got this "The new smallupdate version will be : 7.1-42661-3" I pressed yes and everything worked well and in DSM I can see "DSM 7.1-42661 Update 4" Is that normal?
  14. I have a dual port Intel X550 but my DS918+ it's installed on a VM therefore I am passing through only one port.
  15. Because since Jun's Loader I was always using USB and never had an issue with it therefore I am still using that approach. Even my current DS918+ production is set to USB also. Is there an issue with it? I am testing ARPL my CPU is AMD Ryzen 3900X, I do not have any issues with the DS918+. Maybe is better to install DS2422 for my CPU and also I want to be able to use NVME. I do not think you can do that on DS918+. It's working now but I do not know what happened. I will try to build the loader again later today to find out why it failed in the first place...
  16. EDIT: I built the loader with 1 disk without messing a lot with the ARPL configuration and it worked... Hmmmm will investigate more. It's a VM. I have UNRAID which uses KVM. This is what I get with fdisk -l. I am just testing, I already have a working DS918+ with TCRP... but I am testing 2422+ with ARPL. The image is always set as USB (as on TCRP) and a single Virtual Disk (SATA).
  17. Trying to build DS3622xs+ or DS2422+ and always stops at 40%/55% during installation. In the console I see the following. SynologyNAS login: [ 46.201634] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 46.206037] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 47.502403] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 47.506447] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 47.538204] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 47.542126] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 47.556501] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 47.559144] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 48.189653] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 48.203373] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
  18. https://kb.synology.com/en-id/DSM/tutorial/How_can_I_update_to_the_latest_DSM_version_from_an_older_version You are long way to DSM 7. The link above contains information about the upgrade path. Read it carefully. The main issue is that every time you might need to load different loaders and that it's troublesome. If I was in your position I will find a way to backup my stuff and make a clean install to DSM 7.1 3622xs+
  19. Your are correct about the number of drives, it's displayed based on the model. In DSM 6 you could install as many drives you like and they were visible. Now they changed it based on the model. It does not matter though, even if you have a DS918+ which technically has 4 drives you can have maybe upto 16 drives. For the PCIE, I know for sure in order to have NVME cache you need to change a file and add the PCI addresses of your NVMEs. I do not know if you can do the same thing for any type of PCIE card. That will be very interesting. As for the expansion unit I never read a post about them, I do not know if you have an original expansion unit and an e-sata if you connect it will be visible...
  20. I think the correct is ./rploader.sh postupdate apollolake-7.1.0-42661 Yes that should be all.
  21. By the way important. Make sure you have the latest tinycore. You might need to also run these commands before postupdate ./rploader.sh update ./rploader.sh fullupgrade
  22. I believe there is no need to install Update 1,2. If you install Update 3 should include the previous updates. You go to the GUI and you install manually the Update 3, when the Syno reboots go back to TinyCore and just run the following command: ./rploader.sh postupdate {WITH YOUR MODEL}
×
×
  • Create New...