Jump to content
XPEnology Community

merve04

Member
  • Posts

    320
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by merve04

  1. I've attached a screenshot of the cat /proc/cmdline I have a Gigabyte B365M DS3H, Intel i5-8400, 2x 16GB Corsair ram, 2x jmicron jmb585. My server is currently occupied hosting streams but at my next availability, I can boot the usb key back up and take a picture of when the tcrp friend screen comes on. It's my understanding I do not need to do "./rploader.sh satamap" due to DVA1622 uses devicetree and sometime ago TCRP had an automated approach in finding the drives.
  2. Thanks for the response, I followed the command as you suggested, I see many lines with values. Which ones should I be paying attention too?
  3. Hi, I’m really hoping someone can point me in the right direction. I’m using a fairly dated version of TCRP 0.9 and dva1622 7.1 I really want to upgrade to latest TCRP so I can be up to date on DSM. Here are the steps I’ve taken this far. Download/write latest TCRP to usb drive Booted flash drive and performed these commands. ./rploader.sh update ./rploader.sh fullupgrade ./rploader.sh identifyusb ./rploader.sh serialgen DVA1622 realmac ./rploader.sh build dva1622-7.1.1-42962 withfriend exitcheck.sh reboot when system booted back up, the tcrp friend page came one but no IP detected. when I opened synology assistant, machine was discovered but status was not installed. When I open the IP, I get no drives detected. i shut down the machine, reinserted my previous usb key and rebooted machine, everything is back now. what am I not doing correctly here? any help is much appreciated.
  4. Hi everyone, Well didnt get much luck else where so will try here. I'm still using tinycore-redpill.v0.9.0.2 running DVA1622 DSM 7.1-42661 Update 1. What is the best approach to upgrading to latest tcrp? Thanks
  5. Hey all, I'm still rocking tinycore-redpill.v0.9.0.2 using DVA1622 DSM 7.1-42661 Update 1. What is the best approach to upgrading to latest tcrp? Thanks in advance.
  6. Quick question, when I upgraded to 7.0.1 from 6.2.3, I built a loader using tcrp 0.9.x i want to upgrade to 7.1.1, do I just boot into tcrp and do full upgrade before updating via gui? or is there a specific way of upgrading? Thanks in advance
  7. Thank you for your input on this, yes I have time to wait for a definitive answer.
  8. I much appreciate your reply on this, but once again i feel nervous about what to enter in "<yourplatform>", hence why i ask is inputing "geminilake-7.1.0-42661" the correct value for the process? Thanks again.
  9. Unfortunately I couldn’t tell y’a what exactly it does, and I’m still in the dark in the correct command procedure for applying an update to DSM. I’ve read if you don’t do it, machine goes in an infinite loop.
  10. Not sure, but I’ve seen this posted several times, I’ve used it myself when building the loader in TC. I guess I figure since dva1622 is based of Geminilake that it would be the command line to use for post update. But I’m really not sure if it’s correct as when building the loader I never used the word “geminilake” in any of the commands.
  11. For those who have update to latest version of DSM, if the following command correct? Thanks in advance ./rploader.sh update sudo ./rploader.sh postupdate geminilake-7.1.0-42661 exitcheck.sh reboot
  12. Maybe it needs legit SN/Mac for it to work with video station? Not sure, I use plex and hw transcoding is working properly fine.
  13. Did you manually update from DSM gui and run post update commands in TC? seems odd DSM says system is up to date on U1
  14. I’m assuming no as the DVA lineup does not have nvme slots natively, so nothing is programmed in the dsm software to support it.
  15. Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3 Update 3 - JUN'S LOADER v1.04b - DS918+ - Loader version and model: tinycore-redpill.v0.9.0.2 - DVA1622 - Using custom extra.lzma: NO - Installation type: BAREMETAL - Gigabyte B365 DS3H, Intel i5 8400, 32GB DDR4, 2x JMB585 PCI-e 3.0 - Additional comments: Standard install as per guides made available on this site.
  16. I've noticed that when i download stuff in sabnzbd i max out at 70MB\s but when i was on TCRP 0.8 using 918+ dsm 7.1.0 i was getting 105MB\s
  17. Sure, I use plex to decode hvec files. I don’t use photo station, video station or really any other built in dsm apps to do media viewing, that’s what client pcs are for. One draw back may be if you wanted to use hvec compatible security cameras, imo storage space is cheap in the grand scheme of things.
  18. I don't think you'll find too many folks recommending to buy a license to apply on an xpenology install, as I think you have one shot with the license so if something "bad" happens you'll be sol. I also recall reading years ago, that you need legit SN\Mac. An alternative would be looking at using DVA3221 or DVA1622 loaders which include 8 camera licenses with surveillance station by default.
  19. Happy to report this updated progress on the dva1622 loader now works on my system. Although it once again reset DSM forcing me reload all my packages and scrub my data, its a small price to pay to have all of my cameras working and plex transcoding for remote users. Many thanks to @pocopico and others who have put the time and effort into making this happen.
  20. Well i'll give up on this dva1622 dream for now, i just dont understand where it went wrong. It seemed just the drives on the jmb585 cards wouldn't load but where visible in a sense that when i did the ssh command, i could see them. I also tried the ARPL loader, i eventually got it working after tinkering in the bios, but it gave me a worse result only showing 2 hdd's. I also thought could it be the expander cards the issue as far as compatibility, well i took one card out and plunked it in another pc i got and plugged 1 hdd on it and it showed up in dsm, so i figure that rules it out. I've rebuilt a usb loader for ds918+, all drives show up and is repairing now, the down fall is i've taken a step back with my surveillance setup. hopefully the dva1622 loader can be polished a bit more to allow more hdd's in my setup.
  21. ok so i used filezilla to upload the file, check in tcrp, terminal vi dva1622.dts, everything was there, rebooted and back in dsm, still only 6 hdd's I tried removing the ",00.0" on each port of the expansion cards, no change. Could having mutliple DTS files in the directory cause an issue? I notice theres a ds1621p.dts and ds920p.dts file
  22. I'm assuming this like? /dts-v1/; / { compatible = "Synology"; model = "synology_geminilake_dva1622"; version = <0x01>; syno_spinup_group = <0x01 0x01>; syno_spinup_group_delay = <0x0b>; syno_hdd_powerup_seq = "true"; syno_cmos_reg_secure_flash = <0x66>; syno_cmos_reg_secure_boot = <0x68>; internal_slot@1 { protocol_type = "sata"; power_pin_gpio = <0x16 0x00>; detect_pin_gpio = <0x25 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:17.0"; ata_port = <0x00>; }; led_green { led_name = "syno_led0"; }; led_orange { led_name = "syno_led1"; }; }; internal_slot@2 { protocol_type = "sata"; power_pin_gpio = <0x17 0x00>; detect_pin_gpio = <0x26 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:17.0"; ata_port = <0x01>; }; led_green { led_name = "syno_led2"; }; led_orange { led_name = "syno_led3"; }; }; internal_slot@3 { protocol_type = "sata"; power_pin_gpio = <0x18 0x00>; detect_pin_gpio = <0x27 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:17.0"; ata_port = <0x02>; }; led_green { led_name = "syno_led4"; }; led_orange { led_name = "syno_led5"; }; }; internal_slot@4 { protocol_type = "sata"; power_pin_gpio = <0x19 0x00>; detect_pin_gpio = <0x28 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:17.0"; ata_port = <0x03>; }; led_green { led_name = "syno_led6"; }; led_orange { led_name = "syno_led7"; }; }; internal_slot@5 { protocol_type = "sata"; power_pin_gpio = <0x20 0x00>; detect_pin_gpio = <0x29 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:17.0"; ata_port = <0x04>; }; led_green { led_name = "syno_led8"; }; led_orange { led_name = "syno_led9"; }; }; internal_slot@6 { protocol_type = "sata"; power_pin_gpio = <0x21 0x00>; detect_pin_gpio = <0x30 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:17.0"; ata_port = <0x05>; }; led_green { led_name = "syno_led10"; }; led_orange { led_name = "syno_led11"; }; }; internal_slot@7 { protocol_type = "sata"; power_pin_gpio = <0x22 0x00>; detect_pin_gpio = <0x31 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:01.0,00.0"; ata_port = <0x00>; }; led_green { led_name = "syno_led12"; }; led_orange { led_name = "syno_led13"; }; }; internal_slot@8 { protocol_type = "sata"; power_pin_gpio = <0x23 0x00>; detect_pin_gpio = <0x32 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:01.0,00.0"; ata_port = <0x01>; }; led_green { led_name = "syno_led14"; }; led_orange { led_name = "syno_led15"; }; }; internal_slot@9 { protocol_type = "sata"; power_pin_gpio = <0x24 0x00>; detect_pin_gpio = <0x33 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:01.0,00.0"; ata_port = <0x02>; }; led_green { led_name = "syno_led16"; }; led_orange { led_name = "syno_led17"; }; }; internal_slot@10 { protocol_type = "sata"; power_pin_gpio = <0x25 0x00>; detect_pin_gpio = <0x34 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:01.0,00.0"; ata_port = <0x03>; }; led_green { led_name = "syno_led18"; }; led_orange { led_name = "syno_led19"; }; }; internal_slot@11 { protocol_type = "sata"; power_pin_gpio = <0x35 0x00>; detect_pin_gpio = <0x36 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:01.0,00.0"; ata_port = <0x04>; }; led_green { led_name = "syno_led20"; }; led_orange { led_name = "syno_led21"; }; }; internal_slot@12 { protocol_type = "sata"; power_pin_gpio = <0x37 0x00>; detect_pin_gpio = <0x38 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:1b.4,00.0"; ata_port = <0x00>; }; led_green { led_name = "syno_led22"; }; led_orange { led_name = "syno_led23"; }; }; internal_slot@13 { protocol_type = "sata"; power_pin_gpio = <0x39 0x00>; detect_pin_gpio = <0x40 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:1b.4,00.0"; ata_port = <0x01>; }; led_green { led_name = "syno_led24"; }; led_orange { led_name = "syno_led25"; }; }; internal_slot@14 { protocol_type = "sata"; power_pin_gpio = <0x41 0x00>; detect_pin_gpio = <0x42 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:1b.4,00.0"; ata_port = <0x02>; }; led_green { led_name = "syno_led26"; }; led_orange { led_name = "syno_led27"; }; }; internal_slot@15 { protocol_type = "sata"; power_pin_gpio = <0x43 0x00>; detect_pin_gpio = <0x44 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:1b.4,00.0"; ata_port = <0x03>; }; led_green { led_name = "syno_led28"; }; led_orange { led_name = "syno_led29"; }; }; internal_slot@16 { protocol_type = "sata"; power_pin_gpio = <0x45 0x00>; detect_pin_gpio = <0x46 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:1b.4,00.0"; ata_port = <0x04>; }; led_green { led_name = "syno_led30"; }; led_orange { led_name = "syno_led31"; }; }; usb_slot@1 { vbus { syno_gpio = <0x1d 0x01>; }; usb2 { usb_port = "1-1"; }; usb3 { usb_port = "2-1"; }; }; usb_slot@2 { vbus { syno_gpio = <0x1e 0x01>; }; usb2 { usb_port = "1-2"; }; usb3 { usb_port = "2-2"; }; }; };
  23. I also notice that the pci address differs from when I ssh vs building key
  24. I'm sorry, but when i got in tcrp, terminal, i type vi dva1622.dts and all i get is ~ going down the length of screen followed by dva1622.dts 1/1 100%
×
×
  • Create New...