Dvalin21 Posted January 24, 2022 Share #526 Posted January 24, 2022 On 1/23/2022 at 2:51 AM, PincoPalla said: Hello everyone, today finally after some failed attempts (because I was wrong with the procedure) I was able to install a new diskstation 918+ vers. DSM 7.0.1 in vm mode on virtualbox to test it (I need to install it in baremetal mode on a special server) with an image downloaded from the network, unfortunately I am not able to build it myself and everything is ok, it seems to work correctly and I will test it for a few days with installation tests of the applications I need. I needed to know something for those who have already done it or are aware of it and it is this; having the need to install DSM 7.0.1 on a special machine in baremetal mode where a DSM 6.2.3 up3 version already runs, must a new installation be made or can you do a migration? The migration obviously (as long as everything goes well) is much faster and less expensive in terms of time, obviously for safety I would back up the whole machine but if it were possible to do the migration it would be much better. Does anyone know if it is possible and possibly how ??? Thank you Can you write out something to show how you got it up and running on Virtualbox? Would most appreciate it!! Awesome job!! 1 Quote Link to comment Share on other sites More sharing options...
Dvalin21 Posted January 24, 2022 Share #527 Posted January 24, 2022 4 hours ago, adamadam said: A working bootloader only has mpt3sas. When I add other installations, it loops for me. I will try the DS3615 soon, I will let you know, I will do according to your post I have the exact same raid card, been trying to get it to work. However I've tried the different mpt drivers with no success. When I try lspci -v it tells me that the card is megaraid so I use the megaraid_sas. Every time i go to install it keeps giving me the same thing, corrupted file failed install. Thats using the pat file from the cache or just downloading it myself. When I have my on board sata controller enable, identifyusb reads everything satamap 6 diskid 00. Let me know when you get everything running cause i still need help with 7.0.1. Was able to install 6.2.3 with ZERO problem. I did a dmesg on 6.2.3 and I noticed something crazy [ 2.508044] megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006) [ 2.511247] megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006) [ 2.520969] Fusion MPT base driver 3.04.20 [ 2.520971] Copyright (c) 1999-2008 LSI Corporation [ 2.527336] Fusion MPT SPI Host driver 3.04.20 [ 2.530594] Fusion MPT SAS Host driver 3.04.20 [ 2.533833] Fusion MPT misc device (ioctl) driver 3.04.20 [ 2.533909] mptctl: Registered with Fusion MPT base driver [ 2.533911] mptctl: /dev/mptctl @ (major,minor=10,220) [ 2.537139] megasas: 06.506.00.00-rc1 Sat. Feb. 9 17:00:00 PDT 2013 [ 2.537151] megasas: 0x1000:0x0073:0x1028:0x1f4e: bus 8:slot 0:func 0 <---- here is the controller [ 2.537243] 32bit 0000:08:00.0 uses non-identity mapping <-----But this is what I thought was crazy!! [ 2.537281] megasas: FW now in Ready state [ 2.537294] megaraid_sas 0000:08:00.0: irq 84 for MSI/MSI-X [ 2.558010] megasas_init_mfi: fw_support_ieee=67108864 [ 2.558013] megasas: INIT adapter done [ 2.625103] scsi0 : LSI SAS based MegaRAID driver [ 2.637206] scsi 0:0:1:0: Direct-Access TOSHIBA MQ01ABD100 3D PQ: 0 ANSI: 5 [ 2.642248] sd 0:0:1:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 2.642251] sd 0:0:1:0: [sda] 4096-byte physical blocks [ 2.673598] scsi 0:0:2:0: Direct-Access ST750LM0 HN-M750MBB 0002 PQ: 0 ANSI: 5 [ 2.681372] sd 0:0:2:0: [sdb] 1465149168 512-byte logical blocks: (750 GB/698 GiB) [ 2.681376] sd 0:0:2:0: [sdb] 4096-byte physical blocks [ 2.709804] scsi 0:0:3:0: Direct-Access SAMSUNG HD642JJ 1113 PQ: 0 ANSI: 5 [ 2.717871] sd 0:0:3:0: [sdc] 1250261615 512-byte logical blocks: (640 GB/596 GiB) [ 2.747857] scsi 0:0:32:0: Enclosure DP BP12G+ 1.00 PQ: 0 ANSI: 5 [ 2.748032] ses 0:0:32:0: Attached Enclosure device [ 2.751068] sd 0:0:3:0: [sdc] Write Protect is off [ 2.751071] sd 0:0:3:0: [sdc] Mode Sense: 73 00 00 08 [ 2.780246] usb 1-1: new high-speed USB device number 2 using ehci-pci [ 2.794107] sd 0:0:3:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 2.812086] ses 0:0:32:0: Wrong diagnostic page; asked for 7 got 0 Quote Link to comment Share on other sites More sharing options...
Unregistrado Posted January 24, 2022 Share #528 Posted January 24, 2022 7 minutes ago, Dvalin21 said: I have the exact same raid card, been trying to get it to work. However I've tried the different mpt drivers with no success. When I try lspci -v it tells me that the card is megaraid so I use the megaraid_sas. Every time i go to install it keeps giving me the same thing, corrupted file failed install. Thats using the pat file from the cache or just downloading it myself. When I have my on board sata controller enable, identifyusb reads everything satamap 6 diskid 00. Let me know when you get everything running cause i still need help with 7.0.1. Was able to install 6.2.3 with ZERO problem. I did a dmesg on 6.2.3 and I noticed something crazy [ 2.508044] megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006) [ 2.511247] megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006) [ 2.520969] Fusion MPT base driver 3.04.20 [ 2.520971] Copyright (c) 1999-2008 LSI Corporation [ 2.527336] Fusion MPT SPI Host driver 3.04.20 [ 2.530594] Fusion MPT SAS Host driver 3.04.20 [ 2.533833] Fusion MPT misc device (ioctl) driver 3.04.20 [ 2.533909] mptctl: Registered with Fusion MPT base driver [ 2.533911] mptctl: /dev/mptctl @ (major,minor=10,220) [ 2.537139] megasas: 06.506.00.00-rc1 Sat. Feb. 9 17:00:00 PDT 2013 [ 2.537151] megasas: 0x1000:0x0073:0x1028:0x1f4e: bus 8:slot 0:func 0 <---- here is the controller [ 2.537243] 32bit 0000:08:00.0 uses non-identity mapping <-----But this is what I thought was crazy!! [ 2.537281] megasas: FW now in Ready state [ 2.537294] megaraid_sas 0000:08:00.0: irq 84 for MSI/MSI-X [ 2.558010] megasas_init_mfi: fw_support_ieee=67108864 [ 2.558013] megasas: INIT adapter done [ 2.625103] scsi0 : LSI SAS based MegaRAID driver [ 2.637206] scsi 0:0:1:0: Direct-Access TOSHIBA MQ01ABD100 3D PQ: 0 ANSI: 5 [ 2.642248] sd 0:0:1:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 2.642251] sd 0:0:1:0: [sda] 4096-byte physical blocks [ 2.673598] scsi 0:0:2:0: Direct-Access ST750LM0 HN-M750MBB 0002 PQ: 0 ANSI: 5 [ 2.681372] sd 0:0:2:0: [sdb] 1465149168 512-byte logical blocks: (750 GB/698 GiB) [ 2.681376] sd 0:0:2:0: [sdb] 4096-byte physical blocks [ 2.709804] scsi 0:0:3:0: Direct-Access SAMSUNG HD642JJ 1113 PQ: 0 ANSI: 5 [ 2.717871] sd 0:0:3:0: [sdc] 1250261615 512-byte logical blocks: (640 GB/596 GiB) [ 2.747857] scsi 0:0:32:0: Enclosure DP BP12G+ 1.00 PQ: 0 ANSI: 5 [ 2.748032] ses 0:0:32:0: Attached Enclosure device [ 2.751068] sd 0:0:3:0: [sdc] Write Protect is off [ 2.751071] sd 0:0:3:0: [sdc] Mode Sense: 73 00 00 08 [ 2.780246] usb 1-1: new high-speed USB device number 2 using ehci-pci [ 2.794107] sd 0:0:3:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 2.812086] ses 0:0:32:0: Wrong diagnostic page; asked for 7 got 0 You sure it is the same card? 01:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03) megasas: 0x1000:0x0073 The pci id looks more like mine. But i could be mistaken. Quote Link to comment Share on other sites More sharing options...
Dvalin21 Posted January 24, 2022 Share #529 Posted January 24, 2022 (edited) 8 minutes ago, Unregistrado said: You sure it is the same card? 01:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03) megasas: 0x1000:0x0073 The pci id looks more like mine. But i could be mistaken. This is what I get running lspci -nnq 0000:08:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS 2008 [Falcon] [1000:0073] (rev 03) And when you look at my last post it says it doesnt use identity mapping.... Edited January 24, 2022 by Dvalin21 Quote Link to comment Share on other sites More sharing options...
Unregistrado Posted January 24, 2022 Share #530 Posted January 24, 2022 Just now, Dvalin21 said: This is what I get running lspci -nnq 0000:08:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS 2008 [Falcon] [1000:0073] (rev 03) The weird thing is that adamadam has a 1000:0072. So i think he can be helped with ds3615xs and mpt2sas. I can be mistaken too. 1 Quote Link to comment Share on other sites More sharing options...
Dvalin21 Posted January 24, 2022 Share #531 Posted January 24, 2022 2 minutes ago, Unregistrado said: The weird thing is that adamadam has a 1000:0072. So i think he can be helped with ds3615xs and mpt2sas. I can be mistaken too. I think your right with that. I've tried megaraid_sas for 3615 and 3617 and always get the "file corrupted" error Quote Link to comment Share on other sites More sharing options...
Unregistrado Posted January 24, 2022 Share #532 Posted January 24, 2022 For appololake with mpt2sas only it won't load. Loading kmod #0 "raid_class.ko" for pocopico.mpt2sas (args: ) Loading kmod #1 "scsi_transport_sas.ko" for pocopico.mpt2sas (args: ) Loading kmod #2 "mpt2sas.ko" for pocopico.mpt2sas (args: ) [ 1.938494] mpt3sas: Unknown rela relocation: 4 [ 1.939285] mpt3sas: Unknown rela relocation: 4 insmod: can't insert 'mpt2sas.ko': invalid module format ERROR: kernel extensions "mpt2sas.ko" from pocopico.mpt2sas failed to load Exit on error [99] rp ext init exec failure... Mon Jan 24 21:03:02 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 umount: /etc/mtab: No such file or directory linuxrc.syno failed on 99 And with mpt3sas only also not loaded. Running "check-mpt3sas.sh" for pocopico.mpt3sas->on_boot Loading module mpt3sas -> Module mpt3sas is not loaded Ran "check-mpt3sas.sh" for pocopico.mpt3sas->on_boot - exit=0 Quote Link to comment Share on other sites More sharing options...
Dvalin21 Posted January 24, 2022 Share #533 Posted January 24, 2022 31 minutes ago, Unregistrado said: For appololake with mpt2sas only it won't load. Loading kmod #0 "raid_class.ko" for pocopico.mpt2sas (args: ) Loading kmod #1 "scsi_transport_sas.ko" for pocopico.mpt2sas (args: ) Loading kmod #2 "mpt2sas.ko" for pocopico.mpt2sas (args: ) [ 1.938494] mpt3sas: Unknown rela relocation: 4 [ 1.939285] mpt3sas: Unknown rela relocation: 4 insmod: can't insert 'mpt2sas.ko': invalid module format ERROR: kernel extensions "mpt2sas.ko" from pocopico.mpt2sas failed to load Exit on error [99] rp ext init exec failure... Mon Jan 24 21:03:02 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 umount: /etc/mtab: No such file or directory linuxrc.syno failed on 99 And with mpt3sas only also not loaded. Running "check-mpt3sas.sh" for pocopico.mpt3sas->on_boot Loading module mpt3sas -> Module mpt3sas is not loaded Ran "check-mpt3sas.sh" for pocopico.mpt3sas->on_boot - exit=0 So after some further research, I need the megaraid_sas which I already know, but I also need LSI Fusion-MPT base driver (mptbase) updated to 4.28.20.01. Quote Link to comment Share on other sites More sharing options...
adamadam Posted January 24, 2022 Share #534 Posted January 24, 2022 57 minutes ago, Unregistrado said: For appololake with mpt2sas only it won't load. Loading kmod #0 "raid_class.ko" for pocopico.mpt2sas (args: ) Loading kmod #1 "scsi_transport_sas.ko" for pocopico.mpt2sas (args: ) Loading kmod #2 "mpt2sas.ko" for pocopico.mpt2sas (args: ) [ 1.938494] mpt3sas: Unknown rela relocation: 4 [ 1.939285] mpt3sas: Unknown rela relocation: 4 insmod: can't insert 'mpt2sas.ko': invalid module format ERROR: kernel extensions "mpt2sas.ko" from pocopico.mpt2sas failed to load Exit on error [99] rp ext init exec failure... Mon Jan 24 21:03:02 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 umount: /etc/mtab: No such file or directory linuxrc.syno failed on 99 And with mpt3sas only also not loaded. Running "check-mpt3sas.sh" for pocopico.mpt3sas->on_boot Loading module mpt3sas -> Module mpt3sas is not loaded Ran "check-mpt3sas.sh" for pocopico.mpt3sas->on_boot - exit=0 I was able to run ds3615xs, below the screen. I made a clean tinycore pendrive and on it: sudo ./rploader.sh update now sudo ./rploader.sh serialgen DS3615xs now sudo ./rploader.sh identifyusb now sudo ./rploader.sh satamap now SataPortMap = 6, DiskIdxMap = 00 I left these two parameters aside as the satamap detected them. I added this: sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json Then: sudo ./rploader.sh build bromolow-7.0.1-42218 The drives are working, but I am not satisfied because the ds3615xs is only two cores and my i5-4690 has 4 of them, I performed tests via ssh, it shows correctly that there are 4 cores, their speed is also not correct, I do not know how to understand it, does synology indicate incorrectly? However, when creating virtual machines later, I will be limited. I did the same procedure for the 918+ adding mpt2sas but there is a disk 5,6 error after detecting the drive. Interestingly, if only the drives under the h310 hearts are connected, it enters. Quote Link to comment Share on other sites More sharing options...
kami001 Posted January 24, 2022 Share #535 Posted January 24, 2022 28 minutes ago, adamadam said: I was able to run ds3615xs, below the screen. I made a clean tinycore pendrive and on it: sudo ./rploader.sh update now sudo ./rploader.sh serialgen DS3615xs now sudo ./rploader.sh identifyusb now sudo ./rploader.sh satamap now SataPortMap = 6, DiskIdxMap = 00 I left these two parameters aside as the satamap detected them. I added this: sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json Then: sudo ./rploader.sh build bromolow-7.0.1-42218 The drives are working, but I am not satisfied because the ds3615xs is only two cores and my i5-4690 has 4 of them, I performed tests via ssh, it shows correctly that there are 4 cores, their speed is also not correct, I do not know how to understand it, does synology indicate incorrectly? However, when creating virtual machines later, I will be limited. I did the same procedure for the 918+ adding mpt2sas but there is a disk 5,6 error after detecting the drive. Interestingly, if only the drives under the h310 hearts are connected, it enters. Can you tell what is your hardware on which the system works? Quote Link to comment Share on other sites More sharing options...
adamadam Posted January 24, 2022 Share #536 Posted January 24, 2022 2 minutes ago, kami001 said: Can you tell what is your hardware on which the system works? Dell Optiplex 9020 i5 4690 1 Quote Link to comment Share on other sites More sharing options...
kami001 Posted January 24, 2022 Share #537 Posted January 24, 2022 I managed to run DS3615xs on BareMetal having my NIC recognised after having included all the Realtek extensions (r8169, r8168, r8152, r8125, r8101). However, even though I could see the DiskStation in the LAN via the web browser, it gave me an error due to the failure of the SATA controller. I am sure it is a matter of drivers/extensions since during the building of my tinycore build I encountered the following: It looks that you will need the following modules : Found VGA Controller : pciid 8086d00000162 Required Extension : i915 Searching for matching extension for i915 Found SATA Controller : pciid 8086d00001c02 Required Extension : ahci Searching for matching extension for ahci Found SATA Controller : pciid 1b4bd00009215 Required Extension : No matching extension So is there any way to provide drivers or extensions for the two SATA controllers? My hardware build: Motherboard: Asus P8H61-I LX CPU: Intel i3 3245 Quote Link to comment Share on other sites More sharing options...
seanone Posted January 25, 2022 Share #538 Posted January 25, 2022 GREAT! It's easy to make and install loader! It run very well in unraid vm. Thank you for your work @pocopico Quote Link to comment Share on other sites More sharing options...
cferra Posted January 25, 2022 Share #539 Posted January 25, 2022 Would it be possible to add toggles for max disks and to enable SHR for images that don’t have that enabled by default? Quote Link to comment Share on other sites More sharing options...
Brunox Posted January 25, 2022 Share #540 Posted January 25, 2022 16 hours ago, zahni said: Hello @Brunox, thank for your replying. I've found serveral posting from buggy25200 under the given link. Which post exactly do you mean? Sorry, but I still at the beginning with learning about this stuff. Please describe your error as precisely as possible! Then it's easier to help! 1 Quote Link to comment Share on other sites More sharing options...
soulcola Posted January 25, 2022 Share #541 Posted January 25, 2022 (edited) 23 часа назад, Cubitus сказал: Dear all, I have tried out the RedPill loader along with this tinycore environement and I am getting stuck just after rebooting : The Synology assistant detects disks error and stops the SATA controllers : My initial machine is DS918+ / DSM6.2.3 update 3 with jun's loader I am trying to upgrade to DSM7.0.1 I think I have done correctly the user_config operations (sataportmap = 6 / diskidxmap = 00 and I am using the previous mac address and serial) But rploader.sh sends a warning during the build : ------------------------------------------------------------------------------------------------ It looks that you will need the following modules : Found SATA Controller : pciid 8086d0000a282 Required Extension : No matching extension Which corresponds to the SATA / AHCI controller ; effectively there are none declared in the "modules.alias.json" file corresponding to 8086 / A282. I suspect I should put an entry here, but which one ? The HW is a ASROCK B365 M mothe'rboard with intel core i3. Many thanks for your help and congrats to pocopico for this nice job. Cubitus. Hello! Here is my boot log with same problem. No idea how to fix it. I tried to playaround with sataportmap and diskIdxMap, but no success Цитата Jan 25 09:39:13 kernel: klogd started: BusyBox v1.30.1 () Jan 25 09:39:13 kernel: [ 0.000000] Initializing cgroup subsys cpuset Jan 25 09:39:13 kernel: [ 0.000000] Initializing cgroup subsys cpu Jan 25 09:39:13 kernel: [ 0.000000] Initializing cgroup subsys cpuacct Jan 25 09:39:13 kernel: [ 0.000000] Linux version 4.4.180+ (root@build15) (gc c version 7.5.0 (GCC) ) #41890 SMP Thu Jul 15 03:43:42 CST 2021 Jan 25 09:39:13 kernel: [ 0.000000] Command line: BOOT_IMAGE=/zImage withefi earlyprintk syno_hw_version=DS918+ console=ttyS0,115200n8 netif_num=1 pid=0x1625 earlycon=uart8250,io,0x3f8,115200n8 syno_port_thaw=1 mac1=0011322A46E7 sn=1230L WN009033 vi Jan 25 09:39:13 kernel: [ 0.000000] KERNEL supported cpus: Jan 25 09:39:13 kernel: [ 0.000000] Intel GenuineIntel Jan 25 09:39:13 kernel: [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_s izes[2]: 256 Jan 25 09:39:13 kernel: [ 0.000000] x86/fpu: xstate_offset[3]: 960, xstate_s izes[3]: 64 Jan 25 09:39:13 kernel: [ 0.000000] x86/fpu: xstate_offset[4]: 1024, xstate_s izes[4]: 64 Jan 25 09:39:13 kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x01: ' x87 floating point registers' Jan 25 09:39:13 kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x02: ' SSE registers' Jan 25 09:39:13 kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x04: ' AVX registers' Jan 25 09:39:13 kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x08: ' MPX bounds registers' Jan 25 09:39:13 kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x10: ' MPX CSR' Jan 25 09:39:13 kernel: [ 0.000000] x86/fpu: Enabled xstate features 0x1f, co ntext size is 1088 bytes, using 'standard' format. Jan 25 09:39:13 kernel: [ 0.000000] e820: BIOS-provided physical RAM map: Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000 00000009c3ff] usable Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x000000000009c400-0x0000 00000009ffff] reserved Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x0000 0000000fffff] reserved Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000 00003fffffff] usable Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000040000000-0x0000 0000403fffff] reserved Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000040400000-0x0000 000072261fff] usable Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000072262000-0x0000 000072262fff] ACPI NVS Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000072263000-0x0000 000072263fff] reserved Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000072264000-0x0000 00007c4f3fff] usable Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x000000007c4f4000-0x0000 00007df0dfff] reserved Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x000000007df0e000-0x0000 00007e06bfff] usable Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x000000007e06c000-0x0000 00007e414fff] ACPI NVS Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x000000007e415000-0x0000 00007effefff] reserved Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x000000007efff000-0x0000 00007effffff] usable Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x000000007f000000-0x0000 00008fffffff] reserved Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x0000 0000efffffff] reserved Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fe000000-0x0000 0000fe010fff] reserved Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x0000 0000fec00fff] reserved Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x0000 0000fed00fff] reserved Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x0000 0000fee00fff] reserved Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x0000 0000ffffffff] reserved Jan 25 09:39:13 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x0000 00026effffff] usable Jan 25 09:39:13 kernel: [ 0.000000] earlycon: Early serial console at I/O por t 0x3f8 (options '115200n8') Jan 25 09:39:13 kernel: [ 0.000000] bootconsole [uart0] enabled Jan 25 09:39:13 kernel: [ 0.000000] NX (Execute Disable) protection: active Jan 25 09:39:13 kernel: [ 0.000000] SMBIOS 2.8 present. Jan 25 09:39:13 kernel: [ 0.000000] DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./B365M-ITX/ac, BIOS P4.20 05/15/2019 Jan 25 09:39:13 kernel: [ 0.000000] Kernel/User page tables isolation: disabl ed Jan 25 09:39:13 kernel: [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved Jan 25 09:39:13 kernel: [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable Jan 25 09:39:13 kernel: [ 0.000000] e820: last_pfn = 0x26f000 max_arch_pfn = 0x400000000 Jan 25 09:39:13 kernel: [ 0.000000] MTRR default type: write-back Jan 25 09:39:13 kernel: [ 0.000000] MTRR fixed ranges enabled: Jan 25 09:39:13 kernel: [ 0.000000] 00000-9FFFF write-back Jan 25 09:39:13 kernel: [ 0.000000] A0000-BFFFF uncachable Jan 25 09:39:13 kernel: [ 0.000000] C0000-FFFFF write-protect Jan 25 09:39:13 kernel: [ 0.000000] MTRR variable ranges enabled: Jan 25 09:39:13 kernel: [ 0.000000] 0 base 0080000000 mask 7F80000000 uncac hable Jan 25 09:39:13 kernel: [ 0.000000] 1 base 007F800000 mask 7FFF800000 uncac hable Jan 25 09:39:13 kernel: [ 0.000000] 2 disabled Jan 25 09:39:13 kernel: [ 0.000000] 3 disabled Jan 25 09:39:13 kernel: [ 0.000000] 4 disabled Jan 25 09:39:13 kernel: [ 0.000000] 5 disabled Jan 25 09:39:13 kernel: [ 0.000000] 6 disabled Jan 25 09:39:13 kernel: [ 0.000000] 7 disabled Jan 25 09:39:13 kernel: [ 0.000000] 8 disabled Jan 25 09:39:13 kernel: [ 0.000000] 9 disabled Jan 25 09:39:13 kernel: [ 0.000000] x86/PAT: Configuration [0-7]: WB WT UC- UC WB WT UC- UC Jan 25 09:39:13 kernel: [ 0.000000] e820: last_pfn = 0x7f000 max_arch_pfn = 0 x400000000 Jan 25 09:39:13 kernel: [ 0.000000] Base memory trampoline at [ffff8800000940 00] 94000 size 28672 Jan 25 09:39:13 kernel: [ 0.000000] Using GB pages for direct mapping Jan 25 09:39:13 kernel: [ 0.000000] BRK [0x01a6c000, 0x01a6cfff] PGTABLE Jan 25 09:39:13 kernel: [ 0.000000] BRK [0x01a6d000, 0x01a6dfff] PGTABLE Jan 25 09:39:13 kernel: [ 0.000000] BRK [0x01a6e000, 0x01a6efff] PGTABLE Jan 25 09:39:13 kernel: [ 0.000000] BRK [0x01a6f000, 0x01a6ffff] PGTABLE Jan 25 09:39:13 kernel: [ 0.000000] BRK [0x01a70000, 0x01a70fff] PGTABLE Jan 25 09:39:13 kernel: [ 0.000000] BRK [0x01a71000, 0x01a71fff] PGTABLE Jan 25 09:39:13 kernel: [ 0.000000] log_buf_len: 33554432 bytes Jan 25 09:39:13 kernel: [ 0.000000] early log buf free: 125996(96%) Jan 25 09:39:13 kernel: [ 0.000000] RAMDISK: [mem 0x35e63000-0x36f28fff] Jan 25 09:39:13 kernel: [ 0.000000] ACPI: Early table checksum verification d isabled Jan 25 09:39:13 kernel: [ 0.000000] ACPI: RSDP 0x00000000000F05B0 000024 (v02 ALASKA) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: XSDT 0x000000007E06C0A0 0000C4 (v01 ALASKA A M I 01072009 AMI 00010013) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: FACP 0x000000007E096988 000114 (v06 ALASKA A M I 01072009 AMI 00010013) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: DSDT 0x000000007E06C200 02A785 (v02 ALASKA A M I 01072009 INTL 20160422) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: FACS 0x000000007E414F00 000040 Jan 25 09:39:13 kernel: [ 0.000000] ACPI: APIC 0x000000007E096AA0 000084 (v03 ALASKA A M I 01072009 AMI 00010013) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: FPDT 0x000000007E096B28 000044 (v01 ALASKA A M I 01072009 AMI 00010013) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: FIDT 0x000000007E096B70 00009C (v01 ALASKA A M I 01072009 AMI 00010013) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: MCFG 0x000000007E096C10 00003C (v01 ALASKA A M I 01072009 MSFT 00000097) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: SSDT 0x000000007E096C50 0003A3 (v01 SataRe SataTabl 00001000 INTL 20160422) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: AAFT 0x000000007E096FF8 000201 (v01 ALASKA OEMAAFT 01072009 MSFT 00000097) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: SSDT 0x000000007E097200 003165 (v02 SaSsdt SaSsdt 00003000 INTL 20160422) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: HPET 0x000000007E09A368 000038 (v01 INTEL KBL 00000001 MSFT 0000005F) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: SSDT 0x000000007E09A3A0 000B60 (v02 INTEL xh_kbl_s 00000000 INTL 20160422) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: UEFI 0x000000007E09AF00 000048 (v01 ALASKA A M I 00000002 01000013) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: SSDT 0x000000007E09AF48 0017AE (v02 CpuRef CpuSsdt 00003000 INTL 20160422) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: LPIT 0x000000007E09C6F8 000094 (v01 INTEL KBL 00000000 MSFT 0000005F) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: SSDT 0x000000007E09C790 000141 (v02 INTEL HdaDsp 00000000 INTL 20160422) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: SSDT 0x000000007E09C8D8 000517 (v02 INTEL TbtTypeC 00000000 INTL 20160422) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: SSDT 0x000000007E09CDF0 0002E9 (v02 INTEL Wwan 00000001 INTL 20160422) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: DBGP 0x000000007E09D0E0 000034 (v01 INTEL 00000002 MSFT 0000005F) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: DBG2 0x000000007E09D118 000054 (v00 INTEL 00000002 MSFT 0000005F) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: DMAR 0x000000007E09D170 0000A8 (v01 INTEL EDK2 00000001 INTL 00000001) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: WSMT 0x000000007E09D218 000028 (v01 ALASKA A M I 01072009 AMI 00010013) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: Local APIC address 0xfee00000 Jan 25 09:39:13 kernel: [ 0.000000] Zone ranges: Jan 25 09:39:13 kernel: [ 0.000000] DMA [mem 0x0000000000001000-0x0000 000000ffffff] Jan 25 09:39:13 kernel: [ 0.000000] DMA32 [mem 0x0000000001000000-0x0000 0000ffffffff] Jan 25 09:39:13 kernel: [ 0.000000] Normal [mem 0x0000000100000000-0x0000 00026effffff] Jan 25 09:39:13 kernel: [ 0.000000] Movable zone start for each node Jan 25 09:39:13 kernel: [ 0.000000] Early memory node ranges Jan 25 09:39:13 kernel: [ 0.000000] node 0: [mem 0x0000000000001000-0x000 000000009bfff] Jan 25 09:39:13 kernel: [ 0.000000] node 0: [mem 0x0000000000100000-0x000 000003fffffff] Jan 25 09:39:13 kernel: [ 0.000000] node 0: [mem 0x0000000040400000-0x000 0000072261fff] Jan 25 09:39:13 kernel: [ 0.000000] node 0: [mem 0x0000000072264000-0x000 000007c4f3fff] Jan 25 09:39:13 kernel: [ 0.000000] node 0: [mem 0x000000007df0e000-0x000 000007e06bfff] Jan 25 09:39:13 kernel: [ 0.000000] node 0: [mem 0x000000007efff000-0x000 000007effffff] Jan 25 09:39:13 kernel: [ 0.000000] node 0: [mem 0x0000000100000000-0x000 000026effffff] Jan 25 09:39:13 kernel: [ 0.000000] Initmem setup node 0 [mem 0x0000000000001 000-0x000000026effffff] Jan 25 09:39:13 kernel: [ 0.000000] On node 0 totalpages: 2011628 Jan 25 09:39:13 kernel: [ 0.000000] DMA zone: 64 pages used for memmap Jan 25 09:39:13 kernel: [ 0.000000] DMA zone: 22 pages reserved Jan 25 09:39:13 kernel: [ 0.000000] DMA zone: 3995 pages, LIFO batch:0 Jan 25 09:39:13 kernel: [ 0.000000] DMA32 zone: 7882 pages used for memmap Jan 25 09:39:13 kernel: [ 0.000000] DMA32 zone: 504401 pages, LIFO batch:31 Jan 25 09:39:13 kernel: [ 0.000000] Normal zone: 23488 pages used for memma p Jan 25 09:39:13 kernel: [ 0.000000] Normal zone: 1503232 pages, LIFO batch: 31 Jan 25 09:39:13 kernel: [ 0.000000] Reserving Intel graphics memory at [mem 0 x80000000-0x8fffffff] Jan 25 09:39:13 kernel: [ 0.000000] ACPI: PM-Timer IO Port: 0x1808 Jan 25 09:39:13 kernel: [ 0.000000] ACPI: Local APIC address 0xfee00000 Jan 25 09:39:13 kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) Jan 25 09:39:13 kernel: [ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119 Jan 25 09:39:13 kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global _irq 2 dfl dfl) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global _irq 9 high level) Jan 25 09:39:13 kernel: [ 0.000000] ACPI: IRQ0 used by override. Jan 25 09:39:13 kernel: [ 0.000000] ACPI: IRQ9 used by override. Jan 25 09:39:13 kernel: [ 0.000000] Using ACPI (MADT) for SMP configuration i nformation Jan 25 09:39:13 kernel: [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed0000 0 Jan 25 09:39:13 kernel: [ 0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x0000 0000-0x00000fff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x0009 c000-0x0009cfff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x0009 d000-0x0009ffff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x000a 0000-0x000dffff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x000e 0000-0x000fffff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x4000 0000-0x403fffff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x7226 2000-0x72262fff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x7226 3000-0x72263fff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x7c4f 4000-0x7df0dfff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x7e06 c000-0x7e414fff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x7e41 5000-0x7effefff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x7f00 0000-0x8fffffff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x9000 0000-0xdfffffff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xe000 0000-0xefffffff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xf000 0000-0xfdffffff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xfe00 0000-0xfe010fff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xfe01 1000-0xfebfffff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xfec0 0000-0xfec00fff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xfec0 1000-0xfecfffff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xfed0 0000-0xfed00fff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xfed0 1000-0xfedfffff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xfee0 0000-0xfee00fff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xfee0 1000-0xfeffffff] Jan 25 09:39:13 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xff00 0000-0xffffffff] Jan 25 09:39:13 kernel: [ 0.000000] e820: [mem 0x90000000-0xdfffffff] availab le for PCI devices Jan 25 09:39:13 kernel: [ 0.000000] clocksource: refined-jiffies: mask: 0xfff fffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns Jan 25 09:39:13 kernel: [ 0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1 Jan 25 09:39:13 kernel: [ 0.000000] PERCPU: Embedded 33 pages/cpu @ffff88026c c00000 s95128 r8192 d31848 u524288 Jan 25 09:39:13 kernel: [ 0.000000] pcpu-alloc: s95128 r8192 d31848 u524288 a lloc=1*2097152 Jan 25 09:39:13 kernel: [ 0.000000] pcpu-alloc: [0] 0 1 2 3 Jan 25 09:39:13 kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1980172 Jan 25 09:39:13 kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=/zImage w ithefi earlyprintk syno_hw_version=DS918+ console=ttyS0,115200n8 netif_num=1 pid =0x1625 earlycon=uart8250,io,0x3f8,115200n8 syno_port_thaw=1 mac1=0011322A46E7 s n=1230LWN00 Jan 25 09:39:13 kernel: [ 0.000000] Synology Hardware Version: DS918+ Jan 25 09:39:13 kernel: [ 0.000000] Internal netif num: 1 Jan 25 09:39:13 kernel: [ 0.000000] Mac1: 0011322A46E7 Jan 25 09:39:13 kernel: [ 0.000000] Serial Number: 1230LWN009033 Jan 25 09:39:13 kernel: [ 0.000000] Disk Index Map: 01 Jan 25 09:39:13 kernel: [ 0.000000] SYNO GPIO hdd detect pin: 0 Jan 25 09:39:13 kernel: [ 0.000000] Vender format version: 2 Jan 25 09:39:13 kernel: [ 0.000000] Power on seq num: 1 Jan 25 09:39:13 kernel: [ 0.000000] Sata Port Map: 4 Jan 25 09:39:13 kernel: [ 0.000000] PID hash table entries: 4096 (order: 3, 3 2768 bytes) Jan 25 09:39:13 kernel: [ 0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes) Jan 25 09:39:13 kernel: [ 0.000000] Inode-cache hash table entries: 524288 (o rder: 10, 4194304 bytes) Jan 25 09:39:13 kernel: [ 0.000000] Memory: 7779768K/8046512K available (5623 K kernel code, 863K rwdata, 1748K rodata, 916K init, 664K bss, 266744K reserved, 0K cma-reserved) Jan 25 09:39:13 kernel: [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0 , CPUs=4, Nodes=1 Jan 25 09:39:13 kernel: [ 0.000000] Hierarchical RCU implementation. Jan 25 09:39:13 kernel: [ 0.000000] Build-time adjustment of leaf fanout to 64. Jan 25 09:39:13 kernel: [ 0.000000] RCU restricting CPUs from NR_CPUS=8 to n r_cpu_ids=4. Jan 25 09:39:13 kernel: [ 0.000000] RCU: Adjusting geometry for rcu_fanout_le af=64, nr_cpu_ids=4 Jan 25 09:39:13 kernel: [ 0.000000] NR_IRQS:4352 nr_irqs:1024 16 Jan 25 09:39:13 kernel: [ 0.000000] Console: colour dummy device 80x25 Jan 25 09:39:13 kernel: [ 0.000000] clocksource: hpet: mask: 0xffffffff max_c ycles: 0xffffffff, max_idle_ns: 79635855245 ns Jan 25 09:39:13 kernel: [ 0.000000] hpet clockevent registered Jan 25 09:39:13 kernel: [ 0.000000] tsc: Unable to calibrate against PIT Jan 25 09:39:13 kernel: [ 0.000000] tsc: using HPET reference calibration Jan 25 09:39:13 kernel: [ 0.000000] tsc: Detected 3600.089 MHz processor Jan 25 09:39:13 kernel: [ 0.000001] Calibrating delay loop (skipped), value c alculated using timer frequency.. 7200.17 BogoMIPS (lpj=3600089) Jan 25 09:39:13 kernel: [ 0.000877] pid_max: default: 32768 minimum: 301 Jan 25 09:39:13 kernel: [ 0.001288] ACPI: Core revision 20150930 Jan 25 09:39:13 kernel: [ 0.021164] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] N amespace lookup failure, AE_NOT_FOUND (20150930/dswload-210) Jan 25 09:39:13 kernel: [ 0.022066] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20150930/psobject-238) Jan 25 09:39:13 kernel: [ 0.022802] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_kb l_s) while loading table (20150930/tbxfload-193) Jan 25 09:39:13 kernel: [ 0.025803] ACPI Error: 1 table load failures, 7 succ essful (20150930/tbxfload-214) Jan 25 09:39:13 kernel: [ 0.026489] Security Framework initialized Jan 25 09:39:13 kernel: [ 0.026832] AppArmor: AppArmor initialized Jan 25 09:39:13 kernel: [ 0.027201] Mount-cache hash table entries: 16384 (or der: 5, 131072 bytes) Jan 25 09:39:13 kernel: [ 0.027763] Mountpoint-cache hash table entries: 1638 4 (order: 5, 131072 bytes) Jan 25 09:39:13 kernel: [ 0.028506] Initializing cgroup subsys io Jan 25 09:39:13 kernel: [ 0.028840] Initializing cgroup subsys memory Jan 25 09:39:13 kernel: [ 0.029229] Initializing cgroup subsys devices Jan 25 09:39:13 kernel: [ 0.029598] Initializing cgroup subsys freezer Jan 25 09:39:13 kernel: [ 0.030006] CPU: Physical Processor ID: 0 Jan 25 09:39:13 kernel: [ 0.030339] CPU: Processor Core ID: 0 Jan 25 09:39:13 kernel: [ 0.030648] ENERGY_PERF_BIAS: Set to 'normal', was 'p erformance' Jan 25 09:39:13 kernel: [ 0.031166] ENERGY_PERF_BIAS: View and update with x8 6_energy_perf_policy(8) Jan 25 09:39:13 kernel: [ 0.032771] mce: CPU supports 10 MCE banks Jan 25 09:39:13 kernel: [ 0.033150] CPU0: Thermal monitoring enabled (TM1) Jan 25 09:39:13 kernel: [ 0.033553] process: using mwait in idle threads Jan 25 09:39:13 kernel: [ 0.033963] Last level iTLB entries: 4KB 128, 2MB 8, 4MB 8 Jan 25 09:39:13 kernel: [ 0.034414] Last level dTLB entries: 4KB 64, 2MB 0, 4 MB 0, 1GB 4 Jan 25 09:39:13 kernel: [ 0.034936] Speculative Store Bypass: Vulnerable Jan 25 09:39:13 kernel: [ 0.035577] Freeing SMP alternatives memory: 24K Jan 25 09:39:13 kernel: [ 0.040089] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2 =-1 pin2=-1 Jan 25 09:39:13 kernel: [ 0.050588] TSC deadline timer enabled Jan 25 09:39:13 kernel: [ 0.050905] smpboot: CPU0: Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz (family: 0x6, model: 0x9e, stepping: 0xb) Jan 25 09:39:13 kernel: [ 0.051755] Performance Events: PEBS fmt3+, generic a rchitected perfmon, full-width counters, Intel PMU driver. Jan 25 09:39:13 kernel: [ 0.052632] ... version: 4 Jan 25 09:39:13 kernel: [ 0.052965] ... bit width: 48 Jan 25 09:39:13 kernel: [ 0.053307] ... generic registers: 8 Jan 25 09:39:13 kernel: [ 0.053640] ... value mask: 0000fffffffff fff Jan 25 09:39:13 kernel: [ 0.054078] ... max period: 00007ffffffff fff Jan 25 09:39:13 kernel: [ 0.054517] ... fixed-purpose events: 3 Jan 25 09:39:13 kernel: [ 0.054850] ... event mask: 0000000700000 0ff Jan 25 09:39:13 kernel: [ 0.055427] x86: Booting SMP configuration: Jan 25 09:39:13 kernel: [ 0.055776] .... node #0, CPUs: #1 #2 #3 Jan 25 09:39:13 kernel: [ 0.066529] x86: Booted up 1 node, 4 CPUs Jan 25 09:39:13 kernel: [ 0.066891] smpboot: Total of 4 processors activated (28800.71 BogoMIPS) Jan 25 09:39:13 kernel: [ 0.069400] NMI watchdog: enabled on all CPUs, perman ently consumes one hw-PMU counter. Jan 25 09:39:13 kernel: [ 0.070198] devtmpfs: initialized Jan 25 09:39:13 kernel: [ 0.070622] PM: Registering ACPI NVS region [mem 0x72 262000-0x72262fff] (4096 bytes) Jan 25 09:39:13 kernel: [ 0.071254] PM: Registering ACPI NVS region [mem 0x7e 06c000-0x7e414fff] (3837952 bytes) Jan 25 09:39:13 kernel: [ 0.071969] clocksource: jiffies: mask: 0xffffffff ma x_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns Jan 25 09:39:13 kernel: [ 0.072764] futex hash table entries: 1024 (order: 4, 65536 bytes) Jan 25 09:39:13 kernel: [ 0.073323] pinctrl core: initialized pinctrl subsyst em Jan 25 09:39:13 kernel: [ 0.073827] NET: Registered protocol family 16 Jan 25 09:39:13 kernel: [ 0.079297] cpuidle: using governor ladder Jan 25 09:39:13 kernel: [ 0.084310] cpuidle: using governor menu Jan 25 09:39:13 kernel: [ 0.084690] ACPI FADT declares the system doesn't sup port PCIe ASPM, so disable it Jan 25 09:39:13 kernel: [ 0.085310] ACPI: bus type PCI registered Jan 25 09:39:13 kernel: [ 0.085679] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000) Jan 25 09:39:13 kernel: [ 0.086438] PCI: MMCONFIG at [mem 0xe0000000-0xefffff ff] reserved in E820 Jan 25 09:39:13 kernel: [ 0.086999] PCI: Using configuration type 1 for base access Jan 25 09:39:13 kernel: [ 0.092660] ACPI: Added _OSI(Module Device) Jan 25 09:39:13 kernel: [ 0.093007] ACPI: Added _OSI(Processor Device) Jan 25 09:39:13 kernel: [ 0.093376] ACPI: Added _OSI(3.0 _SCP Extensions) Jan 25 09:39:13 kernel: [ 0.093780] ACPI: Added _OSI(Processor Aggregator Dev ice) Jan 25 09:39:13 kernel: [ 0.098432] ACPI Exception: AE_BAD_PARAMETER, Could n ot install PciConfig handler for Root Bridge PCI0 (20150930/evrgnini-244) Jan 25 09:39:13 kernel: [ 0.101432] ACPI: Executed 30 blocks of module-level executable AML code Jan 25 09:39:13 kernel: [ 0.106573] ACPI: Dynamic OEM Table Load: Jan 25 09:39:13 kernel: [ 0.106938] ACPI: SSDT 0xFFFF880263FA1800 000738 (v02 PmRef Cpu0Ist 00003000 INTL 20160422) Jan 25 09:39:13 kernel: [ 0.108148] ACPI: Executed 1 blocks of module-level e xecutable AML code Jan 25 09:39:13 kernel: [ 0.108758] ACPI: \_PR_.PR00: _OSC native thermal LVT Acked Jan 25 09:39:13 kernel: [ 0.109916] ACPI: Dynamic OEM Table Load: Jan 25 09:39:13 kernel: [ 0.110279] ACPI: SSDT 0xFFFF880263E69400 0003FF (v02 PmRef Cpu0Cst 00003001 INTL 20160422) Jan 25 09:39:13 kernel: [ 0.111476] ACPI: Executed 1 blocks of module-level e xecutable AML code Jan 25 09:39:13 kernel: [ 0.112290] ACPI: Dynamic OEM Table Load: Jan 25 09:39:13 kernel: [ 0.112653] ACPI: SSDT 0xFFFF8802636B2000 000D14 (v02 PmRef ApIst 00003000 INTL 20160422) Jan 25 09:39:13 kernel: [ 0.114126] ACPI: Executed 1 blocks of module-level e xecutable AML code Jan 25 09:39:13 kernel: [ 0.114788] ACPI: Dynamic OEM Table Load: Jan 25 09:39:13 kernel: [ 0.115151] ACPI: SSDT 0xFFFF880263E69C00 00030A (v02 PmRef ApCst 00003000 INTL 20160422) Jan 25 09:39:13 kernel: [ 0.116374] ACPI: Executed 1 blocks of module-level e xecutable AML code Jan 25 09:39:13 kernel: [ 0.117774] ACPI: Interpreter enabled Jan 25 09:39:13 kernel: [ 0.118093] ACPI: (supports S0 S4 S5) Jan 25 09:39:13 kernel: [ 0.118398] ACPI: Using IOAPIC for interrupt routing Jan 25 09:39:13 kernel: [ 0.118877] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug Jan 25 09:39:13 kernel: [ 0.130712] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe]) Jan 25 09:39:13 kernel: [ 0.131223] acpi PNP0A08:00: _OSC: OS supports [Exten dedConfig ASPM ClockPM Segments MSI] Jan 25 09:39:13 kernel: [ 0.131970] acpi PNP0A08:00: _OSC: platform does not support [PME] Jan 25 09:39:13 kernel: [ 0.132550] acpi PNP0A08:00: _OSC: OS now controls [A ER PCIeCapability] Jan 25 09:39:13 kernel: [ 0.133093] acpi PNP0A08:00: FADT indicates ASPM is u nsupported, using BIOS configuration Jan 25 09:39:13 kernel: [ 0.133946] PCI host bridge to bus 0000:00 Jan 25 09:39:13 kernel: [ 0.134288] pci_bus 0000:00: root bus resource [io 0 x0000-0x0cf7 window] Jan 25 09:39:13 kernel: [ 0.134843] pci_bus 0000:00: root bus resource [io 0 x0d00-0xffff window] Jan 25 09:39:13 kernel: [ 0.135400] pci_bus 0000:00: root bus resource [mem 0 x000a0000-0x000bffff window] Jan 25 09:39:13 kernel: [ 0.136011] pci_bus 0000:00: root bus resource [mem 0 x90000000-0xdfffffff window] Jan 25 09:39:13 kernel: [ 0.136624] pci_bus 0000:00: root bus resource [mem 0 xfd000000-0xfe7fffff window] Jan 25 09:39:13 kernel: [ 0.137236] pci_bus 0000:00: root bus resource [bus 0 0-fe] Jan 25 09:39:13 kernel: [ 0.137693] pci 0000:00:00.0: [8086:3e1f] type 00 cla ss 0x060000 Jan 25 09:39:13 kernel: [ 0.138377] pci 0000:00:02.0: [8086:3e91] type 00 cla ss 0x030000 Jan 25 09:39:13 kernel: [ 0.138881] pci 0000:00:02.0: reg 0x10: [mem 0xde0000 00-0xdeffffff 64bit] Jan 25 09:39:13 kernel: [ 0.139440] pci 0000:00:02.0: reg 0x18: [mem 0xc00000 00-0xcfffffff 64bit pref] Jan 25 09:39:13 kernel: [ 0.140035] pci 0000:00:02.0: reg 0x20: [io 0xf000-0 xf03f] Jan 25 09:39:13 kernel: [ 0.140626] pci 0000:00:14.0: [8086:a2af] type 00 cla ss 0x0c0330 Jan 25 09:39:13 kernel: [ 0.141143] pci 0000:00:14.0: reg 0x10: [mem 0xdf0300 00-0xdf03ffff 64bit] Jan 25 09:39:13 kernel: [ 0.141743] pci 0000:00:14.0: PME# supported from D3h ot D3cold Jan 25 09:39:13 kernel: [ 0.142323] pci 0000:00:14.0: System wakeup disabled by ACPI Jan 25 09:39:13 kernel: [ 0.142812] pci 0000:00:14.2: [8086:a2b1] type 00 cla ss 0x118000 Jan 25 09:39:13 kernel: [ 0.143328] pci 0000:00:14.2: reg 0x10: [mem 0xdf04e0 00-0xdf04efff 64bit] Jan 25 09:39:13 kernel: [ 0.144000] pci 0000:00:16.0: [8086:a2ba] type 00 cla ss 0x078000 Jan 25 09:39:13 kernel: [ 0.144516] pci 0000:00:16.0: reg 0x10: [mem 0xdf04d0 00-0xdf04dfff 64bit] Jan 25 09:39:13 kernel: [ 0.145106] pci 0000:00:16.0: PME# supported from D3h ot Jan 25 09:39:13 kernel: [ 0.145653] pci 0000:00:17.0: [8086:a282] type 00 cla ss 0x010601 Jan 25 09:39:13 kernel: [ 0.146163] pci 0000:00:17.0: reg 0x10: [mem 0xdf0480 00-0xdf049fff] Jan 25 09:39:13 kernel: [ 0.146684] pci 0000:00:17.0: reg 0x14: [mem 0xdf04c0 00-0xdf04c0ff] Jan 25 09:39:13 kernel: [ 0.147203] pci 0000:00:17.0: reg 0x18: [io 0xf090-0 xf097] Jan 25 09:39:13 kernel: [ 0.147667] pci 0000:00:17.0: reg 0x1c: [io 0xf080-0 xf083] Jan 25 09:39:13 kernel: [ 0.148131] pci 0000:00:17.0: reg 0x20: [io 0xf060-0 xf07f] Jan 25 09:39:13 kernel: [ 0.148594] pci 0000:00:17.0: reg 0x24: [mem 0xdf04b0 00-0xdf04b7ff] Jan 25 09:39:13 kernel: [ 0.149133] pci 0000:00:17.0: PME# supported from D3h ot Jan 25 09:39:13 kernel: [ 0.149661] pci 0000:00:1f.0: [8086:a2cc] type 00 cla ss 0x060100 Jan 25 09:39:13 kernel: [ 0.150318] pci 0000:00:1f.2: [8086:a2a1] type 00 cla ss 0x058000 Jan 25 09:39:13 kernel: [ 0.150822] pci 0000:00:1f.2: reg 0x10: [mem 0xdf0440 00-0xdf047fff] Jan 25 09:39:13 kernel: [ 0.151453] pci 0000:00:1f.3: [8086:a2f0] type 00 cla ss 0x040300 Jan 25 09:39:13 kernel: [ 0.151977] pci 0000:00:1f.3: reg 0x10: [mem 0xdf0400 00-0xdf043fff 64bit] Jan 25 09:39:13 kernel: [ 0.152561] pci 0000:00:1f.3: reg 0x20: [mem 0xdf0200 00-0xdf02ffff 64bit] Jan 25 09:39:13 kernel: [ 0.153146] pci 0000:00:1f.3: PME# supported from D3h ot D3cold Jan 25 09:39:13 kernel: [ 0.153744] pci 0000:00:1f.3: System wakeup disabled by ACPI Jan 25 09:39:13 kernel: [ 0.154236] pci 0000:00:1f.4: [8086:a2a3] type 00 cla ss 0x0c0500 Jan 25 09:39:13 kernel: [ 0.154782] pci 0000:00:1f.4: reg 0x10: [mem 0xdf04a0 00-0xdf04a0ff 64bit] Jan 25 09:39:13 kernel: [ 0.155407] pci 0000:00:1f.4: reg 0x20: [io 0xf040-0 xf05f] Jan 25 09:39:13 kernel: [ 0.156010] pci 0000:00:1f.6: [8086:15b8] type 00 cla ss 0x020000 Jan 25 09:39:13 kernel: [ 0.156537] pci 0000:00:1f.6: reg 0x10: [mem 0xdf0000 00-0xdf01ffff] Jan 25 09:39:13 kernel: [ 0.157135] pci 0000:00:1f.6: PME# supported from D0 D3hot D3cold Jan 25 09:39:13 kernel: [ 0.157700] pci 0000:00:1f.6: System wakeup disabled by ACPI Jan 25 09:39:13 kernel: [ 0.158182] pci_bus 0000:00: on NUMA node 0 Jan 25 09:39:13 kernel: [ 0.159222] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15) Jan 25 09:39:13 kernel: [ 0.159968] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15) Jan 25 09:39:13 kernel: [ 0.160712] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15) Jan 25 09:39:13 kernel: [ 0.161457] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15) Jan 25 09:39:13 kernel: [ 0.162201] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 *11 12 14 15) Jan 25 09:39:13 kernel: [ 0.162945] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 *11 12 14 15) Jan 25 09:39:13 kernel: [ 0.163689] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15) Jan 25 09:39:13 kernel: [ 0.164433] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15) Jan 25 09:39:13 kernel: [ 0.165305] ACPI: Enabled 6 GPEs in block 00 to 7F Jan 25 09:39:13 kernel: [ 0.165797] vgaarb: setting as boot device: PCI:0000: 00:02.0 Jan 25 09:39:13 kernel: [ 0.166263] vgaarb: device added: PCI:0000:00:02.0,de codes=io+mem,owns=io+mem,locks=none Jan 25 09:39:13 kernel: [ 0.166926] vgaarb: loaded Jan 25 09:39:13 kernel: [ 0.167155] vgaarb: bridge control possible 0000:00:0 2.0 Jan 25 09:39:13 kernel: [ 0.167628] SCSI subsystem initialized Jan 25 09:39:13 kernel: [ 0.167967] libata version 3.00 loaded. Jan 25 09:39:13 kernel: [ 0.168313] pps_core: LinuxPPS API ver. 1 registered Jan 25 09:39:13 kernel: [ 0.168725] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> Jan 25 09:39:13 kernel: [ 0.169471] PTP clock support registered Jan 25 09:39:13 kernel: [ 0.169858] PCI: Using ACPI for IRQ routing Jan 25 09:39:13 kernel: [ 0.198366] PCI: pci_cache_line_size set to 64 bytes Jan 25 09:39:13 kernel: [ 0.198806] e820: reserve RAM buffer [mem 0x0009c400- 0x0009ffff] Jan 25 09:39:13 kernel: [ 0.199300] e820: reserve RAM buffer [mem 0x72262000- 0x73ffffff] Jan 25 09:39:13 kernel: [ 0.199797] e820: reserve RAM buffer [mem 0x7c4f4000- 0x7fffffff] Jan 25 09:39:13 kernel: [ 0.200291] e820: reserve RAM buffer [mem 0x7e06c000- 0x7fffffff] Jan 25 09:39:13 kernel: [ 0.200785] e820: reserve RAM buffer [mem 0x7f000000- 0x7fffffff] Jan 25 09:39:13 kernel: [ 0.201283] e820: reserve RAM buffer [mem 0x26f000000 -0x26fffffff] Jan 25 09:39:13 kernel: [ 0.201935] clocksource: Switched to clocksource hpet Jan 25 09:39:13 kernel: [ 0.206653] AppArmor: AppArmor Filesystem Enabled Jan 25 09:39:13 kernel: [ 0.207158] pnp: PnP ACPI init Jan 25 09:39:13 kernel: [ 0.207592] system 00:00: [io 0x0280-0x028f] has bee n reserved Jan 25 09:39:13 kernel: [ 0.208215] system 00:00: [io 0x0290-0x029f] has bee n reserved Jan 25 09:39:13 kernel: [ 0.208701] system 00:00: [io 0x02a0-0x02af] has bee n reserved Jan 25 09:39:13 kernel: [ 0.209300] system 00:00: [io 0x02b0-0x02bf] has bee n reserved Jan 25 09:39:13 kernel: [ 0.209788] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active) Jan 25 09:39:13 kernel: [ 0.210531] system 00:01: [io 0x0680-0x069f] has bee n reserved Jan 25 09:39:13 kernel: [ 0.211155] system 00:01: [io 0xffff] has been reser ved Jan 25 09:39:13 kernel: [ 0.211592] system 00:01: [io 0xffff] has been reser ved Jan 25 09:39:13 kernel: [ 0.212121] system 00:01: [io 0xffff] has been reser ved Jan 25 09:39:13 kernel: [ 0.212559] system 00:01: [io 0x1800-0x18fe] has bee n reserved Jan 25 09:39:13 kernel: [ 0.213140] system 00:01: [io 0x164e-0x164f] has bee n reserved Jan 25 09:39:13 kernel: [ 0.213628] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active) Jan 25 09:39:13 kernel: [ 0.214331] system 00:02: [io 0x0800-0x087f] has bee n reserved Jan 25 09:39:13 kernel: [ 0.214843] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active) Jan 25 09:39:13 kernel: [ 0.215506] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active) Jan 25 09:39:13 kernel: [ 0.216178] system 00:04: [io 0x1854-0x1857] has bee n reserved Jan 25 09:39:13 kernel: [ 0.216690] system 00:04: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active) Jan 25 09:39:13 kernel: [ 0.217534] system 00:05: [mem 0xfed10000-0xfed17fff] has been reserved Jan 25 09:39:13 kernel: [ 0.218205] system 00:05: [mem 0xfed18000-0xfed18fff] has been reserved Jan 25 09:39:13 kernel: [ 0.218748] system 00:05: [mem 0xfed19000-0xfed19fff] has been reserved Jan 25 09:39:13 kernel: [ 0.219387] system 00:05: [mem 0xe0000000-0xefffffff] has been reserved Jan 25 09:39:13 kernel: [ 0.219983] system 00:05: [mem 0xfed20000-0xfed3ffff] has been reserved Jan 25 09:39:13 kernel: [ 0.220564] system 00:05: [mem 0xfed90000-0xfed93fff] has been reserved Jan 25 09:39:13 kernel: [ 0.221202] system 00:05: [mem 0xfed45000-0xfed8ffff] has been reserved Jan 25 09:39:13 kernel: [ 0.221743] system 00:05: [mem 0xff000000-0xffffffff] has been reserved Jan 25 09:39:13 kernel: [ 0.222381] system 00:05: [mem 0xfee00000-0xfeefffff] could not be reserved Jan 25 09:39:13 kernel: [ 0.223049] system 00:05: [mem 0xdffe0000-0xdfffffff] has been reserved Jan 25 09:39:13 kernel: [ 0.223591] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active) Jan 25 09:39:13 kernel: [ 0.224273] system 00:06: [mem 0xfd000000-0xfdabffff] has been reserved Jan 25 09:39:13 kernel: [ 0.224840] system 00:06: [mem 0xfdad0000-0xfdadffff] has been reserved Jan 25 09:39:13 kernel: [ 0.225476] system 00:06: [mem 0xfdb00000-0xfdffffff] has been reserved Jan 25 09:39:13 kernel: [ 0.226121] system 00:06: [mem 0xfe000000-0xfe01ffff] could not be reserved Jan 25 09:39:13 kernel: [ 0.226691] system 00:06: [mem 0xfe036000-0xfe03bfff] has been reserved Jan 25 09:39:13 kernel: [ 0.227329] system 00:06: [mem 0xfe03d000-0xfe3fffff] has been reserved Jan 25 09:39:13 kernel: [ 0.227871] system 00:06: [mem 0xfe410000-0xfe7fffff] has been reserved Jan 25 09:39:13 kernel: [ 0.228508] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active) Jan 25 09:39:13 kernel: [ 0.229342] system 00:07: [io 0xff00-0xfffe] has bee n reserved Jan 25 09:39:13 kernel: [ 0.229853] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active) Jan 25 09:39:13 kernel: [ 0.231181] system 00:08: [mem 0xfdaf0000-0xfdafffff] has been reserved Jan 25 09:39:13 kernel: [ 0.231748] system 00:08: [mem 0xfdae0000-0xfdaeffff] has been reserved Jan 25 09:39:13 kernel: [ 0.232386] system 00:08: [mem 0xfdac0000-0xfdacffff] has been reserved Jan 25 09:39:13 kernel: [ 0.233018] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active) Jan 25 09:39:13 kernel: [ 0.233998] system 00:09: [mem 0x40000000-0x403fffff] has been reserved Jan 25 09:39:13 kernel: [ 0.234579] system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active) Jan 25 09:39:13 kernel: [ 0.235377] pnp: PnP ACPI: found 10 devices Jan 25 09:39:13 kernel: [ 0.243561] clocksource: acpi_pm: mask: 0xffffff max_ cycles: 0xffffff, max_idle_ns: 2085701024 ns Jan 25 09:39:13 kernel: [ 0.244375] pci_bus 0000:00: resource 4 [io 0x0000-0 x0cf7 window] Jan 25 09:39:13 kernel: [ 0.244883] pci_bus 0000:00: resource 5 [io 0x0d00-0 xffff window] Jan 25 09:39:13 kernel: [ 0.245486] pci_bus 0000:00: resource 6 [mem 0x000a00 00-0x000bffff window] Jan 25 09:39:13 kernel: [ 0.246143] pci_bus 0000:00: resource 7 [mem 0x900000 00-0xdfffffff window] Jan 25 09:39:13 kernel: [ 0.246706] pci_bus 0000:00: resource 8 [mem 0xfd0000 00-0xfe7fffff window] Jan 25 09:39:13 kernel: [ 0.247380] NET: Registered protocol family 2 Jan 25 09:39:13 kernel: [ 0.247808] TCP established hash table entries: 65536 (order: 7, 524288 bytes) Jan 25 09:39:13 kernel: [ 0.248540] TCP bind hash table entries: 65536 (order : 8, 1048576 bytes) Jan 25 09:39:13 kernel: [ 0.249259] TCP: Hash tables configured (established 65536 bind 65536) Jan 25 09:39:13 kernel: [ 0.249803] UDP hash table entries: 4096 (order: 5, 1 31072 bytes) Jan 25 09:39:13 kernel: [ 0.250400] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes) Jan 25 09:39:13 kernel: [ 0.251046] NET: Registered protocol family 1 Jan 25 09:39:13 kernel: [ 0.251416] pci 0000:00:02.0: Video device with shado wed ROM Jan 25 09:39:13 kernel: [ 0.252328] PCI: CLS 64 bytes, default 64 Jan 25 09:39:13 kernel: [ 0.513786] Trying to unpack rootfs image as initramf s... Jan 25 09:39:13 kernel: [ 0.521403] Freeing initrd memory: 17176K Jan 25 09:39:13 kernel: [ 0.522509] redpill: loading out-of-tree module taint s kernel. Jan 25 09:39:13 kernel: [ 0.523134] redpill: module verification failed: sign ature and/or required key missing - tainting kernel Jan 25 09:39:13 kernel: [ 0.541298] PCI host bridge to bus 0001:01 Jan 25 09:39:13 kernel: [ 0.541688] pci_bus 0001:01: root bus resource [io 0 x0000-0xffff] Jan 25 09:39:13 kernel: [ 0.542273] pci_bus 0001:01: root bus resource [mem 0 x00000000-0x7fffffffff] Jan 25 09:39:13 kernel: [ 0.542851] pci_bus 0001:01: root bus resource [bus 0 0-ff] Jan 25 09:39:13 kernel: [ 0.543401] pci 0001:01:00.0: [1b4b:9215] type 00 cla ss 0x010601 Jan 25 09:39:13 kernel: [ 0.544050] pci 0001:01:00.0: Can't map mv9235 regist ers Jan 25 09:39:13 kernel: [ 0.544603] PCI host bridge to bus 0001:02 Jan 25 09:39:13 kernel: [ 0.545133] pci_bus 0001:02: root bus resource [io 0 x0000-0xffff] Jan 25 09:39:13 kernel: [ 0.545785] pci_bus 0001:02: root bus resource [mem 0 x00000000-0x7fffffffff] Jan 25 09:39:13 kernel: [ 0.546521] pci_bus 0001:02: busn_res: can not insert [bus 02-ff] under domain [bus 00-ff] (conflicts with (null) [bus 01-ff]) Jan 25 09:39:13 kernel: [ 0.547532] pci_bus 0001:02: root bus resource [bus 0 0-ff] Jan 25 09:39:13 kernel: [ 0.548071] pci 0001:02:00.0: [8086:1539] type 00 cla ss 0x020000 Jan 25 09:39:13 kernel: [ 0.548593] PCI host bridge to bus 0001:03 Jan 25 09:39:13 kernel: [ 0.549116] pci_bus 0001:03: root bus resource [io 0 x0000-0xffff] Jan 25 09:39:13 kernel: [ 0.549723] pci_bus 0001:03: root bus resource [mem 0 x00000000-0x7fffffffff] Jan 25 09:39:13 kernel: [ 0.550477] pci_bus 0001:03: busn_res: can not insert [bus 03-ff] under domain [bus 00-ff] (conflicts with (null) [bus 01-ff]) Jan 25 09:39:13 kernel: [ 0.551487] pci_bus 0001:03: root bus resource [bus 0 0-ff] Jan 25 09:39:13 kernel: [ 0.552021] pci 0001:03:00.0: [8086:1539] type 00 cla ss 0x020000 Jan 25 09:39:13 kernel: [ 0.552550] PCI host bridge to bus 0001:00 Jan 25 09:39:13 kernel: [ 0.553056] pci_bus 0001:00: root bus resource [io 0 x0000-0xffff] Jan 25 09:39:13 kernel: [ 0.553662] pci_bus 0001:00: root bus resource [mem 0 x00000000-0x7fffffffff] Jan 25 09:39:13 kernel: [ 0.554433] pci_bus 0001:00: busn_res: can not insert [bus 00-ff] under domain [bus 00-ff] (conflicts with (null) [bus 01-ff]) Jan 25 09:39:13 kernel: [ 0.555443] pci_bus 0001:00: root bus resource [bus 0 0-ff] Jan 25 09:39:13 kernel: [ 0.555897] pci 0001:00:12.0: [8086:5ae3] type 00 cla ss 0x010601 Jan 25 09:39:13 kernel: [ 0.556501] pci 0001:00:13.0: [8086:5ad8] type 00 cla ss 0x060400 Jan 25 09:39:13 kernel: [ 0.557136] pci 0001:00:13.0: ignoring class 0x060400 (doesn't match header type 00) Jan 25 09:39:13 kernel: [ 0.557876] pci 0001:00:14.0: [8086:5ad6] type 00 cla ss 0x060400 Jan 25 09:39:13 kernel: [ 0.558524] pci 0001:00:14.0: ignoring class 0x060400 (doesn't match header type 00) Jan 25 09:39:13 kernel: [ 0.559342] pci 0001:00:15.0: [8086:5aa8] type 00 cla ss 0x0c0330 Jan 25 09:39:13 kernel: [ 0.560013] pci 0001:00:16.0: [8086:5aac] type 00 cla ss 0x118000 Jan 25 09:39:13 kernel: [ 0.560700] pci 0001:00:18.0: [8086:5abc] type 00 cla ss 0x118000 Jan 25 09:39:13 kernel: [ 0.561368] pci 0001:00:19.0: [8086:5ac6] type 00 cla ss 0x118000 Jan 25 09:39:13 kernel: [ 0.562062] pci 0001:00:19.2: [8086:5ac6] type 00 cla ss 0x118000 Jan 25 09:39:13 kernel: [ 0.562608] pci 0001:00:1f.0: [8086:5ad4] type 00 cla ss 0x0c0500 Jan 25 09:39:13 kernel: [ 0.563243] pci 0001:00:1f.1: [8086:5ad4] type 00 cla ss 0x0c0500 Jan 25 09:39:13 kernel: [ 0.572680] DMAR: Host address width 39 Jan 25 09:39:13 kernel: [ 0.573105] DMAR: DRHD base: 0x000000fed90000 flags: 0x0 Jan 25 09:39:13 kernel: [ 0.573550] DMAR: dmar0: reg_base_addr fed90000 ver 1 :0 cap 1c0000c40660462 ecap 19e2ff0505e Jan 25 09:39:13 kernel: [ 0.574350] DMAR: DRHD base: 0x000000fed91000 flags: 0x1 Jan 25 09:39:13 kernel: [ 0.574790] DMAR: dmar1: reg_base_addr fed91000 ver 1 :0 cap d2008c40660462 ecap f050da Jan 25 09:39:13 kernel: [ 0.575531] DMAR: RMRR base: 0x0000007eb4a000 end: 0x 0000007ed93fff Jan 25 09:39:13 kernel: [ 0.576149] DMAR: RMRR base: 0x0000007f800000 end: 0x 0000008fffffff Jan 25 09:39:13 kernel: [ 0.576670] DMAR: No ATSR found Jan 25 09:39:13 kernel: [ 0.577084] DMAR: dmar0: Using Queued invalidation Jan 25 09:39:13 kernel: [ 0.577483] DMAR: dmar1: Using Queued invalidation Jan 25 09:39:13 kernel: [ 0.578093] DMAR: Setting RMRR: Jan 25 09:39:13 kernel: [ 0.578366] DMAR: Setting identity map for device 000 0:00:02.0 [0x7f800000 - 0x8fffffff] Jan 25 09:39:13 kernel: [ 0.579129] DMAR: Setting identity map for device 000 0:00:14.0 [0x7eb4a000 - 0x7ed93fff] Jan 25 09:39:13 kernel: [ 0.579796] DMAR: Prepare 0-16MiB unity mapping for L PC Jan 25 09:39:13 kernel: [ 0.580341] DMAR: Setting identity map for device 000 0:00:1f.0 [0x0 - 0xffffff] Jan 25 09:39:13 kernel: [ 0.581219] DMAR: Intel(R) Virtualization Technology for Directed I/O Jan 25 09:39:13 kernel: [ 0.581780] iommu: Adding device 0000:00:00.0 to grou p 0 Jan 25 09:39:13 kernel: [ 0.582396] iommu: Adding device 0000:00:02.0 to grou p 1 Jan 25 09:39:13 kernel: [ 0.583039] iommu: Adding device 0000:00:14.0 to grou p 2 Jan 25 09:39:13 kernel: [ 0.583585] iommu: Adding device 0000:00:14.2 to grou p 2 Jan 25 09:39:13 kernel: [ 0.584124] iommu: Adding device 0000:00:16.0 to grou p 3 Jan 25 09:39:13 kernel: [ 0.584566] iommu: Adding device 0000:00:17.0 to grou p 4 Jan 25 09:39:13 kernel: [ 0.585108] iommu: Adding device 0000:00:1f.0 to grou p 5 Jan 25 09:39:13 kernel: [ 0.585550] iommu: Adding device 0000:00:1f.2 to grou p 5 Jan 25 09:39:13 kernel: [ 0.586083] iommu: Adding device 0000:00:1f.3 to grou p 5 Jan 25 09:39:13 kernel: [ 0.586525] iommu: Adding device 0000:00:1f.4 to grou p 5 Jan 25 09:39:13 kernel: [ 0.587071] iommu: Adding device 0000:00:1f.6 to grou p 6 Jan 25 09:39:13 kernel: [ 0.588873] audit: initializing netlink subsys (disab led) Jan 25 09:39:13 kernel: [ 0.589458] audit: type=2000 audit(1643103535.583:1): initialized Jan 25 09:39:13 kernel: [ 0.590172] Initialise system trusted keyring Jan 25 09:39:13 kernel: [ 0.605171] VFS: Disk quotas dquot_6.6.0 Jan 25 09:39:13 kernel: [ 0.605543] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Jan 25 09:39:13 kernel: [ 0.657819] Key type asymmetric registered Jan 25 09:39:13 kernel: [ 0.658223] Asymmetric key parser 'x509' registered Jan 25 09:39:13 kernel: [ 0.658666] Block layer SCSI generic (bsg) driver ver sion 0.4 loaded (major 251) Jan 25 09:39:13 kernel: [ 0.659508] io scheduler noop registered Jan 25 09:39:13 kernel: [ 0.659981] io scheduler deadline registered Jan 25 09:39:13 kernel: [ 0.660405] io scheduler cfq registered (default) Jan 25 09:39:13 kernel: [ 0.672157] Serial: 8250/16550 driver, 4 ports, IRQ s haring enabled Jan 25 09:39:13 kernel: [ 0.693183] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A Jan 25 09:39:13 kernel: [ 0.693973] console [ttyS0] enabled Jan 25 09:39:13 kernel: [ 0.694623] bootconsole [uart0] disabled Jan 25 09:39:13 kernel: [ 0.881585] Linux agpgart interface v0.103 Jan 25 09:39:13 kernel: [ 0.884597] brd: module loaded Jan 25 09:39:13 kernel: [ 0.884996] intel-lpss: probe of 0001:00:16.0 failed with error -22 Jan 25 09:39:13 kernel: [ 0.885569] intel-lpss: probe of 0001:00:18.0 failed with error -22 Jan 25 09:39:13 kernel: [ 0.886231] intel-lpss: probe of 0001:00:19.0 failed with error -22 Jan 25 09:39:13 kernel: [ 0.886808] intel-lpss: probe of 0001:00:19.2 failed with error -22 Jan 25 09:39:13 kernel: [ 0.887462] Loading iSCSI transport class v2.0-870. Jan 25 09:39:13 kernel: [ 0.892293] ahci 0000:00:17.0: version 3.0 Jan 25 09:39:13 kernel: [ 0.892819] ahci 0000:00:17.0: AHCI 0001.0301 32 slot s 5 ports 6 Gbps 0x3e impl SATA mode Jan 25 09:39:13 kernel: [ 0.893596] ahci 0000:00:17.0: flags: 64bit ncq sntf led clo only pio slum part ems deso sadm sds apst Jan 25 09:39:13 kernel: [ 0.904662] scsi host0: ahci Jan 25 09:39:13 kernel: [ 0.912464] scsi host1: ahci Jan 25 09:39:13 kernel: [ 0.918234] scsi host2: ahci Jan 25 09:39:13 kernel: [ 0.921767] scsi host3: ahci Jan 25 09:39:13 kernel: [ 0.922143] ata1: DUMMY Jan 25 09:39:13 kernel: [ 0.922353] ata2: SATA max UDMA/133 abar m2048@0xdf04 b000 port 0xdf04b180 irq 122 Jan 25 09:39:13 kernel: [ 0.923073] ata3: SATA max UDMA/133 abar m2048@0xdf04 b000 port 0xdf04b200 irq 122 Jan 25 09:39:13 kernel: [ 0.923721] ata4: SATA max UDMA/133 abar m2048@0xdf04 b000 port 0xdf04b280 irq 122 Jan 25 09:39:13 kernel: [ 0.924460] ata1: send port disabled event Jan 25 09:39:13 kernel: [ 0.924829] ata1: No present pin info for send port d isabled event Jan 25 09:39:13 kernel: [ 1.229936] ata2: SATA link down (SStatus 4 SControl 300) Jan 25 09:39:13 kernel: [ 1.230398] ata2: No present pin info for SATA link d own event Jan 25 09:39:13 kernel: [ 1.536927] ata3: SATA link down (SStatus 4 SControl 300) Jan 25 09:39:13 kernel: [ 1.537387] ata3: No present pin info for SATA link d own event Jan 25 09:39:13 kernel: [ 1.589935] tsc: Refined TSC clocksource calibration: 3600.020 MHz Jan 25 09:39:13 kernel: [ 1.590459] clocksource: tsc: mask: 0xfffffffffffffff f max_cycles: 0x33e4660c5e7, max_idle_ns: 440795263402 ns Jan 25 09:39:13 kernel: [ 1.842921] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Jan 25 09:39:13 kernel: [ 1.844329] ata4.00: ACPI cmd ef/10:06:00:00:00:00 (S ET FEATURES) succeeded Jan 25 09:39:13 kernel: [ 1.844920] ata4.00: ACPI cmd f5/00:00:00:00:00:00 (S ECURITY FREEZE LOCK) filtered out Jan 25 09:39:13 kernel: [ 1.845566] ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (D EVICE CONFIGURATION OVERLAY) filtered out Jan 25 09:39:13 kernel: [ 1.846806] ata4.00: ATA-7: TOSHIBA MK8040GSX, AH001C , max UDMA/100 Jan 25 09:39:13 kernel: [ 1.847352] ata4.00: 156301488 sectors, multi 16: LBA 48 Jan 25 09:39:13 kernel: [ 1.847790] ata4.00: SN: 76HH2728S Jan 25 09:39:13 kernel: [ 1.849105] ata4.00: ACPI cmd ef/10:06:00:00:00:00 (S ET FEATURES) succeeded Jan 25 09:39:13 kernel: [ 1.849675] ata4.00: ACPI cmd f5/00:00:00:00:00:00 (S ECURITY FREEZE LOCK) filtered out Jan 25 09:39:13 kernel: [ 1.850340] ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (D EVICE CONFIGURATION OVERLAY) filtered out Jan 25 09:39:13 kernel: [ 1.851577] ata4.00: configured for UDMA/100 Jan 25 09:39:13 kernel: [ 1.852785] scsi 3:0:0:0: Direct-Access TOSHIBA MK8040GSX 1C PQ: 0 ANSI: 5 Jan 25 09:39:13 kernel: [ 1.853728] ahci: probe of 0001:01:00.0 failed with e rror -22 Jan 25 09:39:13 kernel: [ 1.853765] sd 3:0:0:0: [sde] 156301488 512-byte logi cal blocks: (80.0 GB/74.5 GiB) Jan 25 09:39:13 kernel: [ 1.853846] sd 3:0:0:0: [sde] Write Protect is off Jan 25 09:39:13 kernel: [ 1.853847] sd 3:0:0:0: [sde] Mode Sense: 00 3a 00 00 Jan 25 09:39:13 kernel: [ 1.853974] sd 3:0:0:0: [sde] Write cache: enabled, r ead cache: enabled, doesn't support DPO or FUA Jan 25 09:39:13 kernel: [ 1.857156] ahci: probe of 0001:00:12.0 failed with e rror -22 Jan 25 09:39:13 kernel: [ 1.857705] i2c /dev entries driver Jan 25 09:39:13 kernel: [ 1.858142] i801_smbus 0001:00:1f.0: SMBus base addre ss uninitialized, upgrade BIOS Jan 25 09:39:13 kernel: [ 1.858828] i801_smbus 0001:00:1f.1: SMBus base addre ss uninitialized, upgrade BIOS Jan 25 09:39:13 kernel: [ 1.859647] md: raid1 personality registered for leve l 1 Jan 25 09:39:13 kernel: [ 1.860242] NET: Registered protocol family 17 Jan 25 09:39:13 kernel: [ 1.860638] Key type dns_resolver registered Jan 25 09:39:13 kernel: [ 1.861403] registered taskstats version 1 Jan 25 09:39:13 kernel: [ 1.861775] Loading compiled-in untrusted X.509 certi ficates Jan 25 09:39:13 kernel: [ 1.862357] Loading compiled-in X.509 certificates Jan 25 09:39:13 kernel: [ 1.862820] Loaded X.509 cert 'Synology SDG kernel mo dule signing key: 7bd0b0d6bcd31651c22ce3978bdc8c8bdc417329' Jan 25 09:39:13 kernel: [ 1.864339] Loaded X.509 cert 'Synology Root Certific ation Authority: f2c075361f168425f8b5ef31b796406c3aab2089' Jan 25 09:39:13 kernel: [ 1.865303] Loaded X.509 cert 'Synology Kernel Module Signing Certification Authority: 600839b5d127e0e11d817a31f0575d323a7c0e28' Jan 25 09:39:13 kernel: [ 1.866360] Loaded X.509 cert 'Synology kernel module signing key: 4646ce54489669338118a3b1286da156ac366fa5' Jan 25 09:39:13 kernel: [ 1.867253] page_owner is disabled Jan 25 09:39:13 kernel: [ 1.867593] AppArmor: AppArmor sha1 policy hashing en abled Jan 25 09:39:13 kernel: [ 1.868645] hctosys: unable to open rtc device (rtc0) Jan 25 09:39:13 kernel: [ 2.367037] sde: sde1 sde2 sde3 Jan 25 09:39:13 kernel: [ 2.367625] sd 3:0:0:0: [sde] Attached SCSI disk Jan 25 09:39:13 kernel: [ 2.368620] Freeing unused kernel memory: 916K Jan 25 09:39:13 kernel: [ 2.369093] Write protecting the kernel read-only dat a: 8192k Jan 25 09:39:13 kernel: [ 2.369725] Freeing unused kernel memory: 508K Jan 25 09:39:13 kernel: [ 2.370541] Freeing unused kernel memory: 300K Jan 25 09:39:13 kernel: [ 2.400012] ACPI: bus type USB registered Jan 25 09:39:13 kernel: [ 2.400400] usbcore: registered new interface driver usbfs Jan 25 09:39:13 kernel: [ 2.400987] usbcore: registered new interface driver hub Jan 25 09:39:13 kernel: [ 2.401479] usbcore: registered new interface driver ethub Jan 25 09:39:13 kernel: [ 2.402060] usbcore: registered new device driver usb Jan 25 09:39:13 kernel: [ 2.411800] xhci_hcd 0000:00:14.0: xHCI Host Controll er Jan 25 09:39:13 kernel: [ 2.412379] xhci_hcd 0000:00:14.0: new USB bus regist ered, assigned bus number 1 Jan 25 09:39:13 kernel: [ 2.614238] xhci_hcd 0000:00:14.0: hcc params 0x20007 7c1 hci version 0x100 quirks 0x00009010 Jan 25 09:39:13 kernel: [ 2.615001] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported Jan 25 09:39:13 kernel: [ 2.615609] clocksource: Switched to clocksource tsc Jan 25 09:39:13 kernel: [ 2.615709] hub 1-0:1.0: USB hub found Jan 25 09:39:13 kernel: [ 2.615768] hub 1-0:1.0: 16 ports detected Jan 25 09:39:13 kernel: [ 2.616051] xhci_hcd 0000:00:14.0: xHCI Host Controll er Jan 25 09:39:13 kernel: [ 2.616053] xhci_hcd 0000:00:14.0: new USB bus regist ered, assigned bus number 2 Jan 25 09:39:13 kernel: [ 2.616129] usb usb2: We don't know the algorithms fo r LPM for this host, disabling LPM. Jan 25 09:39:13 kernel: [ 2.616195] hub 2-0:1.0: USB hub found Jan 25 09:39:13 kernel: [ 2.616224] hub 2-0:1.0: 8 ports detected Jan 25 09:39:13 kernel: [ 2.616388] xhci_hcd 0001:00:15.0: init 0001:00:15.0 fail, -16 Jan 25 09:39:13 kernel: [ 2.616389] xhci_hcd: probe of 0001:00:15.0 failed wi th error -16 Jan 25 09:39:13 kernel: [ 2.624623] usbcore: registered new interface driver usb-storage Jan 25 09:39:13 kernel: [ 2.628789] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.4-NAPI Jan 25 09:39:13 kernel: [ 2.629305] e1000e: Copyright(c) 1999 - 2020 Intel Co rporation. Jan 25 09:39:13 kernel: [ 2.629931] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode Jan 25 09:39:13 kernel: [ 2.926617] e1000e 0000:00:1f.6 eth0: (PCI Express:2. 5GT/s:Width x1) 70:85:c2:d7:4b:db Jan 25 09:39:13 kernel: [ 2.927267] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/10 00 Network Connection Jan 25 09:39:13 kernel: [ 2.927880] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 1 2, PBA No: FFFFFF-0FF Jan 25 09:39:13 kernel: [ 2.938861] usb 1-1: new high-speed USB device number 2 using xhci_hcd Jan 25 09:39:13 kernel: [ 3.074637] usb 1-1: ep 0x81 - rounding interval to 1 28 microframes, ep desc says 255 microframes Jan 25 09:39:13 kernel: [ 3.075364] usb 1-1: ep 0x2 - rounding interval to 12 8 microframes, ep desc says 255 microframes Jan 25 09:39:13 kernel: [ 3.076311] usb-storage 1-1:1.0: USB Mass Storage dev ice detected Jan 25 09:39:13 kernel: [ 3.076861] scsi host4: usb-storage 1-1:1.0 Jan 25 09:39:13 kernel: [ 4.238204] scsi 4:0:0:0: Direct-Access Kingston DT 101 II 1.00 PQ: 0 ANSI: 2 Jan 25 09:39:13 kernel: [ 4.239526] sd 4:0:0:0: [synoboot] 3905407 512-byte l ogical blocks: (2.00 GB/1.86 GiB) Jan 25 09:39:13 kernel: [ 4.240354] sd 4:0:0:0: [synoboot] Write Protect is o ff Jan 25 09:39:13 kernel: [ 4.240786] sd 4:0:0:0: [synoboot] Mode Sense: 0b 00 00 08 Jan 25 09:39:13 kernel: [ 4.241416] sd 4:0:0:0: [synoboot] No Caching mode pa ge found Jan 25 09:39:13 kernel: [ 4.241893] sd 4:0:0:0: [synoboot] Assuming drive cac he: write through Jan 25 09:39:13 kernel: [ 4.249028] synoboot: synoboot1 synoboot2 synoboot3 Jan 25 09:39:13 kernel: [ 4.250581] sd 4:0:0:0: [synoboot] Attached SCSI remo vable disk Jan 25 09:39:13 kernel: [ 4.947095] apollolake_synobios: module license 'Syno logy Inc.' taints kernel. Jan 25 09:39:13 kernel: [ 4.947687] Disabling lock debugging due to kernel ta int Jan 25 09:39:13 kernel: [ 4.950986] synobios open /dev/ttyS1 success Jan 25 09:39:13 kernel: [ 4.951341] WARNING: inconsistent syno gpio info, hdd detect Jan 25 09:39:13 kernel: [ 4.951920] 2022-1-25 9:39:0 UTC Jan 25 09:39:13 kernel: [ 4.952191] synobios: load, major number 201 Jan 25 09:39:13 kernel: [ 4.952546] Brand: Synology Jan 25 09:39:13 kernel: [ 4.952809] Model: DS-918+ Jan 25 09:39:13 kernel: [ 4.953052] This is default settings: set group disks wakeup number to 1, spinup time deno 1 Jan 25 09:39:13 kernel: [ 4.953755] synobios cpu_arch proc entry initialized Jan 25 09:39:13 kernel: [ 4.954166] synobios crypto_hw proc entry initialized Jan 25 09:39:13 kernel: [ 4.954582] synobios syno_platform proc entry initial ized Jan 25 09:39:13 kernel: [ 4.957070] Module [apollolake_synobios] is removed. Jan 25 09:39:13 kernel: [ 4.957491] synobios: unload Jan 25 09:39:13 kernel: [ 5.021013] md: md0 stopped. Jan 25 09:39:13 kernel: [ 5.021927] md: bind<sde1> Jan 25 09:39:13 kernel: [ 5.022256] md/raid1:md0: active with 1 out of 16 mir rors Jan 25 09:39:13 kernel: [ 5.033525] md0: detected capacity change from 0 to 2 549940224 Jan 25 09:39:13 kernel: [ 5.431050] random: nonblocking pool is initialized Jan 25 09:39:13 kernel: [ 8.639930] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Jan 25 09:39:13 kernel: [ 8.662420] EXT4-fs (md0): mounted filesystem with or dered data mode. Opts: (null) Jan 25 09:39:13 kernel: [ 16.137689] VFS: opened file in mnt_point: (/dev), fi le: (/null), comm: (inetd) Jan 25 09:39:13 kernel: [ 16.150768] VFS: opened file in mnt_point: (/dev), fi le: (/null), comm: (inetd) Jan 25 09:39:13 kernel: [ 16.193039] md: md1 stopped. Jan 25 09:39:13 kernel: [ 16.193964] md: bind<sde2> Jan 25 09:39:13 kernel: [ 16.194290] md/raid1:md1: active with 1 out of 16 mir rors Jan 25 09:39:13 kernel: [ 16.205973] md1: detected capacity change from 0 to 2 147418112 Jan 25 09:39:13 kernel: [ 16.235159] Adding 2097084k swap on /dev/md1. Priori ty:-1 extents:1 across:2097084k Jan 25 09:39:13 kernel: [ 16.286831] Intel(R) Gigabit Ethernet Linux Driver - version 5.3.5.22 Jan 25 09:39:13 kernel: [ 16.287361] Copyright(c) 2007 - 2018 Intel Corporatio n. Jan 25 09:39:13 kernel: [ 16.287815] igb: probe of 0001:02:00.0 failed with er ror -5 Jan 25 09:39:13 kernel: [ 16.288279] igb: probe of 0001:03:00.0 failed with er ror -5 Jan 25 09:39:13 kernel: [ 16.302296] RPC: Registered named UNIX socket transpo rt module. Jan 25 09:39:13 kernel: [ 16.302786] RPC: Registered udp transport module. Jan 25 09:39:13 kernel: [ 16.303176] RPC: Registered tcp transport module. Jan 25 09:39:13 kernel: [ 16.303565] RPC: Registered tcp NFSv4.1 backchannel t ransport module. Jan 25 09:39:13 kernel: [ 16.325840] synobios open /dev/ttyS1 success Jan 25 09:39:13 kernel: [ 16.326195] WARNING: inconsistent syno gpio info, hdd detect Jan 25 09:39:13 kernel: [ 16.326776] 2022-1-25 9:39:12 UTC Jan 25 09:39:13 kernel: [ 16.327055] synobios: load, major number 201 Jan 25 09:39:13 kernel: [ 16.327410] Brand: Synology Jan 25 09:39:13 kernel: [ 16.327673] Model: DS-918+ Jan 25 09:39:13 kernel: [ 16.327917] This is default settings: set group disks wakeup number to 1, spinup time deno 1 Jan 25 09:39:13 kernel: [ 16.328622] synobios cpu_arch proc entry initialized Jan 25 09:39:13 kernel: [ 16.329032] synobios crypto_hw proc entry initialized Jan 25 09:39:13 kernel: [ 16.329450] synobios syno_platform proc entry initial ized Jan 25 09:39:13 kernel: [ 16.932791] Module [apollolake_synobios] is removed. Jan 25 09:39:13 kernel: [ 16.933211] synobios: unload Jan 25 09:39:13 kernel: [ 16.953070] synobios open /dev/ttyS1 success Jan 25 09:39:13 kernel: [ 16.953426] WARNING: inconsistent syno gpio info, hdd detect Jan 25 09:39:13 kernel: [ 16.954009] 2022-1-25 9:39:12 UTC Jan 25 09:39:13 kernel: [ 16.954287] synobios: load, major number 201 Jan 25 09:39:13 kernel: [ 16.954643] Brand: Synology Jan 25 09:39:13 kernel: [ 16.954906] Model: DS-918+ Jan 25 09:39:13 kernel: [ 16.955149] This is default settings: set group disks wakeup number to 1, spinup time deno 1 Jan 25 09:39:13 kernel: [ 16.955854] synobios cpu_arch proc entry initialized Jan 25 09:39:13 kernel: [ 16.956263] synobios crypto_hw proc entry initialized Jan 25 09:39:13 kernel: [ 16.956682] synobios syno_platform proc entry initial ized Jan 25 09:39:13 scemd: scemd.c:802(main) start scemd Jan 25 09:39:17 kernel: [ 22.042264] e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Jan 25 09:39:17 udhcpc: networking/udhcp/synoether.c (172) MAC address of interf ace eth0 is [00:11:32:2a:46:e7] Jan 25 09:39:17 udhcpc: networking/udhcp/synoether.c (280) Broadcasting ARPOP_RE QUEST for 169.254.12.68 Jan 25 09:39:20 avahi-daemon[5974]: /etc/avahi/services/http.service: parse fail ure: service group incomplete. Jan 25 09:39:20 avahi-daemon[5974]: Failed to load service group file /etc/avahi /services/http.service, ignoring. Jan 25 09:39:20 findhostd: ninstaller.c:683 Dev: sde, DiskPath: /dev/sde, Partit ion version: 8 Jan 25 09:39:20 findhostd: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:39:20 kernel: [ 25.351087] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Jan 25 09:39:20 kernel: [ 25.356431] usbcore: registered new interface driver usbhid Jan 25 09:39:20 kernel: [ 25.356891] usbhid: USB HID core driver insmod: can't insert '/lib/modules/syno_hddmon.ko': Operation not permitted Jan 25 09:39:20 kernel: [ 25.384585] EXT4-fs (md0): mounted filesystem with or dered data mode. Opts: (null) Jan 25 09:39:20 synohwctrl: invalid microp command 16388 Jan 25 09:39:20 getty[6113]: tcgetattr: Input/output error^M Jan 25 09:39:20 findhostd: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:39:23 synoagentregisterd: synoagentregisterd.c:129 Generating register key... Jan 25 09:39:23 synoagentregisterd: synoagentregisterd.c:143 Generated register key [0570F32E.FA29.450C.87C1.1D06C9218295]. Jan 25 09:39:23 findhostd: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:39:23 kernel: [ 28.940029] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Jan 25 09:39:24 kernel: [ 28.962472] EXT4-fs (md0): mounted filesystem with or dered data mode. Opts: (null) Jan 25 09:39:24 findhostd: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:39:24 findhostd: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:39:24 kernel: [ 29.028915] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Jan 25 09:39:24 kernel: [ 29.040253] EXT4-fs (md0): mounted filesystem with or dered data mode. Opts: (null) Jan 25 09:39:24 findhostd: ninstaller.c:494 fail to get admin port from /tmpRoot /etc/synoinfo.conf... try another way Jan 25 09:39:24 findhostd: ninstaller.c:858 flash version is newer than disk ver sion Jan 25 09:39:24 findhostd: ninstaller.c:1207 SYSTEM_NORMAL, [Recoverable=0] Jan 25 09:39:24 findhostd: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:39:24 findhostd: ninstaller.c:1114(FillUpgradeVolumeInfo): gszUpgradeV olDev = /dev/md0 Jan 25 09:39:24 findhostd: ninstaller.c:1115(FillUpgradeVolumeInfo): gszUpgradeV olMnt = /tmpData Jan 25 09:39:24 findhostd: ninstaller.c:1223 gblSupportRaid: 1, gSysStatus: 1, g blCreateDataVol: 0, gblSystemRecoverable: 0 Jan 25 09:39:30 getty[6136]: tcgetattr: Input/output error^M Jan 25 09:39:40 getty[6138]: tcgetattr: Input/output error^M Jan 25 09:39:50 getty[6163]: tcgetattr: Input/output error^M Jan 25 09:40:00 getty[6165]: tcgetattr: Input/output error^M Jan 25 09:40:10 getty[6182]: tcgetattr: Input/output error^M Jan 25 09:40:22 getty[6223]: tcgetattr: Input/output error^M Jan 25 09:40:32 getty[6224]: tcgetattr: Input/output error^M Jan 25 09:40:39 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk' Jan 25 09:40:39 kernel: [ 102.740253] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Jan 25 09:40:39 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero Jan 25 09:40:39 synoupgrade: get_disk_dsm_version.c:99 try reading disk dsm's ve rsion at file '/_disk//etc.defaults/VERSION' of key 'buildnumber' Jan 25 09:40:39 kernel: [ 102.773788] EXT4-fs (md0): mounted filesystem with or dered data mode. Opts: (null) Jan 25 09:40:39 synoupgrade: autocleanup/mount.c:44 run '/usr/bin/umount -l /_di sk' Jan 25 09:40:39 synoupgrade: autocleanup/mount.c:54 umount's exit status is zero Jan 25 09:40:39 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0 Jan 25 09:40:40 synoupgrade: ninstaller.c:683 Dev: sde, DiskPath: /dev/sde, Part ition version: 8 Jan 25 09:40:40 synoupgrade: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:40:40 kernel: [ 103.884704] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Jan 25 09:40:40 kernel: [ 103.918268] EXT4-fs (md0): mounted filesystem with or dered data mode. Opts: (null) Jan 25 09:40:40 synoupgrade: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:40:42 getty[6292]: tcgetattr: Input/output error^M Jan 25 09:40:44 synoupgrade: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:40:44 kernel: [ 107.495901] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Jan 25 09:40:44 kernel: [ 107.518289] EXT4-fs (md0): mounted filesystem with or dered data mode. Opts: (null) Jan 25 09:40:44 synoupgrade: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:40:44 synoupgrade: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:40:44 kernel: [ 107.584731] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Jan 25 09:40:44 kernel: [ 107.596002] EXT4-fs (md0): mounted filesystem with or dered data mode. Opts: (null) Jan 25 09:40:44 synoupgrade: ninstaller.c:494 fail to get admin port from /tmpRo ot/etc/synoinfo.conf... try another way Jan 25 09:40:44 synoupgrade: ninstaller.c:858 flash version is newer than disk v ersion Jan 25 09:40:44 synoupgrade: ninstaller.c:1207 SYSTEM_NORMAL, [Recoverable=0] Jan 25 09:40:44 synoupgrade: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:40:44 synoupgrade: ninstaller.c:1114(FillUpgradeVolumeInfo): gszUpgrad eVolDev = /dev/md0 Jan 25 09:40:44 synoupgrade: ninstaller.c:1115(FillUpgradeVolumeInfo): gszUpgrad eVolMnt = /tmpData Jan 25 09:40:44 synoupgrade: ninstaller.c:1223 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0 Jan 25 09:40:52 getty[6347]: tcgetattr: Input/output error^M Jan 25 09:41:02 getty[6348]: tcgetattr: Input/output error^M Jan 25 09:41:12 getty[6351]: tcgetattr: Input/output error^M Jan 25 09:41:13 login[6350]: root login on 'pts/0' Jan 25 09:41:22 getty[6361]: tcgetattr: Input/output error^M Jan 25 09:41:32 getty[6362]: tcgetattr: Input/output error^M Edited January 25, 2022 by soulcola Quote Link to comment Share on other sites More sharing options...
PincoPalla Posted January 25, 2022 Share #542 Posted January 25, 2022 13 hours ago, Dvalin21 said: Can you write out something to show how you got it up and running on Virtualbox? Would most appreciate it!! Awesome job!! Hello, actually it's very easy, it's like in vmware, only the commands are placed in different places, the machine is in virtualbox (like Linux oracle 64bit) I have configured 2048Mb of ram and 2 cpu (so I just have to do tests) , in the network section make sure you have selected network bridge and put aside the mac it gives you, now you have to take the RedPill image (redpill-DS918 + _7.0.1-42218_b1635406499), start Xpenology_Tool_V142 and with OSFMount open the image and select the first one (48Gb, make sure Read only drive is not checked) open the local disk boot / grub / grub.cfg at the bottom go to modify (both in the section for usb and in that for sata disk) the mac with the one that gave you the machine creation (if you want you can also modify the s / n with one that you always get from the xpenology tool, save, close and unmount the disk, open the local disk boot / grub / grub.cfg at the bottom go to modify (both in the section for usb and in that for sata disk) the mac with the one that gave you the machine creation (if you want you can also modify the s / n with one that always comes from the xpenology tool, save, close and unmount the disk, start StartwindV2v converter load the image and create a startup file vmdk (growable image). at this point meii of two files (image and vmdk in the created folder from virtualbox go to the storage section, select SATA controllers and add the vmdk file, then create hard drives always the same section you need, close and start the machine, "it should" start then the procedure is always the same, find.synology.com etc. etc. .putting it like this seems difficult, but on the practical and very easy side just follow what I wrote to you step by step 1 Quote Link to comment Share on other sites More sharing options...
Cubitus Posted January 25, 2022 Share #543 Posted January 25, 2022 Hi everybody This morning I tried again upgrading my DSM (DS918 + Jun loader + DSM6.2.3 upd2) to DSM7.0.1 As it was not working yesterday with DS918+ conf I restarted from scratch with DS3615xs model. But results is the same : the system boots on the usb dongle and states disks errors when trying to upgrade. Below are the trace I could made accessing the system via telnet. If anyone could help ! New USB key balena etcher tinycore img from pocopico github Prepare the user_config : sudo ./rploader.sh update now sudo ./rploader.sh identifyusb now sudo ./rploader.sh satamap now SataPortMap=6 DiskIdxMap=00 sudo ./rploader.sh serialgen DS3615xs now sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubuser (don't know if strictly necessary ?) sudo ./rploader.sh build bromolow-7.0.1-42218 -- BOOT on the new key with existing disks -- http://192.168.1.13:5000/webman/start_telnet.cgi (on web browser) {"success": true} -- START a putty session -- DiskStation login: root Synology strongly advises you not to run commands as the root user, who has the highest privileges on the system. Doing so may cause major damages to the system. Please note that if you choose to proceed, all consequences are at your own risk. -- CHECK for disks -- DiskStation> fdisk -l Disk /dev/sde: 932 GB, 1000204886016 bytes, 1953525168 sectors 121601 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sde1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sde2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect /dev/sde3 587,111,37 1023,254,63 9437184 1953292287 1943855104 926G fd Linux raid autodetect Disk /dev/sdf: 932 GB, 1000204886016 bytes, 1953525168 sectors 121601 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdf1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sdf2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect /dev/sdf3 587,111,37 1023,254,63 9437184 1953292287 1943855104 926G fd Linux raid autodetect Disk /dev/sdc: 233 GB, 250059350016 bytes, 488397168 sectors 30401 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdc1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sdc2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect /dev/sdc3 587,111,37 1023,254,63 9437184 488192351 478755168 228G fd Linux raid autodetect Disk /dev/synoboot: 15 GB, 15833497600 bytes, 30924800 sectors 15100 cylinders, 64 heads, 32 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/synoboot1 * 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux /dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux /dev/synoboot3 15,205,63 130,138,8 253952 2097151 1843200 900M 83 Linux Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors 622544 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors 524272 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md1 doesn't contain a valid partition table -- HERE IS THE CONTENT OF LOG FILE -- DiskStat DiskStation> cat linuxrc.syno.log START /linuxrc.syno.impl Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module ehci-hcd ... [ OK ] :: Loading module ehci-pci ... [ OK ] :: Loading module uhci-hcd ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: ) Loading kmod #0 "mpt2sas.ko" for pocopico.mpt2sas (args: ) Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script Checking for VirtIO *No* VirtIO hypervisor detected NOT loading kmods for thethorgroup.virtio :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000e.sh" for pocopico.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for pocopico.e1000e->on_boot - exit=0 Running "check-mpt2sas.sh" for pocopico.mpt2sas->on_boot Loading module mpt2sas -> Module mpt2sas loaded succesfully Ran "check-mpt2sas.sh" for pocopico.mpt2sas->on_boot - exit=0 Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Still waiting for boot device (waited 4 of 30 seconds) Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0 :: Executing "on_boot" custom scripts ... [ OK ] Extensions processed Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 All disk ready or timeout execeed Assemble args: -u fc4d7be4:b0512f9f:3017a5a8:c86610be /dev/sdc1 /dev/sde1 /dev/sdf1 mdadm: /dev/md0 has been started with 3 drives (out of 16). Partition Version=8 /sbin/e2fsck exists, checking /dev/md0... e2fsck 1.44.1 (24-Mar-2018) /sbin/e2fsck -yvf returns 0 Mounting /dev/md0 /tmpRoot ------------upgrade Begin upgrade procedure Mount data partition: /dev/md0 -> /tmpData No upgrade file exists End upgrade procedure ============upgrade ------------bootup-smallupdate Try bootup smallupdate Total: 22 packages {"action":"stop","id":"MariaDB10","status":"skip"} {"action":"stop","id":"FileStation","status":"begin"} {"action":"stop","id":"FileStation","status":"end"} {"action":"stop","id":"SynologyMoments","status":"begin"} {"action":"stop","id":"SynologyDrive","status":"begin"} {"action":"stop","id":"SynoFinder","status":"begin"} {"action":"stop","id":"SynoFinder","status":"end"} {"action":"stop","id":"Virtualization","status":"begin"} {"action":"stop","id":"ReplicationService","status":"begin"} {"action":"stop","id":"ReplicationService","status":"end"} {"action":"stop","id":"SynologyApplicationService","status":"begin"} {"action":"stop","id":"Docker","status":"begin"} {"action":"stop","id":"phpMyAdmin","status":"begin"} {"action":"stop","id":"PHP7.3","status":"begin"} {"action":"stop","id":"MediaServer","status":"begin"} {"action":"stop","id":"Node.js_v12","status":"begin"} {"action":"stop","id":"syncthing.net","status":"begin"} {"action":"stop","id":"MariaDB","status":"begin"} {"action":"stop","id":"DownloadStation","status":"begin"} {"action":"stop","id":"VideoStation","status":"begin"} {"action":"stop","id":"AudioStation","status":"begin"} {"action":"stop","id":"OAuthService","status":"begin"} {"action":"stop","id":"OAuthService","status":"end"} {"action":"stop","id":"LogCenter","status":"begin"} {"action":"stop","id":"HyperBackup","status":"begin"} {"action":"stop","id":"WebStation","status":"begin"} Failed to stop all packages 150 BOOTUP_UPGRADE_SMALLUPDATE No new update to download Fail to bootup smallupdate Failed to synoupgrade --bootup-smallupdate [255] Exit on error [6] bootup-smallupdate failed... Tue Jan 25 09:07:31 UTC 2022 /dev/md0 /tmpRoot ext4 rw,relatime,journal_checksum,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0ion> Quote Link to comment Share on other sites More sharing options...
Cubitus Posted January 25, 2022 Share #544 Posted January 25, 2022 Hi again, Some more log from 'messages.log' : seems there is an error with md0 & md1 file systems. So what shall be done ? Jan 25 09:47:30 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk' Jan 25 09:47:30 kernel: [ 2401.714377] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:30 kernel: [ 2401.715176] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:30 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero Jan 25 09:47:30 synoupgrade: get_disk_dsm_version.c:99 try reading disk dsm's version at file '/_disk//etc.defaults/VERSION' of key 'buildnumber' Jan 25 09:47:30 synoupgrade: autocleanup/mount.c:44 run '/usr/bin/umount -l /_disk' Jan 25 09:47:30 kernel: [ 2401.753718] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jan 25 09:47:30 synoupgrade: autocleanup/mount.c:54 umount's exit status is zero Jan 25 09:47:30 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0 Jan 25 09:47:31 synoupgrade: ninstaller.c:683 Dev: sdc, DiskPath: /dev/sdc, Partition version: 8 Jan 25 09:47:31 synoupgrade: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:47:31 kernel: [ 2402.570349] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.571156] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.628869] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jan 25 09:47:31 synoupgrade: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:47:31 synoupgrade: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:47:31 kernel: [ 2402.945713] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.946507] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.955562] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jan 25 09:47:31 synoupgrade: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:47:31 synoupgrade: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:47:31 kernel: [ 2402.967834] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.968587] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.977562] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jan 25 09:47:31 synoupgrade: ninstaller.c:494 fail to get admin port from /tmpRoot/etc/synoinfo.conf... try another way Jan 25 09:47:31 synoupgrade: ninstaller.c:847 unique not match Jan 25 09:47:31 synoupgrade: ninstaller.c:1207 SYSTEM_NORMAL, [Recoverable=0] Jan 25 09:47:31 synoupgrade: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:47:31 synoupgrade: ninstaller.c:1114(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0 Jan 25 09:47:31 synoupgrade: ninstaller.c:1115(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData Jan 25 09:47:31 synoupgrade: ninstaller.c:1223 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0 Quote Link to comment Share on other sites More sharing options...
adamadam Posted January 25, 2022 Share #545 Posted January 25, 2022 I had a similar one. turn on hirens boot USB and remove all partitions from disks helped me Quote Link to comment Share on other sites More sharing options...
adamadam Posted January 25, 2022 Share #546 Posted January 25, 2022 1 hour ago, Cubitus said: Hi again, Some more log from 'messages.log' : seems there is an error with md0 & md1 file systems. So what shall be done ? Jan 25 09:47:30 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk' Jan 25 09:47:30 kernel: [ 2401.714377] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:30 kernel: [ 2401.715176] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:30 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero Jan 25 09:47:30 synoupgrade: get_disk_dsm_version.c:99 try reading disk dsm's version at file '/_disk//etc.defaults/VERSION' of key 'buildnumber' Jan 25 09:47:30 synoupgrade: autocleanup/mount.c:44 run '/usr/bin/umount -l /_disk' Jan 25 09:47:30 kernel: [ 2401.753718] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jan 25 09:47:30 synoupgrade: autocleanup/mount.c:54 umount's exit status is zero Jan 25 09:47:30 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0 Jan 25 09:47:31 synoupgrade: ninstaller.c:683 Dev: sdc, DiskPath: /dev/sdc, Partition version: 8 Jan 25 09:47:31 synoupgrade: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:47:31 kernel: [ 2402.570349] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.571156] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.628869] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jan 25 09:47:31 synoupgrade: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:47:31 synoupgrade: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:47:31 kernel: [ 2402.945713] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.946507] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.955562] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jan 25 09:47:31 synoupgrade: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:47:31 synoupgrade: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:47:31 kernel: [ 2402.967834] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.968587] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.977562] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jan 25 09:47:31 synoupgrade: ninstaller.c:494 fail to get admin port from /tmpRoot/etc/synoinfo.conf... try another way Jan 25 09:47:31 synoupgrade: ninstaller.c:847 unique not match Jan 25 09:47:31 synoupgrade: ninstaller.c:1207 SYSTEM_NORMAL, [Recoverable=0] Jan 25 09:47:31 synoupgrade: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:47:31 synoupgrade: ninstaller.c:1114(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0 Jan 25 09:47:31 synoupgrade: ninstaller.c:1115(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData Jan 25 09:47:31 synoupgrade: ninstaller.c:1223 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0 I had a similar one. turn on hirens boot USB and remove all partitions from disks helped me Quote Link to comment Share on other sites More sharing options...
soulcola Posted January 25, 2022 Share #547 Posted January 25, 2022 47 минут назад, adamadam сказал: I had a similar one. turn on hirens boot USB and remove all partitions from disks helped me What you mean? What is hirens boot USB? Quote Link to comment Share on other sites More sharing options...
adamadam Posted January 25, 2022 Share #548 Posted January 25, 2022 1 minute ago, soulcola said: What you mean? What is hirens boot USB? https://www.hirensbootcd.org/usb-booting/ Quote Link to comment Share on other sites More sharing options...
soulcola Posted January 25, 2022 Share #549 Posted January 25, 2022 You use hirens instead tinycore? Quote Link to comment Share on other sites More sharing options...
Cubitus Posted January 25, 2022 Share #550 Posted January 25, 2022 @adamadam Do you mean I boot the system onto 'Hirens' and use it to remove partitions from the disks ? But that will delete my current system whereas I want to upgrade it, unless you refer to other disks ? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.