hendry Posted February 15, 2022 Share #76 Posted February 15, 2022 (edited) after updating with debian bullseye based images, it can start boot but harddrive cannot detected as seen below.. here's the log.. GNU GRUB version 2.06 ┌────────────────────────────────────────────────────────────────────────────┐ │*RedPill DS3615xs v7.0.1-42218 (USB, Verbose) │ │ RedPill DS3615xs v7.0.1-42218 (SATA, Verbose) │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └────────────────────────────────────────────────────────────────────────────┘ Use the ↑ and ↓ keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands The highlighted entry will be executed automatically in 0s. The highlighted entry will be executed automatically in 0s. Booting `RedPill DS3615xs v7.0.1-42218 (USB, Verbose)' Booting `RedPill DS3615xs v7.0.1-42218 (USB, Verbose) ' LoadingLoadin gLinux... Linux.. . LoadingLoadin ginitramfs... initramfs.. . StartingStartin gkernel kerne lwith wit hUSB US Bboot boo [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.10.108 (root@build13) (gcc version 7.5.0 (GCC) ) #42218 SMP Mon Oct 18 19:15:14 CST 2021 [ 0.000000] Command line: BOOT_IMAGE=/zImage withefi earlyprintk syno_hw_version=DS3615xs console=ttyS0,115200n8 netif_num=1 pid=0x0001 earlycon=uart8250,io,0x8 [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable [ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003ffd3fff] usable [ 0.000000] BIOS-e820: [mem 0x000000003ffd4000-0x000000003fffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved [ 0.000000] Early serial console at I/O port 0x3f8 (options '115200n') [ 0.000000] bootconsole [uart0] enabled [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] SMBIOS 2.8 present. [ 0.000000] DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.000000] e820: last_pfn = 0x3ffd4 max_arch_pfn = 0x400000000 [ 0.000000] MTRR default type: write-back [ 0.000000] MTRR fixed ranges enabled: [ 0.000000] 00000-9FFFF write-back [ 0.000000] A0000-BFFFF uncachable [ 0.000000] C0000-FFFFF write-protect [ 0.000000] MTRR variable ranges enabled: [ 0.000000] 0 base 00C0000000 mask FFC0000000 uncachable [ 0.000000] 1 disabled [ 0.000000] 2 disabled [ 0.000000] 3 disabled [ 0.000000] 4 disabled [ 0.000000] 5 disabled [ 0.000000] 6 disabled [ 0.000000] 7 disabled [ 0.000000] found SMP MP-table at [mem 0x000f5b40-0x000f5b4f] mapped at [ffff8800000f5b40] [ 0.000000] Base memory trampoline at [ffff880000099000] 99000 size 24576 [ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff] [ 0.000000] [mem 0x00000000-0x000fffff] page 4k [ 0.000000] BRK [0x01b2c000, 0x01b2cfff] PGTABLE [ 0.000000] BRK [0x01b2d000, 0x01b2dfff] PGTABLE [ 0.000000] BRK [0x01b2e000, 0x01b2efff] PGTABLE [ 0.000000] init_memory_mapping: [mem 0x3fc00000-0x3fdfffff] [ 0.000000] [mem 0x3fc00000-0x3fdfffff] page 2M [ 0.000000] init_memory_mapping: [mem 0x3c000000-0x3fbfffff] [ 0.000000] [mem 0x3c000000-0x3fbfffff] page 2M [ 0.000000] init_memory_mapping: [mem 0x00100000-0x3bffffff] [ 0.000000] [mem 0x00100000-0x001fffff] page 4k [ 0.000000] [mem 0x00200000-0x3bffffff] page 2M [ 0.000000] init_memory_mapping: [mem 0x3fe00000-0x3ffd3fff] [ 0.000000] [mem 0x3fe00000-0x3ffd3fff] page 4k [ 0.000000] BRK [0x01b2f000, 0x01b2ffff] PGTABLE [ 0.000000] log_buf_len: 33554432 [ 0.000000] early log buf free: 1045004(99%) [ 0.000000] RAMDISK: [mem 0x35963000-0x36ca8fff] [ 0.000000] ACPI: RSDP 0x00000000000F5990 00014 (v00 BOCHS ) [ 0.000000] ACPI: RSDT 0x000000003FFE5991 00038 (v01 BOCHS BXPC 00000001 BXPC 00000001) [ 0.000000] ACPI: FACP 0x000000003FFE5789 000F4 (v03 BOCHS BXPC 00000001 BXPC 00000001) [ 0.000000] ACPI: DSDT 0x000000003FFE0040 05749 (v01 BOCHS BXPC 00000001 BXPC 00000001) [ 0.000000] ACPI: FACS 0x000000003FFE0000 00040 [ 0.000000] ACPI: APIC 0x000000003FFE587D 00078 (v01 BOCHS BXPC 00000001 BXPC 00000001) [ 0.000000] ACPI: HPET 0x000000003FFE58F5 00038 (v01 BOCHS BXPC 00000001 BXPC 00000001) [ 0.000000] ACPI: MCFG 0x000000003FFE592D 0003C (v01 BOCHS BXPC 00000001 BXPC 00000001) [ 0.000000] ACPI: WAET 0x000000003FFE5969 00028 (v01 BOCHS BXPC 00000001 BXPC 00000001) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] [ffffea0000000000-ffffea0000dfffff] PMD -> [ffff88003c600000-ffff88003d3fffff] on node 0 [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x00001000-0x00ffffff] [ 0.000000] DMA32 [mem 0x01000000-0xffffffff] [ 0.000000] Normal empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00001000-0x0009efff] [ 0.000000] node 0: [mem 0x00100000-0x3ffd3fff] [ 0.000000] On node 0 totalpages: 262002 [ 0.000000] DMA zone: 56 pages used for memmap [ 0.000000] DMA zone: 21 pages reserved [ 0.000000] DMA zone: 3998 pages, LIFO batch:0 [ 0.000000] DMA32 zone: 3528 pages used for memmap [ 0.000000] DMA32 zone: 258004 pages, LIFO batch:31 [ 0.000000] ACPI: PM-Timer IO Port: 0x608 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level) [ 0.000000] ACPI: IRQ0 used by override. [ 0.000000] ACPI: IRQ2 used by override. [ 0.000000] ACPI: IRQ5 used by override. [ 0.000000] ACPI: IRQ9 used by override. [ 0.000000] ACPI: IRQ10 used by override. [ 0.000000] ACPI: IRQ11 used by override. [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000 [ 0.000000] smpboot: Allowing 1 CPUs, 0 hotplug CPUs [ 0.000000] nr_irqs_gsi: 40 [ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000 [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000 [ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000 [ 0.000000] e820: [mem 0x40000000-0xafffffff] available for PCI devices [ 0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 27 pages/cpu @ffff88003dc00000 s80704 r8192 d21696 u2097152 [ 0.000000] pcpu-alloc: s80704 r8192 d21696 u2097152 alloc=1*2097152 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 258397 [ 0.000000] Kernel command line: BOOT_IMAGE=/zImage withefi earlyprintk syno_hw_version=DS3615xs console=ttyS0,115200n8 netif_num=1 pid=0x0001 earlycon=uart8258 [ 0.000000] Synology Hardware Version: DS3615xs-j [ 0.000000] Internal netif num: 1 [ 0.000000] Mac1: 0011322CA785 [ 0.000000] Serial Number: C7LWN09761 [ 0.000000] Disk Index Map: 0A00 [ 0.000000] Vender format version: 2 [ 0.000000] Power on seq num: 0 [ 0.000000] Sata Port Map: 58 [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) [ 0.000000] Memory: 967896k/1048400k available (4820k kernel code, 392k absent, 80112k reserved, 4065k data, 828k init) [ 0.000000] Kernel/User page tables isolation: disabled [ 0.000000] Hierarchical RCU implementation. [ 0.000000] CONFIG_RCU_FANOUT set to non-default value of 32 [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled. [ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=1. [ 0.000000] NR_IRQS:4352 nr_irqs:256 16 [ 0.000000] Console: colour dummy device 80x25 [ 0.000000] console [ttyS0] enabled, bootconsole disabled [ 1.513995] PCI host bridge to bus 0001:07 [ 1.515073] pci_bus 0001:07: root bus resource [io 0x0000-0xffff] [ 1.516603] pci_bus 0001:07: root bus resource [mem 0x00000000-0xffffffffff] [ 1.518394] pci_bus 0001:07: root bus resource [bus 00-ff] [ 1.519762] pci 0001:07:00.0: [1b4b:9235] type 00 class 0x010601 [ 1.521547] pci 0001:07:00.0: Can't map mv9235 registers [ 1.524547] PCI host bridge to bus 0001:08 [ 1.525539] pci_bus 0001:08: root bus resource [io 0x0000-0xffff] [ 1.527063] pci_bus 0001:08: root bus resource [mem 0x00000000-0xffffffffff] [ 1.528706] pci_bus 0001:08: root bus resource [bus 00-ff] [ 1.530089] pci 0001:08:00.0: [1b4b:9235] type 00 class 0x010601 [ 1.543329] pci 0001:08:00.0: Can't map mv9235 registers [ 1.548601] PCI host bridge to bus 0001:09 [ 1.549662] pci_bus 0001:09: root bus resource [io 0x0000-0xffff] [ 1.551153] pci_bus 0001:09: root bus resource [mem 0x00000000-0xffffffffff] [ 1.552984] pci_bus 0001:09: root bus resource [bus 00-ff] [ 1.554295] pci 0001:09:00.0: [1b4b:9235] type 00 class 0x010601 [ 1.566457] pci 0001:09:00.0: Can't map mv9235 registers [ 1.569677] PCI host bridge to bus 0001:0a [ 1.570792] pci_bus 0001:0a: root bus resource [io 0x0000-0xffff] [ 1.572297] pci_bus 0001:0a: root bus resource [mem 0x00000000-0xffffffffff] [ 1.574112] pci_bus 0001:0a: root bus resource [bus 00-ff] [ 1.575517] pci 0001:0a:00.0: [1b4b:9235] type 00 class 0x010601 [ 1.584383] pci 0001:0a:00.0: Can't map mv9235 registers [ 1.629783] Initialise module verification [ 1.631475] audit: initializing netlink socket (disabled) [ 1.633478] type=2000 audit(1644922308.633:1): initialized [ 1.677631] bounce pool size: 64 pages [ 1.685986] VFS: Disk quotas dquot_6.5.2 [ 1.687069] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 1.688788] msgmni has been set to 1929 [ 1.694951] Key type asymmetric registered [ 1.696093] Asymmetric key parser 'x509' registered [ 1.697564] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [ 1.699806] io scheduler noop registered [ 1.700924] io scheduler deadline registered [ 1.702067] io scheduler cfq registered (default) [ 1.706872] pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X [ 1.718418] pcieport 0000:00:1c.1: irq 41 for MSI/MSI-X [ 1.733903] pcieport 0000:00:1c.2: irq 42 for MSI/MSI-X [ 1.749893] pcieport 0000:00:1c.3: irq 43 for MSI/MSI-X [ 1.765823] aer 0000:00:1c.0:pcie02: service driver aer loaded [ 1.768661] aer 0000:00:1c.1:pcie02: service driver aer loaded [ 1.771439] aer 0000:00:1c.2:pcie02: service driver aer loaded [ 1.775683] aer 0000:00:1c.3:pcie02: service driver aer loaded [ 2.602078] tsc: Refined TSC clocksource calibration: 1996.795 MHz [ 2.603562] Switching to clocksource tsc [ 4.463135] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 4.498027] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 4.542842] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 4.578360] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 4.855397] brd: module loaded [ 4.877170] lpc_ich 0000:00:1f.0: I/O space for GPIO uninitialized [ 4.892616] Loading iSCSI transport class v2.0-870. [ 5.010501] rdac: device handler registered [ 5.034181] ahci 0000:00:1f.2: version 3.0 [ 5.035923] ahci 0000:00:1f.2: irq 44 for MSI/MSI-X [ 5.037941] ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 6 ports 1.5 Gbps 0x3f impl SATA mode [ 5.040304] ahci 0000:00:1f.2: flags: 64bit ncq only [ 5.041718] ahci 0000:00:1f.2: setting latency timer to 64 [ 5.121963] scsi0 : ahci [ 5.132313] scsi1 : ahci [ 5.142455] scsi2 : ahci [ 5.154127] scsi3 : ahci [ 5.165723] scsi4 : ahci [ 5.172491] ata1: SATA max UDMA/133 abar m4096@0xfd850000 port 0xfd850100 irq 44 [ 5.174490] ata2: SATA max UDMA/133 abar m4096@0xfd850000 port 0xfd850180 irq 44 [ 5.176415] ata3: SATA max UDMA/133 abar m4096@0xfd850000 port 0xfd850200 irq 44 [ 5.178478] ata4: SATA max UDMA/133 abar m4096@0xfd850000 port 0xfd850280 irq 44 [ 5.180534] ata5: SATA max UDMA/133 abar m4096@0xfd850000 port 0xfd850300 irq 44 [ 5.182934] ahci 0000:06:07.0: irq 45 for MSI/MSI-X [ 5.184892] ahci 0000:06:07.0: AHCI 0001.0000 32 slots 6 ports 1.5 Gbps 0x3f impl SATA mode [ 5.187181] ahci 0000:06:07.0: flags: 64bit ncq only [ 5.188555] ahci 0000:06:07.0: setting latency timer to 64 [ 5.317640] scsi5 : ahci [ 5.331085] scsi6 : ahci [ 5.345231] scsi7 : ahci [ 5.356030] scsi8 : ahci [ 5.365838] scsi9 : ahci [ 5.379061] scsi10 : ahci [ 5.391030] scsi11 : ahci [ 5.406259] scsi12 : ahci [ 5.413461] ata6: SATA max UDMA/133 abar m4096@0xfcc00000 port 0xfcc00100 irq 45 [ 5.415541] ata7: SATA max UDMA/133 abar m4096@0xfcc00000 port 0xfcc00180 irq 45 [ 5.417547] ata8: SATA max UDMA/133 abar m4096@0xfcc00000 port 0xfcc00200 irq 45 [ 5.419652] ata9: SATA max UDMA/133 abar m4096@0xfcc00000 port 0xfcc00280 irq 45 [ 5.421678] ata10: SATA max UDMA/133 abar m4096@0xfcc00000 port 0xfcc00300 irq 45 [ 5.423747] ata11: SATA max UDMA/133 abar m4096@0xfcc00000 port 0xfcc00380 irq 45 [ 5.425755] ata12: DUMMY [ 5.426443] ata13: DUMMY [ 5.427233] ahci: probe of 0001:07:00.0 failed with error -22 [ 5.428774] ahci: probe of 0001:08:00.0 failed with error -22 [ 5.430398] ahci: probe of 0001:09:00.0 failed with error -22 [ 5.432021] ahci: probe of 0001:0a:00.0 failed with error -22 [ 5.448061] ata12: send port disabled event [ 5.451322] ata13: send port disabled event [ 5.468497] rtc_cmos 00:04: RTC can wake from S4 [ 5.474105] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0 [ 5.475978] rtc_cmos 00:04: alarms up to one day, y3k, 242 bytes nvram, hpet irqs [ 5.483326] i2c /dev entries driver [ 5.487183] md: raid1 personality registered for level 1 [ 5.488932] cpuidle: using governor ladder [ 5.489981] cpuidle: using governor menu [ 5.490995] TCP: cubic registered [ 5.492032] NET: Registered protocol family 17 [ 5.493115] Key type dns_resolver registered [ 5.500240] ata2: SATA link down (SStatus 0 SControl 300) [ 5.501941] ata1: SATA link down (SStatus 0 SControl 300) [ 5.506196] ata3: SATA link down (SStatus 0 SControl 300) [ 5.507732] ata4: SATA link down (SStatus 0 SControl 300) [ 5.509272] ata5: SATA link down (SStatus 0 SControl 300) [ 5.739233] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 5.741484] ata6.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100 [ 5.743574] ata6.00: 33554432 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 5.749226] ata6.00: SN:QM00013 [ 5.752213] ata6.00: applying bridge limits [ 5.753925] ata6.00: configured for UDMA/100 [ 5.755892] ata6.00: Find SSD disks. [QEMU HARDDISK] [ 5.758375] ata11: SATA link down (SStatus 0 SControl 300) [ 5.760608] ata10: SATA link down (SStatus 0 SControl 300) [ 5.763473] ata8: SATA link down (SStatus 0 SControl 300) [ 5.767459] ata7: SATA link down (SStatus 0 SControl 300) [ 5.771560] ata9: SATA link down (SStatus 0 SControl 300) [ 5.775812] scsi 5:0:0:0: Direct-Access QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5 [ 5.786253] sd 5:0:0:0: [sda] 33554432 512-byte logical blocks: (17.1 GB/16.0 GiB) [ 5.808302] sd 5:0:0:0: [sda] Write Protect is off [ 5.811053] sd 5:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 5.820120] sd 5:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 5.826846] sda: unknown partition table [ 5.829732] sd 5:0:0:0: [sda] Attached SCSI disk [ 5.832030] Loading module verification blacklist certificates [ 5.834366] Loading module verification certificates [ 5.836281] MODSIGN: Loaded cert 'Synology SDG kernel module signing key: 7bd0b0d6bcd31651c22ce3978bdc8c8bdc417329' [ 5.840263] MODSIGN: Loaded cert 'Synology Root Certification Authority: f2c075361f168425f8b5ef31b796406c3aab2089' [ 5.843043] MODSIGN: Loaded cert 'Synology Kernel Module Signing Certification Authority: 600839b5d127e0e11d817a31f0575d323a7c0e28' [ 5.846311] MODSIGN: Loaded cert 'Synology kernel module signing key: 4646ce54489669338118a3b1286da156ac366fa5' [ 5.849329] registered taskstats version 1 [ 5.865173] rtc_cmos 00:04: setting system clock to 2022-02-15 10:51:53 UTC (1644922313) [ 5.870269] Freeing unused kernel memory: 828k freed [ 5.871973] Write protecting the kernel read-only data: 8192k [ 5.873534] Freeing unused kernel memory: 1312k freed [ 5.876906] Freeing unused kernel memory: 480k freed START /linuxrc.syno START /linuxrc.syno.impl Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore[ 5.997728] ACPI: bus type USB registered [ 6.002088] usbcore: registered new interface driver usbfs [ 6.005894] usbcore: registered new interface driver hub [ 6.011176] usbcore: registered new interface driver ethub [ 6.019089] usbcore: registered new device driver usb ... [ OK ] :: Loading module ehci-hcd[ 6.054093] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ... [ OK ] :: Loading module ehci-pci[ 6.070713] ehci-pci: EHCI PCI platform driver [ 6.073094] ehci-pci 0000:00:1a.7: setting latency timer to 64 [ 6.074524] ehci-pci 0000:00:1a.7: EHCI Host Controller [ 6.075755] ehci-pci 0000:00:1a.7: new USB bus registered, assigned bus number 1 [ 6.077732] ehci-pci 0000:00:1a.7: irq 19, io mem 0xfd84a000 [ 6.085096] ehci-pci 0000:00:1a.7: USB 2.0 started, EHCI 1.00 [ 6.087942] hub 1-0:1.0: USB hub found [ 6.088902] hub 1-0:1.0: 6 ports detected [ 6.091235] ehci-pci 0000:00:1d.7: setting latency timer to 64 [ 6.092642] ehci-pci 0000:00:1d.7: EHCI Host Controller [ 6.093890] ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 2 [ 6.095931] ehci-pci 0000:00:1d.7: irq 19, io mem 0xfd84f000 [ 6.103112] ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00 [ 6.108884] hub 2-0:1.0: USB hub found [ 6.109864] hub 2-0:1.0: 6 ports detected ... [ OK ] :: Loading module uhci-hcd[ 6.169305] uhci_hcd: USB Universal Host Controller Interface driver [ 6.171975] uhci_hcd 0000:00:1a.0: setting latency timer to 64 [ 6.173372] uhci_hcd 0000:00:1a.0: UHCI Host Controller [ 6.174615] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3 [ 6.176498] uhci_hcd 0000:00:1a.0: irq 16, io base 0x000050a0 [ 6.188504] hub 3-0:1.0: USB hub found [ 6.189576] hub 3-0:1.0: 2 ports detected [ 6.191865] uhci_hcd 0000:00:1a.1: setting latency timer to 64 [ 6.193259] uhci_hcd 0000:00:1a.1: UHCI Host Controller [ 6.195137] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4 [ 6.200399] uhci_hcd 0000:00:1a.1: irq 17, io base 0x000050c0 [ 6.208706] hub 4-0:1.0: USB hub found [ 6.209842] hub 4-0:1.0: 2 ports detected [ 6.212528] uhci_hcd 0000:00:1a.2: setting latency timer to 64 [ 6.214175] uhci_hcd 0000:00:1a.2: UHCI Host Controller [ 6.215802] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5 [ 6.218308] uhci_hcd 0000:00:1a.2: irq 18, io base 0x000050e0 [ 6.233190] hub 5-0:1.0: USB hub found [ 6.234397] hub 5-0:1.0: 2 ports detected [ 6.236483] uhci_hcd 0000:00:1d.0: setting latency timer to 64 [ 6.238002] uhci_hcd 0000:00:1d.0: UHCI Host Controller [ 6.239395] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6 [ 6.241376] uhci_hcd 0000:00:1d.0: irq 16, io base 0x00005100 [ 6.293104] hub 6-0:1.0: USB hub found [ 6.294174] hub 6-0:1.0: 2 ports detected [ 6.297049] uhci_hcd 0000:00:1d.1: setting latency timer to 64 [ 6.299137] uhci_hcd 0000:00:1d.1: UHCI Host Controller [ 6.300910] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7 [ 6.303543] uhci_hcd 0000:00:1d.1: irq 17, io base 0x00005120 [ 6.318340] hub 7-0:1.0: USB hub found [ 6.323631] hub 7-0:1.0: 2 ports detected [ 6.328199] uhci_hcd 0000:00:1d.2: setting latency timer to 64 [ 6.334508] uhci_hcd 0000:00:1d.2: UHCI Host Controller [ 6.336973] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8 [ 6.340669] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00005140 [ 6.394398] hub 8-0:1.0: USB hub found [ 6.395495] hub 8-0:1.0: 2 ports detected ... [ OK ] :: Loading module xhci-hcd[ 6.456258] xhci_hcd 0000:00:01.0: xHCI Host Controller [ 6.457606] xhci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 9 [ 6.460102] xhci_hcd 0000:00:01.0: irq 46 for MSI/MSI-X [ 6.461529] xhci_hcd 0000:00:01.0: irq 47 for MSI/MSI-X [ 6.470266] xHCI xhci_add_endpoint called for root hub [ 6.471599] xHCI xhci_check_bandwidth called for root hub [ 6.478331] hub 9-0:1.0: USB hub found [ 6.479614] hub 9-0:1.0: 4 ports detected [ 6.481134] xhci_hcd 0000:00:01.0: xHCI Host Controller [ 6.482763] xhci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 10 [ 6.501123] xHCI xhci_add_endpoint called for root hub [ 6.502608] xHCI xhci_check_bandwidth called for root hub [ 6.507179] hub 10-0:1.0: USB hub found [ 6.508317] hub 10-0:1.0: 4 ports detected ... [ OK ] :: Loading module usb-storage[ 6.597587] usbcore: registered new interface driver usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "button.ko" for jg.acpid (args:[ 6.639133] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 [ 6.641022] ACPI: Power Button [PWRF] ) Loading kmod #1 "evdev.ko" for jg.acpid (args: ) Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script Checking for VirtIO VirtIO hypervisor detected Loading kmod #0 "virtio.ko" for thethorgroup.virtio (args: ) Loading kmod #1 "virtio_ring.ko" for thethorgroup.virtio (args: ) Loading kmod #2 "virtio_mmio.ko" for thethorgroup.virtio (args: ) Loading kmod #3 "virtio_pci.ko" for thethorgroup.virtio (args: ) [ 6.763461] virtio-pci 0000:00:02.0: setting latency timer to 64 [ 6.768188] virtio-pci 0000:00:03.0: setting latency timer to 64 [ 6.774237] virtio-pci 0000:06:03.0: setting latency timer to 64 [ 6.778617] virtio-pci 0000:06:0a.0: setting latency timer to 64 Loading kmod #4 "virtio_blk.ko" for thethorgroup.virtio (args: ) [ 6.817904] virtio-pci 0000:06:0a.0: irq 48 for MSI/MSI-X [ 6.819585] virtio-pci 0000:06:0a.0: irq 49 for MSI/MSI-X [ 6.823592] vda: unknown partition table Loading kmod #5 "virtio_net.ko" for thethorgroup.virtio (args: ) [ 6.855738] virtio-pci 0000:00:02.0: irq 50 for MSI/MSI-X [ 6.857259] virtio-pci 0000:00:02.0: irq 51 for MSI/MSI-X [ 6.858832] virtio-pci 0000:00:02.0: irq 52 for MSI/MSI-X Loading kmod #6 "virtio_scsi.ko" for thethorgroup.virtio (args: ) Loading kmod #7 "9pnet.ko" for thethorgroup.virtio (args: ) [ 6.924451] 9pnet: module has bad taint, not creating trace events [ 6.926083] 9pnet: Installing 9P2000 support Loading kmod #8 "9pnet_virtio.ko" for thethorgroup.virtio (args: ) [ 6.942718] virtio-pci 0000:00:03.0: irq 53 for MSI/MSI-X [ 6.944704] virtio-pci 0000:00:03.0: irq 54 for MSI/MSI-X Loading kmod #9 "9p.ko" for thethorgroup.virtio (args: ) [ 6.973797] 9p: Installing v9fs 9p2000 file system support :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot [ 7.833383] usb 10-1: new SuperSpeed USB device number 2 using xhci_hcd [ 7.852470] usb 10-1: Parent hub missing LPM exit latency info. Power management will be impacted. [ 7.859372] usb-storage 10-1:1.0: USB Mass Storage device detected [ 7.865050] scsi13 : usb-storage 10-1:1.0 Still waiting for boot device (waited 1 of 30 seconds) [ 8.872899] scsi 13:0:0:0: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5 [ 8.878658] sd 13:0:0:0: [synoboot] 262144 512-byte logical blocks: (134 MB/128 MiB) [ 8.881149] sd 13:0:0:0: [synoboot] Write Protect is off [ 8.882453] sd 13:0:0:0: [synoboot] Mode Sense: 63 00 00 08 [ 8.890931] sd 13:0:0:0: [synoboot] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Still waiting for boot device (waited 2 of 30 seconds) The /dev/synoboot device exists but it does not contain expected partitions (>=3 partitions) ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== [ 10.179290] synoboot: synoboot1 synoboot2 synoboot3 [ 10.464506] sd 13:0:0:0: [synoboot] Attached SCSI removable disk Error: /dev/sda: unrecognised disk label Error: /dev/vda: unrecognised disk label get disk fail get disk fail /dev/synoboot1 2048 100351 98304 83 /dev/synoboot2 100352 253951 153600 83 /dev/synoboot3 253952 262143 8192 83 ========== END OF DUMP OF ALL PARTITIONS DETECTED ========== Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=1 ERROR: Some of the scripts failed! See above for any with exit != 0 :: Executing "on_booumount: /etc/mtab: No such file or directory linuxrc.syno failed on 99 starting pid 4387, tty '': '/etc/rc' :: Starting /etc/rc :: Mounting procfs ... [ OK ] :: Mounting tmpfs ... [ OK ] :: Mounting devtmpfs ... [ OK ] :: Mounting devpts ... [ OK ] :: Mounting sysfs ... [ OK ] :: Loading module sg[ 10.827796] sd 5:0:0:0: Attached scsi generic sg0 type 0 [ 10.842597] sd 13:0:0:0: Attached scsi generic sg1 type 0 ... [ OK ] :: Loading module fat ... [ OK ] :: Loading module vfat ... [ OK ] :: Loading module ip_tunnel ... [ OK ] :: Loading module vxlan ... [ OK ] :: Loading module dca[ 10.997746] dca service started, version 1.12.1 ... [ OK ] :: Loading module e1000e[ 11.030152] e1000e: Intel(R) PRO/1000 Network Driver - 3.4.2.4-NAPI [ 11.035132] e1000e: Copyright(c) 1999 - 2019 Intel Corporation. ... [ OK ] :: Loading module i2c-algo-bit ... [ OK ] :: Loading module igb[ 11.080839] Intel(R) Gigabit Ethernet Linux Driver - version 5.3.5.22 [ 11.089298] Copyright(c) 2007 - 2018 Intel Corporation. ... [ OK ] :: Loading module ixgbe[ 11.120808] Intel(R) 10GbE PCI Express Linux Network Driver - version 5.5.5 [ 11.125976] Copyright(c) 1999 - 2019 Intel Corporation. ... [ OK ] :: Loading module i40e[ 11.163130] i40e: Intel(R) 40-10 Gigabit Ethernet Connection Network Driver - version 2.7.29 [ 11.173542] i40e: Copyright(c) 2013 - 2018 Intel Corporation. ... [ OK ] :: Loading module sunrpc[ 11.220032] RPC: Registered named UNIX socket transport module. [ 11.224502] RPC: Registered udp transport module. [ 11.227995] RPC: Registered tcp transport module. [ 11.230640] RPC: Registered tcp NFSv4.1 backchannel transport module. ... [ OK ] :: Loading module lockd ... [ OK ] :: Loading module nfs ... [ OK ] :: Loading module nfsv3 ... [ OK ] :: Loading module i2c-i801[ 11.308620] i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt ... [ OK ] :: Loading module adt7475 ... [ OK ] Can not detect ADT device, Retry: 1... :: Unloading module adt7475[ 12.375211] Module [adt7475] is removed. ... [ OK ] :: Unloading module i2c-i801[ 12.396176] Module [i2c_i801] is removed. ... [ OK ] :: Loading module i2c-i801[ 13.463413] i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt ... [ OK ] :: Loading module adt7475 ... [ OK ] Can not detect ADT device, Retry: 2... :: Unloading module adt7475[ 14.565502] Module [adt7475] is removed. ... [ OK ] :: Unloading module i2c-i801[ 14.584461] Module [i2c_i801] is removed. ... [ OK ] :: Loading module i2c-i801[ 15.631981] i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt ... [ OK ] :: Loading module adt7475 ... [ OK ] Can not detect ADT device, Retry: 3... :: Unloading module adt7475[ 16.685294] Module [adt7475] is removed. ... [ OK ] :: Unloading module i2c-i801[ 16.715804] Module [i2c_i801] is removed. ... [ OK ] :: Loading module i2c-i801[ 17.764671] i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt ... [ OK ] :: Loading module adt7475 ... [ OK ] [ 17.817310] bromolow_synobios: module license 'Synology Inc.' taints kernel. [ 17.819246] Disabling lock debugging due to kernel taint [ 17.824286] synobios open /dev/ttyS1 success [ 17.825681] 2022-2-15 10:52:5 UTC [ 17.826480] synobios: load, major number 201 [ 17.827516] Brand: Synology [ 17.828180] Model: DS-3615xs [ 17.828908] set group disks wakeup number to 4, spinup time deno 7 [ 17.830338] synobios cpu_arch proc entry initialized [ 17.831525] synobios crypto_hw proc entry initialized [ 17.832799] synobios syno_platform proc entry initialized Starting SW init... [ 17.852974] Module [bromolow_synobios] is removed. [ 17.854211] synobios: unload :: Loading module synobios[ 17.909887] synobios open /dev/ttyS1 success [ 17.911255] 2022-2-15 10:52:5 UTC [ 17.912060] synobios: load, major number 201 [ 17.913107] Brand: Synology [ 17.913750] Model: DS-3615xs [ 17.914468] set group disks wakeup number to 4, spinup time deno 7 [ 17.915942] synobios cpu_arch proc entry initialized [ 17.917143] synobios crypto_hw proc entry initialized [ 17.918572] synobios syno_platform proc entry initialized ... [ OK ] udhcpc: started, v1.30.1 eth0 Link encap:Ethernet HWaddr 00:11:32:2C:A7:85 inet addr:20.20.20.21 Bcast:20.20.20.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:684 (684.0 B) TX bytes:642 (642.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) :: Starting syslogd ... [ OK ] :: Starting scemd :: Starting services in background Starting findhostd in flash_rd... Starting services in flash_rd... Running /usr/syno/etc/rc.d/J01httpd.sh... Starting httpd:80 in flash_rd... Starting httpd:5000 in flash_rd... Running /usr/syno/etc/rc.d/J03ssdpd.sh... /usr/bin/minissdpd -i eth0 (15): upnp:rootdevice (51): uuid:upnp_SynologyNAS-0011322ca785::upnp:rootdevice (55): Synology/synology_bromolow_3615xs/7.0-42218/20.20.20.21 (44): http://20.20.20.21:5000/description-eth0.xml Connected. done. /usr/syno/bin/reg_ssdp_service 20.20.20.21 0011322ca785 7.0-42218 synology_bromolow_3615xs eth0 Running /usr/syno/etc/rc.d/J04synoagentregisterd.sh... Starting synoagentregisterd... Running /usr/syno/etc/rc.d/J30DisableNCQ.sh... Running /usr/syno/etc/rc.d/J80ADTFanControl.sh... Running /usr/syno/etc/rc.d/J98nbnsd.sh... Starting nbnsd... Running /usr/syno/etc/rc.d/J99avahi.sh... Starting Avahi mDNS/DNS-SD Daemon cname_load_conf failed:/var/tmp/nginx/avahi-aliases.conf :: Loading module etxhci-hcd ... [ OK ] :: Loading module hid ... [ OK ] :: Loading module usbhid[ 25.818105] usbcore: registered new interface driver usbhid [ 25.819603] usbhid: USB HID core driver ... [ OK ] Excution Error ============ Date ============ Tue Feb 15 10:52:12 UTC 2022 ============================== starting pid 5883, tty '': '/sbin/getty 115200 console' Tue Feb 15 10:52:12 2022 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. BusyBox v1.30.1 () built-in shell (ash) DiskStation> df Filesystem 1K-blocks Used Available Use% Mounted on /tmp 495136 12 495124 0% /tmp none 483956 0 483956 0% /dev none 483956 0 483956 0% /proc/bus/usb DiskStation> please give me solutions.. EDIT: ubuntu:latest based image also same.. Edited February 15, 2022 by hendry Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 15, 2022 Share #77 Posted February 15, 2022 (edited) On 2/14/2022 at 12:37 PM, hendry said: please fix your code for this error Ok, ty. Typo fixed in source code and push in docker. 12 hours ago, hendry said: did you success to install DSM 7.0.1 on docker ? Yes, it seems to work pretty well. On 2/14/2022 at 12:37 PM, hendry said: va not found Failed to process header It's usually that you updated to a DSM version that the bootloader does not support. Well... You do too much posting and give too information about different things ... and mix up things ... that i am lost about what u are trying or succeed to do (especially reading on a phone). Calm down and just do step by step. Delete all docker container and image about uxora/xpenology . Then just run the docker command to launch xpenology (it should pull the latest image on docker server) And just post the output to see if any error. (I mean just the script output without log of the booting process) And in your last post, I don't see any issue. You go up to the login prompt without any serious error and even login. Just open a web browser on IP:5000 and you should see DSM working for installation step. Edited February 15, 2022 by uxora-com Quote Link to comment Share on other sites More sharing options...
hendry Posted February 16, 2022 Share #78 Posted February 16, 2022 10 hours ago, uxora-com said: Ok, ty. Typo fixed in source code and push in docker. Yes, it seems to work pretty well. It's usually that you updated to a DSM version that the bootloader does not support. Well... You do too much posting and give too information about different things ... and mix up things ... that i am lost about what u are trying or succeed to do (especially reading on a phone). Calm down and just do step by step. Delete all docker container and image about uxora/xpenology . Then just run the docker command to launch xpenology (it should pull the latest image on docker server) And just post the output to see if any error. (I mean just the script output without log of the booting process) And in your last post, I don't see any issue. You go up to the login prompt without any serious error and even login. Just open a web browser on IP:5000 and you should see DSM working for installation step. Sorry... i'm so panic to see some errors.. the last experience, i re create container and pulled from uxora/xpenology latest (which using debian as based image). Yes, i can go to DSM web ui, but as my last post.. i can't install DSM pat file because it tells me there's no harddrive or SATA interface. you can see on the boot process at my last post.. please give me a clue.. Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 16, 2022 Share #79 Posted February 16, 2022 (edited) 8 hours ago, hendry said: there's no harddrive or SATA interface In your log posted, it seems you have some error especially with the bootloader ... so maybe the bootloader or virtual disk has issue. And the "df" command you did, it's just to see mounted partition ... it does not show you disks attached to the machine. Can you give me all your command line to run the xpenology docker ? Did you remove all image container before running the docker command ? If not, you can do it with the following command: docker rmi $( docker image ls --filter 'reference=uxora/*' -q ) And you need to delete all file in "/xpenology/syst/" as well. (except "bootloader.img" if you do not use BOOTLOADER_URL). Edited February 16, 2022 by uxora-com Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 16, 2022 Share #80 Posted February 16, 2022 I just figured out that this repository of this guy contains several bootloader for proxmox. I tested its 1.03b / redpill for ds3615xs and it seems to be working pretty well with xpenology-docker. Maybe you can give a try with this. Quote Link to comment Share on other sites More sharing options...
hendry Posted February 16, 2022 Share #81 Posted February 16, 2022 22 minutes ago, uxora-com said: In your log posted, it seems you have some error especially with the bootloader ... so maybe the bootloader or virtual disk has issue. And the "df" command you did, it's just to see mounted partition ... it does not show you disks attached to the machine. Can you give me all your command line to run the xpenology docker ? Did you remove all image container before running the docker command ? If not, you can do it with the following command: docker rmi $( docker image ls --filter 'reference=uxora/*' -q ) And you need to delete all file in "/xpenology/syst/" as well. (except "bootloader.img" if you do not use BOOTLOADER_URL). ok.. i remove all docker images and leave with empty images. then i run container with this command docker run --privileged --name xpenology --cap-add=NET_ADMIN \ --device=/dev/net/tun --device=/dev/kvm \ -p 5500:5000 -p 5001:5001 -p 2224:22 -p 8084:80 \ -e CPU="qemu64" \ -e THREADS=1 \ -e RAM=1024 \ -e DISK_SIZE="8G 16G" \ -e DISK_PATH="/xpy_syst" \ -e BOOTLOADER_AS_USB="Y" \ -e VM_ENABLE_VIRTIO="Y" \ -e VM_PATH_9P="/xpy_data /xpy_syst" \ -v /share/CACHEDEV1_DATA/Public/XPE/data:/xpy_data \ -v /share/CACHEDEV1_DATA/Public/XPE/syst:/xpy_syst \ -it --entrypoint /bin/bash \ uxora/xpenology then on the container prompt i run /usr/bin/vm-startup but ended with iptables error.. the latest iptables has some problem issue. i found another thread to restore with iptables-legacy. you should add your Dockerfile script with these statement. and please update uxora/xpenology too. mv /usr/sbin/iptables /usr/sbin/iptables-broken && \ cp /usr/sbin/iptables-legacy /usr/sbin/iptables && \ mv /usr/sbin/iptables-restore /usr/sbin/iptables-restore-broken && \ mv /usr/sbin/ip6tables-restore /usr/sbin/ip6tables-restore-broken && \ mv /usr/sbin/iptables-save /usr/sbin/iptables-save-broken && \ mv /usr/sbin/ip6tables-save /usr/sbin/ip6tables-save-broken && \ cp /usr/sbin/iptables-legacy-restore /usr/sbin/iptables-restore && \ cp /usr/sbin/ip6tables-legacy-restore /usr/sbin/ip6tables-restore && \ cp /usr/sbin/iptables-legacy-save /usr/sbin/iptables-save && \ cp /usr/sbin/ip6tables-legacy-save /usr/sbin/ip6tables-save after running those statement, i can type iptables -t nat -L with no error anymore. then i start to run the vm-startup script again. but still stuck with no harddrive or sata warning. do u think, it's bootloader problem related ? can u give me your bootloader.img ? but weird, i can see the boot process detect the harddisk but using SCSI not SATA. [ 5.842462] scsi 5:0:0:0: Direct-Access QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5 [ 5.851227] sd 5:0:0:0: [sda] 16777216 512-byte logical blocks: (8.58 GB/8.00 GiB) [ 5.861632] sd 5:0:0:0: [sda] Write Protect is off [ 5.867085] sd 5:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 5.871131] ata7.00: Find SSD disks. [QEMU HARDDISK] [ 5.882901] scsi 6:0:0:0: Direct-Access QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5 [ 5.907067] sd 5:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 5.930885] sd 6:0:0:0: [sdb] 33554432 512-byte logical blocks: (17.1 GB/16.0 GiB) [ 5.956046] sda: unknown partition table [ 5.970445] sd 6:0:0:0: [sdb] Write Protect is off [ 5.974232] sd 6:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 5.978865] sd 5:0:0:0: [sda] Attached SCSI disk [ 5.983172] sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 5.995054] sdb: unknown partition table [ 6.000893] sd 6:0:0:0: [sdb] Attached SCSI disk Quote Link to comment Share on other sites More sharing options...
hendry Posted February 16, 2022 Share #82 Posted February 16, 2022 (edited) 11 minutes ago, uxora-com said: I just figured out that this repository of this guy contains several bootloader for proxmox. I tested its 1.03b / redpill for ds3615xs and it seems to be working pretty well with xpenology-docker. Maybe you can give a try with this. yes, i found and download it from that same site.. and i choose redpill_DS3615xs_701_42218_virtio_9p.img.tgz file, extracted it into .img file then rename it into bootloader.img and put it on /share/CACHEDEV1_DATA/Public/XPE/syst host folder which symlink to /xpy_syst inside docker container. Edited February 16, 2022 by hendry Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 16, 2022 Share #83 Posted February 16, 2022 22 minutes ago, hendry said: then i start to run the vm-startup script again What is the ouput of the script (at the beginning without the booting process log)? Quote Link to comment Share on other sites More sharing options...
hendry Posted February 16, 2022 Share #84 Posted February 16, 2022 37 minutes ago, uxora-com said: What is the ouput of the script (at the beginning without the booting process log)? root@1855bde5781d:/# /usr/bin/vm-startup INFO: Xpenology docker is starting ... INFO: Skip URL download, raw bootloader already exist: /xpy_syst/bootloader.img . INFO: Backing up bootloader: /xpy_syst/bootloader.img.tar.gz INFO: Modification of grub.cfg ... INFO: ddReplace for: vid=0x46f4 INFO: ... Successful replacement of: vid=0x46f4 INFO: ... Successful replacement of: vid=0x46f4 INFO: ddReplace for: pid=0x0001 INFO: ... Successful replacement of: pid=0x0001 INFO: ... Successful replacement of: pid=0x0001 INFO: ddReplace for: mac1=0011322CA785 INFO: ... Successful replacement of: mac1=0011322CA785 INFO: ... Successful replacement of: mac1=0011322CA785 INFO: Bootloader has been converted to qcow2 INFO: Adding snapshot disk ... Formatting '/xpy_syst/vm-disk-snapshot.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=8388608 lazy_refcounts=off refcount_bits=16 INFO: ... new snapshot disk created INFO: Adding bootloader as USB ... INFO: Adding disk(s) ... INFO: ... No Initial Disk found, creating disk : /xpy_syst/vm-disk-data0.qcow2 Formatting '/xpy_syst/vm-disk-data0.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=8589934592 lazy_refcounts=off refcount_bits=16 INFO: ... No Initial Disk found, creating disk : /xpy_syst/vm-disk-data1.qcow2 Formatting '/xpy_syst/vm-disk-data1.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=17179869184 lazy_refcounts=off refcount_bits=16 INFO: Adding 9p sharefolders ... INFO: ... path=/xpy_data , mount_tag=hostdata0 INFO: ... path=/xpy_syst , mount_tag=hostdata1 INFO: KVM acceleration enabled INFO: Configuring network ... net.ipv4.ip_forward = 1 INFO: DHCP configured to serve IP 20.20.20.21/24 via dockerbridge INFO: Hack for guest VMs complaining about: bad udp checksums in 5 packets iptables v1.8.7 (legacy): unknown option "--checksum-fill" Try `iptables -h' or 'iptables --help' for more information. WARNING: Iptables hack for checksum FAILED Actual changes: tx-checksum-ip-generic: off tx-tcp-segmentation: off [not requested] tx-tcp-ecn-segmentation: off [not requested] tx-tcp-mangleid-segmentation: off [not requested] tx-tcp6-segmentation: off [not requested] tx-checksum-sctp: off INFO: Lauching dnsmasq DEBUG: dnsmasq options: --dhcp-range=20.20.20.21,20.20.20.21 --dhcp-host=00:11:32:2C:A7:85,,20.20.20.21,VirtualMachine,infinite --dhcp-option=option:netmask,255.255.255.0 --dhcp-option=option:dns-server,10.100.3.1 --dhcp-option=option:router,20.20.20.1 --dhcp-option=option:domain-search, --dhcp-option=option:domain-name, INFO: Launching qemu-kvm ... DEBUG: qemu-system-x86_64 -machine q35 -readconfig /qemu_cfg/pve-q35-4.0.cfg -nodefaults -overcommit mem-lock=off -msg timestamp=on -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -serial stdio -monitor unix:/run/qemu-monitor.sock,server,nowait -pidfile /run/qemu.pid -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -enable-kvm -machine accel=kvm,usb=off -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/xpy_syst/vm-disk-snapshot.qcow2,if=none,id=drive-disk-snap,format=qcow2,cache=writeback,discard=on,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-disk-snap,id=virtio-disk-snap,bus=pci.0,addr=0xa' -device 'nec-usb-xhci,id=usb-bus0,multifunction=on' -drive 'file=/xpy_syst/bootloader.qcow2,format=qcow2,if=none,id=drive-disk-bootloader,cache=none,aio=native,detect-zeroes=on' -device 'usb-storage,bus=usb-bus0.0,port=1,drive=drive-disk-bootloader,id=usb-disk-bootloader,bootindex=1,removable=on' -drive 'file=/xpy_syst/vm-disk-data0.qcow2,if=none,id=drive-sata0,format=qcow2,cache=writeback,discard=on,aio=threads,detect-zeroes=on' -device 'ide-hd,bus=ahci0.0,drive=drive-sata0,id=sata0,rotation_rate=1' -drive 'file=/xpy_syst/vm-disk-data1.qcow2,if=none,id=drive-sata1,format=qcow2,cache=writeback,discard=on,aio=threads,detect-zeroes=on' -device 'ide-hd,bus=ahci0.1,drive=drive-sata1,id=sata1,rotation_rate=1' -nographic -m 1024 -cpu qemu64 -smp 1,sockets=1,cores=1,threads=1 -netdev tap,ifname=vm-nat,script=no,downscript=no,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,mac=00:11:32:2C:A7:85,id=net0 -fsdev local,security_model=passthrough,id=fsdev-fs0,path=/xpy_data -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=hostdata0,bus=pcie.0 -fsdev local,security_model=passthrough,id=fsdev-fs1,path=/xpy_syst -device virtio-9p-pci,id=fs1,fsdev=fsdev-fs1,mount_tag=hostdata1,bus=pcie.0 char device redirected to /dev/pts/1 (label charserial0) SeaBIOS (version 1.14.0-2) iPXE (http://ipxe.org) 00:02.0 C000 PCI2.10 PnP PMM+3FF74BD0+3FEB4BD0 C000 Booting from Hard Disk... GRUB loading. Welcome to GRUB! error: file `/boot/grub/i386-pc/efi_gop.mod' not found. error: file `/boot/grub/i386-pc/efi_gop.mod' not founderror: file `/boot/grub/i386-pc/efi_uga.mod' not found. . error: file `/boot/grub/i386-pc/efi_uga.mod' not founderror: file `/boot/grub/unicode.pf2' not found. . error: file `/boot/grub/unicode.pf2' not found GNU GRUB version 2.06 +----------------------------------------------------------------------------+ |*RedPill DS3615xs v7.0.1-42218 (USB, Verbose) .| | RedPill DS3615xs v7.0.1-42218 (SATA, Verbose) | | | | | | | | | | | | | | | | | | | | | +----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. GNU GRUB version 2.06 this is the log from the script file.. Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 16, 2022 Share #85 Posted February 16, 2022 Ok, I think I figured it out. It's something about the bootloader which has set DiskIdxMap and SataPortMap values too high that xpenology-docker does not seem to like. There is GRUBCFG_DISKIDXMAP and GRUBCFG_SATAPORTMAP variable to fix that ... but it does not seems functional with the way how it changes the value in bootloader, I will fix that later with iptables stuff. Quote Link to comment Share on other sites More sharing options...
hendry Posted February 16, 2022 Share #86 Posted February 16, 2022 32 minutes ago, uxora-com said: Ok, I think I figured it out. It's something about the bootloader which has set DiskIdxMap and SataPortMap values too high that xpenology-docker does not seem to like. There is GRUBCFG_DISKIDXMAP and GRUBCFG_SATAPORTMAP variable to fix that ... but it does not seems functional with the way how it changes the value in bootloader, I will fix that later with iptables stuff. hmm, i don't know how to change DiskIdxMap & SataPortMap parameter inside the bootloader. Do i need to build redpill loader by putting the loader img file into vm guest and boot into linux mode then run redpill script as the instruction from redpill's github? or from your docker container u add those 2 param? and what value should be set? Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 16, 2022 Share #87 Posted February 16, 2022 Here it is, I just pushed modification on github and docker server. You can now add the following option to docker command line: -e GRUBCFG_DISKIDXMAP="00" -e GRUBCFG_SATAPORTMAP="1" This should fix your disk sata error. About your your iptables thing, I don't know if it's fixed because I cannot test it (and i dont want it your cp/mv stuff coz it break in other system) but let me know. Quote Link to comment Share on other sites More sharing options...
hendry Posted February 17, 2022 Share #88 Posted February 17, 2022 15 hours ago, uxora-com said: Here it is, I just pushed modification on github and docker server. You can now add the following option to docker command line: -e GRUBCFG_DISKIDXMAP="00" -e GRUBCFG_SATAPORTMAP="1" This should fix your disk sata error. About your your iptables thing, I don't know if it's fixed because I cannot test it (and i dont want it your cp/mv stuff coz it break in other system) but let me know. YESS... Adding both 2 new parameters bring me success install Xpenology docker on my QNAP. 9p datashare also can be mounted. so i can indexing my audio files taken from host folder inside docker. then audio station working to detect all of my mp3 files from host folder.. good !! if i put some files inside it, how can i access samba folder from outside ? usually i just type \\xpenology on windows explorer to access shared folder, but i can't. i think maybe docker container cannot bring smb service to outside docker. any idea ? another things, if i want to change or add some 9p datashare folder after container created, is it possible ? i follow this site to edit the mountpoints of docker volume, but when i restart docker, xpenology goes to the default first installation screen with asking to format the harddrive, etc. @uxora-com Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 17, 2022 Share #89 Posted February 17, 2022 (edited) Congratulation! 5 hours ago, hendry said: if i put some files inside it, how can i access samba folder from outside ? usually i just type \\xpenology on windows explorer to access shared folder, but i can't. i think maybe docker container cannot bring smb service to outside docker. any idea ? For smb, you need to port forward smb port on docker with option: "-p 137-139:137-139 -p 445:445". Then you can access smb with its IP (ie. "\\192.168.0.10"). If you want to name it, you can add it to hosts file on your windows/linux. (Needs administrator privileges) 5 hours ago, hendry said: another things, if i want to change or add some 9p datashare folder after container created, is it possible ? Not sure how to change option (-e and -v) of an existing container ... it was possible in old docker version, maybe it still possible ... well, I will let u find it in google, and let us know if u find it. Otherwise as alternative, you can recreate a new container with new options (with keeping vm disks) as follow : - In "syst/" folder, uncompress : "$ "tar -xzf bootloader.img.tar.gz" - Delete (or move it): "$ rm bootloader.img.tar.gz bootloader.qcow2" - Delete (if you want): "$ docker container rm $( docker container ls -qf 'ancestor=uxora/xpenology' )" - Then recreate a container with new option: "$ docker run --privileged [...]" And about automount 9p at boot time, use "Control Panel > Task Scheduler > Create > Triggered Task" to run your command line as root. HTH, Edited February 17, 2022 by uxora-com Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 17, 2022 Share #90 Posted February 17, 2022 11 hours ago, hendry said: edit the mountpoints of docker volume Actually if it's just to change the mount point, you don't need to delete bootloader ... you can just recreate a new container with the same options but just changing mount point option (-v). The instruction with delete, I gave you, is if you want to change an option about the bootloader ... otherwise you just need to recreate the container without any delete (except the old container if you want). Don't worry about that, you should get back your dsm xpenology with all your data in place even in a new container as long as it uses the same vm disks. Quote Link to comment Share on other sites More sharing options...
seanone Posted February 18, 2022 Share #91 Posted February 18, 2022 On 2/12/2022 at 12:02 AM, uxora-com said: @seanone @hendry @s2k7 Hi all, It's been a while ... I had some free time, so I have just updated https://github.com/uxora-com/xpenology-docker repository : - to take in count Redpill bootloader compatibility - to be able to change vid, pid and sn just by providing variables in cmd line (GRUBCFG_VID, GRUBCFG_PID and GRUBCFG_SN) - to be able to run docker without BOOTLOADER_URL To compile your own redpill loader with virtio and 9p, you may want to use RedPill Tinycore loader img and check this: - https://github.com/uxora-com/rpext I did a quick test with redpill for DS3615xs with virtio/9p and it seems to be working pretty well. I did not test it long enough to know if it's as much stable as Jun's loader 1.03b. HTH, Thank you for your work. I have created DS918+ bootloader with pocopico's tinycore and s2k7's virio dirver. 9pfs also works well in unraid vm with share(9pfs actually), not only in docker. But there's a problom that FileStation can only read, delete, and rename files mounted in 9pfs, but cannot add or move files. Other kits like Photo have a similar problom. Not a permissions issue as files can be created via ssh shell with same user. Do you met same problom? Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 18, 2022 Share #92 Posted February 18, 2022 (edited) 5 hours ago, seanone said: But there's a problom that FileStation can only read, delete, and rename files mounted in 9pfs, but cannot add or move files. Other kits like Photo have a similar problom. Not a permissions issue as files can be created via ssh shell with same user. I just did some test and i did have some issue of editing a file with FileEditor and it cannot save the change. This 9p folder is not configure to use dsm ACL permission, but use the basic linux filesystem permission. I just run these commands in ssh to fix this: $ sudo chown -R root:users /volume1/datashare9p $ sudo chmod -R g+w /volume1/datashare9p And it may depends on your qemu and mount option as well, you may want to check this about that (especially "access" option) : https://wiki.qemu.org/Documentation/9psetup I didn't really play and try to optimize qemu and mounting options about 9pfs, I just get and keep the same command from an older project. I just see that it works and never check its reliability and speed performance. HTH, Edited February 18, 2022 by uxora-com Quote Link to comment Share on other sites More sharing options...
hendry Posted February 19, 2022 Share #93 Posted February 19, 2022 (edited) On 2/18/2022 at 9:52 AM, seanone said: Thank you for your work. I have created DS918+ bootloader with pocopico's tinycore and s2k7's virio dirver. 9pfs also works well in unraid vm with share(9pfs actually), not only in docker. But there's a problom that FileStation can only read, delete, and rename files mounted in 9pfs, but cannot add or move files. Other kits like Photo have a similar problom. Not a permissions issue as files can be created via ssh shell with same user. Do you met same problom? i test it with redpill_DS3615xs_701_42218.img loader compiled included with 9p drivers, then i tried on the folder mounted using 9p drivers. it's okay using file station create folder, and push 1 file inside that folder. then delete that folder. no problem at all. i saw local host folder also affected. may i know, how did u create DS918+ bootloader from tinycore ? did u use VMWare do create it ? after the bootloader done created, when boot process, did u see the grub has 3 options as the 3rd option is to boot into tinycore UI ? because the bootloader of ds3615xs i downloaded only has 2 options, no option to boot into tinycore. Edited February 19, 2022 by hendry Quote Link to comment Share on other sites More sharing options...
hendry Posted February 19, 2022 Share #94 Posted February 19, 2022 (edited) On 2/17/2022 at 8:28 PM, uxora-com said: Congratulation! For smb, you need to port forward smb port on docker with option: "-p 137-139:137-139 -p 445:445". Then you can access smb with its IP (ie. "\\192.168.0.10"). If you want to name it, you can add it to hosts file on your windows/linux. (Needs administrator privileges) Not sure how to change option (-e and -v) of an existing container ... it was possible in old docker version, maybe it still possible ... well, I will let u find it in google, and let us know if u find it. Otherwise as alternative, you can recreate a new container with new options (with keeping vm disks) as follow : - In "syst/" folder, uncompress : "$ "tar -xzf bootloader.img.tar.gz" - Delete (or move it): "$ rm bootloader.img.tar.gz bootloader.qcow2" - Delete (if you want): "$ docker container rm $( docker container ls -qf 'ancestor=uxora/xpenology' )" - Then recreate a container with new option: "$ docker run --privileged [...]" And about automount 9p at boot time, use "Control Panel > Task Scheduler > Create > Triggered Task" to run your command line as root. HTH, about container volume, i try to delete the container and re-run a new one with the additional or changes volume, and it running well. all apps that i installed before & configuration was not lost. good.. about smb share, since i run container inside the NAS (Qnap), i think the smb port will be conflict with the host Qnap. because Qnap also has smb service. what is the solution if i want to access shared folder from xpenology container using smb in windows explorer ? so far, i run surveillance station recording to the local qnap host folder mounted using 9p is okay.. synology audio station & photos also okay.. can see all mp3 audio files & photos stored on qnap host folder using synology application on smartphone. for mp3 files & photos i also create volume in docker mounted using 9p drivers. great job.. !! i only see there's some laggy in performance and took some more memory also.. only 1GB RAM i used and 1 core on container. is it enough ? my QNAP is using 12GB RAM so, i no need to worry about it.. also i feel the synology surveilance station take memory less than QNAP QVR Pro which using more memory. then i uninstall Qnap QVR Pro, better using surveillance station on xpenology container. and when i reindex all mp3 & photo files, it took so long and occupy more resource on CPU usage. thank you so much to guide me @uxora-comfor the success.. PS: i want to try using DS918+ bootloader.. but i don't have it.. if u have, would u pls share to me ? Edited February 19, 2022 by hendry Quote Link to comment Share on other sites More sharing options...
hendry Posted February 19, 2022 Share #95 Posted February 19, 2022 (edited) i just added 1 mountpoint for 9p data share. and found an issue.. if i restart the container, why sometimes it bring back to the default installation screen at beginning ? at a glance i see on the boot log process, these log sometimes doesn't show ------------upgrade Begin upgrade procedure Mount data partition: /dev/md0 -> /tmpData No upgrade file exists End upgrade procedure ============upgrade ------------bootup-smallupdate Try bootup smallupdate UPGRADE_BOOTUP_SMALLUPDATE No patch exist. Skip Packed Bootup SmallUpdate Sparse files don't exist. Skip Sparse Bootup SmallUpdate Finished synoupgrade --bootup-smallupdate if it's not show, then the screen bring back to beginning installation process. but if i restart container once again, the boot process is normal and the web ui bring back to login page. another question, how can i mount using 9p to /volume1/homes folder ? this is the default permissions and ACL for /volume1/homes drwx--x--x+ 1 root root 34 Feb 19 16:35 homes [0] group:administrators:allow:rwxpdDaARWc--:fd-- (level: 0) [1] owner::allow:rwxpdDaARWcCo:fd-- (level: 0) [2] everyone::allow:--x----------:fd-- (level: 0) but when i run mount 9p symlink then it become drwxrwxrwx 5 root root 4096 Feb 19 16:58 homes the ACL permissions was lost. that's why i cannot open synology office apps. it failed to load. and the indexing process for universal search running forever, it never stop.. any solutions for this ? Edited February 19, 2022 by hendry Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 19, 2022 Share #96 Posted February 19, 2022 11 hours ago, hendry said: if i restart the container, why sometimes it bring back to the default installation screen at beginning ? No, I never get this issue ... maybe this is something to do with trying to 9p fs mountpoint /xpy_syst folder. (I should remove this in my README example). 11 hours ago, hendry said: how can i mount using 9p to /volume1/homes folder ? this is the default permissions and ACL for /volume1/homes You can try to different VM_9P_OPTS and mount option to see if ACL works with xpenology. 16 hours ago, hendry said: about smb share, since i run container inside the NAS (Qnap), i think the smb port will be conflict with the host Qnap. because Qnap also has smb service. what is the solution if i want to access shared folder from xpenology container using smb in windows explorer ? Maybe you want your xpenology to be more expose by setting it its own fixed IP. You can do it by creating a macvlan then add "--network MyMacvlanName --ip=192.168.x.x" (then i wont need -p option no more) Check this : https://docs.docker.com/network/network-tutorial-macvlan/ HTH, Quote Link to comment Share on other sites More sharing options...
LittleLama Posted February 19, 2022 Share #97 Posted February 19, 2022 i just added 1 mountpoint for 9p data share. and found an issue.. if i restart the container, why sometimes it bring back to the default installation screen at beginning ?I got no answer, I just want to let you know that this was my major issue with Xpenology in Docker. I got no solution but run it in a VM. I would be interested by the fix. Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 19, 2022 Share #98 Posted February 19, 2022 2 hours ago, LittleLama said: I got no answer, I just want to let you know that this was my major issue with Xpenology in Docker What is the step to reproduce this issue? I did hundred of restart of the same containers without any issue. Quote Link to comment Share on other sites More sharing options...
hendry Posted February 20, 2022 Share #99 Posted February 20, 2022 (edited) On 2/19/2022 at 3:21 PM, hendry said: i just added 1 mountpoint for 9p data share. and found an issue.. if i restart the container, why sometimes it bring back to the default installation screen at beginning ? at a glance i see on the boot log process, these log sometimes doesn't show ------------upgrade Begin upgrade procedure Mount data partition: /dev/md0 -> /tmpData No upgrade file exists End upgrade procedure ============upgrade ------------bootup-smallupdate Try bootup smallupdate UPGRADE_BOOTUP_SMALLUPDATE No patch exist. Skip Packed Bootup SmallUpdate Sparse files don't exist. Skip Sparse Bootup SmallUpdate Finished synoupgrade --bootup-smallupdate if it's not show, then the screen bring back to beginning installation process. but if i restart container once again, the boot process is normal and the web ui bring back to login page. another question, how can i mount using 9p to /volume1/homes folder ? this is the default permissions and ACL for /volume1/homes drwx--x--x+ 1 root root 34 Feb 19 16:35 homes [0] group:administrators:allow:rwxpdDaARWc--:fd-- (level: 0) [1] owner::allow:rwxpdDaARWcCo:fd-- (level: 0) [2] everyone::allow:--x----------:fd-- (level: 0) but when i run mount 9p symlink then it become drwxrwxrwx 5 root root 4096 Feb 19 16:58 homes the ACL permissions was lost. that's why i cannot open synology office apps. it failed to load. and the indexing process for universal search running forever, it never stop.. any solutions for this ? i tried macvlan method docker network create -d macvlan --subnet=192.168.10.0/24 --gateway=192.168.10.1 -o parent=qvs0 my-macvlan-net docker run --privileged --name xpenology --cap-add=NET_ADMIN \ --device=/dev/net/tun --device=/dev/kvm --restart always \ --network my-macvlan-net \ -p 5500:5000 -p 5001:5001 -p 2224:22 \ -e CPU="qemu64" \ -e THREADS=1 \ -e RAM=1024 \ -e DISK_SIZE="16G" \ -e DISK_PATH="/xpy_syst" \ -e BOOTLOADER_AS_USB="Y" \ -e VM_ENABLE_VIRTIO="Y" \ -e VM_PATH_9P="/xpy_data /xpy_data1 /xpy_data2 /xpy_data3" \ -e GRUBCFG_DISKIDXMAP="00" -e GRUBCFG_SATAPORTMAP="1" \ -v /share/CACHEDEV2_DATA:/xpy_data \ -v /share/CACHEDEV1_DATA/Public/XPE/syst:/xpy_syst \ -v /share/CACHEDEV1_DATA/QVRProSpace_DataVol1:/xpy_data1 \ -v /share/CACHEDEV2_DATA/PHOTO:/xpy_data2 \ -v /share/CACHEDEV1_DATA/Public/XPE/data:/xpy_data3 \ uxora/xpenology it started completely, but i cannot find the ip address for xpenology container.. just checked with synology assistant & see dhcp ip address from my router also didn't find it. Edited February 20, 2022 by hendry Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 20, 2022 Share #100 Posted February 20, 2022 7 hours ago, hendry said: it started completely, but i cannot find the ip address for xpenology container.. The answer is on my last post about that: 21 hours ago, uxora-com said: You can do it by creating a macvlan then add "--network MyMacvlanName --ip=192.168.x.x" (then i wont need -p option no more) 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.