NooL Posted October 18, 2022 Share #126 Posted October 18, 2022 Thank you If it's any help this is the VM: First PCI device is SATA controller Second is Intel X520-T2 Dual port NIC. 1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted October 18, 2022 Author Share #127 Posted October 18, 2022 (edited) 3 hours ago, NooL said: Thank you If it's any help this is the VM: First PCI device is SATA controller Second is Intel X520-T2 Dual port NIC. The hardware settings of my proxmox are as follows: I can't figure out how to set PCIE passthrough in proxmox. I've been looking for a way to enable IOMMU, but I can't find a well-written guide. Is this guide for PCIE? I didn't proceed as it was because it seemed to end with the content about the GPU. Most of the guides only describe GPU pass-through. Edited October 18, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
NooL Posted October 18, 2022 Share #128 Posted October 18, 2022 Hi Peter Its just a matter of clicking Add Device (Pci device) selecting the one you want to pass through and thats it, perhaps select "All Functions" but thats it Not sure why its failing on my end as this is a fairly simple setup. Any idea why are those conf folders missing for RS3618xs? They are there for all the other models - Seems like an error somewhere? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted October 19, 2022 Author Share #129 Posted October 19, 2022 (edited) 7 hours ago, NooL said: Hi Peter Its just a matter of clicking Add Device (Pci device) selecting the one you want to pass through and thats it, perhaps select "All Functions" but thats it Not sure why its failing on my end as this is a fairly simple setup. Any idea why are those conf folders missing for RS3618xs? They are there for all the other models - Seems like an error somewhere? I am currently checking for possible conflicts between ixgbe, the Intel 10Gbps nic extension driver for RS3618xs, and the vanilla ixgbe extension driver built into DSM. https://www.synology.com/en-us/products/RS3618xs The specification description for this model mentions that Intel 10Gbps is also supported. RS3618xs is based on the same Broadwell platform as the original DS3615xs. I haven't been able to find the specification manual for DS3615xs yet, so I'm trying to compare it. It's an older model, so it doesn't seem to support Intel 10Gbps. ixgbe is currently being added by the automatic extension driver addition function of my.sh and rploader.sh. On Broadwellnk platforms like DS3622xs+, when ixgbe is automatically added, it actually conflicts with the vanilla ixgbe extension driver built into DSM. This part has already been raised as an issue several times in pocopico's rp-ext repo. https://github.com/pocopico/rp-ext/issues/103 https://github.com/pocopico/rp-ext/issues/143 The solution at that time was to adjust the loader build time so that ixgbe was not automatically added. First of all, you should check that there are no driver conflicts in your junior log. It looks like you have already added a virtual serial port. Select xterm.js at the bottom of the console button combo on the right and connect to the serial port Send the junior log by command as below. cat /var/log/*rc* Edited October 19, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted October 19, 2022 Author Share #130 Posted October 19, 2022 [Notice of modification of m shell function] The Broadwellnk platform has a vanilla.ixgbe ext driver built into the DSM, so they conflict with each other if ixgbe is added separately. So, the following 3 DS3622xs+, DS1621xs+, RS4021xs+ Broadwellnk platform models will automatically delete the ixgbe ext driver even if it is automatically added. During loader build with my.sh , you can check the following logs in the middle. Target Platform : broadwellnk Removing: PeterSuh-Q3.ixgbe Reason : The Broadwellnk platform has a vanilla.ixgbe ext driver built into the DSM, so they conflict with each other if ixgbe is added separately. Quote Link to comment Share on other sites More sharing options...
NooL Posted October 19, 2022 Share #131 Posted October 19, 2022 Hi Peter Strange indeed. I tried to capture what I could during the startup, before it shuts down again: (is there a way to save it all to disk as the buffer seems to cut off before i can copy it all?) Spoiler [ 0.705557] PCI host bridge to bus 0001:02 [ 0.705987] pci_bus 0001:02: root bus resource [io 0x0000-0xffff] [ 0.706665] pci_bus 0001:02: root bus resource [mem 0x00000000-0x7fffffffff] [ 0.707359] pci_bus 0001:02: busn_res: can not insert [bus 02-ff] under domain [bus 00-ff] (conflicts with (null) [bus 01-ff]) [ 0.708147] pci_bus 0001:02: root bus resource [bus 00-ff] [ 0.708524] pci 0001:02:00.0: [1b4b:9215] type 00 class 0x010601 [ 0.708957] pci 0001:02:00.0: Can't map mv9235 registers [ 0.709365] PCI host bridge to bus 0001:08 [ 0.709652] pci_bus 0001:08: root bus resource [io 0x0000-0xffff] [ 0.710115] pci_bus 0001:08: root bus resource [mem 0x00000000-0x7fffffffff] [ 0.710664] pci_bus 0001:08: busn_res: can not insert [bus 08-ff] under domain [bus 00-ff] (conflicts with (null) [bus 01-ff]) [ 0.711492] pci_bus 0001:08: root bus resource [bus 00-ff] [ 0.711891] pci 0001:08:00.0: [1b4b:9235] type 00 class 0x010601 [ 0.712405] pci 0001:08:00.0: Can't map mv9235 registers [ 0.720221] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 0.720870] software IO TLB: mapped [mem 0x7bfd5000-0x7ffd5000] (64MB) [ 0.722616] audit: initializing netlink subsys (disabled) [ 0.723059] audit: type=2000 audit(1666169486.723:1): initialized [ 0.723698] Initialise system trusted keyring [ 0.734896] VFS: Disk quotas dquot_6.6.0 [ 0.735323] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.769652] Key type asymmetric registered [ 0.770142] Asymmetric key parser 'x509' registered [ 0.770686] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [ 0.771528] io scheduler noop registered [ 0.771960] io scheduler deadline registered [ 0.772492] io scheduler cfq registered (default) [ 0.778098] aer 0000:00:1c.0:pcie02: service driver aer loaded [ 0.778890] aer 0000:00:1c.1:pcie02: service driver aer loaded [ 0.779656] aer 0000:00:1c.2:pcie02: service driver aer loaded [ 0.780423] aer 0000:00:1c.3:pcie02: service driver aer loaded [ 0.781084] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt [ 0.781811] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded [ 0.782562] pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt [ 0.783333] pcie_pme 0000:00:1c.1:pcie01: service driver pcie_pme loaded [ 0.784323] pcieport 0000:00:1c.2: Signaling PME through PCIe PME interrupt [ 0.785055] pcie_pme 0000:00:1c.2:pcie01: service driver pcie_pme loaded [ 0.785753] pcieport 0000:00:1c.3: Signaling PME through PCIe PME interrupt [ 0.786497] pcie_pme 0000:00:1c.3:pcie01: service driver pcie_pme loaded [ 0.806514] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 0.829498] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A [ 0.955268] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A [ 0.959709] brd: module loaded [ 0.960259] lpc_ich 0000:00:1f.0: I/O space for GPIO uninitialized [ 0.960993] Loading iSCSI transport class v2.0-870. [ 0.962889] rdac: device handler registered [ 0.970936] i2c /dev entries driver [ 0.971458] i801_smbus 0000:00:1f.3: SMBus using polling [ 0.972571] ahci 0000:00:1f.2: version 3.0 [ 0.973533] ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 6 ports 1.5 Gbps 0x3f impl SATA mode [ 0.974483] ahci 0000:00:1f.2: flags: 64bit ncq only [ 0.980645] scsi host0: ahci [ 0.980959] ata1: SATA max UDMA/133 abar m4096@0xfea1b000 port 0xfea1b100 irq 28 [ 0.982248] ACPI: PCI Interrupt Link [GSIF] enabled at IRQ 21 [ 0.983292] ACPI: PCI Interrupt Link [GSIE] enabled at IRQ 20 [ 0.983892] ahci 0000:06:07.0: AHCI 0001.0000 32 slots 6 ports 1.5 Gbps 0x3f impl SATA mode [ 0.984469] ahci 0000:06:07.0: flags: 64bit ncq only [ 0.987896] scsi host1: ahci [ 0.988263] ata2: SATA max UDMA/133 abar m4096@0xfdf02000 port 0xfdf02100 irq 29 [ 1.004594] ahci 0000:06:10.0: AHCI 0001.0301 32 slots 8 ports 6 Gbps 0xff impl SATA mode [ 1.005498] ahci 0000:06:10.0: flags: 64bit ncq sntf led clo only pio slum part ems deso sadm sds apst [ 1.022961] scsi host2: ahci [ 1.026131] scsi host3: ahci [ 1.028478] scsi host4: ahci [ 1.029351] scsi host5: ahci [ 1.029722] scsi host6: ahci [ 1.030488] scsi host7: ahci [ 1.031362] scsi host8: ahci [ 1.032094] scsi host9: ahci [ 1.032320] ata3: SATA max UDMA/133 abar m2048@0xfdf05000 port 0xfdf05100 irq 30 [ 1.032836] ata4: SATA max UDMA/133 abar m2048@0xfdf05000 port 0xfdf05180 irq 30 [ 1.033353] ata5: SATA max UDMA/133 abar m2048@0xfdf05000 port 0xfdf05200 irq 30 [ 1.033871] ata6: SATA max UDMA/133 abar m2048@0xfdf05000 port 0xfdf05280 irq 30 [ 1.034451] ata7: SATA max UDMA/133 abar m2048@0xfdf05000 port 0xfdf05300 irq 30 [ 1.034973] ata8: SATA max UDMA/133 abar m2048@0xfdf05000 port 0xfdf05380 irq 30 [ 1.035532] ata9: SATA max UDMA/133 abar m2048@0xfdf05000 port 0xfdf05400 irq 30 [ 1.036085] ata10: SATA max UDMA/133 abar m2048@0xfdf05000 port 0xfdf05480 irq 30 [ 1.036636] ahci: probe of 0001:01:00.0 failed with error -22 [ 1.037103] ahci: probe of 0001:02:00.0 failed with error -22 [ 1.037533] ahci: probe of 0001:08:00.0 failed with error -22 [ 1.038057] rtc_cmos 00:03: RTC can wake from S4 [ 1.038547] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0 [ 1.039082] rtc_cmos 00:03: alarms up to one day, y3k, 242 bytes nvram, hpet irqs [ 1.039627] md: raid1 personality registered for level 1 [ 1.040385] NET: Registered protocol family 17 [ 1.040708] Key type dns_resolver registered [ 1.041169] mce: Using 10 MCE banks [ 1.041520] registered taskstats version 1 [ 1.041786] Loading compiled-in untrusted X.509 certificates [ 1.042200] Loading compiled-in X.509 certificates [ 1.042537] Loaded X.509 cert 'Synology SDG kernel module signing key: 7bd0b0d6bcd31651c22ce3978bdc8c8bdc417329' [ 1.043586] Loaded X.509 cert 'Synology Root Certification Authority: f2c075361f168425f8b5ef31b796406c3aab2089' [ 1.044303] Loaded X.509 cert 'Synology Kernel Module Signing Certification Authority: 600839b5d127e0e11d817a31f0575d323a7c0e28' [ 1.045100] Loaded X.509 cert 'Synology kernel module signing key: 4646ce54489669338118a3b1286da156ac366fa5' [ 1.045755] page_owner is disabled [ 1.046029] AppArmor: AppArmor sha1 policy hashing enabled [ 1.049384] rtc_cmos 00:03: setting system clock to 2022-10-19 08:51:27 UTC (1666169487) [ 1.287313] ata1: SATA link down (SStatus 0 SControl 300) [ 1.307117] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 1.307722] ata2.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100 [ 1.308272] ata2.00: 2097152 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 1.308863] ata2.00: SN:QM00013 [ 1.309143] ata2.00: applying bridge limits [ 1.309648] ata2.00: configured for UDMA/100 [ 1.310024] ata2.00: Find SSD disks. [QEMU HARDDISK] [ 1.311232] scsi 1:0:0:0: Direct-Access QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5 [ 1.314831] sd 1:0:0:0: [synoboot] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB) [ 1.315711] sd 1:0:0:0: [synoboot] Write Protect is off [ 1.316329] sd 1:0:0:0: [synoboot] Mode Sense: 00 3a 00 00 [ 1.317028] sd 1:0:0:0: [synoboot] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.327203] synoboot: synoboot1 synoboot2 synoboot3 [ 1.328575] sd 1:0:0:0: [synoboot] Attached SCSI disk [ 1.341118] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.342230] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.342754] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.343335] ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.343941] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.344521] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.345098] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.345681] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.346799] ata9.00: ATA-10: TOSHIBA HDWG480, 0601, max UDMA/133 [ 1.347452] ata9.00: 15628053168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 1.348240] ata9.00: SN: 9160A00CFA3H [ 1.348830] ata10.00: ATA-10: TOSHIBA HDWG480, 0601, max UDMA/133 [ 1.349287] ata10.00: 15628053168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 1.349792] ata10.00: SN: 9140A009FA3H [ 1.352466] ata9.00: configured for UDMA/133 [ 1.353285] ata10.00: configured for UDMA/133 [ 1.395474] ata7.00: disabling queued TRIM support [ 1.395810] ata7.00: ATA-11: WDC WUH721816ALE6L4, PCGNW232, max UDMA/133 [ 1.396302] ata7.00: 31251759104 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 1.396792] ata7.00: SN:2BJ6G5BN [ 1.399394] ata6.00: disabling queued TRIM support [ 1.399724] ata6.00: ATA-11: WDC WUH721816ALE6L4, PCGNW232, max UDMA/133 [ 1.400212] ata6.00: 31251759104 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 1.400700] ata6.00: SN:2CKHAH5N [ 1.403256] ata5.00: disabling queued TRIM support [ 1.403639] ata5.00: ATA-11: WDC WUH721816ALE6L4, PCGNW232, max UDMA/133 [ 1.404250] ata5.00: 31251759104 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 1.404851] ata5.00: SN:2CKGMGGN [ 1.407471] ata7.00: disabling queued TRIM support [ 1.407855] ata7.00: configured for UDMA/133 [ 1.410641] ata6.00: disabling queued TRIM support [ 1.410968] ata6.00: configured for UDMA/133 [ 1.411297] ata8.00: disabling queued TRIM support [ 1.411809] ata8.00: ATA-11: WDC WUH721816ALE6L4, PCGNW680, max UDMA/133 [ 1.412528] ata8.00: 31251759104 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 1.413303] ata8.00: SN:4YG0SDDH [ 1.413638] ata4.00: disabling queued TRIM support [ 1.414092] ata4.00: ATA-11: WDC WUH721816ALE6L4, PCGNW232, max UDMA/133 [ 1.414661] ata4.00: 31251759104 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 1.415313] ata4.00: SN:3WKZZMYK [ 1.415591] ata3.00: disabling queued TRIM support [ 1.415963] ata3.00: ATA-11: WDC WUH721816ALE6L4, PCGNW232, max UDMA/133 [ 1.416451] ata3.00: 31251759104 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 1.416943] ata3.00: SN:2CKHT63J [ 1.417191] ata5.00: disabling queued TRIM support [ 1.417521] ata5.00: configured for UDMA/133 [ 1.422938] ata8.00: disabling queued TRIM support [ 1.423302] ata8.00: configured for UDMA/133 [ 1.423607] ata4.00: disabling queued TRIM support [ 1.423954] ata4.00: configured for UDMA/133 [ 1.424852] ata3.00: disabling queued TRIM support [ 1.425206] ata3.00: configured for UDMA/133 [ 1.426259] scsi 2:0:0:0: Direct-Access WDC WDC WUH721816ALE6L4 W232 PQ: 0 ANSI: 5 [ 1.427385] sd 2:0:0:0: [sda] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB) [ 1.427767] scsi 3:0:0:0: Direct-Access WDC WDC WUH721816ALE6L4 W232 PQ: 0 ANSI: 5 [ 1.428202] sd 3:0:0:0: [sdb] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB) [ 1.428203] sd 3:0:0:0: [sdb] 4096-byte physical blocks [ 1.428336] sd 3:0:0:0: [sdb] Write Protect is off [ 1.428337] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 10 [ 1.428357] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 1.428922] scsi 4:0:0:0: Direct-Access WDC WDC WUH721816ALE6L4 W232 PQ: 0 ANSI: 5 [ 1.429272] sd 4:0:0:0: [sdc] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB) [ 1.429272] sd 4:0:0:0: [sdc] 4096-byte physical blocks [ 1.429371] sd 4:0:0:0: [sdc] Write Protect is off [ 1.429371] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 10 [ 1.429402] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 1.430160] scsi 5:0:0:0: Direct-Access WDC WDC WUH721816ALE6L4 W232 PQ: 0 ANSI: 5 [ 1.430366] sd 5:0:0:0: [sdd] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB) [ 1.430367] sd 5:0:0:0: [sdd] 4096-byte physical blocks [ 1.430491] sd 5:0:0:0: [sdd] Write Protect is off [ 1.430492] sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 10 [ 1.430623] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 1.431847] scsi 6:0:0:0: Direct-Access WDC WDC WUH721816ALE6L4 W232 PQ: 0 ANSI: 5 [ 1.432236] sd 6:0:0:0: [sde] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB) [ 1.432236] sd 6:0:0:0: [sde] 4096-byte physical blocks [ 1.432295] sd 6:0:0:0: [sde] Write Protect is off [ 1.432296] sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 10 [ 1.432329] sd 6:0:0:0: [sde] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 1.433305] scsi 7:0:0:0: Direct-Access WDC WDC WUH721816ALE6L4 W680 PQ: 0 ANSI: 5 [ 1.433510] sd 7:0:0:0: [sdf] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB) [ 1.433510] sd 7:0:0:0: [sdf] 4096-byte physical blocks [ 1.433718] sd 7:0:0:0: [sdf] Write Protect is off [ 1.433719] sd 7:0:0:0: [sdf] Mode Sense: 00 3a 00 10 [ 1.433753] sd 7:0:0:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 1.437731] scsi 8:0:0:0: Direct-Access TOSHIBA HDWG480 0601 PQ: 0 ANSI: 5 [ 1.437936] sd 8:0:0:0: [sdg] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) [ 1.437937] sd 8:0:0:0: [sdg] 4096-byte physical blocks [ 1.438137] sd 8:0:0:0: [sdg] Write Protect is off [ 1.438138] sd 8:0:0:0: [sdg] Mode Sense: 00 3a 00 10 [ 1.438175] sd 8:0:0:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 1.441921] scsi 9:0:0:0: Direct-Access TOSHIBA HDWG480 0601 PQ: 0 ANSI: 5 [ 1.442312] sd 9:0:0:0: [sdh] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) [ 1.442312] sd 9:0:0:0: [sdh] 4096-byte physical blocks [ 1.442467] sd 9:0:0:0: [sdh] Write Protect is off [ 1.442468] sd 9:0:0:0: [sdh] Mode Sense: 00 3a 00 10 [ 1.442500] sd 9:0:0:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 1.456104] sd 2:0:0:0: [sda] 4096-byte physical blocks [ 1.456691] sd 2:0:0:0: [sda] Write Protect is off [ 1.457047] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 10 [ 1.457497] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 1.477489] random: nonblocking pool is initialized [ 1.478136] sdf: sdf1 sdf2 sdf3 [ 1.478338] sdb: sdb1 sdb2 sdb3 [ 1.478527] sdd: sdd1 sdd2 sdd3 [ 1.478736] sde: sde1 sde2 sde3 [ 1.478744] sdc: sdc1 sdc2 sdc3 [ 1.479257] sd 3:0:0:0: [sdb] Attached SCSI disk [ 1.479807] sd 4:0:0:0: [sdc] Attached SCSI disk [ 1.479869] sd 6:0:0:0: [sde] Attached SCSI disk [ 1.480122] sd 5:0:0:0: [sdd] Attached SCSI disk [ 1.482478] sd 7:0:0:0: [sdf] Attached SCSI disk [ 1.490827] sdg: sdg1 sdg2 sdg3 [ 1.491328] sd 8:0:0:0: [sdg] Attached SCSI disk [ 1.495656] sdh: sdh1 sdh2 sdh3 [ 1.496209] sd 9:0:0:0: [sdh] Attached SCSI disk [ 1.510555] sda: sda1 sda2 sda3 [ 1.511530] sd 2:0:0:0: [sda] Attached SCSI disk [ 1.513249] Freeing unused kernel memory: 924K [ 1.513624] Write protecting the kernel read-only data: 8192k [ 1.514684] Freeing unused kernel memory: 584K [ 1.515590] Freeing unused kernel memory: 268K START /linuxrc.syno START /linuxrc.syno.impl Insert Marvell 1475 SATA controller driver Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore[ 1.571880] ACPI: bus type USB registered [ 1.572417] usbcore: registered new interface driver usbfs [ 1.573097] usbcore: registered new interface driver hub [ 1.573839] usbcore: registered new interface driver ethub [ 1.574630] usbcore: registered new device driver usb ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory Insert net driver(Mindspeed only)... [ 1.597661] broadwell_synobios: module license 'Synology Inc.' taints kernel. [ 1.598249] Disabling lock debugging due to kernel taint [ 1.601389] synobios open /dev/ttyS1 success [ 1.601872] 2022-10-19 8:51:28 UTC [ 1.602148] synobios: load, major number 201 [ 1.602467] Brand: Synology [ 1.602679] Model: RS-3618xs [ 1.602907] set group disks wakeup number to 4, spinup time deno 7 [ 1.603423] synobios cpu_arch proc entry initialized [ 1.603761] synobios crypto_hw proc entry initialized [ 1.604145] synobios syno_platform proc entry initialized Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 [ 1.608197] Module [broadwell_synobios] is removed. [ 1.608543] synobios: unload Insert synorbd kernel module Insert synofsbd kernel module Insert sha256 kernel module All disk ready or timeout execeed [ 1.724062] tsc: Refined TSC clocksource calibration: 3600.019 MHz [ 1.724731] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x33e4656411b, max_idle_ns: 440795284465 ns mdadm: No md superblock detected on /dev/sda1. no MD_UUID found for /dev/sda1; try next... mdadm: No md superblock detected on /dev/sdb1. no MD_UUID found for /dev/sdb1; try next... mdadm: No md superblock detected on /dev/sdc1. no MD_UUID found for /dev/sdc1; try next... mdadm: No md superblock detected on /dev/sdd1. no MD_UUID found for /dev/sdd1; try next... mdadm: No md superblock detected on /dev/sde1. no MD_UUID found for /dev/sde1; try next... mdadm: No md superblock detected on /dev/sdf1. no MD_UUID found for /dev/sdf1; try next... Assemble args: -u e62eb1c6:3739c89e:c69de3af:22ddbed7 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1 /dev/sdh1 mdadm: no recogniseable superblock on /dev/sda1 mdadm: no recogniseable superblock on /dev/sdb1 mdadm: no recogniseable superblock on /dev/sdc1 mdadm: no recogniseable superblock on /dev/sdd1 mdadm: no recogniseable superblock on /dev/sde1 mdadm: no recogniseable superblock on /dev/sdf1 [ 1.972472] md: md0 stopped. [ 1.973772] md: bind<sdh1> [ 1.974150] md: bind<sdg1> [ 1.974942] md/raid1:md0: active with 2 out of 16 mirrors [ 2.009351] md0: detected capacity change from 0 to 8589869056 mdadm: /dev/md0 has been started with 2 drives (out of 16). Partition Version=9 [ 2.064420] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 2.106861] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) /sbin/e2fsck exists, checking /dev/md0... e2fsck 1.44.1 (24-Mar-2018) ^A/sbin/e2fsck -yvf returns 0 Mounting /dev/md0 /tmpRoot [ 2.705954] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 2.721236] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: prjquota,rootprjquota [ 2.725448] clocksource: Switched to clocksource tsc ------------upgrade Begin upgrade procedure [ 2.813380] loop: module loaded [ 2.847317] EXT4-fs (loop0): couldn't mount as ext3 due to feature incompatibilities [ 2.903333] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) Failed to found any patch No upgrade file found ============upgrade ------------bootup-smallupdate mkdir: can't create directory '/tmpRoot/proc': File exists mkdir: can't create directory '/tmpRoot/sys': File exists mkdir: can't create directory '/tmpRoot/dev': File exists Try bootup smallupdate No patch exist. Skip Packed Bootup SmallUpdate Sparse files don't exist. Skip Sparse Bootup SmallUpdate Finished synoautonano ============bootup-smallupdate Wait 2 seconds for synology manufactory device Wed Oct 19 08:51:33 UTC 2022 /dev/md0 /tmpRoot ext4 rw,relatime,prjquota,rootprjquota,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 root: Start backing up logs in junior mode [ 7.049365] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 7.073486] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) umount: /etc/mtab: No such file or directory linuxrc.syno executed successfully. Post init [ 7.288953] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 7.306973] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1,prjquota,rootprjquota [ 7.654587] systemd[1]: systemd 219 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR -SMACK +SYSVINIT -UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS -ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN) [ 7.656126] systemd[1]: Detected virtualization kvm. [ 7.656537] systemd[1]: Detected architecture x86-64. Welcome to Linux! [ 7.657175] systemd[1]: Set hostname to <RackStation>. [ 8.255539] systemd[1]: Cannot add dependency job for unit syno-mlnx-rdma-modules-load.service, ignoring: Unit syno-mlnx-rdma-modules-load.service is masked. [ 8.256683] systemd[1]: Cannot add dependency job for unit syno-qlogic-rdma-modules-load.service, ignoring: Unit syno-qlogic-rdma-modules-load.service is masked. [ 8.257862] systemd[1]: Cannot add dependency job for unit SynoLedBrightness.service, ignoring: Unit SynoLedBrightness.service is masked. [ 8.258742] systemd[1]: Cannot add dependency job for unit pkg-install-low-priority-builtin.service, ignoring: Unit pkg-install-low-priority-builtin.service failed to load: No such file or directory. [ 8.260028] systemd[1]: Cannot add dependency job for unit pkg-install-high-priority-builtin.service, ignoring: Unit pkg-install-high-priority-builtin.service failed to load: No such file or directory. [ 8.261870] systemd[1]: Reached target Timers. [ OK [ 8.262249] systemd[1]: Starting Timers. ] Reached target Timers. [ OK ] Reac[ 8.262904] systemd[1]: Reached target Paths. hed target Paths[ 8.263366] systemd[1]: Starting Paths. . [ 8.263898] systemd[1]: Created slice Root Slice. [ 8.264251] systemd[1]: Starting Root Slice. [ OK ] Created slice [ 8.264691] systemd[1]: Created slice BTRFS Optimization. Root Slice. [ 8.265200] systemd[1]: Starting BTRFS Optimization. 32m OK ] Created slice BTR[ 8.265836] systemd[1]: Created slice FileStation's slice. FS Optimization.[ 8.266354] systemd[1]: Starting FileStation's slice. [ OK ] Created slic[ 8.266963] systemd[1]: Created slice OAuthService's slice. e FileStation's [ 8.267515] systemd[1]: Starting OAuthService's slice. slice. [ OK ] Create[ 8.268170] systemd[1]: Created slice BTRFS Space Reclaim. d slice OAuthSer[ 8.268678] systemd[1]: Starting BTRFS Space Reclaim. vice's slice. [ OK ][ 8.269289] systemd[1]: Created slice synobackup daemon slice. Created slice B[ 8.269818] systemd[1]: Starting synobackup daemon slice. TRFS Space Reclaim. [ OK [ 8.270483] systemd[1]: Created slice Task Scheduler Group. ] Created s[ 8.270992] systemd[1]: Starting Task Scheduler Group. lice synobackup daemon slice. [[ 8.271609] systemd[1]: Created slice SecureSignIn's slice. OK ][ 8.272163] systemd[1]: Starting SecureSignIn's slice. Created slice Task Scheduler Gr[ 8.272773] systemd[1]: Created slice SNMP. oup. [ OK[ 8.273225] systemd[1]: Starting SNMP. ] Created slice SecureSign[ 8.273752] systemd[1]: Created slice Synology DSM internal service. In's slice. [ 8.274327] systemd[1]: Starting Synology DSM internal service. 32m OK ] Created slice SNM[ 8.275010] systemd[1]: Created slice BackupRestoreManager's slice. P. [ OK [ 8.275637] systemd[1]: Starting BackupRestoreManager's slice. ] Created slice Synology DSM[ 8.276333] systemd[1]: Created slice RAID Resync Process. Including Resync, Repair and Reshape.. internal servic[ 8.277066] systemd[1]: Starting RAID Resync Process. Including Resync, Repair and Reshape.. e. [ OK ] Created sl[ 8.277890] systemd[1]: Created slice Synology DSM Storage Service. ice BackupRestor[ 8.278465] systemd[1]: Starting Synology DSM Storage Service. eManager's slice. [ OK systemd[1]: Created slice ScsiTarget's slice. [0m] Created sli[ 8.279635] systemd[1]: Starting ScsiTarget's slice. ce RAID Resync Process. ...ing R[ 8.280290] systemd[1]: Created slice Synology Index slice (WAT). esync, Repair an[ 8.280835] systemd[1]: Starting Synology Index slice (WAT). d Reshape.. [ OK ] C[ 8.281547] systemd[1]: Created slice HybridShare's slice. reated slice Syn[ 8.282089] systemd[1]: Starting HybridShare's slice. ology DSM Storage Service. [ 8.282796] systemd[1]: Created slice Synology Cache Advisor. 2m OK ] Cr[ 8.283338] systemd[1]: Starting Synology Cache Advisor. [ 8.283981] systemd[1]: Created slice scemd. [ OK 8.284563] systemd[1]: Starting scemd. m] Created slice Synology Index slice (WAT). [ systemd[1]: Created slice Shared Folder Sync. [32m OK ] [ 8.285949] systemd[1]: Starting Shared Folder Sync. Created slice HybridShare's slic[ 8.286559] systemd[1]: Listening on udev Control Socket. e. [ OK [ 8.287122] systemd[1]: Starting udev Control Socket. ] Created slice Synology Cac[ 8.287849] systemd[1]: Created slice System Slice. he Advisor. [ 8.288334] systemd[1]: Starting System Slice. 32m OK ] Created slice sce[ 8.289021] systemd[1]: Created slice system-syno\x2dmd\x2dresync\x2dspeed\x2dadjust.slice. md. [ OK [ 8.289786] systemd[1]: Starting system-syno\x2dmd\x2dresync\x2dspeed\x2dadjust.slice. ] Created slice Shared Fold[ 8.290596] systemd[1]: Created slice system-serial\x2dgetty.slice. er Sync. [[ 8.291171] systemd[1]: Starting system-serial\x2dgetty.slice. OK ] Listening on udev Control Socket. [[ 8.291972] systemd[1]: Created slice User and Session Slice. OK ][ 8.292518] systemd[1]: Starting User and Session Slice. Created slice System Slice. [ systemd[1]: Created slice ActiveInsight's slice. [32m OK ] [ 8.293673] systemd[1]: Starting ActiveInsight's slice. Created slice system-syno\x2dmd\[ 8.294306] systemd[1]: Created slice Synology DSM desktop service. x2dresync\x2dspe[ 8.294871] systemd[1]: Starting Synology DSM desktop service. ed\x2dadjust.slice. [ OK [ 8.295540] systemd[1]: Created slice SynoFinder's slice. ] Created s[ 8.296061] systemd[1]: Starting SynoFinder's slice. lice system-serial\x2dgetty.slic[ 8.296675] systemd[1]: Created slice Performance alarm. e. [ OK [ 8.297186] systemd[1]: Starting Performance alarm. ] Created slice User and Ses[ 8.297789] systemd[1]: Listening on udev Kernel Socket. sion Slice. [ 8.298304] systemd[1]: Starting udev Kernel Socket. 32m OK ] Created slice Act[ 8.298919] systemd[1]: Created slice Package Center Slice. iveInsight's sli[ 8.299445] systemd[1]: Starting Package Center Slice. ce. [ OK ] Created slice Synology DS[ 8.300198] systemd[1]: Listening on Journal Socket. M desktop servic[ 8.300687] systemd[1]: Starting Journal Socket. e. [ OK ] Created slice SynoFinder's slice. [ OK ] Created slice Performance alarm. [ OK ] Listening on udev Kernel Socket. [ OK ] Created slice Package Center Slice. [ OK ] Listening on Journal Socket. [ 8.306158] systemd[1]: Started Machine Check Exception Logging Daemon. [ 8.306635] systemd[1]: Starting Machine Check Exception Logging Daemon... [ OK ] Started Machine Check Exceptio[ 8.307504] systemd[1]: Starting Load ntb_brd module... n Logging Daemon. Starting Machine Check Exception Log[ 8.308395] systemd[1]: Starting Link coredump path to volume if possible... ging Daemon... Starting Load ntb_brd module... Starting Link coredump path to volume if possible... [ 8.341223] systemd[1]: Starting Load Kernel Modules... Starting Load Kernel Mo[ 8.341849] systemd[1]: Starting Set boot sequence config... dules... Starting Set boot sequence config... [ 8.342705] systemd[1]: Mounting Debug File System... Mountin[ 8.343163] systemd[1]: Started Set project quota ID for /var/log. g Debug File System... [ 8.344081] systemd[1]: Starting Set hostname... Starting Set hostname... [ 8.344752] systemd[1]: Starting Disabling fan checking flag ...... Starting Disabling fan [ 8.345457] systemd[1]: Starting Set time zone information to kernel... checking flag ...... Starting Set time zone information to kernel... [ 8.416055] systemd[1]: Mounting Temporary Directory... Mounting Temporary Directory... [ 8.416675] systemd[1]: Starting unbind USB device... Starting unbind USB dev[ 8.417290] systemd[1]: Starting SED Bootup Action... ice... Starting SED Bootup Act[ 8.417798] systemd[1]: Created slice Synology Flashcache. ion... [ [ 8.418281] systemd[1]: Starting Synology Flashcache. OK ] Created slice Synology Flashcache. [ systemd[1]: Reached target Slices. [32m OK ] [ 8.419340] systemd[1]: Starting Slices. Reached target Slices. [ OK ] Reache[ 8.419874] systemd[1]: Reached target Swap. d target Swap. [ 8.420278] systemd[1]: Starting Swap. [ 8.420845] systemd[1]: Starting Journal Socket (/dev/log). [ 8.421303] systemd[1]: Created slice Synology Swap Works. [ OK [ 8.421717] systemd[1]: Starting Synology Swap Works. ] Created slice Synology Swap Wo[ 8.422227] systemd[1]: Created slice SSDP service. rks. [ OK[ 8.422654] systemd[1]: Starting SSDP service. ] Created slice SSDP servi[ 8.423150] systemd[1]: Created slice Python2's slice. ce. [ OK [ 8.423592] systemd[1]: Starting Python2's slice. ] Created slice Python2's s[ 8.424108] systemd[1]: Listening on Journal Audit Socket. lice. [ O[ 8.424580] systemd[1]: Starting Journal Audit Socket. K ] Listening on Journal Audit Socket. [ 8.425291] systemd[1]: Starting check integrity of rd.gz decompression... Starting check integrity of rd.gz decom[ 8.426071] systemd[1]: Starting Synology Task Scheduler Init... pression... Starting Synology Task [ 8.426722] systemd[1]: Created slice SMBService's slice. Scheduler Init..[ 8.427204] systemd[1]: Starting SMBService's slice. . [ OK ] Created slice SMBService's slice. [ [ 8.427927] systemd[1]: Mounted Debug File System. OK ] Mounted Debug File System. [ OK[ 8.428559] systemd[1]: Mounted Temporary Directory. ] Mounted Temporary Directory. [ OK ] Started [ 8.429301] systemd[1]: Started Load ntb_brd module. Load ntb_brd module. [ OK [ 8.429896] systemd[1]: Started Set boot sequence config. ] Started Set boot sequence config. [ OK [ 8.430563] systemd[1]: Started Set hostname. ] Started Set hostname. [ systemd[1]: Started Disabling fan checking flag .... [32m OK ] Started Disablin[ 8.431652] systemd[1]: Started Set time zone information to kernel. g fan checking flag .... [ OK ] Star[ 8.432384] systemd[1]: Started unbind USB device. ted Set time zone information to[ 8.432909] systemd[1]: Started SED Bootup Action. kernel. [ OK ] Star[ 8.433431] systemd[1]: Listening on Journal Socket (/dev/log). ted unbind USB device. [ OK ] Starte[ 8.434211] systemd[1]: Starting Journal Service... d SED Bootup Action. [ OK ] Listenin[ 8.434757] systemd[1]: Reached target Sockets. g on Journal Soc[ 8.435188] systemd[1]: Starting Sockets. ket (/dev/log). Starting Journal Servi[ 8.435744] systemd[1]: Reached target Local File Systems. ce... [ O[ 8.436263] systemd[1]: Starting Local File Systems. K ] Reached target Sockets. [ OK 8.436876] systemd[1]: Starting D-Bus Session Message Bus... 0m] Reached target Local File Systems. Starting D-Bus Session Message [ 8.437759] systemd[1]: Starting udev Coldplug all Devices... Bus... Starting udev Coldplug all Devices... [ 8.438522] systemd[1]: Starting D-Bus System Message Bus... Starting D-Bus System Message Bus... [ 8.439276] systemd[1]: Starting Set boot sequence config for temporary use... Starting Set boot sequence config for t[ 8.440096] systemd[1]: Starting Mount usb fs... emporary use... Starting Mount usb fs... [ 8.554120] systemd[1]: Started Journal Service. [ OK ] Started Journal Service. Starting Flush Journal to Persistent Storage... [ OK ] Started Set boot sequence config for temporary use. [ OK ] Started check integrity of rd.gz decompression. [FAILED] Failed to start Mount usb fs. See "systemctl status syno-mount-usbfs.service" for details. [ 8.621878] systemd-journald[6290]: Received request to flush runtime journal from PID 1 [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Started udev Coldplug all Devices. [ OK ] Started D-Bus Session Message Bus. [ OK ] Started D-Bus System Message Bus. [ OK ] Started Synology Task Scheduler Init. [ OK ] Started Create Volatile Files and Directories. [ OK ] Reached target Create SDK locks directory. Starting Check Synology group info consistency... Starting Check /etc/synoinfo.conf... Starting Check Synology user info consistency... Starting Synology Database Update... Starting synodsmnotify... [ OK ] Started synodsmnotify. [ OK ] Started Synology Database Update. [ 8.886899] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: dm-devel@redhat.com [ 8.932927] flashcache: flashcache-1.0-2022-09-21-01:11 initialized [ 8.944162] flashcache_syno: flashcache-1.0-syno-v25-pin-file-2022-09-21-01:11-debug initialized [ 8.997210] NET: Registered protocol family 10 [ 9.007046] sit: IPv6 over IPv4 tunneling driver [ OK ] Started Check /etc/synoinfo.conf. [ 9.136281] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 9.136861] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 9.137439] sd 3:0:0:0: Attached scsi generic sg2 type 0 [ 9.137950] sd 4:0:0:0: Attached scsi generic sg3 type 0 [ 9.138529] sd 5:0:0:0: Attached scsi generic sg4 type 0 [ 9.139127] sd 6:0:0:0: Attached scsi generic sg5 type 0 [ 9.139573] sd 7:0:0:0: Attached scsi generic sg6 type 0 [ 9.140120] sd 8:0:0:0: Attached scsi generic sg7 type 0 [ 9.140748] sd 9:0:0:0: Attached scsi generic sg8 type 0 [ 9.149164] e1000e: Intel(R) PRO/1000 Network Driver - 3.4.2.4-NAPI [ 9.149577] e1000e: Copyright(c) 1999 - 2019 Intel Corporation. [ 9.168882] dca service started, version 1.12.1 [ 9.176814] Intel(R) Gigabit Ethernet Linux Driver - version 5.3.5.22 [ 9.177257] Copyright(c) 2007 - 2018 Intel Corporation. [ OK ] Started Link coredump path to volume if possible. Starting System Logger Daemon... [ 9.216646] Intel(R) 10GbE PCI Express Linux Network Driver - version 5.5.5 [ 9.217254] Copyright(c) 1999 - 2019 Intel Corporation. [ OK ] Started Check Synology user info consistency. [ OK ] Started Check Synology group info consistency. [ OK ] Reached target User and Group Name Lookups. Starting move domain or ldap user p...der to domain or ldap folder.... [ OK ] Reached target Synology local user and group ready. [ OK ] Reached target Synology synoscheduler functions. [ OK ] Started move domain or ldap user pr...older to domain or ldap folder.. [ 9.600202] ixgbe 0000:06:11.0: Multiqueue Enabled: Rx Queue count = 6, Tx Queue count = 6 [ 9.686150] ixgbe 0000:06:11.0: 0.000 Gb/s available PCIe bandwidth (Unknown speed x255 link) [ 9.735199] ixgbe 0000:06:11.0 eth0: MAC: 4, PHY: 9, PBA No: H86377-005 [ 9.735807] ixgbe 0000:06:11.0: 00:11:32:a9:b0:a6 [ 9.736211] ixgbe 0000:06:11.0 eth0: Enabled Features: RxQ: 6 TxQ: 6 FdirHash vxlan_rx [ 9.742887] ixgbe 0000:06:11.0 eth0: Intel(R) 10 Gigabit Network Connection [ 10.126559] ixgbe 0000:06:11.1: Multiqueue Enabled: Rx Queue count = 6, Tx Queue count = 6 [ 10.212914] ixgbe 0000:06:11.1: 0.000 Gb/s available PCIe bandwidth (Unknown speed x255 link) [ 10.266756] ixgbe 0000:06:11.1 eth1: MAC: 4, PHY: 9, PBA No: H86377-005 [ 10.267428] ixgbe 0000:06:11.1: 00:11:32:a9:b0:a7 [ 10.267902] ixgbe 0000:06:11.1 eth1: Enabled Features: RxQ: 6 TxQ: 6 FdirHash vxlan_rx [ 10.274831] ixgbe 0000:06:11.1 eth1: Intel(R) 10 Gigabit Network Connection [ 10.299723] i40e: Intel(R) 40-10 Gigabit Ethernet Connection Network Driver - version 2.7.29 [ 10.300608] i40e: Copyright(c) 2013 - 2018 Intel Corporation. [ 10.311393] tn40xx low_mem_msg proc entry initialized [ 10.311931] tn40xx low_mem_counter proc entry initialized [ 10.312486] tn40xx debug_msg proc entry initialized [ 10.312996] tn40xx: Tehuti Network Driver, 0.3.6.12.3 [ 10.344721] Compat-mlnx-ofed backport release: c22af88 [ 10.345264] Backport based on mlnx_ofed/mlnx-ofa_kernel-4.0.git c22af88 [ 10.345713] compat.git: mlnx_ofed/mlnx-ofa_kernel-4.0.git [ OK ] Started System Logger Daemon. [ 10.407336] qed_init called [ 10.407611] QLogic FastLinQ 4xxxx Core Module qed 8.33.9.0 [ 10.408083] creating debugfs root node Starting Synology Log bootup start... [DEPEND] Dependency failed for rebuild local user and group db. [ OK ] Reached target Synology root filesystem (rw) ready. Starting Load AppArmor profiles... Starting syno-cgi-keygen.service... Starting Synology Default TLS Profile... Starting Synology check locale... Starting Umount initrd... Starting Set Eunit Sequence... Starting DSM Boot Health Check... [ OK ] Reached target Network (Pre). Starting Set arp ignore... [ 10.415522] qede_init: QLogic FastLinQ 4xxxx Ethernet Driver qede 8.33.9.0 Starting Synology Network Daemon... Starting DSM Installation ID... Starting Clean UPS config... Starting synodrnode... [ OK ] Started Clean UPS config. [ 10.426424] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.713.36 ($DateTime: 2016/06/16 03:53:41 $) [ 10.429164] usbcore: registered new interface driver usb-storage [ 10.430139] uhci_hcd: USB Universal Host Controller Interface driver [ 10.431301] uhci_hcd 0000:00:1a.0: UHCI Host Controller [ 10.431800] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1 [ 10.432528] uhci_hcd 0000:00:1a.0: irq 16, io base 0x00005040 [ 10.433540] hub 1-0:1.0: USB hub found [ 10.433962] hub 1-0:1.0: 2 ports detected [ 10.435163] uhci_hcd 0000:00:1a.1: UHCI Host Controller [ 10.435547] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 2 [ 10.436333] uhci_hcd 0000:00:1a.1: irq 17, io base 0x00005060 [ 10.437176] hub 2-0:1.0: USB hub found [ 10.437612] hub 2-0:1.0: 2 ports detected [ 10.438627] uhci_hcd 0000:00:1a.2: UHCI Host Controller [ 10.439101] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 3 [ 10.439788] uhci_hcd 0000:00:1a.2: irq 18, io base 0x00005080 [ 10.440922] hub 3-0:1.0: USB hub found [ 10.441529] hub 3-0:1.0: 2 ports detected [ 10.442433] uhci_hcd 0000:00:1d.0: UHCI Host Controller [ 10.442793] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 4 [ 10.443374] uhci_hcd 0000:00:1d.0: irq 16, io base 0x000050a0 [ 10.444284] hub 4-0:1.0: USB hub found [ 10.444724] hub 4-0:1.0: 2 ports detected [ 10.445764] uhci_hcd 0000:00:1d.1: UHCI Host Controller [ 10.446332] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 5 [ 10.446912] uhci_hcd 0000:00:1d.1: irq 17, io base 0x000050c0 [ 10.447702] hub 5-0:1.0: USB hub found [ 10.448193] hub 5-0:1.0: 2 ports detected [ 10.449067] uhci_hcd 0000:00:1d.2: UHCI Host Controller [ 10.449474] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 6 [ 10.450026] uhci_hcd 0000:00:1d.2: irq 18, io base 0x000050e0 [ 10.450790] hub 6-0:1.0: USB hub found [ 10.451135] hub 6-0:1.0: 2 ports detected [ OK ] Started Synology check locale. [ OK ] Started Set arp ignore. [ OK ] Started DSM Installation ID. [ OK ] Started Set Eunit Sequence. [ OK ] Started Synology Log bootup start. [ OK ] Started Umount initrd. [ OK ] Started Synology Default TLS Profile. [FAILED] Failed to start Load Kernel Modules. See "systemctl status systemd-modules-load.service" for details. [DEPEND] Dependency failed for Load Kernel Modules in Kernel Project. [DEPEND] Dependency failed for Prepare notification cache data. [DEPEND] Dependency failed for Software Init Led for support led v2 models. [DEPEND] Dependency failed for Load Fan Modules in Kernel Project. Starting SAS early initial... Mounting Configuration File System... Starting Adjust NIC sequence... Starting Apply default and user cus... sysctl.conf kernel variable.... Starting DSM Release Rolling Group ID... [ OK ] Mounted Configuration File System. [ OK ] Started DSM Release Rolling Group ID. [ OK ] Started Apply default and user cust...ed sysctl.conf kernel variable.. Starting Apply Kernel Variables... [ OK ] Started SAS early initial. Starting Synology swap... [ OK ] Started Apply Kernel Variables. Starting Apply kernel variable vm.min-free-kbytes... Starting Apply kernel variable kernel.sem at least 1024... Starting Apply kernel variable vm.kswapd_threads... Starting Apply kernel variable kernel-shmmni at least 16384... [FAILED] Failed to start Adjust NIC sequence. See "systemctl status SynoInitEth.service" for details. [ OK ] Started synodrnode. [ OK ] Started Apply kernel variable vm.kswapd_threads. [ OK ] Started Apply kernel variable kernel-shmmni at least 16384. [ OK ] Started Synology Network Daemon. Starting Wait for Synology Network to be Configured... [ OK ] Started syno-cgi-keygen.service. [ 11.107512] zram: Added device: zram0 [ 11.108142] zram: Added device: zram1 [ 11.108812] zram: Added device: zram2 [ 11.109465] zram: Added device: zram3 [ 11.110106] zram: Added device: zram4 [ 11.110748] zram: Added device: zram5 [ OK ] Started Wait for Synology Network to be Configured. Starting Synology Network Event Daemon... [ OK ] Started Synology Network Event Daemon. Starting rc.network... [ 11.423023] md: md1 stopped. [ OK ] Started Apply kernel variable kernel.sem at least 1024. [ OK ] Started Apply kernel variable vm.min-free-kbytes. [ 11.600588] md: bind<sdh2> [ 11.655073] md: bind<sdg2> [ 11.656379] md/raid1:md1: active with 2 out of 16 mirrors [ 11.680210] md1: detected capacity change from 0 to 2147418112 [ OK ] Started DSM Boot Health Check. [ OK ] Started Load AppArmor profiles. [ 12.005605] Adding 2097084k swap on /dev/md1. Priority:-1 extents:1 across:2097084k [ 12.007635] zram0: detected capacity change from 0 to 1677721600 [ 12.009844] Adding 1638396k swap on /dev/zram0. Priority:1 extents:1 across:1638396k SS [ 12.012255] zram1: detected capacity change from 0 to 1677721600 [ 12.014382] Adding 1638396k swap on /dev/zram1. Priority:1 extents:1 across:1638396k SS [ 12.016341] zram2: detected capacity change from 0 to 1677721600 [ 12.018458] Adding 1638396k swap on /dev/zram2. Priority:1 extents:1 across:1638396k SS [ 12.020995] zram3: detected capacity change from 0 to 1677721600 [ 12.023400] Adding 1638396k swap on /dev/zram3. Priority:1 extents:1 across:1638396k SS [ 12.025819] zram4: detected capacity change from 0 to 1677721600 [ 12.028068] Adding 1638396k swap on /dev/zram4. Priority:1 extents:1 across:1638396k SS [ 12.030646] zram5: detected capacity change from 0 to 1677721600 [ 12.032904] Adding 1638396k swap on /dev/zram5. Priority:1 extents:1 across:1638396k SS [ OK ] Started Synology swap. Starting udev Kernel Device Manager... [ OK ] Stopped eth0 DHCP Client. [ OK ] Stopped eth0-info DHCP Client v6. [ OK ] Stopped eth0-client DHCP Client v6. [ 12.193960] ixgbe 0000:06:11.0: registered PHC device on eth0 [ OK ] Stopped eth0-pd DHCP Client v6. [ 12.240096] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Starting DHCP client init... [ OK ] Created slice system-dhclient.slice. [ OK ] Started DHCP client init. Starting eth0 DHCP Client... [ OK ] Started eth0 DHCP Client. [ 12.333699] ixgbe 0000:06:11.1: registered PHC device on eth1 [ OK ] Started udev Kernel Device Manager. [ OK ] Reached target System Initialization. Starting bootup upgrade sha package... [ OK ] Started Synology token manager. Starting Synology token manager... [ OK ] Started Synology task manager. Starting Synology task manager... [ OK ] Started Serial Getty on ttyS0. Starting Serial Getty on ttyS0... [ OK ] Reached target Login Prompts. [ 12.379922] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready Starting eth1 DHCP Client... [ OK ] Started eth1 DHCP Client. [ OK ] Started rc.network. Starting Set Multiple Geteway... Starting PPPoE... Starting Check if network is ready... [ OK ] Started bootup upgrade sha package. [ OK ] Started PPPoE. [ OK ] Found device /dev/synoboot2. [ OK ] Reached target Synology synoboot2 done. [ OK ] Reached target Basic System. Starting Synology Schedule Daemon... Starting Samba Environment Setup Unit... Starting synoconfd daemon... Starting Synology filesytem check on bootup... [ OK ] Started Synology log accounting service. Starting Synology log accounting service... Starting always preprocess jobs before any package is started... Starting Synology firmware DLMC... Starting Hibernation debug check... Starting Log Rotate Daemon... Starting Login Service... Starting WD idle3 timer... Starting Control RC power... Starting Write back disk latency to DB... Starting Synology log notification service... [ OK ] Started synobackup daemon. Starting synobackup daemon... Starting System Profile Tuning... Starting Service for irq balance... Starting synoindex check if there a...ny synoindex-related packages... [ OK ] Started Set Multiple Geteway. [ OK ] Started Synology filesytem check on bootup. [ OK ] Started Synology firmware DLMC. [ OK ] Started WD idle3 timer. [ OK ] Started Write back disk latency to DB. Starting Synology space service... [ OK ] Reached target Network. Starting Redis data structure server for webapi... Starting Network Time Service... Starting findhost daemon... Starting Synology SCGI SocketIO... [ OK ] Started Synology Schedule Daemon. [ OK ] Started Hibernation debug check. [ OK ] Started Login Service. [ OK ] Stopped eth1-info DHCP Client v6. [ OK ] Stopped eth1-client DHCP Client v6. [ OK ] Stopped eth1-pd DHCP Client v6. [ OK ] Started findhost daemon. [ OK ] Started synoconfd daemon. [ OK ] Started Service for irq balance. [ OK ] Started Control RC power. [ OK ] Started Redis data structure server for webapi. [ OK ] Started Synology SCGI. Starting Synology SCGI... [ OK ] Started Log Rotate Daemon. [ OK ] Stopped Synology Task Scheduler Vmtouch. [ OK ] Started Synology Task Scheduler Vmtouch. Starting Synology Task Scheduler Vmtouch... [ OK ] Started always preprocess jobs before any package is started. [ OK ] Reached target Hook on root ready. Starting ActiveInsight's service unit... Starting SMBService's service unit... Starting SecureSignIn's service unit... Starting BackupRestoreManager's service unit... Starting Python2's service unit... [ OK ] Started System Profile Tuning. [ OK ] Started Network Time Service. [ OK ] Started Samba Environment Setup Unit. [FAILED] Failed to start synoindex check if ... any synoindex-related packages. See "systemctl status synoindex-checkpackage.service" for details. [DEPEND] Dependency failed for synoindex plugind. [DEPEND] Dependency failed for synomkthumbd. [DEPEND] Dependency failed for synoindex mediad. [DEPEND] Dependency failed for synoindex notifyd. [DEPEND] Dependency failed for synoindexd. [DEPEND] Dependency failed for synoindex scand. [DEPEND] Dependency failed for synomkflvd. [DEPEND] Dependency failed for synoindex workerd. [ OK ] Started Synology log notification service. [ 14.494932] md: md2 stopped. [ 14.497955] md: bind<sdd3> [ 14.498462] md: bind<sda3> [ 14.498976] md: bind<sdb3> [ 14.499448] md: bind<sdf3> [ 14.499979] md: bind<sde3> [ 14.500447] md: bind<sdc3> [ 14.541061] raid6: sse2x1 gen() 16667 MB/s [ 14.558070] raid6: sse2x1 xor() 12419 MB/s [ 14.575057] raid6: sse2x2 gen() 20511 MB/s [ 14.592012] raid6: sse2x2 xor() 14003 MB/s [ 14.609038] raid6: sse2x4 gen() 24046 MB/s [ 14.626038] raid6: sse2x4 xor() 15457 MB/s [ 14.643004] raid6: avx2x1 gen() 33785 MB/s [ 14.660011] raid6: avx2x1 xor() 23679 MB/s [ 14.677049] raid6: avx2x2 gen() 40199 MB/s [ 14.694038] raid6: avx2x2 xor() 25720 MB/s [ 14.711037] raid6: avx2x4 gen() 46707 MB/s [ 14.728011] raid6: avx2x4 xor() 28318 MB/s [ 14.728304] raid6: using algorithm avx2x4 gen() 46707 MB/s [ 14.728678] raid6: .... xor() 28318 MB/s, rmw enabled [ 14.729039] raid6: using avx2x2 recovery algorithm [ 14.733401] async_tx: api initialized (async) [ 14.740865] xor: automatically using best checksumming function: [ 14.751005] avx : 40244.000 MB/sec [ 14.802655] md: raid6 personality registered for level 6 [ 14.803225] md: raid5 personality registered for level 5 [ 14.803756] md: raid4 personality registered for level 4 [ 14.804315] md: raidF1 personality registered for level 45 [ 14.805303] md/raid:md2: device sdc3 operational as raid disk 0 [ 14.805705] md/raid:md2: device sde3 operational as raid disk 5 [ 14.806142] md/raid:md2: device sdf3 operational as raid disk 4 [ 14.806582] md/raid:md2: device sdb3 operational as raid disk 3 [ 14.806985] md/raid:md2: device sda3 operational as raid disk 2 [ 14.807404] md/raid:md2: device sdd3 operational as raid disk 1 [ 14.808205] md/raid:md2: allocated 6512kB [ 14.808836] md/raid:md2: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 14.809372] RAID conf printout: [ 14.809599] --- level:6 rd:6 wd:6 [ 14.809837] disk 0, o:1, dev:sdc3 [ 14.810088] disk 1, o:1, dev:sdd3 [ 14.810351] disk 2, o:1, dev:sda3 [ 14.810584] disk 3, o:1, dev:sdb3 [ 14.810817] disk 4, o:1, dev:sdf3 [ 14.811067] disk 5, o:1, dev:sde3 [ 14.827254] md2: detected capacity change from 0 to 63983851667456 [ 14.828479] md: md3 stopped. [ 14.886159] md: bind<sdh3> [ 14.903218] md: bind<sdg3> [ 14.916784] md: raid0 personality registered for level 0 [ 14.917350] md/raid0:md3: md_size is 31213208832 sectors. [ 14.917725] md: RAID0 configuration for md3 - 1 zone [ 14.918093] md: zone0=[sdg3/sdh3] [ 14.918374] zone-offset= 0KB, device-offset= 0KB, size=15606604416KB [ 14.918957] [ 14.940576] md3: detected capacity change from 0 to 15981162921984 [ OK ] Started Python2's service unit. [ OK ] Started SMBService's service unit. Starting ActiveBackup Daemon for DSM... [ OK ] Started ActiveBackup Daemon for DSM. [ OK ] Started BackupRestoreManager's service unit. Stopping Synology Task Scheduler Vmtouch... [ OK ] Stopped Synology Task Scheduler Vmtouch. [ OK ] Started Synology Task Scheduler Vmtouch. Starting Synology Task Scheduler Vmtouch... [ OK ] Started Synology space service. Starting Synology virtual space service... [ 16.498724] flashcache_syno: /dev/vg1/volume_2 exclude check success [ 16.503804] flashcache_syno: /dev/md2 exclude check success [ OK ] Started Synology virtual space service. Starting Synology virtual space service phase2... [ OK ] Started SecureSignIn's service unit. [ OK ] Started Synology virtual space service phase2. [ OK ] Reached target Synology storage pool. Starting Synology Building Tasks Restore for Storage Manager... Starting Synology filesystem check service... Starting Check Synology HotSpare Config... [ OK ] Started Synology Building Tasks Restore for Storage Manager. [ OK ] Started Synology filesystem check service. Starting Synology volume service... [ 16.892075] ixgbe 0000:06:11.0 eth0: NIC Link is Up 10 Gbps, Flow Control: None [ 16.893124] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Stopping Synology Task Scheduler Vmtouch... [ OK ] Stopped Synology Task Scheduler Vmtouch. [ OK ] Started Synology Task Scheduler Vmtouch. Starting Synology Task Scheduler Vmtouch... [ OK ] Started ActiveInsight's service unit. [ OK ] Started Check Synology HotSpare Config. Stopping eth0 DHCP Client... [ OK ] Stopped eth0 DHCP Client. Starting eth0 DHCP Client... [ OK ] Started eth0 DHCP Client. [ 17.234022] Btrfs loaded, crc32c=crc32c-intel [ 17.234915] BTRFS: device label 2021.10.25-22:30:52 v25426 devid 1 transid 252736 /dev/mapper/cachedev_1 [ 17.236776] BTRFS info (device dm-3): enabling auto syno reclaim space [ 17.237567] BTRFS info (device dm-3): use ssd allocation scheme [ 17.238364] BTRFS info (device dm-3): using free space tree [ 17.239165] BTRFS info (device dm-3): has skinny extents [ 17.246208] BTRFS: device label 2022.10.10-01:08:27 v42962 devid 1 transid 58 /dev/mapper/cachedev_0 [ 17.247668] BTRFS info (device dm-2): enabling auto syno reclaim space [ 17.248103] BTRFS info (device dm-2): use ssd allocation scheme [ 17.248485] BTRFS info (device dm-2): using free space tree [ 17.248838] BTRFS info (device dm-2): using free block group cache tree [ 17.249281] BTRFS info (device dm-2): has skinny extents [ OK ] Started Synology SCGI SocketIO. Starting synodrnode_reset... [ OK ] Started synodrnode_reset. [ 17.347209] BTRFS info (device dm-2): BTRFS: root of syno feature tree is null [ 18.351063] ixgbe 0000:06:11.0 eth0: NIC Link is Down Wed Oct 19 01:51:44 2022 RackStation login: [ 21.903233] BTRFS info (device dm-3): BTRFS: root of syno feature tree is null [ 24.025847] Synotify use 16384 event queue size [ 24.026272] Synotify use 16384 event queue size [ 24.597565] capability: warning: `nginx' uses 32-bit capabilities (legacy support in use) [ 25.076947] ixgbe 0000:06:11.0 eth0: NIC Link is Up 10 Gbps, Flow Control: None [ 25.214684] ata10.00: configured for UDMA/133 [ 25.215024] ata10: EH complete [ 25.296136] ata3.00: disabling queued TRIM support [ 25.303723] ata3.00: disabling queued TRIM support [ 25.304095] ata3.00: configured for UDMA/133 [ 25.304396] ata3: EH complete [ 25.334069] ata4.00: disabling queued TRIM support [ 25.340268] ata4.00: disabling queued TRIM support [ 25.340602] ata4.00: configured for UDMA/133 [ 25.340911] ata4: EH complete [ 25.378538] ata5.00: disabling queued TRIM support [ 25.386107] ata5.00: disabling queued TRIM support [ 25.386609] ata5.00: configured for UDMA/133 [ 25.387072] ata5: EH complete [ 25.420015] ata6.00: disabling queued TRIM support [ 25.426198] ata6.00: disabling queued TRIM support [ 25.426734] ata6.00: configured for UDMA/133 [ 25.427252] ata6: EH complete [ 25.457964] ata7.00: disabling queued TRIM support [ 25.465679] ata7.00: disabling queued TRIM support [ 25.466020] ata7.00: configured for UDMA/133 [ 25.466330] ata7: EH complete [ 25.496366] ata8.00: disabling queued TRIM support [ 25.502745] ata8.00: disabling queued TRIM support [ 25.503114] ata8.00: configured for UDMA/133 [ 25.503497] ata8: EH complete [ 25.541904] ata9.00: configured for UDMA/133 [ 25.542235] ata9: EH complete [ 37.930729] iSCSI:target_core_rodsp_server.c:1027:rodsp_server_init RODSP server started, login_key(d4c992dcd116). [ 37.976222] iSCSI:extent_pool.c:766:ep_init syno_extent_pool successfully initialized [ 37.999658] iSCSI:target_core_device.c:613:se_dev_align_max_sectors Rounding down aligned max_sectors from 4294967295 to 4294967288 [ 38.000603] iSCSI:target_core_configfs.c:5777:target_init_dbroot db_root: cannot open: /etc/target [ 38.001291] iSCSI:target_core_lunbackup.c:361:init_io_buffer_head 512 buffers allocated, total 2097152 bytes successfully [ 38.131372] iSCSI:target_core_file.c:152:fd_attach_hba RODSP plugin for fileio is enabled. [ 38.132116] iSCSI:target_core_file.c:159:fd_attach_hba ODX Token Manager is enabled. [ 38.132865] iSCSI:target_core_multi_file.c:91:fd_attach_hba RODSP plugin for multifile is enabled. [ 38.133744] iSCSI:target_core_ep.c:795:ep_attach_hba RODSP plugin for epio is enabled. [ 38.134492] iSCSI:target_core_ep.c:802:ep_attach_hba ODX Token Manager is enabled. [ 38.254212] workqueue: max_active 1024 requested for vhost_scsi is out of range, clamping between 1 and 512 [ 38.437300] iSCSI:qla_dbg.c:2605:ql_log qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 8.07.00.38-k. [ 38.467458] [13778]: ocs_fc_lio: ocs_scsi_ini_driver_init:1104::disabling the app heartbeat timeout detection [ 38.468493] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1225::ocs_fc_lio: driver version 12.2.385.0 [ 38.469478] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1227:: Module parameters: [ 38.470322] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1228:: Initiator = 0 [ 38.471118] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1229:: Target = 1 [ 38.471875] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1230:: ctrlmask = 0x000a [ 38.472706] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1231:: loglevel = 5 [ 38.473496] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1232:: logmask = 0x0000 [ 38.474315] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1233:: ramlog_size = 1048576 [ 38.475180] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1234:: rq_threads = 0 [ 38.475974] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1235:: wwn_bump = 0 [ 38.476761] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1236:: topology = 0 [ 38.477549] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1237:: speed = 0 [ 38.478489] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1238:: holdoff_link_online = 2 [ 38.479463] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1239:: enable_hlm = 0 [ 38.480346] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1240:: hlm_group_size = 8 [ 38.481190] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1241:: max_remote_nodes = 2048 [ 38.482073] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1242:: ethernet_license = 0 [ 38.482997] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1243:: num_scsi_ios = 8192 [ 38.483876] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1244:: dif_separate = 0 [ 38.485390] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1245:: tow_feature = 0 [ 38.486234] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1246:: tow_io_size = 65536 [ 38.487081] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1247:: tow_xri_cnt = 512 [ 38.487899] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1248:: queue_topology = eq cq rq cq mq $nulp($nwq(cq wq:ulp=$rpt1)) cq wq:len=256:class=1 [ 38.489285] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1249:: rq_selection_policy = 0 [ 38.490165] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1250:: rr_quanta = 1 [ 38.490895] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1251:: filter_ref = 0,0,0,0 [ 38.491746] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1252:: cq_process_limit = 64 [ 38.492611] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1253:: explicit_buffer_list = 0 [ 38.493500] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1254:: external_loopback = 0 [ 38.494361] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1255:: target_io_timer = 0 [ 38.495206] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1256:: target_wqe_timer = 30 [ 38.496072] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1257:: ddump_saved_size = 0 [ 38.496906] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1258:: hal_war_version = (null) [ 38.497794] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1259:: hw_cmpl_context = 1 [ 38.498643] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1260:: watchdog_timeout = 0 [ 38.499501] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1261:: heartbeat_cpu_mask = 0x0 [ 38.500393] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1262:: sliport_healthcheck = 0 [ 38.501275] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1263:: disable_fec = 0 [ 38.502091] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1264:: enable_dpp = 1 [ 38.502878] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1265:: sliport_pause_errors = disabled [ 38.503832] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1266:: enable_bbcr = 1 [ 38.504647] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1267:: fw_dump_type = 1 [ 38.505483] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1268:: enable_auto_recovery = 0 [ 38.506384] [13778]: ocs_fc_lio: ocs_driver_print_module_params:1269:: cfg_suppress_rsp = 1 [ 38.507341] [13779]: ocs_fc_lio: ocs_thread_thunk:1046::ocs_proxy running [ 38.650303] ext2: synoboot2 mounted, process=synopkicompatsy [ 38.702391] vfat: synoboot2 mounted, process=synopkicompatsy [ 38.709376] FAT-fs (synoboot2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 38.711232] synoboot2 unmounted, process=synopkicompatsy [ 38.975660] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) [ 39.660629] 8021q: 802.1Q VLAN Support v1.8 [ 39.660949] 8021q: adding VLAN 0 to HW filter on device eth0 [ 39.661379] 8021q: adding VLAN 0 to HW filter on device eth1 [ 41.932161] fuse init (API version 7.23) It stays there at Fuse init until i try to access it via http it seems, then it begins shutdown. I notice there are a few "taints kernel" it that normal? I've tried just now to install DS3622xs with arpl an that works fine (I've also previously used your own RS4021xs with the same setup, but stopped due to the Power supply warnings) so im not sure this is a network card issue, or maybe multiple issues? Quote Link to comment Share on other sites More sharing options...
NooL Posted October 19, 2022 Share #132 Posted October 19, 2022 Well reading a bit more, it seems there is also something with the NIC driver as well as this does not seem right?: [ 9.600202] ixgbe 0000:06:11.0: Multiqueue Enabled: Rx Queue count = 6, Tx Queue count = 6 [ 9.686150] ixgbe 0000:06:11.0: 0.000 Gb/s available PCIe bandwidth (Unknown speed x255 link) [ 9.735199] ixgbe 0000:06:11.0 eth0: MAC: 4, PHY: 9, PBA No: H86377-005 [ 9.735807] ixgbe 0000:06:11.0: 00:11:32:a9:b0:a6 [ 9.736211] ixgbe 0000:06:11.0 eth0: Enabled Features: RxQ: 6 TxQ: 6 FdirHash vxlan_rx [ 9.742887] ixgbe 0000:06:11.0 eth0: Intel(R) 10 Gigabit Network Connection [ 10.126559] ixgbe 0000:06:11.1: Multiqueue Enabled: Rx Queue count = 6, Tx Queue count = 6 [ 10.212914] ixgbe 0000:06:11.1: 0.000 Gb/s available PCIe bandwidth (Unknown speed x255 link) [ 10.266756] ixgbe 0000:06:11.1 eth1: MAC: 4, PHY: 9, PBA No: H86377-005 [ 10.267428] ixgbe 0000:06:11.1: 00:11:32:a9:b0:a7 [ 10.267902] ixgbe 0000:06:11.1 eth1: Enabled Features: RxQ: 6 TxQ: 6 FdirHash vxlan_rx [ 10.274831] ixgbe 0000:06:11.1 eth1: Intel(R) 10 Gigabit Network Connection Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted October 25, 2022 Author Share #133 Posted October 25, 2022 (edited) Introduces how to use rtc-cmos, a new extension driver of pocopico related to starting power reservation in m shell. apollolake (DS918+) / geminilake (DS920+) / v1000 (DS1621+) These three platform-based models cannot start power reservation because the /dev/rtc0 device is not active. rtc-cmos of pocopico activates /dev/rtc0 device and enables setting of alarm time related to power reservation start. The rtc-cmos extension driver is automatically bundled in all Synology models based on the apollolake / geminilake / v1000 platform built through m shell, so there is no need to add it separately. If possible, build each model using TCRP FREIND. (F) ./my.sh DS918+F ./my.sh DS920+F ./my.sh DS1621+F When used as an existing Jot / Jun Mod, it may be difficult to prepare for the disappearance of the Synoboot partition of USB. The disappearance of Synoboot partition is closely related to the 55% file corruption message during DSM installation. It is currently not possible to set the power schedule start setting by using the power schedule function of the control panel directly. You can set the alarm time you want the power to start by using the command below. Once set, the alarm time is automatically updated to the next day when that time has elapsed. Be sure to initialize it to 0 as shown below and then set the desired time. sudo sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm" sudo sh -c "echo `date '+%s' -d 'tomorrow 19:00'` > /sys/class/rtc/rtc0/wakealarm" Check if the settings are correct as follows. cat /proc/driver/rtc Below is an example of the reserved time. alrm_time and alrm_date are set. It is based on UK UTC, so you can calculate the time difference from your current time zone. I used 19:00, which is 7 pm tomorrow, as a sample.. A time difference of 9 hours from Seoul, Korea was applied. rtc_time : 09:22:03 rtc_date: 2022-10-25 alrm_time : 10:00:00 alrm_date: 2022-10-26 pocopico is currently producing a script so that the power reservation start scheduling of the control panel can be linked with the above alarm reservation time. Edited October 25, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted October 26, 2022 Author Share #134 Posted October 26, 2022 (edited) [NOTICE] Between 11 pm last night and 9 am today, 11 hours ago, For the purpose of power reservation processing of apollolake (DS918+) / geminilake (DS920+) / v1000 (DS1621+) with my.sh, If you have built it, please build the loader only once again. Full automation of power reservation processing of @pocopico and the control panel has been completed. But During this 11-hour period, the driver had an error in processing the reservation time. If you do not use the GUI of the control panel Those who only use scripts that modify /sys/class/rtc/rtc0/wakealarm only have no problem. If you want to use full automation like the existing models, please rebuild the loader. And currently, only one automatic start reservation can be processed. With the help of ARPL fabio, it is currently being modified to enable multi-registration like the original function. Edited October 26, 2022 by Peter Suh 1 Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted October 26, 2022 Share #135 Posted October 26, 2022 Hi @Peter Suh I have Juns Loader on v6.x i am not sure what one to use for this as i see you have an jot one as well. OR should i just build a new USB and then run it with my disks i have now and select Migrate ? Thanks Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted October 26, 2022 Author Share #136 Posted October 26, 2022 (edited) 7 hours ago, Vodka2014 said: Hi @Peter Suh I have Juns Loader on v6.x i am not sure what one to use for this as i see you have an jot one as well. OR should i just build a new USB and then run it with my disks i have now and select Migrate ? Thanks The m shell can be built in three ways: jot only / jun only / jot + friend. I also used jot when migrating from dSM 6 to 7, but there was no 'friend loader' at the time. Friend mode has the highest success rate. Rather than performing actual data migration right away, it is recommended to practice with a backup and a blank disk first. Edited October 27, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted October 27, 2022 Share #137 Posted October 27, 2022 (edited) 6 hours ago, Peter Suh said: The m shell can be built in three ways: jot only / jun only / jot + friend. I also used jot when migrating from dSM 6 to 7, but there was no 'friend loader' at the time. Friend mode has the highest success rate. Rather than performing actual data migration right away, it is recommended to practice with a backup and a blank disk first. Hi @Peter Suh Thanks but i am still lost as there is alot of updates throughout the topic and the main post is not updated so this is where it is getting to me. I get that i need to use ./my.sh DS3622xs+ manual Friend as i want to see what will do and i will select what i need to add or remove manual. The other modes like Jun , jumkey etc... i do not know what i need to use here. or what it actually does. Is there a full guide on how to do a migration with the latest options and settings please. Sorry if this is asking again i just do not want to mess this up. Do i need to keep my jun settings and start over on an new USB or how should i do all of this. Thanks. Edited October 27, 2022 by Vodka2014 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted October 27, 2022 Author Share #138 Posted October 27, 2022 16 minutes ago, Vodka2014 said: Hi @Peter Suh Thanks but i am still lost as there is alot of updates throughout the topic and the main post is not updated so this is where it is getting to me. I get that i need to use ./my.sh DS3622xs+ manual Friend as i want to see what will do and i will select what i need to add or remove manual. The other modes like Jun , jumkey etc... i do not know what i need to use here. or what it actually does. Is there a full guide on how to do a migration with the latest options and settings please. Sorry if this is asking again i just do not want to mess this up. Do i need to keep my jun settings and start over on an new USB or how should i do all of this. Thanks. Here's what I've said about the benefits of the new loader today in the topic below. If you read it once, it might be helpful. Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted October 27, 2022 Share #139 Posted October 27, 2022 12 minutes ago, Peter Suh said: Here's what I've said about the benefits of the new loader today in the topic below. If you read it once, it might be helpful. Thanks i get all of this but still i do not know how to migrate from old to new and keep all my data. Is it a new USB setup, copy old settings to new configs. Also with your ./my.sh is it just 1 option to use. This is the things i am trying to find out but i am finding it hard as iti s not all in 1 place and like i stated i do not want to mess this up. I am not an expert here at all this is why i am asking for help please. Thanks again Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted October 27, 2022 Author Share #140 Posted October 27, 2022 (edited) 2 hours ago, Vodka2014 said: I am not an expert here at all this is why i am asking for help please. Thanks again There are many similarities between grub.cfg of Jun loader used in DSM 6 and grub.cfg of REDPILL of DSM 7. (Do you know what grub.cfg is?) However, there doesn't seem to be a need to keep copying grub.cfg from 6 and using it from 7. In 6 everything was done manually, In 7, everything is automated thanks to TCRP. It also finds the VID / PID of the USB, It also creates a virtual serial number for each model and finds the real MAC address. (Don't you have Synology Real Serial?) So, if it fits in ./my.sh , the part above it will be covered by itself. If you want to use the real MAC address I recommend, use the command below. ./my.sh DS3622xs+F realmac The VID/PID/Virtual Serial/Real MAC address mentioned earlier are automatically searched and processed. The core of this part is the user_config.json file. When Redfill builds the loader, it references this file and creates grub.cfg . So, it is important to configure the user_config.json file well. One of the most troublesome things is to map the MOBO's SATA port. I had a similar problem with the DSM 6's Jun loader. So the method I recommend is to build all the loaders once with the my.sh option above. In the middle, you will see a suggestion of mapping values for SataPort. At this time, write down any random number. And after building the loader, edit user_config.json through vi editor. The parts that need to be modified among the contents are SataPortMap and DiskIdxMap. Please use "" to empty the contents inside as shown below. The reason for emptying the value as shown below is to entrust the SataPort mapping to the redfill loader. This method is recommended by TTG. "extra_cmdline": { "pid": "blabla", "vid": "blabla", "sn": "blabla", "mac1": "blabla", "netif_num": "1", "SataPortMap": "", "DiskIdxMap": "" }, If you are unfamiliar with the VI editor, process the two-line command as shown below to make SataPortMap and DiskIdxMap empty as above. json="$(jq --arg var "$sataportmap" '.extra_cmdline.SataPortMap = ""' user_config.json)" && echo -E "${json}" | jq. >user_config.json json="$(jq --arg var "$diskidxmap" '.extra_cmdline.DiskIdxMap = ""' user_config.json)" && echo -E "${json}" | jq. >user_config.json Finally, we use cat to double-check that the process was successful. cat user_config.json And, please build the loader once more. The options noconfig, noclean are used. ./my.sh DS3622xs+F noconfig noclean noconfig uses the user_config.json modified once above as it is, but does not make any changes. noclean leaves the redpill-load / redpill-lkm directory without deleting it. The reason for putting it like this is to check whether the extension drivers automatically detected when building the loader for the first time are inserted properly. On the last screen where TCRP FRIEND is loaded A warning message appears stating that the SataPortMap and DiskIdxMap values are empty, but you can ignore this part. As I said before, make sure you have a backup of your data. Practice migrating from DSM 6 to 7 with a spare disk. It is recommended to prepare 1 USB for DSM 6 and 1 USB for DSM 7 respectively. The guide I'm giving you right now is the basics for beginners that no guide has ever found. Edited October 27, 2022 by Peter Suh 1 Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted October 27, 2022 Share #141 Posted October 27, 2022 2 minutes ago, Peter Suh said: There are many similarities between grub.cfg of Jun loader used in DSM 6 and grub.cfg of REDPILL of DSM 7. (Do you know what grub.cfg is?) However, there doesn't seem to be a need to keep copying grub.cfg from 6 and using it from 7. In 6 everything was done manually, In 7, everything is automated thanks to TCRP. It also finds the VID / PID of the USB, It also creates a virtual serial number for each model and finds the real MAC address. (Don't you have Synology Real Serial?) So, if it fits in ./my.sh , the part above it will be covered by itself. If you want to use the real MAC address I recommend, use the command below. ./my.sh DS3622xs+F realmac The VID/PID/Virtual Serial/Real MAC address mentioned earlier are automatically searched and processed. The core of this part is the user_config.json file. When Redfill builds the loader, it references this file and creates grub.cfg . So, it is important to configure the user_config.json file well. One of the most troublesome things is to map the MOBO's SATA port. I had a similar problem with the DSM 6's Jun loader. So the method I recommend is to build all the loaders once with the my.sh option above. In the middle, you will see a suggestion of mapping values for SataPort. At this time, write down any random number. And after building the loader, edit user_config.json through vi editor. The parts that need to be modified among the contents are SataPortMap and DiskIdxMap. Please use "" to empty the contents inside as shown below. The reason for emptying the value as shown below is to entrust the SataPort mapping to the redfill loader. This method is recommended by TTG. "extra_cmdline": { "pid": "blabla", "vid": "blabla", "sn": "blabla", "mac1": "blabla", "netif_num": "1", "SataPortMap": "", "DiskIdxMap": "" }, And, please build the loader once more. The options noconfig, noclean are used. ./my.sh DS3622xs+F noconfig noclean noconfig uses the user_config.json modified once above as it is, but does not make any changes. noclean leaves the redpill-load / redpill-lkm directory without deleting it. The reason for putting it like this is to check whether the extension drivers automatically detected when building the loader for the first time are inserted properly. On the last screen where TCRP FRIEND is loaded A warning message appears stating that the SataPortMap and DiskIdxMap values are empty, but you can ignore this part. As I said before, make sure you have a backup of your data. Practice migrating from DSM 6 to 7 with a spare disk. It is recommended to prepare 1 USB for DSM 6 and 1 USB for DSM 7 respectively. The guide I'm giving you right now is the basics for beginners that no guide has ever found. Thanks alot @Peter Suh appreciate your time to help and explain this all to me. Yes i know the grub,cfg. Let me give this all a go with and backup of my settings and see how this all goes. Quote Link to comment Share on other sites More sharing options...
bdrwu Posted October 31, 2022 Share #142 Posted October 31, 2022 ./my.sh DS1019+F <--- This can only compile 7.0.1-42218 not 7.1.1-42962 version? I need 7.0.1-42218 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted October 31, 2022 Author Share #143 Posted October 31, 2022 22 minutes ago, bdrwu said: ./my.sh DS1019+F <--- This can only compile 7.0.1-42218 not 7.1.1-42962 version? I need 7.0.1-42218 FRIEND mode is fixed in 7.1.1-42962 and Only JUN mode is fixed in 7.0.1-42218. ./my.sh DS1019+J Quote Link to comment Share on other sites More sharing options...
shibby Posted November 8, 2022 Share #144 Posted November 8, 2022 which choice is better? JUN or FRIEND? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted November 8, 2022 Author Share #145 Posted November 8, 2022 20 minutes ago, shibby said: which choice is better? JUN or FRIEND? USE FRIEND MODE. 1 Quote Link to comment Share on other sites More sharing options...
dimakv2014 Posted November 8, 2022 Share #146 Posted November 8, 2022 В 31.10.2022 в 10:05, Peter Suh сказал: FRIEND mode is fixed in 7.1.1-42962 and Only JUN mode is fixed in 7.0.1-42218. ./my.sh DS1019+J You can actually update Jun to latest version 1. Factory Reset DSM and when it shows Start button it will ask if you want to download .pat file from synology servers, it will install 7.1 update4 2. After that go to updates and will show newer version available 7.1.1 Update 2, do that and it will install it. At least worked with dva3221J and dva3219J without errors. 1 Quote Link to comment Share on other sites More sharing options...
shibby Posted November 9, 2022 Share #147 Posted November 9, 2022 @Peter Suh i need your help. I`m trying to compile DS920+F but with tx40xx driver for my 10gigs LAN. TCRP desn`t see this NIC but your script does: Two or more Ethernet Interface was detected!! 2 Add mac2 automatically. but wont download drivers Found Ethernet Interface : pciid 1fc9d00004027 Required Extension : No matching extension At the moment i`m on 6.2.3 and ls -vvv return 0000:05:00.0 Class 0200: Device 1fc9:4027 [..] Kernel driver in use: tn40xx So how can i force to include tn40xx driver in redpill-loader using your M-shell script? I tried ./rploader.sh ext ds920p-7.1.1-42962 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/main/tn40xx/rpext-index.json ./my.sh DS920+F noconfig noclean but it does not work - driver has not been included to redpill-loader Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted November 9, 2022 Author Share #148 Posted November 9, 2022 1 hour ago, shibby said: @Peter Suh i need your help. I`m trying to compile DS920+F but with tx40xx driver for my 10gigs LAN. TCRP desn`t see this NIC but your script does: Two or more Ethernet Interface was detected!! 2 Add mac2 automatically. but wont download drivers Found Ethernet Interface : pciid 1fc9d00004027 Required Extension : No matching extension At the moment i`m on 6.2.3 and ls -vvv return 0000:05:00.0 Class 0200: Device 1fc9:4027 [..] Kernel driver in use: tn40xx So how can i force to include tn40xx driver in redpill-loader using your M-shell script? I tried ./rploader.sh ext ds920p-7.1.1-42962 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/main/tn40xx/rpext-index.json ./my.sh DS920+F noconfig noclean but it does not work - driver has not been included to redpill-loader ./my.sh starts the build by first clearing the extension drivers that were pre-added earlier. So the tn40xx you added in advance will have already been deleted. Instead use myv.sh like below. ./myv.sh DS920+F noconfig noclean 68) at tn40xx. Just choose this one. As a final result, check whether tn40xx exists in the extensions folder below. Quote Link to comment Share on other sites More sharing options...
Orphée Posted November 9, 2022 Share #149 Posted November 9, 2022 (edited) On 10/18/2022 at 4:10 PM, Peter Suh said: The hardware settings of my proxmox are as follows: I can't figure out how to set PCIE passthrough in proxmox. I've been looking for a way to enable IOMMU, but I can't find a well-written guide. Is this guide for PCIE? I didn't proceed as it was because it seemed to end with the content about the GPU. Most of the guides only describe GPU pass-through. Did you sort it ? In my DVA3221 thread I gave my experience with Proxmox passthrough and I succeded with it. Quote I was able to run the loader on Proxmox VE virtual machine with GPU passthrough working. BUT there are some prerequisites : https://pve.proxmox.com/wiki/Pci_passthrough (I personnally had to configure GRUB boot menu like this : GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction video=efifb:off" ) Remember to run "update-grub" after you edit your grub config Edit : you may not need all the command as for me it was for the NVIDIA GPU passthrough Edited November 9, 2022 by Orphée 1 Quote Link to comment Share on other sites More sharing options...
shibby Posted November 9, 2022 Share #150 Posted November 9, 2022 (edited) //deleted Edited November 9, 2022 by shibby 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.