Jump to content
XPEnology Community

QNAP auf eigener Hardware


fa2k

Recommended Posts

11 minutes ago, xenix96 said:

Ich benutze hierzu den Onboard USB Slot :)  

Wenn alle passt ist der im Gehäuse verschlossen drine 

20220205_192952.jpg

 

===> die Ausgabe dokumentieren und umrechnen
z.B.
/devices/pci0000:00/0000:00:14.0/usb4/4-4/4-4:1.0/host6/target6:0:0/6:0:0:0/block/sda/

=> diese Wert in model.conf eintragen (wenn das nicht stimmt, bootet er nur bis ca. 18Sek)
=> [Boot Disk 1]
DEV_BUS = B00:D20:F0
DEV_PORT = 4

 

m.W.n. sind das die Werte die du benötigst

 

 

Link to comment
Share on other sites

 

30 minutes ago, snoopy78 said:

 

===> die Ausgabe dokumentieren und umrechnen
z.B.
/devices/pci0000:00/0000:00:14.0/usb4/4-4/4-4:1.0/host6/target6:0:0/6:0:0:0/block/sda/

=> diese Wert in model.conf eintragen (wenn das nicht stimmt, bootet er nur bis ca. 18Sek)
=> [Boot Disk 1]
DEV_BUS = B00:D20:F0
DEV_PORT = 4

 

m.W.n. sind das die Werte die du benötigst

 

 

 

Danke @snoopy78

 

.....bei mir stand in der model.conf....

[Boot Disk 1]
DEV_BUS = B00:D20:F0
IN_HUB = 0
DEV_PORT_NS = 1

 

Ändere es nun um auf

[Boot Disk 1]
DEV_BUS = B00:D20:F0
DEV_PORT = 9

 

Wenn das nicht geht mach ich einen 2ten Versuch mit

[Boot Disk 1]
DEV_BUS = B00:D20:F0
DEV_PORT = 4

 

 

00:00/0000:00:14.0/usb2/2-9/2-9:1.0/host8/target8:0:0/8:0:0:0/block/sdc/
00:00/0000:00:14.0/usb2/2-4/2-4:1.0/host9/target9:0:0/9:0:0:0/block/sdd/

 

Edited by xenix96
Link to comment
Share on other sites

54 minutes ago, xenix96 said:

 

Danke @snoopy78

 

.....bei mir stand in der model.conf....

[Boot Disk 1]
DEV_BUS = B00:D20:F0
IN_HUB = 0
DEV_PORT_NS = 1

 

Ändere es nun um auf

[Boot Disk 1]
DEV_BUS = B00:D20:F0
DEV_PORT = 9

 

Wenn das nicht geht mach ich einen 2ten Versuch mit

[Boot Disk 1]
DEV_BUS = B00:D20:F0
DEV_PORT = 4

 

 









00:00/0000:00:14.0/usb2/2-9/2-9:1.0/host8/target8:0:0/8:0:0:0/block/sdc/
00:00/0000:00:14.0/usb2/2-4/2-4:1.0/host9/target9:0:0/9:0:0:0/block/sdd/

 

 

@snoopy78 4 war  der richtige Port :) 

[Boot Disk 1]
DEV_BUS = B00:D20:F0
DEV_PORT = 4

 

Qnap boot Disk bootet nun 😍

 

 

 

1.png

 

 

3.png

4.png

5.png

6.png

Edited by xenix96
Link to comment
Share on other sites

3 minutes ago, snoopy78 said:

👏 wenn du ne ältere Firmware von Qnap genommen hättest, hattest du jetzt das Update prüfen können..

 

Ja stimmt eigentlich .... falls was schief geht werde ich das definitiv testen und hier berichten 👍

 

Sprich 4.5er Firmware installieren ... boooten .. updaten ... rebooten ..sollte danach wieder mit der 5.0er Firmware booten oder ?

Link to comment
Share on other sites

1 hour ago, snoopy78 said:

👏 wenn du ne ältere Firmware von Qnap genommen hättest, hattest du jetzt das Update prüfen können..

Weil du mir so geholfen hast werde ich das gleich machen da die Erstellung der Qnap boot disk mit der image bei richtiger usb port Wahl ein Kinderspiel ist.

Grundvoraussetzung hierfür ist eine richtig modifizierte model.conf 😅

 

Außerdem bootet die Qnap boot disk in 2 minuten im vergleich zur alten .img die 20min gedauert hat :)

 

Bericht folgt

-> Install Firmware 4.5 -> update Firmware auf 5.0 -> reboot -> Funktioniert !!!!!

 

 

Qnap boot Disk erstellt mit 4.5er Firmware

login as: tc
   ( '>')
  /) TC (\   Core is distributed with ABSOLUTELY NO WARRANTY.
 (/-_--_-\)           www.tinycorelinux.net

OpenSSH daemon is running

There are three steps to build the QNAP system boot disk.

1. Get the qnap firmware from offical URL or your device.

   You can do it by using following command:
   get_qnap_firware [ offical_URL | block_device | qnap_firmware.zip ]
   Or
   Manually copy the firmwar files into /home/tc/boot directory

2. Manually edit the /home/tc/patch/etc/model.conf file for your hardware.
   Please see my article on NASYUN for details or refer the model_examples.

3. After confirm the model.conf match your hardware
   You can use the following command to create qnap boot disk.

   create_qnap_boot

tc@box:~$ sudo get_qnap_firmware /home/tc/TS-X72/TS-X72_20211223-4.5.4.1892.zip
Get the qnap firmware from file [/home/tc/TS-X72/TS-X72_20211223-4.5.4.1892.zip]                                       ; Please wait a while.
cp: can't stat '/home/tc/TS-X72/TS-X72_20211223-4.5.4.1892.zip': No such file or                                        directory
Archive:  /home/tc/TS-X72_20211223-4.5.4.1892.zip
  inflating: TS-X72_20211223-4.5.4.1892.img
Using 120-bit encryption - (QNAPNASVERSION4)
len=1048576
model name = TS-X72
version = 4.5.4
bzImage
bzImage.cksum
initrd.boot
initrd.boot.cksum
qpkg.tar
qpkg.tar.cksum
rootfs2.bz
rootfs2.bz.cksum
rootfs_ext.tgz
rootfs_ext.tgz.cksum
=====Start verify qunp firmware=====
[ Verifying the bzImage] => PASSED
[ Verifying the initrd.boot] => PASSED
[ Verifying the qpkg.tar] => PASSED
[ Verifying the rootfs_ext.tgz] => PASSED
[ Verifying the rootfs2.bz] => PASSED
=====Verify qunp firmware is OK=====
Get qnap firmware successful.
tc@box:~$
tc@box:~$ ls -al /sys/block /sd*
ls: /sd*: No such file or directory
/sys/block:
total 0
drwxr-xr-x    2 root     root             0 Feb  5 20:49 ./
dr-xr-xr-x   13 root     root             0 Feb  5 20:49 ../
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop0 -> ../devices/virtual/block/loop0/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop1 -> ../devices/virtual/block/loop1/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop2 -> ../devices/virtual/block/loop2/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop3 -> ../devices/virtual/block/loop3/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop4 -> ../devices/virtual/block/loop4/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop5 -> ../devices/virtual/block/loop5/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop6 -> ../devices/virtual/block/loop6/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop7 -> ../devices/virtual/block/loop7/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram0 -> ../devices/virtual/block/ram0/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram1 -> ../devices/virtual/block/ram1/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram2 -> ../devices/virtual/block/ram2/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram3 -> ../devices/virtual/block/ram3/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram4 -> ../devices/virtual/block/ram4/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram5 -> ../devices/virtual/block/ram5/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram6 -> ../devices/virtual/block/ram6/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram7 -> ../devices/virtual/block/ram7/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 sda -> ../devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 sdb -> ../devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 sdc -> ../devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/host8/target8:0:0/8:0:0:0/block/sdc/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 sdd -> ../devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.0/host9/target9:0:0/9:0:0:0/block/sdd/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 sr0 -> ../devices/pci0000:00/0000:00:17.0/ata5/host4/target4:0:0/4:0:0:0/block/sr0/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 zram0 -> ../devices/virtual/block/zram0/
tc@box:~$ sudo cp model.conf /home/tc/patch/etc/model.conf
tc@box:~$ sudo create_qnap_boot
=====Start verify qunp firmware=====
[ Verifying the bzImage] => PASSED
[ Verifying the initrd.boot] => PASSED
[ Verifying the qpkg.tar] => PASSED
[ Verifying the rootfs_ext.tgz] => PASSED
[ Verifying the rootfs2.bz] => PASSED
=====Verify qunp firmware is OK=====
Re-packing the patch.gz. Please wait a while.
Re-packing the patch.gz successful.

There are following targets for you to install QNAP boot disk:
[1]=>[/dev/sda]
[2]=>[/dev/sdb]
[3]=>[/dev/sdc]
[4]=>[/dev/sdd]
Please select the following [number] for the target device:3
=====[start to install QNAP boot disk on /dev/sdc]=====
Start to make partition on /dev/sdc for EFI boot disk
Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Parted /dev/sdc for EFI boot disk successful.
mkfs.fat 3.0.26 (2014-03-07)
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 307200 1k blocks and 76912 inodes
Filesystem UUID: c0f3e62d-c81d-4496-8b1b-44404e568ecb
Superblock backups stored on blocks:
        8193, 24577, 40961, 57345, 73729, 204801, 221185

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 307200 1k blocks and 76912 inodes
Filesystem UUID: 0cd87806-24ae-4abc-b13d-12dddedf9835
Superblock backups stored on blocks:
        8193, 24577, 40961, 57345, 73729, 204801, 221185

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 8192 1k blocks and 2048 inodes

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 8192 1k blocks and 2048 inodes

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 7334651 4k blocks and 1835008 inodes
Filesystem UUID: d37b3edd-fead-4f43-886a-ebf6ea38b77a
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 8192 1k blocks and 2048 inodes

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

Format all /dev/sdc partitions successful.
Installing for x86_64-efi platform.
Installation finished. No error reported.
Config grub2 main menu
Copy QNAP System into targer disk
Copy tool kit into [/dev/sdc]

Create [/dev/sdc] boot disk successful!

tc@box:~$

 

Boot Firmware 4.5

 

7.thumb.png.9e8b08e452b2a9faa931dfb9733c361d.png

 

Booted Firmware 4.5

 

8.thumb.png.f7d8930f72801dab3e78c84970b85107.png

 

9.thumb.png.b705810e881282a0f67c3dea20e70556.png

 

 

Reboot nach OTA Update Firmware 5.0

 

10.thumb.png.d9f8c92689ac360447c045c51a381a91.png

 

11.thumb.png.0f06d5997689b48e0e2edde0293100c9.png

 

12.thumb.png.1262ec3eca626e9cd45e12d6bb22ae1f.png

 

 

Boot nach OTA Update Firmware 5.0

 

13.thumb.png.d143e081aa6fe53871532386988fe84e.png

 

 

Booted Firmware 5.0 😍   Danke dir  @snoopy78 🤝

 

14.thumb.png.6b48234212bac007885ea762e472f1bd.png

Edited by xenix96
Link to comment
Share on other sites

1 minute ago, xenix96 said:

ok upload it again for everyone...one moment

 

Hallo,
Vielen Dank, ich habe auch den Server vorbereitet, ich habe mich darauf vorbereitet, mir die Freigaben anzusehen, in denen die Installationstests durchgeführt wurden, und es erneut zu versuchen. Wenn es eine andere .iso-Datei gibt, spart es Zeit, wenn ich es damit versuche.

  • Thanks 1
Link to comment
Share on other sites

Hallo,

 

ich habe mir eine QM2-2P-384 gekauft und diese scheint aber nicht erkannt zu werden. Ich hatte es zuerst mal unter Windows 10 getestet und dort wurde im Geräte Manager nichts erkannt, auch nicht als unbekanntes Gerät.

Dann habe ich es mal in mein System eingebaut, auf dem auch das QuTS Hero läuft und dort werden mir auch keine Festplatten angezeigt. 
Die Grünen Lampen an der Karte leuchten aber. Kann es sein, dass die Karte vielleicht einen Defekt hat?
Auf der Karte habe ich zwei SFF-8643 auf M2 Adapter verbaut und dahinter sind zwei Intel Optane 900p mit U2 Anschluss.

Danke.

Edited by hitman22
Link to comment
Share on other sites

25 minutes ago, snoopy78 said:

@hitman22

habe selber eine QM2-4P-384...hab die eingebaut und sofort erkannt..auch die beiden angeschlossenen nvme sind als volume nutzbar..

 

richtiger PCIe Port in der Konfig zugewiesen?

 

@snoopy78 Vielen Dank !!!!!!! 🤝  OTA Updates Funktionieren 😍

 

1 hour ago, xenix96 said:

Weil du mir so geholfen hast werde ich das gleich machen da die Erstellung der Qnap boot disk mit der image bei richtiger usb port Wahl ein Kinderspiel ist.

Grundvoraussetzung hierfür ist eine richtig modifizierte model.conf 😅

 

Außerdem bootet die Qnap boot disk in 2 minuten im vergleich zur alten .img die 20min gedauert hat :)

 

 

-> Install Firmware 4.5 -> update Firmware auf 5.0 -> reboot -> Funktioniert !!!!!

 

 

Qnap boot Disk erstellt mit 4.5er Firmware




login as: tc
   ( '>')
  /) TC (\   Core is distributed with ABSOLUTELY NO WARRANTY.
 (/-_--_-\)           www.tinycorelinux.net

OpenSSH daemon is running

There are three steps to build the QNAP system boot disk.

1. Get the qnap firmware from offical URL or your device.

   You can do it by using following command:
   get_qnap_firware [ offical_URL | block_device | qnap_firmware.zip ]
   Or
   Manually copy the firmwar files into /home/tc/boot directory

2. Manually edit the /home/tc/patch/etc/model.conf file for your hardware.
   Please see my article on NASYUN for details or refer the model_examples.

3. After confirm the model.conf match your hardware
   You can use the following command to create qnap boot disk.

   create_qnap_boot

tc@box:~$ sudo get_qnap_firmware /home/tc/TS-X72/TS-X72_20211223-4.5.4.1892.zip
Get the qnap firmware from file [/home/tc/TS-X72/TS-X72_20211223-4.5.4.1892.zip]                                       ; Please wait a while.
cp: can't stat '/home/tc/TS-X72/TS-X72_20211223-4.5.4.1892.zip': No such file or                                        directory
Archive:  /home/tc/TS-X72_20211223-4.5.4.1892.zip
  inflating: TS-X72_20211223-4.5.4.1892.img
Using 120-bit encryption - (QNAPNASVERSION4)
len=1048576
model name = TS-X72
version = 4.5.4
bzImage
bzImage.cksum
initrd.boot
initrd.boot.cksum
qpkg.tar
qpkg.tar.cksum
rootfs2.bz
rootfs2.bz.cksum
rootfs_ext.tgz
rootfs_ext.tgz.cksum
=====Start verify qunp firmware=====
[ Verifying the bzImage] => PASSED
[ Verifying the initrd.boot] => PASSED
[ Verifying the qpkg.tar] => PASSED
[ Verifying the rootfs_ext.tgz] => PASSED
[ Verifying the rootfs2.bz] => PASSED
=====Verify qunp firmware is OK=====
Get qnap firmware successful.
tc@box:~$
tc@box:~$ ls -al /sys/block /sd*
ls: /sd*: No such file or directory
/sys/block:
total 0
drwxr-xr-x    2 root     root             0 Feb  5 20:49 ./
dr-xr-xr-x   13 root     root             0 Feb  5 20:49 ../
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop0 -> ../devices/virtual/block/loop0/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop1 -> ../devices/virtual/block/loop1/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop2 -> ../devices/virtual/block/loop2/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop3 -> ../devices/virtual/block/loop3/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop4 -> ../devices/virtual/block/loop4/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop5 -> ../devices/virtual/block/loop5/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop6 -> ../devices/virtual/block/loop6/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 loop7 -> ../devices/virtual/block/loop7/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram0 -> ../devices/virtual/block/ram0/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram1 -> ../devices/virtual/block/ram1/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram2 -> ../devices/virtual/block/ram2/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram3 -> ../devices/virtual/block/ram3/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram4 -> ../devices/virtual/block/ram4/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram5 -> ../devices/virtual/block/ram5/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram6 -> ../devices/virtual/block/ram6/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 ram7 -> ../devices/virtual/block/ram7/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 sda -> ../devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 sdb -> ../devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 sdc -> ../devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/host8/target8:0:0/8:0:0:0/block/sdc/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 sdd -> ../devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.0/host9/target9:0:0/9:0:0:0/block/sdd/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 sr0 -> ../devices/pci0000:00/0000:00:17.0/ata5/host4/target4:0:0/4:0:0:0/block/sr0/
lrwxrwxrwx    1 root     root             0 Feb  5 20:49 zram0 -> ../devices/virtual/block/zram0/
tc@box:~$ sudo cp model.conf /home/tc/patch/etc/model.conf
tc@box:~$ sudo create_qnap_boot
=====Start verify qunp firmware=====
[ Verifying the bzImage] => PASSED
[ Verifying the initrd.boot] => PASSED
[ Verifying the qpkg.tar] => PASSED
[ Verifying the rootfs_ext.tgz] => PASSED
[ Verifying the rootfs2.bz] => PASSED
=====Verify qunp firmware is OK=====
Re-packing the patch.gz. Please wait a while.
Re-packing the patch.gz successful.

There are following targets for you to install QNAP boot disk:
[1]=>[/dev/sda]
[2]=>[/dev/sdb]
[3]=>[/dev/sdc]
[4]=>[/dev/sdd]
Please select the following [number] for the target device:3
=====[start to install QNAP boot disk on /dev/sdc]=====
Start to make partition on /dev/sdc for EFI boot disk
Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Information: You may need to update /etc/fstab.

Parted /dev/sdc for EFI boot disk successful.
mkfs.fat 3.0.26 (2014-03-07)
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 307200 1k blocks and 76912 inodes
Filesystem UUID: c0f3e62d-c81d-4496-8b1b-44404e568ecb
Superblock backups stored on blocks:
        8193, 24577, 40961, 57345, 73729, 204801, 221185

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 307200 1k blocks and 76912 inodes
Filesystem UUID: 0cd87806-24ae-4abc-b13d-12dddedf9835
Superblock backups stored on blocks:
        8193, 24577, 40961, 57345, 73729, 204801, 221185

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 8192 1k blocks and 2048 inodes

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 8192 1k blocks and 2048 inodes

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 7334651 4k blocks and 1835008 inodes
Filesystem UUID: d37b3edd-fead-4f43-886a-ebf6ea38b77a
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 8192 1k blocks and 2048 inodes

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

Format all /dev/sdc partitions successful.
Installing for x86_64-efi platform.
Installation finished. No error reported.
Config grub2 main menu
Copy QNAP System into targer disk
Copy tool kit into [/dev/sdc]

Create [/dev/sdc] boot disk successful!

tc@box:~$

 

Boot Firmware 4.5

 

7.thumb.png.9e8b08e452b2a9faa931dfb9733c361d.png

 

Booted Firmware 4.5

 

8.thumb.png.f7d8930f72801dab3e78c84970b85107.png

 

9.thumb.png.b705810e881282a0f67c3dea20e70556.png

 

 

Reboot nach OTA Update Firmware 5.0

 

10.thumb.png.d9f8c92689ac360447c045c51a381a91.png

 

11.thumb.png.0f06d5997689b48e0e2edde0293100c9.png

 

12.thumb.png.1262ec3eca626e9cd45e12d6bb22ae1f.png

 

 

Boot nach OTA Update Firmware 5.0

 

13.thumb.png.d143e081aa6fe53871532386988fe84e.png

 

 

Booted Firmware 5.0 😍   Danke dir  @snoopy78 🤝

 

14.thumb.png.6b48234212bac007885ea762e472f1bd.png

 

Edited by xenix96
Link to comment
Share on other sites

LAG und Portbündelung funktioniert 👍

 

15_1.thumb.png.b9f39242bb324015d2d47d9a41380b7d.png

 

Balanced-alb

 

15.thumb.png.4b17a4dc0212ba0efe02d4f5245dc8e1.png

 

 

 

Broadcast

 

17.thumb.png.7d9f004b1357c38a57cd64c0648738b5.png

 

 

 

Speicherpool RAID1 funktioniert 👍

 

16.thumb.png.4cb8de2b154fa77947b7cece1f626c8f.png

 

Migration VM Pihole Server funktioniert 👍

 

18.thumb.png.4bc114526bf194a5992e1a70b4b76287.png

 

VM Pihole läuft und funktioniert 👍

 

19.thumb.png.b0460dbb0ba47cc3b410e7808b00332b.png

 

20.thumb.png.107017827c3fa822420c9635328db2bc.png

 

21.thumb.png.06c9f7cc5bba059a4cb8722360443464.png

 

Edited by xenix96
  • Like 1
Link to comment
Share on other sites

Hallo,
Ich habe auch die Datei QNAP-BOOT-EN-v1.00.img von dem neu angegebenen Link zum Testen heruntergeladen und eine USB-Startdiskette erstellt.

Der TinyCore-Bildschirm erscheint bei mir nicht, er bleibt auf dem schwarzen Bildschirm, aber ich kann eine Verbindung mit SSH herstellen, indem ich die IP-Adresse des Systems erkenne. Zunächst einmal kann ich das Skript „sudo get_qnap_firmware“ in den kurzen Installationsschritten von @snoopy78 nicht finden. Ich weiß nicht, ob es an der .img-Datei liegt, die ich verwende.

Jetzt teile ich die Befehle, die ich nach dem ersten USB-Boot mit SSH eingegeben habe.

 

Connecting to 192.168.0.109:22...
Connection established.
To escape to local shell, press 'Ctrl+Alt+]'.

WARNING! The remote SSH server rejected X11 forwarding request.
   ( '>')
  /) TC (\   Core is distributed with ABSOLUTELY NO WARRANTY.
 (/-_--_-\)           www.tinycorelinux.net

tc@box:~$ sudo get_qnap_firmware /home/tc/
.Xauthority                     .xsession                       hal_app2
.Xdefaults                      DEVBUS                          hardware_check
.ash_history                    README.txt                      modify_your_initrd
.ashrc                          TS-X72_20211221-5.0.0.1891.zip  my_create_qnap_boot
.local/                         VERSION-1.01                    original_laojifuli_scripts/
.profile                        add_modules_files               pack_your_initrd
.setbackground                  additional/                     pc1
.wbar                           figure_devices                  translated_lajifuli_scripts/
.wmx/                           hal_app1
tc@box:~$ sudo get_qnap_firmware /home/tc/
.Xauthority                     .xsession                       hal_app2
.Xdefaults                      DEVBUS                          hardware_check
.ash_history                    README.txt                      modify_your_initrd
.ashrc                          TS-X72_20211221-5.0.0.1891.zip  my_create_qnap_boot
.local/                         VERSION-1.01                    original_laojifuli_scripts/
.profile                        add_modules_files               pack_your_initrd
.setbackground                  additional/                     pc1
.wbar                           figure_devices                  translated_lajifuli_scripts/
.wmx/                           hal_app1
tc@box:~$ sudo get_qnap_firmware /home/tc/TS-X72_20211221-5.0.0.1891.zip 
sudo: get_qnap_firmware: command not found
tc@box:~$ sudo ./my_create_qnap_boot 
./my_create_qnap_boot: line 7: TVS-472X: not found
Clear the boot, Please wait a while.
Uncompressing QNAP original firmware
Archive:  ./TS-X72_20211221-5.0.0.1891.zip
  inflating: TS-X72_20211221-5.0.0.1891.img
Using 120-bit encryption - (QNAPNASVERSION4)
len=1048576
model name = TS-X72
version = 5.0.0
bzImage
bzImage.cksum
initrd.boot
initrd.boot.cksum
qpkg.tar
qpkg.tar.cksum
rootfs2.bz
rootfs2.bz.cksum
rootfs_ext.tgz
rootfs_ext.tgz.cksum
==================
DEV_BUS=B00:D23:F0
==================
Patch model system disk controller config.
This script will try to determine the DEV_BUS of your devices, please verify generated model.conf
Getting model.conf from your initrd folder
Total eth devices discovered = 8
[System Network 1] 
DEV_BUS = B02:D00:F0
[System Network 2] 
DEV_BUS = B02:D00:F1
[System Network 3] 
DEV_BUS = B02:D00:F2
[System Network 4] 
DEV_BUS = B02:D00:F3
[System Network 5] 
DEV_BUS = B07:D00:F0
[System Network 6] 
DEV_BUS = B07:D00:F1
[System Network 7] 
DEV_BUS = B07:D00:F2
[System Network 8] 
DEV_BUS = B07:D00:F3
Getting Boot Disk information
[Boot Disk 1]
DEV_BUS = B00:D20:F0
Trying to figure out connected disk bus 
Found Disks : 
sda
sdb
sdc
sdd
sde
[System Disk 6] 
DEV_BUS = B00:D23:F0  
DEV_PORT = -1
[System Disk 11] 
DEV_BUS = B00:D23:F0  
DEV_PORT = -1
[System Disk 12] 
DEV_BUS = B00:D23:F0  
DEV_PORT = -1
[System Disk 13] 
DEV_BUS = B00:D23:F0  
DEV_PORT = -1
sde is a USB Disk on PCI BUS 
Total USB controllers  discovered = 2
[Usb Port 1] 
DEV_BUS = B00:D20:F0
[Usb Port 2] 
DEV_BUS = B01:D00:F4
Found more PCI devices than your current model  TVS-472X is supporting, maxing selections to that number verify yourself
Total PCI Bridges discovered = 2
[System PCIE SLOT 1] 
DEV_BUS = B00:D01:F0
[System PCIE SLOT 2] 
DEV_BUS = B00:D27:F0
Finding memory slots
Trying to figure out memory modules
Loading additional tinycore software
dmidecode is already installed!
Done with detection, i'm putting modified model.conf back to initrd location
Please check the below output for changes we performed in initrd/etc/model.conf
-------------------------------------------------------------------------
[System Network 1]
DEV_BUS = B02:D00:F0
--
[System Network 2]
DEV_BUS = B02:D00:F1
--
[System Network 3]
DEV_BUS = B02:D00:F2
[Boot Disk 1]
DEV_BUS = B00:D20:F0
[System Disk 1]
DEV_BUS=B00:D23:F0
DEV_PORT = 3
--
[System Disk 2]
DEV_BUS=B00:D23:F0
DEV_PORT = 2
--
[System Disk 3]
DEV_BUS=B00:D23:F0
DEV_PORT = 1
--
[System Disk 4]
DEV_BUS=B00:D23:F0
DEV_PORT = 0
--
[System Disk 5]
DISK_FORM_TYPE = PD_FORM_M_2_PCIE
BUS_TYPE = NVME
--
[System Disk 6]
DISK_FORM_TYPE = PD_FORM_M_2_PCIE
BUS_TYPE = NVME
[Usb Port 1]
DEV_BUS = B00:D20:F0
--
[Usb Port 2]
DEV_BUS = B01:D00:F4
--
[Usb Port 3]
DEV_BUS = B00:D20:F0
--
[Usb Port 4]
DEV_BUS = B00:D20:F0
--
[Usb Port 5]
DEV_BUS = B00:D20:F0
--
[Usb Port 6]
DEV_BUS = B00:D01:F0
--
[Usb Port 7]
DEV_BUS = B00:D01:F0
--
[Usb Port 8]
DEV_BUS = B00:D28:F0
--
[Usb Port 9]
DEV_BUS = B00:D28:F0
[System PCIE SLOT 1]
DEV_BUS = B00:D01:F0
--
[System PCIE SLOT 2]
DEV_BUS = B00:D27:F0
SLOT1_ADDR = 1, 0x50
SLOT2_ADDR = 2, 0x52
----------------------------------------------------------------={ DONE }=---------
Please verify model.conf and then execute ./pack_your_initrd
Re-packing the QNAP RAM disk. Please wait a while.
Repair the rootfs2.bz file. Please wait a while.

Create QNAP boot disk successful
If you need to modify the model file in the mymodel directory, execute sudo cp -f ./mymodel/* ./initrd/etc/ 
Re-execute sudo ./re_packing to complete boot disk creation
Please restart the system if not needed

tc@box:~$ ls
DEVBUS
README.txt
TS-X72_20211221-5.0.0.1891.050220222347.zip
VERSION-1.01
add_modules_files
additional/
figure_devices
hal_app1
hal_app2
hardware_check
initrd/
model.conf
modify_your_initrd
my_create_qnap_boot
mymodel/
original_laojifuli_scripts/
pack_your_initrd
pc1
translated_lajifuli_scripts/
tc@box:~$ ls -al /sys/block /sd*
ls: /sd*: No such file or directory
/sys/block:
total 0
drwxr-xr-x    2 root     root             0 Feb  5 23:28 ./
dr-xr-xr-x   12 root     root             0 Feb  5 23:28 ../
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop0 -> ../devices/virtual/block/loop0/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop1 -> ../devices/virtual/block/loop1/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop10 -> ../devices/virtual/block/loop10/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop11 -> ../devices/virtual/block/loop11/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop12 -> ../devices/virtual/block/loop12/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop13 -> ../devices/virtual/block/loop13/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop14 -> ../devices/virtual/block/loop14/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop15 -> ../devices/virtual/block/loop15/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop16 -> ../devices/virtual/block/loop16/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop17 -> ../devices/virtual/block/loop17/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop18 -> ../devices/virtual/block/loop18/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop19 -> ../devices/virtual/block/loop19/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop2 -> ../devices/virtual/block/loop2/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop20 -> ../devices/virtual/block/loop20/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop21 -> ../devices/virtual/block/loop21/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop22 -> ../devices/virtual/block/loop22/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop23 -> ../devices/virtual/block/loop23/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop24 -> ../devices/virtual/block/loop24/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop25 -> ../devices/virtual/block/loop25/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop26 -> ../devices/virtual/block/loop26/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop27 -> ../devices/virtual/block/loop27/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop28 -> ../devices/virtual/block/loop28/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop29 -> ../devices/virtual/block/loop29/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop3 -> ../devices/virtual/block/loop3/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop30 -> ../devices/virtual/block/loop30/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop31 -> ../devices/virtual/block/loop31/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop32 -> ../devices/virtual/block/loop32/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop33 -> ../devices/virtual/block/loop33/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop34 -> ../devices/virtual/block/loop34/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop4 -> ../devices/virtual/block/loop4/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop5 -> ../devices/virtual/block/loop5/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop6 -> ../devices/virtual/block/loop6/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop7 -> ../devices/virtual/block/loop7/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop8 -> ../devices/virtual/block/loop8/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 loop9 -> ../devices/virtual/block/loop9/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 ram0 -> ../devices/virtual/block/ram0/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 ram1 -> ../devices/virtual/block/ram1/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 ram2 -> ../devices/virtual/block/ram2/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 ram3 -> ../devices/virtual/block/ram3/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 ram4 -> ../devices/virtual/block/ram4/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 ram5 -> ../devices/virtual/block/ram5/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 ram6 -> ../devices/virtual/block/ram6/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 ram7 -> ../devices/virtual/block/ram7/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 sda -> ../devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 sdb -> ../devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 sdc -> ../devices/pci0000:00/0000:00:17.0/ata3/host2/target2:0:0/2:0:0:0/block/sdc/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 sdd -> ../devices/pci0000:00/0000:00:17.0/ata4/host3/target3:0:0/3:0:0:0/block/sdd/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 sde -> ../devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host8/target8:0:0/8:0:0:0/block/sde/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 sdf -> ../devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/host9/target9:0:0/9:0:0:0/block/sdf/
lrwxrwxrwx    1 root     root             0 Feb  5 23:28 zram0 -> ../devices/virtual/block/zram0/
tc@box:~$ 
 

 

Link to comment
Share on other sites

34 minutes ago, snoopy78 said:

@szararsiz  Sisteminiz UEFI mi? Bu, UEFI olmayan sistemlerle çalışmaz ....

 

SSH ile iletişim kurarsanız, tc'e gerçekten vardır...... PC'de yerel olarak admin/admin

 

 

Ja UEFI. Ich habe auch einen Screenshot eingestellt.

 

 

Ich warte derzeit darauf, dass es mit dem von mir erstellten USB bootet, aber es ist unglaublich langsam.

 

 

UEFI.jpg

Edited by szararsiz
Link to comment
Share on other sites

4 minutes ago, szararsiz said:

Ja UFI. Ich habe auch einen Screenshot eingestellt.

UEFI.jpg

 

Bei HP Proliant kein Smart array für SATA verwenden -> SATA AHCI funktioniert hier bei meinem HPE Proliant ML30 Gen9 👍

Rebooten

F11 Bootmenu

und Rear USB 2 anwählen

dann erscheint auch eine rote Kuh mit Tiny Core :) 👍

Edited by xenix96
  • Thanks 1
Link to comment
Share on other sites

6 minutes ago, xenix96 said:

 

Bei HP Proliant kein Smart array für SATA verwenden -> SATA AHCI funktioniert hier bei meinem HPE Proliant ML30 Gen9 👍

Rebooten

F11 Bootmenu

und Rear USB 2 anwählen

dann erscheint auch eine rote Kuh mit Tiny Core :) 👍

 

Ich sehe nur 2 Startoptionen.

 

BOOT OPT.jpg

Edited by szararsiz
Link to comment
Share on other sites

6 minutes ago, xenix96 said:

 

That's also boot options ......these remain on UEFI

 

You need to look at SATA Controller Options:)

22.png

 

Ja, jetzt habe ich meine Einstellungen überprüft, "SATA AHCI Support" ist aktiv.

 

Hinweis: Ich schreibe immer, indem ich ins Deutsche übersetze, tut mir leid, damit habe ich auch etwas Mühe.

 

SATA.jpg

Edited by szararsiz
  • Like 1
Link to comment
Share on other sites

@xenix96 @snoopy78
Ich habe mal einen Screenshot von Tiyncore gemacht, da ich gerade nicht per SSH auf Tinycore drauf komme.
Einmal ist nur die Ausgabe mit lspci und das zweite Bild ist mir lspci -vtnn, da konnte ich aber nichts zu der Karte erkennen. Ich vermute mal, dass auf dem ersten Bild evtl. die letzten drei Einträge die Karte sind. Bin mir aber nicht ganz sicher.
Allerdings habe ich den Lüfter nicht angeschlossen, da diese mit der Höhe von den SFF-8643 Adaptern nicht passen. Weiß nicht, ob dann vielleicht die Karte nicht richtig funktioniert.
Vielleicht könnt Ihr evtl. die richtige PCI Adresse dafür herausfinden.

Danke.
 

tinycore_qm2.png

tinycore_qm2_1.png

Link to comment
Share on other sites

one question to all the linux cracks here....

 

with the new boot iso i created an bootable usb stick

since i want to modify the

 

i did unpack the initrd.boot to modify some values in "create_udev_rule.sh" (located /etc/init.d/ )

 

so i did

 

mkdir /tmp/initrd_content

cd /tmp/initrd_content

sudo xz -z /tmp/initrd_content/ /mnt/sdc2/boot/initrd.boot -i

 

Then i were anle to find & modify the required values...

 

but HOW can i compress the changes now again so that i have a valid initdr.boot again?

 

Thank you for your help

 

Link to comment
Share on other sites

Hallo, ich habe als Ergebnis meiner Experimente seit gestern Abend mehrere Male erfolgreich installiert.
Zuerst habe ich das 472-Modell installiert und dann die 1283ux-Modelle.
Nachdem ich Qnap mit USB geöffnet habe, habe ich die ersten Installationen mit dem Assistenten durchgeführt und ein Volume mit 1 SSD-Festplatte erstellt. Ich konnte die Virtualisierung und einige Anwendungen erfolgreich installieren.

Aber bei beiden Versuchen sah die CPU nur 1 Kern (Intel Xeon E-2224 4 Kern)

Gibt es eine Möglichkeit, dies zu beheben?

 

 

Main.jpg

Resource.jpg

CPU.jpg

Edited by szararsiz
Link to comment
Share on other sites

12 hours ago, snoopy78 said:

one question to all the linux cracks here....

 

with the new boot iso i created an bootable usb stick

since i want to modify the

 

i did unpack the initrd.boot to modify some values in "create_udev_rule.sh" (located /etc/init.d/ )

 

so i did

 

mkdir /tmp/initrd_content

cd /tmp/initrd_content

sudo xz -z /tmp/initrd_content/ /mnt/sdc2/boot/initrd.boot -i

 

Then i were anle to find & modify the required values...

 

but HOW can i compress the changes now again so that i have a valid initdr.boot again?

 

Thank you for your help

 

PACK

# find . | cpio -o -H newc | gzip > ../initrd.boot

 

UNPACK

# gzip -dc ../initrd.boot | cpio -id

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...