synoxpe
-
Posts
105 -
Joined
-
Last visited
Posts posted by synoxpe
-
-
2 hours ago, Orphée said:
It was working for me with Jun's loader.
I did not try with RP DS3615xs loader.
I could try with a spare disk... but it works currently at Proxmox level... so it is fine like this.
I think there may be an issue with mpt3sas drivers and some LSI cards.
@Orphée OK so these logs could explain why I'm not able to see SMART info on the first screen as well on the ds3622xs:
[ 944.091588] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 984.973386] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 984.993811] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 985.555614] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 986.706584] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 986.717650] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 986.728391] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 986.740350] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 987.789612] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 987.802854] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 987.810408] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 987.817559] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 987.824668] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 987.831894] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 988.439431] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 993.939070] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 999.650491] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
-
15 minutes ago, synoxpe said:
Thanks for pointing this out @Dvalin21 but can't see a solution described there?
I'm already using SATA boot.
OK an update and hope it helps others facing the 55% stall issue:
I was using IDE. Should be SATA! Super naive but that's how we miss the obvious ;)
Internet connectivity wasn't causing it.
-
1
-
-
38 minutes ago, Dvalin21 said:
Everyone having the 55% install error, take a look at this post
Thanks for pointing this out @Dvalin21 but can't see a solution described there?
I'm already using SATA boot.
-
1
-
-
The 55% installation stall of ds3622xs: do we need to disconnect from internet during installation? I read it wasn't required anymore but it seems be messing up with my install.
-
2 minutes ago, Orphée said:
Check my Edit. I have the same working info at this menu level.
But summary is empty. So I'm not sure DSM will actually catch disk error when it will come.
Seems like it's working for me...
-
11 minutes ago, Orphée said:
In DSM I only have partial SMART data working.
At disk level, click on smart, and the 4 lines are only : -
No temp, no error number...
Then in advanced/detailed, there, yes, SMART data appears.
Both with ESXi and Proxmox. Using LSI 9207-8i.I see. Could be the controller then as in my case I'm getting complete SMART info on Proxmox by passing through the JMB 585 PCI SATA controller, where my disks are connected to. ESXi still isn't working for me (stuck at 55% as reported above), but that's another story...
-
11 hours ago, Orphée said:
So as on my installation, currently, I can't trust Smart DATA with LSI passthrough, I decided to give up PCI passthrough and only map disk on proxmox level
Keen to hear why not? On the contrary I've blacklisted the ahci driver at PVE level so that it doesn't fiddle with the disks on booting up and DSM gets a full PCI passthrough.
-
18 minutes ago, Orphée said:
No need to check pid/vid on esxi/proxmox.
But use SATA at boot menuYes I chose SATA. Installation is failing at 55%. I also can’t see any error messages in serial log during the failure.
-
5 minutes ago, Dvalin21 said:
The only thing different (besides the serial, Mac, and pid/vid, is I left the satamap and diskid at default. 58 for Sata and 0A00 for diskid. Sorry I don't remember, but what is your hardware setup?
Intel NUC 10 with the M2 slot hosting a JMB585 PCIe SATA bridge having 5 SATA ports.
Works fine on Proxmox but wasn’t able to make DSM find disks on baremetal -
Just now, Dvalin21 said:
I didn't get that, though I installed on baremetal.
Thanks for your prompt reply. On bare metal the DSM installation can’t find any drives. Can you please share the user_config.json?
-
1
-
-
Anyone else getting installation failure of ds3622xs at 55%? I’m on ESXi 7
@Dvalin21 were you able to proceed?
-
Trying to install ds3622xs on ESXi 7. DSM installation fails at 55% complaining about corrupted file after I upload the .pat file. I’ve tried both with USB and SATA boot and both have the same result.
-
Just now, IG-88 said:
that depends on how tc work (have not check that) but you can edit the resulting grub.cfg after tc is finished configuring
Ack! will do.
-
5 minutes ago, IG-88 said:
the generic's are here
http://redsymbol.net/linux-kernel-boot-parameters/4.4/
for syno's specifics you need to check syno's kernel and documentation (if available)
Thanks again!
My context is redpill tinycore loader's user_config.json. Is it possible to pass the parameter there as I've specified above?
For now I just used this from the DSM command prompt:
root@ds918p:~# echo 0 > /proc/sys/kernel/nmi_watchdog root@ds918p:~# -
39 minutes ago, Orphée said:
I understand, but still, other will come and see your settings and will copy/paste it thinking it is how it works.
I know that on proxmox qc35 the first controller is not used at all, but ... for a correct mindset, you should not set 0000., better remove it or set it as 0A00
Ack!
How about passing the nmi_watchdog parameter? Is this a correct way?
-
22 minutes ago, Orphée said:
Stop playing with random values...
DiskIdxMap 0000 make no sense at all...
Working for me perfectly. The first digit in SataPortMap is apparently incorrectly reported in a Proxmox environment where I'm running my stuff. So effectively the second controller starts from 0.
That's not my question here anyway. I just pasted the config to check if that's the way to disable the nmi_watchdog kernel parameter, which is crashing my DSM if enabled causing Kernel panic.
-
1
-
-
2 hours ago, synoxpe said:
where can I make the change?
@WiteWulf Something like this in user_config.json?
{ "extra_cmdline": { "pid": "0x0001", "vid": "0x46f4", "sn": "xxx", "mac1": "xxx", "SataPortMap": "15", "DiskIdxMap": "0000”, “nmi_watchdog”: “0” }, "synoinfo": { "internalportcfg" : "0xffff", "maxdisks" : "16" }, "ramdisk_copy": { } }-
1
-
-
On 3/3/2022 at 5:47 PM, WiteWulf said:
Looks like you're running into the kernel panic issue we spent quite a while investigating last year:
https://github.com/RedPill-TTG/redpill-lkm/issues/21
The workaround I found was to boot with NMI watchdog disabled, then turn it on manually after booting.
@WiteWulf where can I make the change? I'm running DSM virtualized on Proxmox using @pocopico tinycore loader.
-
2 hours ago, IG-88 said:
accourding to intel spec its two sata ports (one on m.2 and one as sata connector) and if its more then two then its 4 or 6, never seen a uneven number on a intel chipset
the 5 disks looks ok as its jmb585 and that has 5 ports
that one is a two digit hex for every controller, that would imply 1st one starts as sda, 2nd as sdf (a=0, b=1, ...
in theory (from the hardware) it would be
SataPortMap=25
DiskIdxMap=0002
00 and 01 are the two ports of the onboard, 02, 03, 04, 05, 06 are the 5 ports of the jmb585
if you want the jmb to to be the 1st controller in counting it would be
SataPortMap=25
DiskIdxMap=0500
being 00-04 the five ports of the jmb and 05, 06 ...
SataPortMap is kind of hardware dependent as it gives the controller layout that is used in DiskIdxMap
SataPortMap might change is pcie slots are swapped between controllers or if onboard sata is disabled in bios (usually that only works if the whol onbard controlleris disabled, only disabling just ports of a controller usually does not work, dsm akak linux kernel still sees the hardware capabilities of the controller)
edit: seeing a kernel log whare controller drivers are loaded would be nice and might explain why "satamap now" shows three onboard ports
@IG-88
Yes I’ve plugged in a JMB585 PCIe SATA bridge in the M.2 port which has 5 SATA ports so that’s clear.My question is the single port onboard AHCI SATA controller whose extension can’t be found and it’s showing up as 3 ports.
-
How does the module identification take place?
I'm on Intel NUC 10 Frost Canyon, the motherboard SATA controller module can't be found. How can I build one?
It looks that you will need the following modules : Found VGA Controller : pciid 8086d00009bca Required Extension : No matching extension Found SATA Controller : pciid 8086d000002d3 Required Extension : No matching extensiontc@box:~$ lspci -tnnvq -[0000:00]-+-00.0 Intel Corporation Device [8086:9b51] +-02.0 Intel Corporation Comet Lake UHD Graphics [8086:9bca] +-08.0 Intel Corporation Skylake Gaussian Mixture Model [8086:1911] +-12.0 Intel Corporation Comet Lake Thermal Subsytem [8086:02f9] +-14.0 Intel Corporation Comet Lake PCH-LP USB 3.1 xHCI Host Controller [8086:02ed] +-14.2 Intel Corporation Comet Lake PCH-LP Shared SRAM [8086:02ef] +-14.3 Intel Corporation Comet Lake PCH-LP CNVi WiFi [8086:02f0] +-15.0 Intel Corporation Serial IO I2C Host Controller [8086:02e8] +-15.2 Intel Corporation Comet Lake PCH-LP LPSS: I2C Controller #2 [8086:02ea] +-16.0 Intel Corporation Comet Lake Management Engine Interface [8086:02e0] +-17.0 Intel Corporation Comet Lake SATA AHCI Controller [8086:02d3] +-1c.0-[01-39]----00.0-[02-39]--+-00.0-[03]----00.0 Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] [8086:15e8] | +-01.0-[04-38]-- | \-02.0-[39]----00.0 Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] [8086:15e9] +-1d.0-[3a]----00.0 JMicron Technology Corp. JMB58x AHCI SATA controller [197b:0585] +-1d.5-[3b]----00.0 Genesys Logic, Inc GL9755 SD Host Controller [17a0:9755] +-1f.0 Intel Corporation Comet Lake PCH-LP LPC Premium Controller/eSPI Controller [8086:0284] +-1f.3 Intel Corporation Comet Lake PCH-LP cAVS [8086:02c8] +-1f.4 Intel Corporation Comet Lake PCH-LP SMBus Host Controller [8086:02a3] +-1f.5 Intel Corporation Comet Lake SPI (flash) Controller [8086:02a4] \-1f.6 Intel Corporation Ethernet Connection (10) I219-V [8086:0d4f]tc@box:~$ ./rploader.sh satamap now HBA: 00:17.0 Disks : 3 HBA: 00:1d.0 Disks : 5 SataPortMap=35 DiskIdxMap=0005SataPortMap should be 15 as the 00:17.0 SATA Controller has only one port. Tagging a few experts as this is kind of fundamental to understand: @pocopico @IG-88 @Orphée @WiteWulf @haydibe
-
6 hours ago, Orphée said:
If you don't want to use linux command lines at all, go to ESXi. It is easier to manage disk / img upload and deployment with ESXi GUI.
If you don't fear command lines, ssh, etc... Proxmox VE is free and has a better serial port handling for our Xpenology needs. (Actually serial port from network/telnet access is not available without enterprise license on ESXi.)
Proxmox has some usefull features like Let's Encrypt certificates, MFA availability. I did not see it on ESXi.
It is my personnal experience with only one week of Proxmox usage.
I don’t fear ssh at all and would love continuing to use Proxmox but its very unstable. Hence want to go to ESXi.
I also believe that the hardware pass through works better and more reliable there.The serial port is just an output of dmesg right or am I missing something? If yes just a simple “dmesg -Tx —follow > $PATH/dmesg.log” should suffice in case the serial port isn’t available?
-
I’ve ds918+ installed on Proxmox 7.1 running on 5 HDDs (as PCI pass through) with loader 0.4.5.
Due to frequent crashes in the Proxmox environment, mostly triggered by hardware related stuff (e.g plugging in a usb drive, NIC hardware hang etc) I want to move to ESXi.Do I just rebuild the loader on ESXi 7 and pass through the disks stated above? Or is there anything else that needs to be done?
-
1 hour ago, WiteWulf said:
Looks like you're running into the kernel panic issue we spent quite a while investigating last year:
https://github.com/RedPill-TTG/redpill-lkm/issues/21
The workaround I found was to boot with NMI watchdog disabled, then turn it on manually after booting.
@WiteWulf thanks much for responding 🙏
I’m not using docker though but the issue linked above could be the cause.
I just set ‘nmi_watchdog=0’ in user_config.json and rebuild? After booting ‘echo 1> /proc/sys/kernel/nmi_watchdog’?Having said that, I upgraded to v0.4.5 builder and its running rock solid over the last 2 days with heavy data scrubbing and general use (even after the host Proxmox environment crashed after a few hours 😀)
has this issue been tackled in the latest version of the builder 0.4.5.x?
-
OK so the serial port shows kernel panic before crashing and rebooting @IG-88 @Orphée @haydibe
I was running 0.4.4 DS918+ without any glitches since a week back. Then DSM started crashing spontaneously and now I see this:
Proxmox env info:
proxmox-ve: 7.1-1 (running kernel: 5.13.19-3-pve) pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
[ 127.643644] CPU: 2 PID: 0 Comm: swapper/2 Tainted: P OE 4.4.180+ #42218 [ 127.644007] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [ 127.644007] task: ffff880179169b80 ti: ffff880179174000 task.ti: ffff880179174000 [ 127.644007] RIP: 0010:[<ffffffff810570a9>] [<ffffffff810570a9>] irq_exit+0x69/0xb0 [ 127.644007] RSP: 0018:ffff88017dd03f90 EFLAGS: 00000046 [ 127.644007] RAX: 0000000000000002 RBX: 0000000000000000 RCX: 00000000000006e0 [ 127.644007] RDX: 000000000000013e RSI: ffff88017dd0ee80 RDI: 000000000917f000 [ 127.644007] RBP: ffff88017dd03f90 R08: 0000013e7f7b1895 R09: 0000000000000000 [ 127.644007] R10: 000000000000000f R11: 0000000000000020 R12: 00000000ffffffff [ 127.644007] R13: ffff880179178000 R14: 0000000000000000 R15: 0000000000000000 [ 127.644007] FS: 0000000000000000(0000) GS:ffff88017dd00000(0000) knlGS:0000000000000000 [ 127.644007] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 127.644007] CR2: 00007f63a4446798 CR3: 00000000641ff000 CR4: 00000000003606f0 [ 127.644007] Stack: [ 127.644007] ffff88017dd03fa8 ffffffff81035223 0000000000000002 ffff880179177ed0 [ 127.644007] ffffffff8157a9db ffff880179177e08 <EOI> 0000000000000000 0000000000000000 [ 127.644007] ffff880179178000 00000000ffffffff ffff880179177ed0 0000000000000002 [ 127.644007] Call Trace: [ 127.644007] <IRQ> d [<ffffffff81035223>] smp_apic_timer_interrupt+0x43/0x60 [ 127.644007] [<ffffffff8157a9db>] apic_timer_interrupt+0x9b/0xa0 [ 127.644007] <EOI> d [<ffffffff8100e1ad>] ? default_idle+0x2d/0x100 [ 127.644007] [<ffffffff8100efb0>] arch_cpu_idle+0x10/0x20 [ 127.644007] [<ffffffff8108eb68>] default_idle_call+0x28/0x40 [ 127.644007] [<ffffffff8108ed25>] cpu_startup_entry+0x1a5/0x340 [ 127.644007] [<ffffffff810beeb9>] ? clockevents_config_and_register+0x29/0x30 [ 127.644007] [<ffffffff8103336d>] start_secondary+0x10d/0x110 [ 127.644007] Code: 44 48 00 00 48 8b 80 08 c0 ff ff a8 08 75 0e 65 8b 05 bc 64 fb 7e a9 00 ff 1f 00 74 2c e8 60 71 05 00 5d c3 80 3d 23 c6 87 00 00 <74> 2c 65 48 8b 3d 3d 80 fb 7e 48 85 ff 74 b1 48 8b 07 48 85 c0 [ 127.644092] NMI backtrace for cpu 1 [ 127.644092] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P OE 4.4.180+ #42218 [ 127.644092] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [ 127.644092] task: ffff880179168dc0 ti: ffff880179170000 task.ti: ffff880179170000 [ 127.644092] RIP: 0010:[<ffffffff8100e1ad>] [<ffffffff8100e1ad>] default_idle+0x2d/0x100 [ 127.644092] RSP: 0018:ffff880179173eb8 EFLAGS: 00000246 [ 127.644092] RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffff88017dc912b0 [ 127.644092] RDX: ffffffff8183d438 RSI: 0140000000000000 RDI: 0100000000000000 [ 127.644092] RBP: ffff880179173ed0 R08: 0000000000000002 R09: 7fffffffffffffff [ 127.644092] R10: 00000000fffd5eb8 R11: 0000000000005800 R12: 00000000ffffffff [ 127.644092] R13: ffff880179174000 R14: 0000000000000000 R15: 0000000000000000 [ 127.644092] FS: 0000000000000000(0000) GS:ffff88017dc80000(0000) knlGS:0000000000000000 [ 127.644092] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 127.644092] CR2: 00007f1813b4dbdb CR3: 0000000078a5e000 CR4: 00000000003606f0 [ 127.644092] Stack: [ 127.644092] ffffffff818d3638 00000000ffffffff ffff880179174000 ffff880179173ee0 [ 127.644092] ffffffff8100efb0 ffff880179173ef0 ffffffff8108eb68 ffff880179173f30 [ 127.644092] ffffffff8108ed25 ffffffff810beeb9 0000000000000001 0000000000000000 [ 127.644092] Call Trace: [ 127.644092] [<ffffffff8100efb0>] arch_cpu_idle+0x10/0x20 [ 127.644092] [<ffffffff8108eb68>] default_idle_call+0x28/0x40 [ 127.644092] [<ffffffff8108ed25>] cpu_startup_entry+0x1a5/0x340 [ 127.644092] [<ffffffff810beeb9>] ? clockevents_config_and_register+0x29/0x30 [ 127.644092] [<ffffffff8103336d>] start_secondary+0x10d/0x110 [ 127.644092] Code: 89 e5 41 55 41 54 53 65 8b 1d 80 ef ff 7e 8b 05 52 d1 8b 00 85 c0 7f 2b 8b 05 88 e9 9b 00 85 c0 7e 07 0f 00 2d 67 58 5f 00 fb f4 <65> 8b 1d 5c ef ff 7e 8b 05 2e d1 8b 00 85 c0 7f 5c 5b 41 5c 41 [ 127.644106] NMI backtrace for cpu 3 [ 127.644106] CPU: 3 PID: 0 Comm: swapper/3 Tainted: P OE 4.4.180+ #42218 [ 127.644106] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [ 127.644106] task: ffff88017916a940 ti: ffff880179178000 task.ti: ffff880179178000 [ 127.644106] RIP: 0010:[<ffffffff8100e1ad>] [<ffffffff8100e1ad>] default_idle+0x2d/0x100 [ 127.644106] RSP: 0018:ffff88017917beb8 EFLAGS: 00000246 [ 127.644106] RAX: 0000000000000000 RBX: 0000000000000003 RCX: ffff88017dd912b0 [ 127.644106] RDX: ffffffff8183d438 RSI: 0140000000000000 RDI: 0100000000000000 [ 127.644106] RBP: ffff88017917bed0 R08: 0000000000000002 R09: 0000000000000000 [ 127.644106] R10: 00000000fffd5e2b R11: 000000000000b800 R12: 00000000ffffffff [ 127.644106] R13: ffff88017917c000 R14: 0000000000000000 R15: 0000000000000000 [ 127.644106] FS: 0000000000000000(0000) GS:ffff88017dd80000(0000) knlGS:0000000000000000 [ 127.644106] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 127.644106] CR2: 00007feec4003000 CR3: 000000015f1ea000 CR4: 00000000003606f0 [ 127.644106] Stack: [ 127.644106] ffffffff818d3638 00000000ffffffff ffff88017917c000 ffff88017917bee0 [ 127.644106] ffffffff8100efb0 ffff88017917bef0 ffffffff8108eb68 ffff88017917bf30 [ 127.644106] ffffffff8108ed25 ffffffff810beeb9 0000000000000003 0000000000000000 [ 127.644106] Call Trace: [ 127.644106] [<ffffffff8100efb0>] arch_cpu_idle+0x10/0x20 [ 127.644106] [<ffffffff8108eb68>] default_idle_call+0x28/0x40 [ 127.644106] [<ffffffff8108ed25>] cpu_startup_entry+0x1a5/0x340 [ 127.644106] [<ffffffff810beeb9>] ? clockevents_config_and_register+0x29/0x30 [ 127.644106] [<ffffffff8103336d>] start_secondary+0x10d/0x110 [ 127.644106] Code: 89 e5 41 55 41 54 53 65 8b 1d 80 ef ff 7e 8b 05 52 d1 8b 00 85 c0 7f 2b 8b 05 88 e9 9b 00 85 c0 7e 07 0f 00 2d 67 58 5f 00 fb f4 <65> 8b 1d 5c ef ff 7e 8b 05 2e d1 8b 00 85 c0 7f 5c 5b 41 5c 41 [ 127.643001] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0dModules linked in: fuse 8021q 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) vfat fat udf isofs loop synoacl_vfs(PO) 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 raid456 nf_conntrack async_raid6_recov async_memcpy iptable_filter async_pq async_xor async_tx ip_tables x_tables nfsd btrfs ecryptfs zstd_decompress zstd_compress xxhash xor raid6_pq lockd grace rpcsec_gss_krb5 auth_rpcgss sunrpc aesni_intel glue_helper lrw gf128mul ablk_helper apollolake_synobios(PO) hid_generic usbhid hid usblp i915 drm_kms_helper syscopyarea sysfillrect sysim[ 127.643001] CPU: 0 PID: 16355 Comm: transmissiond Tainted: P OE 4.4.180+ #42218 [ 127.643001] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [ 127.643001] task: ffff8801616f44c0 ti: ffff880063568000 task.ti: ffff880063568000 [ 127.643001] RIP: 0033:[<00007f63b310b2eb>] [<00007f63b310b2eb>] 0x7f63b310b2eb [ 127.643001] RSP: 002b:00007f63a9d513d0 EFLAGS: 00000293 [ 127.643001] RAX: 0000000000000000 RBX: 00007f63a9d51420 RCX: 00007f63b310b2eb [ 127.643001] RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007f63a9d51420 [ 127.643001] RBP: 0000000000000001 R08: 0000000000000000 R09: 00007ffc3ffe7080 [ 127.643001] R10: 0000000000000000 R11: 0000000000000293 R12: 000000000000003e [ 127.643001] R13: 00000000ffffffff R14: 00000000ffffffff R15: 00007f63a9d515a0 [ 127.643001] FS: 00007f63a9d52700(0000) GS:ffff88017dc00000(0000) knlGS:0000000000000000 [ 127.643001] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 127.643001] CR2: 00007f639cb3d628 CR3: 00000000641ff000 CR4: 00000000003606f0 [ 127.643001] [ 127.643001] Sending NMI to other CPUs: [ 127.643001] Kernel panic - not syncing: Hard LOCKUP [ 127.643001] CPU: 0 PID: 16355 Comm: transmissiond Tainted: P OE 4.4.180+ #42218 [ 127.643001] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [ 127.643001] 0000000000000000 ffff88006356bb88 ffffffff812ef89d ffffffff81718e33 [ 127.643001] ffff88006356bc18 ffff88006356bc08 ffffffff8112ffc7 0000000000000008 [ 127.643001] ffff88006356bc18 ffff88006356bbb0 ffffffff81304298 0000000000000008 [ 127.643001] Call Trace: [ 127.643001] [<ffffffff812ef89d>] dump_stack+0x4d/0x70 [ 127.643001] [<ffffffff8112ffc7>] panic+0xc5/0x21d [ 127.643001] [<ffffffff81304298>] ? find_next_bit+0x18/0x20 [ 127.643001] [<ffffffff810e4783>] watchdog_overflow_callback+0xe3/0xf0 [ 127.643001] [<ffffffff81129c98>] __perf_event_overflow+0x98/0x1e0 [ 127.643001] [<ffffffff8112a844>] perf_event_overflow+0x14/0x20 [ 127.643001] [<ffffffff8101f97c>] intel_pmu_handle_irq+0x1ec/0x410 [ 127.643001] [<ffffffff811a8110>] ? poll_select_copy_remaining+0x120/0x120 [ 127.643001] [<ffffffff811a7fe1>] ? set_fd_set+0x21/0x30 [ 127.643001] [<ffffffff811a8cd1>] ? core_sys_select+0x291/0x2c0 [ 127.643001] [<ffffffff81017c5d>] perf_event_nmi_handler+0x2d/0x50 [ 127.643001] [<ffffffff81008a38>] nmi_handle+0x58/0x120 [ 127.643001] [<ffffffff81008fd5>] default_do_nmi+0x45/0xe0 [ 127.643001] [<ffffffff81009170>] do_nmi+0x100/0x160 [ 127.643001] [<ffffffff8157bd18>] nmi+0x68/0xb8 [ 127.643001] Kernel Offset: disabled
TinyCore RedPill Loader (TCRP)
in Loaders
Posted
Installed ds3622xs on bare metal (Intel Nuc 10 Frost Canyon). Takes quite a while to start (compared to ESXi or Proxmox). I see the following in Notifications:
Detected non-Synology recommended memory module configurations. You may have
1. Inserted non-Synology memory modules
Please select authentic Synology memory modules for better system reliability.
Anyone else getting this? Can there be a boot time memory check which could explain the delay?