synoxpe
-
Posts
105 -
Joined
-
Last visited
Posts posted by synoxpe
-
-
Oh so this is SHR1, 5 disks. No LSI SAS controllers, but a JMB 585 5x SATA to PCIe (M.2) adapter used to connect the drives. The complete PCI controller hosting the JMicron card is passed through to the DSM VM from Proxmox.
It's a "production" system. And the HDD hibernation was always enabled. Of late (since last weekend) I started seeing these error messages. I've turned off the hibernation completely to avoid the errors, but that beats the purpose of hibernation in the first place.
-
On 6/29/2022 at 6:47 PM, flyride said:
Most people are posting here:
Done:
Thanks!
-
I'm getting the following error messages from dmesg everytime DSM puts the HDDs to hibernation. I'm running ds918+ Redpill Tinycore DSM 7.0.1-42218 Update 2. Tips?
kern :warn : [Mon Jun 27 13:02:38 2022] No such hdd enable pin. Index: 5 kern :warn : [Mon Jun 27 13:02:38 2022] ------------[ cut here ]------------ kern :warn : [Mon Jun 27 13:02:38 2022] WARNING: CPU: 1 PID: 4086 at drivers/ata/libata-core.c:453 SYNO_CTRL_HDD_POWERON+0x4f/0x60() kern :warn : [Mon Jun 27 13:02:38 2022] Modules linked in: cmac cifs tun nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE xt_REDIRECT nf_nat_masquerade_ipv4 xt_nat iptable_nat nf_nat_ipv4 nf_nat_redirect nf_nat xt_recent xt_iprange xt_limit xt_state xt_tcpudp xt_multiport xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_filter ip_tables x_tables fuse 8021q vfat fat udf isofs loop vhost_scsi(O) vhost(O) tcm_loop(O) iscsi_target_mod(O) target_core_user(O) target_core_ep(O) target_core_multi_file(O) target_core_file(O) target_core_iblock(O) target_core_mod(O) syno_extent_pool(PO) rodsp_ep(O) synoacl_vfs(PO) raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx nfsd btrfs ecryptfs zstd_decompress zstd_compress xxhash xor raid6_pq lockd grace rpcsec_gss_krb5 auth_rpcgss sunrpc aesni_intel kern :warn : [Mon Jun 27 13:02:38 2022] glue_helper lrw gf128mul ablk_helper apollolake_synobios(PO) hid_generic usbhid hid usblp i915 drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cfbfillrect cfbcopyarea cfbimgblt drm drm_panel_orientation_quirks iosf_mbi fb fbdev video backlight button uhci_hcd ehci_pci ehci_hcd r8168(O) i2c_algo_bit zram igb(O) e1000e(O) sg dm_snapshot dm_bufio crc_itu_t crc_ccitt psnap p8022 llc hfsplus md4 hmac sit tunnel4 ipv6 flashcache_syno(O) flashcache(O) syno_flashcache_control(O) dm_mod arc4 crc32c_intel cryptd sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance processor cpufreq_stats vxlan ip6_udp_tunnel udp_tunnel ip_tunnel etxhci_hcd virtio_scsi(OE) virtio_net(OE) virtio_blk(OE) virtio_pci(OE) virtio_mmio(OE) virtio_ring(OE) kern :warn : [Mon Jun 27 13:02:38 2022] virtio(OE) usb_storage xhci_pci xhci_hcd usbcore usb_common [last unloaded: apollolake_synobios] kern :warn : [Mon Jun 27 13:02:38 2022] CPU: 1 PID: 4086 Comm: scsi_eh_10 Tainted: P W OE 4.4.180+ #42218 kern :warn : [Mon Jun 27 13:02:38 2022] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 kern :warn : [Mon Jun 27 13:02:38 2022] 0000000000000000 ffff88017830bcb0 ffffffff812ef89d 0000000000000009 kern :warn : [Mon Jun 27 13:02:38 2022] 0000000000000000 ffff88017830bce8 ffffffff8105255f 0000000000000bb8 kern :warn : [Mon Jun 27 13:02:38 2022] 0000000000000000 0000000000000001 ffff880178978000 0000000000000000 kern :warn : [Mon Jun 27 13:02:38 2022] Call Trace: kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff812ef89d>] dump_stack+0x4d/0x70 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff8105255f>] warn_slowpath_common+0x7f/0xb0 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff81052646>] warn_slowpath_null+0x16/0x20 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff8141dcdf>] SYNO_CTRL_HDD_POWERON+0x4f/0x60 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff8142e825>] syno_libata_port_power_ctl+0xc5/0x1a0 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff8142f7c7>] syno_libata_set_deep_sleep+0x2b7/0x9c0 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff81436ee3>] ata_scsi_port_error_handler+0x133/0x1a30 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff8106b0fe>] ? cancel_delayed_work_sync+0xe/0x10 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff81432868>] ? ata_scsi_cmd_error_handler+0x118/0x190 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff8143887b>] ata_scsi_error+0x9b/0xe0 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff813f86f5>] scsi_error_handler+0xa5/0x530 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff81575bcf>] ? __schedule+0x2ef/0x820 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff813f8650>] ? scsi_eh_get_sense+0x170/0x170 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff810700f5>] kthread+0xd5/0xf0 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff81070020>] ? kthread_worker_fn+0x160/0x160 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff81579fef>] ret_from_fork+0x3f/0x80 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff81070020>] ? kthread_worker_fn+0x160/0x160 kern :warn : [Mon Jun 27 13:02:39 2022] ---[ end trace 4d3f8f657722e7be ]--- kern :err : [Mon Jun 27 13:02:42 2022] ata11: wake up successful, the reset fail can be ignored kern :err : [Mon Jun 27 13:02:45 2022] ata10: wake up from deepsleep, reset link now kern :err : [Mon Jun 27 13:02:48 2022] ata10: wake up successful, the reset fail can be ignore
-
On 6/27/2022 at 8:33 PM, flyride said:
Post a new support request in the DSM Installation forum, and include output from the installation scripts.
Which thread please? I see only 6.x. My question is about DSM 7
-
After 100 days of issueless operations (yayyy!!), I saw these from dmesg in quick succession from my ds918+ running DSM 7.0.1-42218 Update 2 on Proxmox:
kern :warn : [Mon Jun 27 13:02:38 2022] No such hdd enable pin. Index: 5 kern :warn : [Mon Jun 27 13:02:38 2022] ------------[ cut here ]------------ kern :warn : [Mon Jun 27 13:02:38 2022] WARNING: CPU: 1 PID: 4086 at drivers/ata/libata-core.c:453 SYNO_CTRL_HDD_POWERON+0x4f/0x60() kern :warn : [Mon Jun 27 13:02:38 2022] Modules linked in: cmac cifs tun nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE xt_REDIRECT nf_nat_masquerade_ipv4 xt_nat iptable_nat nf_nat_ipv4 nf_nat_redirect nf_nat xt_recent xt_iprange xt_limit xt_state xt_tcpudp xt_multiport xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_filter ip_tables x_tables fuse 8021q vfat fat udf isofs loop vhost_scsi(O) vhost(O) tcm_loop(O) iscsi_target_mod(O) target_core_user(O) target_core_ep(O) target_core_multi_file(O) target_core_file(O) target_core_iblock(O) target_core_mod(O) syno_extent_pool(PO) rodsp_ep(O) synoacl_vfs(PO) raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx nfsd btrfs ecryptfs zstd_decompress zstd_compress xxhash xor raid6_pq lockd grace rpcsec_gss_krb5 auth_rpcgss sunrpc aesni_intel kern :warn : [Mon Jun 27 13:02:38 2022] glue_helper lrw gf128mul ablk_helper apollolake_synobios(PO) hid_generic usbhid hid usblp i915 drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cfbfillrect cfbcopyarea cfbimgblt drm drm_panel_orientation_quirks iosf_mbi fb fbdev video backlight button uhci_hcd ehci_pci ehci_hcd r8168(O) i2c_algo_bit zram igb(O) e1000e(O) sg dm_snapshot dm_bufio crc_itu_t crc_ccitt psnap p8022 llc hfsplus md4 hmac sit tunnel4 ipv6 flashcache_syno(O) flashcache(O) syno_flashcache_control(O) dm_mod arc4 crc32c_intel cryptd sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance processor cpufreq_stats vxlan ip6_udp_tunnel udp_tunnel ip_tunnel etxhci_hcd virtio_scsi(OE) virtio_net(OE) virtio_blk(OE) virtio_pci(OE) virtio_mmio(OE) virtio_ring(OE) kern :warn : [Mon Jun 27 13:02:38 2022] virtio(OE) usb_storage xhci_pci xhci_hcd usbcore usb_common [last unloaded: apollolake_synobios] kern :warn : [Mon Jun 27 13:02:38 2022] CPU: 1 PID: 4086 Comm: scsi_eh_10 Tainted: P W OE 4.4.180+ #42218 kern :warn : [Mon Jun 27 13:02:38 2022] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 kern :warn : [Mon Jun 27 13:02:38 2022] 0000000000000000 ffff88017830bcb0 ffffffff812ef89d 0000000000000009 kern :warn : [Mon Jun 27 13:02:38 2022] 0000000000000000 ffff88017830bce8 ffffffff8105255f 0000000000000bb8 kern :warn : [Mon Jun 27 13:02:38 2022] 0000000000000000 0000000000000001 ffff880178978000 0000000000000000 kern :warn : [Mon Jun 27 13:02:38 2022] Call Trace: kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff812ef89d>] dump_stack+0x4d/0x70 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff8105255f>] warn_slowpath_common+0x7f/0xb0 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff81052646>] warn_slowpath_null+0x16/0x20 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff8141dcdf>] SYNO_CTRL_HDD_POWERON+0x4f/0x60 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff8142e825>] syno_libata_port_power_ctl+0xc5/0x1a0 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff8142f7c7>] syno_libata_set_deep_sleep+0x2b7/0x9c0 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff81436ee3>] ata_scsi_port_error_handler+0x133/0x1a30 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff8106b0fe>] ? cancel_delayed_work_sync+0xe/0x10 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff81432868>] ? ata_scsi_cmd_error_handler+0x118/0x190 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff8143887b>] ata_scsi_error+0x9b/0xe0 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff813f86f5>] scsi_error_handler+0xa5/0x530 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff81575bcf>] ? __schedule+0x2ef/0x820 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff813f8650>] ? scsi_eh_get_sense+0x170/0x170 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff810700f5>] kthread+0xd5/0xf0 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff81070020>] ? kthread_worker_fn+0x160/0x160 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff81579fef>] ret_from_fork+0x3f/0x80 kern :warn : [Mon Jun 27 13:02:38 2022] [<ffffffff81070020>] ? kthread_worker_fn+0x160/0x160 kern :warn : [Mon Jun 27 13:02:39 2022] ---[ end trace 4d3f8f657722e7be ]--- kern :err : [Mon Jun 27 13:02:42 2022] ata11: wake up successful, the reset fail can be ignored kern :err : [Mon Jun 27 13:02:45 2022] ata10: wake up from deepsleep, reset link now kern :err : [Mon Jun 27 13:02:48 2022] ata10: wake up successful, the reset fail can be ignore
-
Any chance this will have “better” GPU support in general, compared to the other platforms? I only need Quicksync from Intel frost canyon…
-
7 hours ago, FredT85 said:
I have this Ds3622xs+ on a baremetal (old cpu intel quad 9550 with 8Gb RAM) since 2 days. No prob with windows 7 x64 VM (no uefi bios), no prob with docker.
Something must be wrong with my install then. Blinking cursor is where I’m stuck. For Ubuntu I get a funny logo at the bottom of the screen and things don’t proceed further.
-
@IG-88 I bricked a (test) ds918+ bare metal installation on Intel Nuc 10 frost canyon using the i915.ko module from the links you shared earlier.
Do we need to recompile the driver for this chipset in order to make it work?
-
On 3/9/2022 at 11:11 AM, synoxpe said:
Anyone got the Virtual Machine Manager to boot a Windows VM on ds3622xs+? I'm on a bare metal installation and when I power the VM on, I see the Windows logo appearing very shortly followed by a blank screen with a blinking cursor. Nothing happens further.
@yanjun perhaps you've tested this?
Edit: system is too slow and I was being impatient. Working now
Nopes, the blinking cursor is back. Not able to boot from either windows or linux isos
-
Anyone got the Virtual Machine Manager to boot a Windows VM on ds3622xs+? I'm on a bare metal installation and when I power the VM on, I see the Windows logo appearing very shortly followed by a blank screen with a blinking cursor. Nothing happens further. I'm using compatibility mode CPU and booting from the installation ISO.
-
2 hours ago, Orphée said:
Yes it is.
I mean each baremetal system is different, so it works for me, you may need to adapt/fix things, as always.gotcha
-
3 hours ago, aportnov said:
Is it possible to install update 3 immediately on a working system without testing?
I got an infinite recovery loop. So I'd avoid for now till it's fixed.
-
-
12 hours ago, Orphée said:
Then for baremetal it should work.
The screenshot *is* from a baremetal installation right? What do you mean then?
-
@RedwinX do you have a write up of how you installed the ds920+ and i915 drivers to get hw transcoding to work?
-
6 hours ago, smilenkovski said:
I understand that, I've visited github and, of course , understand nothing. Can You, please , explain me what to do after modifying .dtb file and using ./redpill_tool_chain.sh auto geminilake-7.0.1-42218 to continue. I don't get it that. Where is the image file and how to make usb bootloader.
The image is in the ./image folder, as per the docs. You need to flash it to a usb drive using e.g. balena etcher or rufus.
The github repo is in chinese and I used Google translate to get an english version. The actual English README gives a 404 error. Guess it's private so someone with an active Github account might want to raise an issue.
-
@pocopico any plans to add the ds920p in tinycore? The success stories with the iGPU are promising
-
On 3/7/2022 at 10:51 AM, yanjun said:
The only reason you can't see the smart information is that the driver is too new and the device is too old, mpt3sas41.0 is prepared for LSI 9400/9500, I also tried to extract mpt3sas21.0 (from LSI 9207) official driver page, unfortunately It's that he can't mix with the hard disk of the sata controller to form a raid1. Probably this version of mpt3sas is too old for the 4.4.180 kernel. This means that your system partition is always in a state that needs to be repaired, and once you repair it, your dsm will directly show that you need to reinstall it. My LSI9400-16I on 3622xs+ has no issue with missing smart info. So if you guys want to try to solve the smart information problem with LSI 92xx cards. My suggestion is to try to find the driver of the LSI 9300 series card from the official boradcom, and try to compile it between 21.0 and 41.0. Maybe a certain version can satisfy both the smart information and the two conditions of creating a system partition.
@yanjun I doubt as the same disks do provide that info on DS918+. noop generally means no-operation. So I guess the "ATA_CMD_ID_ATA" command is not implemented in the red pill shim. Could be a bug?
-
1 hour ago, Orphée said:
Does your plex transcode ?
Because if CPU temp thresold happens, you CPU must run high...
Check with "top" commandYes it does. But DSM shows max CPU usage just to be 45%, guess because of the throttling…
how to get rid of that?
-
On 3/5/2022 at 12:09 AM, IG-88 said:
i915_universal_918p_DSM7.zip
@IG-88 trying to get the intel iGPU running on a bare metal install of ds3622xsp (on Intel NUC 10 having Comet Lake UHD). Where can I get i915 driver that you had linked earlier I think?
synoadm@ds3622xsp:/$ lspci -nnq 0000:00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b51] 0000:00:02.0 VGA compatible controller [0300]: Intel Corporation Comet Lake UHD Graphics [8086:9bca] (rev 04)
-
Anyway to get rid of this while Plex is running? ds3622xsp running on bare metal Intel i7:
[ 671.949626] CPU9: Core temperature above threshold, cpu clock throttled (total events = 4642) [ 671.949626] CPU3: Core temperature above threshold, cpu clock throttled (total events = 4642) [ 671.949626] CPU2: Core temperature above threshold, cpu clock throttled (total events = 8533) [ 671.949626] CPU8: Core temperature above threshold, cpu clock throttled (total events = 8533) [ 671.949627] CPU1: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949627] CPU6: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949627] CPU7: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949627] CPU5: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949628] CPU0: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949628] CPU4: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949628] CPU11: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949628] CPU10: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949628] CPU3: Package temperature above threshold, cpu clock throttled (total events = 19575) [ 671.949629] CPU2: Package temperature above threshold, cpu clock throttled (total events = 19574) [ 671.949629] CPU8: Package temperature above threshold, cpu clock throttled (total events = 19575)
-
Anyone got the Virtual Machine Manager to boot a Windows VM on ds3622xs+? I'm on a bare metal installation and when I power the VM on, I see the Windows logo appearing very shortly followed by a blank screen with a blinking cursor. Nothing happens further.
@yanjun perhaps you've tested this?
Edit: system is too slow and I was being impatient. Working now
-
8 hours ago, BableFish said:
If you are trying to install on an ESXi server you are probably experiencing the same problem I had.
When you attach the vmdk to a new disk it defaults to an IDE port. You need to change that to a SATA port.
After I did that it worked to complete the installationExactly. I described it here:
-
7 hours ago, Tibag said:
it gets stuck on "Starting kernel with SATA boot" then nothing happens
That's normal behaviour I guess. Start Synology Assistant or hit find.synology.com to locate your DSM and to proceed with the installation.
DSM 7 | Proxmox | HDD Hibernation issue
in General Installation Questions/Discussions (non-hardware specific)
Posted
@IG-88 Thanks much for checking out on my issue. Very insightful as always 😊
So that means to get the best results I need to test hibernation on a 920+ running DSM 7.1? As there they seem to have dealt with the JMB585 issues in particular?