Selfmade RuLeZ

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Selfmade RuLeZ

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yeah, I think the Dev Guys from Synology are also reading this topic. Can‘t wait to see what they build next to prevent NVMe Usage
  2. My mistake, this is only available for the Apollolake and Avoton CPUs, so I think this is only valid for the DS918+ loader
  3. You have to look, if your card or usb device is marked as supported in the wiki: https://linuxtv.org/wiki/index.php/Hardware_device_information If you don‘t find your device, you have to figure out which demodulator and tuners your card has and find out if these will be supported in the linux kernel. You have to tweak the kernel specific settings in the tutorial to compile it for the DS3615xs Loader. Good Luck!
  4. I just wanna share my found on GitHub. Successfully compiled WinTV DualHD on official Synology DS918+ https://github.com/th0ma7/synology
  5. If it‘s a driver thing, then there‘s no chance to make it working (without the right/compatible hardware). The problem is, the nvme driver is kernelbuild, that means, there‘s no additional module that you can replace like the ethernet driver.
  6. Mac Numbers are octal and Synology added after the first Mac +1. So your mac3 und mac4 should be ..378A and ..378B and not 9A and 9B as mentioned before
  7. Hi, Your tutorial is nice, just had to tweak some things to get it working with DS918+. Building the driver was no problem, but when I want to load the module it throws the knowing pic_disable_link_state(_locked) error. Leaving this lines commented out throws me kernel panics. Does someone know how to solve this issue? Thanks a lot!
  8. I‘ve tried and I failed @ddogg777 could you give it a try and post your lspci output?
  9. It’s getting silent here. I‘ve ordered a NVME to PCIe Card. It‘ll arrive in a few days. I‘ll report if it works
  10. Just a little update: It is a driver issue, when I run "nvme smart-log-add /dev/nvme0", it throws me "NVMe Status:INVALID_LOG_PAGE(2109)". Can anybody with an 918+ and an NVMe Card run this command to show what's the output? Or @flyride, can you run this command with your ESXi Setup?
  11. Hi, I don't want to use DSM behind ESXi, so I have to search for the issue My Setup: Loader 1.04b with DSM 6.2.1-23824U4 i3-8100 AS-Rock H370M-ITX Samsung 960 EVO NVMe Disk What I've found: I think it's an driver or smartctl issue. My scemd.log (in /var/log) is full with this crap: 2019-02-25T16:49:58+01:00 *** scemd: disk_temperature_update.c:52 Can't find the Disk Node whose path is /dev/nvme0n1 2019-02-25T16:49:58+01:00 *** scemd: nvme_dev_port_check.c:16 Failed to get slot informtion of nvme0n1 2019-02-25T16:49:58+01:00 *** scemd: nvme_dev_port_check.c:16 Failed to get slot informtion of nvme0n1 2019-02-25T16:49:59+01:00 *** scemd: nvme_dev_port_check.c:16 Failed to get slot informtion of nvme0n1 2019-02-25T16:49:59+01:00 *** scemd: SYSTEM: Last message 'nvme_dev_port_check.' repeated 6 times, suppressed by syslog-ng on *** So for me, it looks like that DSM want to read the temperature with the smart-parameters. That's point number two: root@***:/var/log# smartctl -a /dev/nvme0n1 smartctl 6.5 (build date Oct 26 2018) [x86_64-linux-4.4.59+] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read NVMe Identify Controller failed: NVMe Status 0x200b Same error with smartctl -x ... I hope someone can use this to determine the error Edit: root@***:/var/log# nvme list Node SN Model Namespace Usage Format FW Rev ---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- -------- /dev/nvme0n1 S3X4NB0K210754P Samsung SSD 960 EVO 500GB 1 7.97 GB / 500.11 GB 512 B + 0 B 3B7QCXE7 NVMe list works like a charm! Edit 2: It's bumping failures into the NVMe disk: ................. Entry[ 0] ................. error_count : 1 sqid : 0 cmdid : 0x1 status_field : 0x4016(INVALID_NS) parm_err_loc : 0x4 lba : 0 nsid : 0xffffffff vs : 0 ................. Entry[ 1] ................. error_count : 0 sqid : 0 cmdid : 0x1 status_field : 0x4016(INVALID_NS) parm_err_loc : 0x4 lba : 0 nsid : 0x1 vs : 0 All the best from Germany! SR