9xoqreyua Posted May 5 Share #601 Posted May 5 35 minutes ago, snoopy78 said: sure...just read the topics above...it's all about bare-metal and not vm I went through it already but: - dont see a bootloader script like RedPill / ARPL - from what I read - it's proxmox/virtualisation-based vs what you suggested => bare-metal? Quote Link to comment Share on other sites More sharing options...
snoopy78 Posted May 5 Share #602 Posted May 5 1 minute ago, 9xoqreyua said: I went through it already but: - dont see a bootloader script like RedPill / ARPL - from what I read - it's proxmox/virtualisation-based vs what you suggested => bare-metal? there is no script...that's right...you need to download an installer, then install the system on a usb/disk...modify the values...and ready you are.... btw....this is fully upgradable ...just installed on one of my test systems qnap 5.2 beta flawless Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 5 Share #603 Posted May 5 you need to download an installer guess I'm stuck here already? Do you mean QNAP-BOOT-EN-v1.00.img or Ox_install_UEFI_BIOS_En.iso then install the system on a usb/disk I've downloaded both and moved to USB using BalenaEtcher ...modify the values which one? I want to use one of the following QNAP's: TS-453D, TS-653D, TVS-472XT, TVS-672XT note: the goal is to run on F2-423 with 32G RAM, 1x 120GB NVME & 2x 4TB WD ...and ready you are can't wait to get there Once I'm done I will write the process descriptions for others - hopefully this will help others, too Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 5 Share #604 Posted May 5 when booting from Ox_install_UEFI_BIOS_En.iso ==> user/pass > admin/admin ==> Its stuck on "Entering TinyCore 10.1 System" Quote Link to comment Share on other sites More sharing options...
snoopy78 Posted May 5 Share #605 Posted May 5 14 minutes ago, 9xoqreyua said: you need to download an installer guess I'm stuck here already? Do you mean QNAP-BOOT-EN-v1.00.img or Ox_install_UEFI_BIOS_En.iso then install the system on a usb/disk I've downloaded both and moved to USB using BalenaEtcher ...modify the values which one? I want to use one of the following QNAP's: TS-453D, TS-653D, TVS-472XT, TVS-672XT note: the goal is to run on F2-423 with 32G RAM, 1x 120GB NVME & 2x 4TB WD ...and ready you are can't wait to get there Once I'm done I will write the process descriptions for others - hopefully this will help others, too use the OX version... define which system you want to use...and get the correct image from qnap support site > you must manually define the boot disk, data disk, nic and such things within the config file you get, when you "create" the real image calculat from HEX to DEC.... Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 5 Share #606 Posted May 5 stuck here: Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 6 Share #607 Posted May 6 can yu please share other tinycore image to boot? Quote Link to comment Share on other sites More sharing options...
snoopy78 Posted May 6 Share #608 Posted May 6 11 hours ago, 9xoqreyua said: stuck here: what's the password you did try? is it via SSH or via WebGUI (inial setup)? Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 6 Share #609 Posted May 6 1) Ive booted it from USB 2) I took the screenshot from connected screen 3) it's neither SSH/WebGui logon - I do not get that far. 4) user/pass =>> admin/admin Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 6 Share #610 Posted May 6 1) main screen: 2) then I enter admin/admin as logon credentials and it gets stuck Quote Link to comment Share on other sites More sharing options...
snoopy78 Posted May 6 Share #611 Posted May 6 On 5/2/2024 at 10:52 PM, medric said: After much research and more Research between the different model.conf this forum and this site --> (https://imnks.com/4925.html) I have been able to build 4 different system TS-2483XU TES-3085U(SAS with expander only) TS-3088XU TS-3087XU [LSI 9211-8I with SAS expander, LSI 3005-24i, m.2 nvme , gpu, Ethernet: 1G Intel I210 Intel 10G x540 and 10G (marvel chipset nic card] Still not sure why my HBA physical drive starts are 8 and the other starts at 12 but QNAP respects the physical port more than the port or slot number Internal nics you should use the Ubuntu usb image and run lspci -PP that will help because some cards have two DEV BUS number and for internal devices you should use the first one and for pcie slot you should use the second 00:1d.0/05:00.0 internal nic vs 00:1b.0/03:00.0 external nic PCI NVME use 00:1c.0/04:00.0 the first for pcie slot and the second one for mapping to a system disk slot I turned of CE1 and CSTATE but I did have success with them on and I use CSM UEFI boot with OX QNAP disk tc@ubuntu:~$ lspci -PP 00:00.0 Host bridge: Intel Corporation Device 3e31 (rev 0a) 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 0a) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x8) (rev 0a) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:15.0 Serial bus controller: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0 (rev 10) 00:15.1 Serial bus controller: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #1 (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:16.4 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller #2 (rev 10) 00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10) 00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (rev f0) 00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0) 00:1d.1 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #10 (rev f0) 00:1d.2 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #11 (rev f0) 00:1e.0 Communication controller: Intel Corporation Cannon Lake PCH Serial IO UART Host Controller (rev 10) 00:1f.0 ISA bridge: Intel Corporation Device a30a (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 00:01.0/01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1) 00:01.0/01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1) 00:01.1/02:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) 00:1c.0/04:00.0 Non-Volatile memory controller: Phison Electronics Corporation Device 5015 (rev 01) 00:1d.0/05:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) 00:1d.1/06:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 04) 00:1d.1/06:00.0/07:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41) 00:1d.2/08:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) hi, i've got the lspci -pp from ubuntu looking like this... " 00:1f.2 SATA controller: Intel Corporation C600/X79 series chipset 6-Port SATA AHCI Controller (rev 06) 00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host Controller (rev 06) 00:1f.6 Signal processing controller: Intel Corporation C600/X79 series chipset Thermal Management Controller (rev 06) 00:01.0/01:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02) 00:02.0/02:00.0 PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA (rev ca) 00:02.0/02:00.0/03:00.0 PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA (rev ca) 00:02.0/02:00.0/03:08.0 PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA (rev ca) 00:02.0/02:00.0/03:09.0 PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA (rev ca) 00:02.0/02:00.0/03:00.0/04:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02) 00:02.0/02:00.0/03:09.0/06:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02) 00:03.0/07:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01) 00:03.0/07:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01) 00:11.0/09:00.0 Serial Attached SCSI controller: Intel Corporation C602 chipset 4-Port SATA Storage Control Unit (rev 06) " I do havy physical 2 HBAs in the system 00:01.0/01:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02) > 9300-4i4e with ext SAS Expander (only external is connected) 00:02.0/02:00.0/03:00.0/04:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02) 00:02.0/02:00.0/03:09.0/06:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02) > 9300-16i with direct attaced drives with ls -al /sys/block /sd* i get this output, which shows 16 external connected and 14 internal connected drives to both HBAs lrwxrwxrwx 1 root root 0 May 6 2024 sdaa -> ../devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:09.0/0000:06:00.0/host10/port-10:1/end_device-10:1/target10:0:1/10:0:1:0/block/sdaa lrwxrwxrwx 1 root root 0 May 6 2024 sdab -> ../devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:09.0/0000:06:00.0/host10/port-10:2/end_device-10:2/target10:0:2/10:0:2:0/block/sdab lrwxrwxrwx 1 root root 0 May 6 2024 sdac -> ../devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:09.0/0000:06:00.0/host10/port-10:3/end_device-10:3/target10:0:3/10:0:3:0/block/sdac lrwxrwxrwx 1 root root 0 May 6 2024 sdad -> ../devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:09.0/0000:06:00.0/host10/port-10:4/end_device-10:4/target10:0:4/10:0:4:0/block/sdad lrwxrwxrwx 1 root root 0 May 6 2024 sdae -> ../devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:09.0/0000:06:00.0/host10/port-10:5/end_device-10:5/target10:0:5/10:0:5:0/block/sdae lrwxrwxrwx 1 root root 0 May 6 2024 sdaf -> ../devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:09.0/0000:06:00.0/host10/port-10:6/end_device-10:6/target10:0:6/10:0:6:0/block/sdaf lrwxrwxrwx 1 root root 0 May 6 2024 sdag -> ../devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:09.0/0000:06:00.0/host10/port-10:7/end_device-10:7/target10:0:7/10:0:7:0/block/sdag lrwxrwxrwx 1 root root 0 May 6 2024 sdb -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:0/end_device-1:0:0/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 May 6 2024 sdc -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:1/end_device-1:0:1/target1:0:1/1:0:1:0/block/sdc lrwxrwxrwx 1 root root 0 May 6 2024 sdd -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:2/end_device-1:0:2/target1:0:2/1:0:2:0/block/sdd lrwxrwxrwx 1 root root 0 May 6 2024 sde -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:3/end_device-1:0:3/target1:0:3/1:0:3:0/block/sde lrwxrwxrwx 1 root root 0 May 6 2024 sdf -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:4/end_device-1:0:4/target1:0:4/1:0:4:0/block/sdf lrwxrwxrwx 1 root root 0 May 6 2024 sdg -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:5/end_device-1:0:5/target1:0:5/1:0:5:0/block/sdg lrwxrwxrwx 1 root root 0 May 6 2024 sdh -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:6/end_device-1:0:6/target1:0:6/1:0:6:0/block/sdh lrwxrwxrwx 1 root root 0 May 6 2024 sdi -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:7/end_device-1:0:7/target1:0:7/1:0:7:0/block/sdi lrwxrwxrwx 1 root root 0 May 6 2024 sdj -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:8/end_device-1:0:8/target1:0:8/1:0:8:0/block/sdj lrwxrwxrwx 1 root root 0 May 6 2024 sdk -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:9/end_device-1:0:9/target1:0:9/1:0:9:0/block/sdk lrwxrwxrwx 1 root root 0 May 6 2024 sdl -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:10/end_device-1:0:10/target1:0:10/1:0:10:0/block/sdl lrwxrwxrwx 1 root root 0 May 6 2024 sdm -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:11/end_device-1:0:11/target1:0:11/1:0:11:0/block/sdm lrwxrwxrwx 1 root root 0 May 6 2024 sdn -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:12/end_device-1:0:12/target1:0:12/1:0:12:0/block/sdn lrwxrwxrwx 1 root root 0 May 6 2024 sdo -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:13/end_device-1:0:13/target1:0:13/1:0:13:0/block/sdo lrwxrwxrwx 1 root root 0 May 6 2024 sdp -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:14/end_device-1:0:14/target1:0:14/1:0:14:0/block/sdp lrwxrwxrwx 1 root root 0 May 6 2024 sdq -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:0/expander-1:0/port-1:0:15/end_device-1:0:15/target1:0:15/1:0:15:0/block/sdq lrwxrwxrwx 1 root root 0 May 6 2024 sdr -> ../devices/pci0000:00/0000:00:1f.2/ata2/host2/target2:0:0/2:0:0:0/block/sdr lrwxrwxrwx 1 root root 0 May 6 2024 sds -> ../devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:00.0/0000:04:00.0/host9/port-9:0/end_device-9:0/target9:0:0/9:0:0:0/block/sds lrwxrwxrwx 1 root root 0 May 6 2024 sdt -> ../devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:00.0/0000:04:00.0/host9/port-9:1/end_device-9:1/target9:0:1/9:0:1:0/block/sdt lrwxrwxrwx 1 root root 0 May 6 2024 sdu -> ../devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:00.0/0000:04:00.0/host9/port-9:2/end_device-9:2/target9:0:2/9:0:2:0/block/sdu lrwxrwxrwx 1 root root 0 May 6 2024 sdv -> ../devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:00.0/0000:04:00.0/host9/port-9:4/end_device-9:4/target9:0:4/9:0:4:0/block/sdv lrwxrwxrwx 1 root root 0 May 6 2024 sdw -> ../devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:00.0/0000:04:00.0/host9/port-9:3/end_device-9:3/target9:0:3/9:0:3:0/block/sdw lrwxrwxrwx 1 root root 0 May 6 2024 sdx -> ../devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:00.0/0000:04:00.0/host9/port-9:5/end_device-9:5/target9:0:5/9:0:5:0/block/sdx lrwxrwxrwx 1 root root 0 May 6 2024 sdy -> ../devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.1/1-1.1:1.0/host4/target4:0:0/4:0:0:0/block/sdy lrwxrwxrwx 1 root root 0 May 6 2024 sdz -> ../devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:09.0/0000:06:00.0/host10/port-10:0/end_device-10:0/target10:0:0/10:0:0:0/block/sdz the drives from HBA 9300-4i4e (0-15) are correctly addressed so far, it's only the internal HBA which right now pushes me to the cliff.... i've got 4 Dev_Bus addresses currently here (because of the pcie switch).... can you please show me your disk-settings and lspci -pp for them? so i can compare to my ones Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 6 Share #612 Posted May 6 I am able to boot tinycore on other machine (laptop), dont know why it's getting frozen on NAS. So my plan is: 1)boot debian on NAS qith 2 USBs connected USB1 - debian live cd USB2 - empty USB that will be target for booting/installing QTS 2) using lspci -pp check port mapping to use for creating model.conf 3) boot laptop with tinycore and modify model.conf respectively 4) boot NAS from new USB would that work? can someone based on lspci -pp create a proper model.conf file for me for TVS-472XT? Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 6 Share #613 Posted May 6 lspci -pp 00:00.0 Host bridge: Intel Corporation Device 4e24 00:02.0 VGA Compatible controller: Intel Corporation JasperLake [UHD Graphics] (rev 01) 00:04.0 Signal processing controller: Intel Corporation Dynamic Tuning Service 00:08.0 System peripheral: Intel Corporation Device 4e11 00:14.0 USB controller: Intel Corporation Device 4ded (rev 01) 00:14.2 RAM memory: Intel Corporation Device 4def (rev 01)) 00:15.0 Serial bus controller: Intel Corporation Serial IO I2C Host Controller (rev 10) 00:15.2 Serial bus controller: Intel Corporation Device 4dea (rev 10) 00:16.0 Communication controller: Intel Corporation Management Engine Interface (rev 01) 00:17.0 SATA controller: Intel Corporation Device 4dd3 (rev 01) 00:19.0 Serial bus controller: Intel Corporation Device 4dc5 (rev 01) 00:19.1 Serial bus controller: Intel Corporation Device 4dc6 (rev 01) 00:1c.0 PCI bridge: Intel Corporation Device 4db8 (rev 01) 00:1c.1 PCI bridge: Intel Corporation Device 4db9 (rev 01) 00:1c.4 PCI bridge: Intel Corporation Device 4dbc (rev 01) 00:1c.5 PCI bridge: Intel Corporation Device 4dbd (rev 01) 00:1e.0 Communication controller: Intel Corporation Device 4da8 (rev 01) 00:1e.3 Serial bus controller: Intel Corporation Device 4dab (rev 01) 00:1f.0 ISA bridge: Intel Corporation Device 4d87 (rev 01) 00:1f.3 Audio device: Intel Corporation JasperLake HD Audio (rev 01) 00:1f.4 SMBus: Intel Corporation JasperLake SMBus (rev 01) 00:1f.5 Serial bus controller: Intel Corporation Jasper Lake SPI Controller (rev 01) 01:00.0 Ethernet controller: Intel Corporation Ethernet controller I225-v (rev 03) 02:00.0 Ethernet controller: Intel Corporation Ethernet controller I225-v (rev 03) 03:00.0 Non-Volatile memory controller: Device 1ed0:2283 04:00.0 Non-Volatile memory controller: Device 1ed0:2283 ls -al /sys/block ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/nvme/nvme0/nvme0n1 ../devices/pci0000:00/0000:00:1c.5/0000:04:00.0/nvme/nvme1/nvme1n1 ../devices/pci0000:00/0000:00:1c.5/ata2/host2/target1:0:0/1:0:0:0/block/sdb ../devices/pci0000:00/0000:00:17.0/ata2/host1/target0:0:0/0:0:0:0/block/sda ../devices/pci0000:00/0000:00:17.0/ata2/host2/target1:0:0/1:0:0:0/block/sdb ../devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host2/target2:0:0/2:0:0:0/block/sdc ../devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host3/target3:0:0/3:0:0:0/block/sdd usb2 (sdc) is the debian usb which I booted from usb1 (sdd) is the empty USB (it will be used for everything later boot included and no longer needs to be removed) please help in creating model.conf for the above disk setup and TVS-472XT as target model Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 6 Share #614 Posted May 6 error I get when booting Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 6 Share #615 Posted May 6 (edited) dont ask my how but I managed to install it (wont be able to repeat the process for now ;P) In the control panel there's no serial number? How to correct it? Also, in the App Center -> there are no apps to be installed (I guess it's connected to missing s/n? Edited May 6 by 9xoqreyua Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 6 Share #616 Posted May 6 firmware error Quote Link to comment Share on other sites More sharing options...
snoopy78 Posted May 6 Share #617 Posted May 6 1 hour ago, 9xoqreyua said: firmware error kein Problem mit der Fehlermeldung.... nach dem nächsten Update der DSM ist die weg... Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 6 Share #618 Posted May 6 I cant get it started from internal usb. I have PenDrive SanDisk Ultra Fit 64 that fits inside the cover, but I;m unable to boot QTS from it - it freezes after a couple of second (more than 18s how to fix it? Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 6 Share #619 Posted May 6 also, NVME disks are not recognized. so, what's the best QNAP system to chose? TS-453D TS-653D TVS-472XT TVS-672XT or any other note: the goal is to run on F2-423 with 32G RAM, 2x 120GB NVME & 2x 4TB WD Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 7 Share #620 Posted May 7 I still struggle to boot into TinyCore 10.1 ) main screen: 2) then I enter admin/admin as logon credentials and it gets stuck what could be the issue? It works on other machine but not on NAS. Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 7 Share #621 Posted May 7 any help with this? ls -al /sys/block ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/nvme/nvme0/nvme0n1 ../devices/pci0000:00/0000:00:1c.5/0000:04:00.0/nvme/nvme1/nvme1n1 ../devices/pci0000:00/0000:00:1c.5/ata2/host2/target1:0:0/1:0:0:0/block/sdb ../devices/pci0000:00/0000:00:17.0/ata2/host1/target0:0:0/0:0:0:0/block/sda ../devices/pci0000:00/0000:00:17.0/ata2/host2/target1:0:0/1:0:0:0/block/sdb ../devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host2/target2:0:0/2:0:0:0/block/sdc ../devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host3/target3:0:0/3:0:0:0/block/sdd usb2 (sdc) is the debian usb which I booted from usb1 (sdd) is the empty USB (it will be used for everything later boot included and no longer needs to be removed) please help in creating model.conf for the above disk setup and TVS-472XT as target model Quote Link to comment Share on other sites More sharing options...
9xoqreyua Posted May 8 Share #622 Posted May 8 here's my model.conf any advice what to correct? model.conf 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.