FiberInternetUser

Moderators
  • Content Count

    47
  • Joined

  • Last visited

Community Reputation

2 Neutral

About FiberInternetUser

  • Rank
    Junior Member

Recent Profile Visitors

2,118 profile views
  1. FiberInternetUser

    Shutdown does work

    Hello rickym, I have a couple motherboards I am testing which are running the DS918+ boot loader and DSM 6.2.1-23824 Update 2. When I set them up initially, I used the 1.03a boot loader and a graceful shutdown was normal When boot loader 1.04b became available, I thought I would switch to it. When I made the switch I discovered a graceful shutdown was not possible. So I just reverted back to the older boot loader. The older 1.03a boot loader only recognizes Intel Network Interface Cards. I am using a couple ASRock J3455-ITX motherboards and have the internal Realtek NIC disabled. I threw in an Intel NIC in the PCIe slot. A little inconvenient but I didn't want to take a chance on corrupting the test data by doing a hard shutdown. Something else I could not get to work with the 1.04b boot loader was hardware transcoding. I have it working with the older 1.03a boot loader.
  2. FiberInternetUser

    DSM 6.2.1-23824 Update 1

    - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 - Loader version and model: Jun's Loader v1.03a - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock J3455-ITX -Additional Comments: /dev/dri directory present with 3 files. 1. card0, 2. controlD64 and 3. renderD123 .. Hardware Transcoding working with Emby Server. Onboard Realtek RTL8111GR Network Adapter disabled, using PCI Intel Network Adapter.
  3. FiberInternetUser

    Unable to boot while attached USB drive

    Hello, I would check the USB boot order in your bios. I have 3 USB External Drives for backup hooked up to my xpenoloby box plus the USB thumb drive which it boots from. In the bios I have the USB thumb drive as the first boot device. I hope this helps.
  4. FiberInternetUser

    DSM 6.2 Loader

    After upgrading to jun's lastest 918+ boot loader 1.04b, ASRock J3455-ITX motherboard does not perform a graceful shutdown. Can't perform a reboot from the DSM GUI as It hangs on shutdown.
  5. FiberInternetUser

    DSM 6.2.1-23824 - WARNING

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 Update 2 - Loader version and model: Jun's LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: Baremetal, ASRock J3455-ITX motherboard - Additional comments: onboard NIC - Realtek RTL8111GR
  6. Loader version and type (918+): 1.03a2 DS918+ DSM version in use (including critical update): DSM 6.2-23739 Update 1 Using custom modules/ramdisk? If yes which one?: None Hardware details: Motherboard: ASRock J344-ITX; NIC: Realtek 8111GR
  7. After you install DSM 6.1.7 using 1.02b loader, you may want to change your Control Panel Update & Restore settings. The following setting will only show you "important and security updates only, while retaining the current version of DSM." As IG-88 stated, each major release of dsm requires a new bootloader. There is also a setting that will automatically install all DSM and Important updates; this should not be selected using xpenology boot loaders. I hope this info is helpful. Control Panel Update & Restore Hide
  8. FiberInternetUser

    Progress of 6.2 loader

    I have other motherboards running DS3615xs and DS3617xs without any problems. I have a couple ASRock J3455-ITX motherboards I am testing Jun's 1.03a2 loader. A failed update is positive feedback to Jun, indicating there could be a problem with the loader. Currently, it is only alpha. I was able to do a reinstall on the J3455-ITX which reverted the system back to the previous state before the update. The ASRock J3455-ITX's are only test systems. No harm done other then the time to do the reinstall. Thanks for your feedback.
  9. FiberInternetUser

    Progress of 6.2 loader

    I just tried the DS918p 6.2-23739 Update 1 on a baremetal ASRock J3455-ITX using Jun's 1.03a2 loader and after the automatic reboot, the update experienced a kernel panic.
  10. FiberInternetUser

    DSM 6.2-23739 Update 1

    - Outcome of the update: UNSUCESSFUL - DSM version prior update: DSM 6.2-23739 UPDATE 1 - Loader version and model: JUN'S LOADER v1.03a2 - DS918p - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock J3455-ITX - Additional comments: AFTER REBOOT, KERNEL PANIC Second Try after reinstall: - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 UPDATE 1 - Loader version and model: JUN'S LOADER v1.03a2 - DS918p - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock J3455-ITX - Additional comments: Automatic REBOOT
  11. FiberInternetUser

    DSM 6.1.7-15284 Update 1

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 - Loader version and model: Jun's loader v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Gigabyte GA-Z87X-UD5H + 8Gb RAM - Additional comments: AUTOMATIC REBOOT
  12. FiberInternetUser

    Progress of 6.2 loader

    No, as I don't think the boot process completed correctly. Usually, with a normal boot using the older 6.1 DS3617xs image the boot completes with "Diskstation Login". At that point I can login through the serial port. When booting the 918+ image it has problems with one module and performs a trace, the boot continues and states network modules are loading ok but the boot process stops at the Loading module synobios ... does not complete to "Diskstation Login". I disabled both internal NIC's and I installed another network card which has a Realtek RTL8111E chip. Same results. I can't determine what module the boot process is having a problem with. Thanks for your help.
  13. FiberInternetUser

    Progress of 6.2 loader

    I disabled/removed each adapter one at a time. With the Ugreen using the RealTek RTL8111G chip, the boot process proceeded a little further. I still get the crash at the start but modules continuing loadiing. It loads OK the " :: Loading modul[ 6.349374] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI [ 6.357725] e1000: Copyright (c) 1999-2006 Intel Corporation. e e1000 ... [ OK ]. The boot process stops at :: Loading module synobios ..
  14. FiberInternetUser

    Progress of 6.2 loader

    System Tested: Shuttle SZ170R8 V2 CPU: i5-7600K Memory: 16 gb DDR4 Network 1: intel i219 Network 2: intel i211 Network 3: Ugreen PCI Express Network Adapter using Realtek RTL8111G chip When booting with jun's 1.03a2 DS918p image I get the following kernel panic. DS-918P Boot Capture GNU GRUB version 2.02~beta2-36ubuntu3.14 +----------------------------------------------------------------------------+ |*DS918+ 6.2 Baremetal with Jun's Mod v1.03a | | DS918+ 6.2 Baremetal with Jun's Mod v1.03a Reinstall | | DS918+ 6.2 VMWare/ESXI with Jun's Mod v1.03a | | | | | | | | | | | | | | | | | | | +----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. [ 0.001093] Spectre V2 : kernel not compiled with retpoline; no mitigation available! [ 1.214533] ata1: send port disabled event [ 1.231424] ata2: send port disabled event patching file etc/rc patching file etc/synoinfo.conf patching file linuxrc.syno patching file usr/sbin/init.post START /linuxrc.syno Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module ohci-hcd ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading module BusLogic ... [ OK ] :: Loading module vmw_pvscsi ... [ OK ] :: Loading module megaraid_mm ... [ OK ] :: Loading module megaraid_mbox ... [ OK ] :: Loading module scsi_transport_spi ... [ OK ] :: Loading module mptbase ... [ OK ] :: Loading module mptscsih ... [ OK ] :: Loading module mptspi ... [ OK ] :: Loading module mptctl ... [ OK ] :: Loading module megaraid ... [ OK ] :: Loading module megaraid_sas ... [ OK ] :: Loading module mdio ... [ OK ] Insert net driver(Mindspeed only[ 3.696559] BUG: unable to handle kernel NULL pointer dereference at 0000000000000090 [ 3.705873] IP: [<ffffffff813f0c5f>] syno_ahci_disk_led_enable+0x7f/0x170 [ 3.713031] PGD 455d73067 PUD 453a96067 PMD 0 [ 3.717775] Oops: 0002 [#1] PREEMPT SMP [ 3.721961] Modules linked in: apollolake_synobios(PO+) etxhci_hcd mdio(E) me garaid_sas(E) megaraid(E) mptctl(E) mptspi(E) mptscsih(E) mptbas ort_spi(E) megaraid_mbox(E) megaraid_mm(E) vmw_pvscsi(E) BusLogic(E) usb_storage xhci_pci xhci_hcd ohci_hcd(E) usbcore usb_common irsnlpnkiootka(OE) [ 3.750763] CPU: 0 PID: 3678 Comm: insmod Tainted: P OE 4.4.59+ # 23739 [ 3.758727] Hardware name: Shuttle Inc. SZ170/FZ170, BIOS 2.09 08/01/2017 [ 3.765857] task: ffff880084849000 ti: ffff88045a87c000 task.ti: ffff88045a87 c000 [ 3.773718] RIP: 0010:[<ffffffff813f0c5f>] [<ffffffff813f0c5f>] syno_ahci_di sk_led_enable+0x7f/0x170 [ 3.783428] RSP: 0018:ffff88045a87fb90 EFLAGS: 00010046 [ 3.789020] RAX: 0000000000000000 RBX: ffff880085270000 RCX: 0000000000000000 [ 3.796529] RDX: 0000000000000000 RSI: ffff880085270000 RDI: 0000000000000008 [ 3.804044] RBP: ffff88045a87fbc0 R08: 0000000000000000 R09: 00000000000024c0 [ 3.811560] R10: 0000000000002640 R11: 0000000000002640 R12: 0000000000000000 [ 3.819086] R13: ffff880456c2f000 R14: 0000000000000001 R15: ffff880085271f40 [ 3.826593] FS: 00007f625b24c700(0000) GS:ff 00000000000 [ 3.835079] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 3.841122] CR2: 0000000000000090 CR3: 00000004592cb000 CR4: 00000000003606f0 [ 3.848628] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 3.856120] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 3.863627] Stack: [ 3.865762] 0000000000000286 ffffffff8180e040 ffff8804510b9500 0000000000000 000 [ 3.873632] ffffffffa01495f0 ffff88008580eec0 ffff88045a87fcb8 ffffffffa014d 14c [ 3.881477] ffff88045c83c248 0000000000000000 0000000000000282 ffff88045a87f c20 [ 3.889322] Call Trace: [ 3.891900] [<ffffffffa01495f0>] ? remove_card_detect_proc+0x20/0x20 [apollo lake_synobios] [ 3.900734] [<ffffffffa014d14c>] synobios_model_init+0xec/0x650 [apollolake_ synobios] [ 3.909056] [<ffffffff812b63ff>] ? ida_pre_get+0x4f/0xe0 [ 3.914760] [<ffffffff8119da2d>] ? proc_alloc_inum+0x3d/0xc0 [ 3.920810] [<ffffffff8119dba9>] ? proc_register+0xb9/0x110 [ 3.926768] [<ffffffffa01495f0>] ? remove_card_detect_proc+0x20/0x20 [apollo lake_synobios] [ 3.935575] [<ffffffff8119dd12>] ? proc_mkdir_data+0x62/0x90 [ 3.941633] [<ffffffff8119dd60>] ? proc_mkdir+0x10/0x20 [ 3.947237] [<ffffffffa0149663>] synobios_init+0x73/0x470 [apollolake_synobi os] [ 3.955011] [<ffffffff810003b6>] do_one_initcall+0x86/0x1b0 [ 3.960976] [<ffffffff810df1d8>] do_init_module+0x56/0x1be [ 3.966847] [<ffffffff810b554d>] load_module+0x1ded/0x2070 [ 3.972714] [<ffffffff810b28b0>] ? __symbol_put+0x50/0x50 [ 3.978512] [<ffffffff81112da5>] ? map_vm_area+0x35/0x50 [ 3.984209] [<ffffffff811140ec>] ? __vmalloc_node_range+0x13c/0x240 [ 3.990902] [<ffffffff810b5858>] ? SYSC_init_module+0x88/0x110 [ 3.997136] [<ffffffff810b58cf>] SYSC_init_module+0xff/0x110 [ 4.003178] [<ffffffff810b5969>] SyS_init_module+0x9/0x10 [ 4.008970] [<ffffffff81566b17>] entry_SYSCALL_64_fastpath+0x12/0x6a [ 4.015756] Code: e8 97 7b fd ff 48 85 c0 4c 8d 38 24 48 89 d0 48 83 c7 08 48 c1 e0 02 48 01 d0 48 c1 e0 04 4a 8d 04 20 <48> c7 80 90 00 00 00 00 00 00 00 48 c7 80 88 00 00 00 00 00 00 [ 4.036936] RIP [<ffffffff813f0c5f>] syno_ahci_disk_led_enable+0x7f/0x170 [ 4.044182] RSP <ffff88045a87fb90> [ 4.047857] CR2: 0000000000000090 [ 4.051344] ---[ end trace ac98f6d41e7a4163 ]--- [ 4.056207] note: insmod[3678] exited with preempt_count 1 )... Killed Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 255 rmmod: can't unload 'apollolake_synobi[ 4.072258] md: Autodetecting RAID arra ys. os': Device or r[ 21.587290] NMI watchdog: Watchdog detected hard LOCKUP on cp u 0 [ 21.593438] Modules linked in: apollolake_synobios(PO+) etxhci_hcd mdio(E) me garaid_sas(E) megaraid(E) mptctl(E) mptspi(E) mptscsih(E) mptbase(E) scsi_transp ort_spi(E) megaraid_mbox(E) megaraid_mm(E) vmw_pvscsi(E) BusLogic(E) usb_storage xhci_pci xhci_hcd ohci_hcd(E) usbcore usb_common irsnlpnkiootka(OE) [ 21.622393] CPU: 0 PID: 3706 Comm: mdadm Tainted: P D OE 4.4.59+ #2 3739 [ 21.630263] Hardware name: Shuttle Inc. SZ170/FZ170, BIOS 2.09 08/01/2017 [ 21.637398] task: ffff880452992f00 ti: ffff880452ae0000 task.ti: ffff880452ae 0000 [ 21.645261] RIP: 0010:[<ffffffff81082828>] [<ffffffff81082828>] queued_spin_ lock_slowpath+0x148/0x160 [ 21.655059] RSP: 0018:ffff880452ae3a58 EFLAGS: 00000002 [ 21.660641] RAX: 0000000000000101 RBX: 0000000000000293 RCX: 0000000000000101 [ 21.668156] RDX: 0000000000000101 RSI: 0000000000000001 RDI: ffff880455c11718 [ 21.675673] RBP: ffff880452ae3a58 R08: 0000000000000001 R09: ffffffffffffffc0 [ 21.683196] R10: ffff8804529edf88 R11: 0000000000000000 R12: ffff880459a21000 [ 21.690704] R13: ffff8800376fc000 R14: ffff880459a21050 R15: ffff88045955a6c0 [ 21.698206] FS: 00007fc0e8e23700(0000) GS:ffff88046ec00000(0000) knlGS:00000 00000000000 [ 21.706700] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 21.712743] CR2: 0000000001f66328 CR3: 000000045394c000 CR4: 00000000003606f0 [ 21.720259] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 21.727766] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 21.735248] Stack: [ 21.737372] ffff880452ae3a70 ffffffff8156675b ffff88045955a6c0 ffff880452ae3 aa0 [ 21.745225] ffffffff813d6b71 ffff88045955a6c0 ffff88045642b000 ffff88044cd5c 9a0 [ 21.753081] ffff880459a21050 ffff880452ae3ac0 ffffffff813a73ab ffff880459a21 000 [ 21.760918] Call Trace: [ 21.763501] [<ffffffff8156675b>] _raw_spin_lock_irqsave+0x2b/0x40 [ 21.769997] [<ffffffff813d6b71>] ata_scsi_queuecmd+0x21/0x440 [ 21.776107] [<ffffffff813a73ab>] scsi_dispatch_cmd+0xfb/0x380 [ 21.782269] [<ffffffff813a8e1e>] scsi_request_fn+0x3be/0x580 [ 21.788333] [<ffffffff81291b1e>] __blk_run_queue+0x2e/0x40 [ 21.794192] [<ffffffff81295ed5>] blk_queue_bio+0x2b5/0x2c0 [ 21.800070] [<ffffffff81294181>] generic_make_request+0xd1/0x1d0 [ 21.806485] [<ffffffff81294302>] submit_bio+0x82/0x160 [ 21.811999] [<ffffffff8128d722>] submit_bio_wait+0x52/0x70 [ 21.817851] [<ffffffff8144c585>] read_disk_sb.constprop.81+0x85/0x170 [ 21.824718] [<ffffffff8144c6b9>] super_90_load+0x49/0x400 [ 21.830499] [<ffffffff8116e0c3>] ? blkdev_get_by_dev+0x33/0x50 [ 21.836723] [<ffffffff81443a8f>] ? lock_rdev+0x2f/0x80 [ 21.842228] [<ffffffff81448312>] md_import_device+0x152/0x230 [ 21.848376] [<ffffffff8144f84c>] md_ioctl+0x31c/0x1fa0 [ 21.853874] [<ffffffff8114d06c>] ? dput+0x5c/0x250 [ 21.858995] [<ffffffff812a29bf>] blkdev_ioctl+0x5ff/0x900 [ 21.864777] [<ffffffff8116cd28>] block_ioctl+0x38/0x40 [ 21.870263] [<ffffffff811490f3>] do_vfs_ioctl+0x463/0x940 [ 21.876054] [<ffffffff81144efb>] ? do_unlinkat+0xcb/0x2d0 [ 21.881828] [<ffffffff8114964a>] SyS_ioctl+0x7a/0x90 [ 21.887179] [<ffffffff81566b17>] entry_SYSCALL_64_fastpath+0x12/0x6a [ 21.893990] Code: 01 48 8b 02 48 85 c0 75 0a f3 90 48 8b 02 48 85 c0 74 f6 c7 40 08 01 00 00 00 e9 51 ff ff ff 83 fa 01 75 07 e9 4e ff ff ff f3 90 <8b> 07 84 c0 75 f8 66 c7 07 01 00 5d c3 66 2e 0f 1f 84 00 00 00 [ 21.915136] Kernel panic - not syncing: Hard LOCKUP [ 21.920260] Kernel Offset: disabled [ 21.923936] ---[ end Kernel panic - not syncing: Hard LOCKUP Hide
  15. FiberInternetUser

    LED prevent hibernation

    Hello, If you are running DSM 6.2 .. go to Control Panel | Hardware & Power ... Scroll down to "LED Brightness Control" and drag the slider to the OFF position.