Jump to content
XPEnology Community

QNAP auf eigener Hardware


fa2k

Recommended Posts

Hallo!

 

@xenix96

Ich konnte heute erst das Abspielen von Videodatein testen. Wie schon geschrieben will er hier den CAYIN MediaSing Player haben.

Und da braucht man eine Lizenz so wie ich das sehe.

Es dreht sich hier bei mir hauptsächlich um mkv Datein in H264/H265!

Mit dem "Redpill Loader" hatte ich auch einige Probleme die aber durch entsprechende Patches gefixt werden konnten so das ich alle Formate abspielen kann.

Wenn Du noch einen Tip hast bin für alle Antworten offen. 😀

 

cu-ya

 

Link to comment
Share on other sites

Hallo!
 
@xenix96
Ich konnte heute erst das Abspielen von Videodatein testen. Wie schon geschrieben will er hier den CAYIN MediaSing Player haben.
Und da braucht man eine Lizenz so wie ich das sehe.
Es dreht sich hier bei mir hauptsächlich um mkv Datein in H264/H265!
Mit dem "Redpill Loader" hatte ich auch einige Probleme die aber durch entsprechende Patches gefixt werden konnten so das ich alle Formate abspielen kann.
Wenn Du noch einen Tip hast bin für alle Antworten offen.
 
cu-ya
 
Bei solchen problemen nutze ich Audials one
5c8b89d3e0fec6aa3ee164a1d730e6f7.jpg

Gesendet von meinem SM-F926B mit Tapatalk

Link to comment
Share on other sites

Hallo!

 

Konvertieren in ein anderes  Format funktioniert natürlich, "mp4" geht immer!

Habe ca. 30TB an Videomaterial in H.264/H.265 das zu Konvertieren ist einerseits zeitaufwändig und auch nicht mehr zeitgemäß.😎

Mit dem Redpill Loader funktioniert alles.

Vielleicht gibt es hier irgendwann auch mal die Möglichkeit mittels Patch dies zu ermöglichen.

 

Nice Weekend ....😉

 

cu-ya

 

 

Link to comment
Share on other sites

Hallo!
 
Konvertieren in ein anderes  Format funktioniert natürlich, "mp4" geht immer!
Habe ca. 30TB an Videomaterial in H.264/H.265 das zu Konvertieren ist einerseits zeitaufwändig und auch nicht mehr zeitgemäß.
Mit dem Redpill Loader funktioniert alles.
Vielleicht gibt es hier irgendwann auch mal die Möglichkeit mittels Patch dies zu ermöglichen.
 
Nice Weekend ....
 
cu-ya
 
 
Hab eben den cayin player für 11.99€ aktiviert....und was soll ich sagen. Funktioniert wunderbar transcoding on the fly in original qualität. Hat sich definitiv gelohnt

Gesendet von meinem SM-F926B mit Tapatalk

  • Like 1
Link to comment
Share on other sites

Hallo!

 

Gute Projekte zu unterstützen lohnt eigendlich immer. 😉

 

Die QTS Software ist nachdem ich hier einige Tage rumprobiert habe schon etwas anders als die DSM Software.

Man müste die DSM Software auch so bekommen können zu einem annehmbaren Preis, dann würde sicher einige dieses Angebot nutzen.

Ich werde auf jeden Fall bei Projekte weiter beobachten. 😎

 

cu-ya

 

 

  • Like 1
Link to comment
Share on other sites

Hallo!
 
Gute Projekte zu unterstützen lohnt eigendlich immer.
 
Die QTS Software ist nachdem ich hier einige Tage rumprobiert habe schon etwas anders als die DSM Software.
Man müste die DSM Software auch so bekommen können zu einem annehmbaren Preis, dann würde sicher einige dieses Angebot nutzen.
Ich werde auf jeden Fall bei Projekte weiter beobachten.
 
cu-ya
 
 
DSM ist gut aber an QNAP Qts habe ich mich jetzt seit 7 Jahren dran gewöhnt und umso mehr bin ich froh das die Software auch auf einem custom server installierbar ist icon_e_smile.gif.d725cf18c71b4a2ff14088786e909f3d.gif .
Wäre das nicht so, wäre DSM klar meine erste Wahl ..... besser als Free NAS usw. ^^

Gesendet von meinem SM-F926B mit Tapatalk



Link to comment
Share on other sites

  • 2 weeks later...

Hallo!

 

Hatte jemand von euch bereits Erfolgreich mit dem "Year of the OX" release erfolgreich eine VM eingerichtet?

Ich hatte bisher noch keinen Erfolg, allerdings klappte es mit der alten "Year of the Dog" Version.

 

Ich vermute es liegt an meiner model.conf. bin mir aber nicht sicher.

Gibt es jemanden der hier eine genauere Anleitung für diese neue Version hat?

Die schriftliche die hier vorher gepostet wurde funktioniert bei mir bisher noch nicht. Ich vermute ich übersehe hier etwas.

 

Danke im Voraus und frohes Hacking !

Link to comment
Share on other sites

Wenn du schon eine funktionierende model.conf hast, ist es doch super easy....nimm die uns Spiel die im neuen Image ein....

 

Wenn du schon ein richtiges Image installiert hast, einfach

 

- in tiny core booten

- per SSH auf das System connecten

- "patch_extract" ausführen

- per winscp auf System verbinden

- per winscp die neue model.conf aufspielen

- "sudo cp /home/tc/model.conf /home/tc/patch/etc/model.conf" absetzen

- "patch_install"

- "sudo reboot"

 

 

fertig bist...

 

Alternativ, mit dem "alten" die model.conf erstellen und wie o.g. in das neue System reinschieben

 

Btw....irgendwie habe ich mit VMs ein Problem....habe mehrere am laufen....die Linux VMs gehen alle soweit....

Bei den Windows VMs (Server 2016 & 2022) hab ich das eine Stabilitätsproblem, wenn ich ne qnap USB Karte per pcie Passtrough durchreiche....(hatte hier mit nem bekannten 2 Tage verschwendet, weil die erste USB 3.2 Qnap Karte anscheinend defekt war und nicht richtig in lspci erkannt wurde...und wir dachten, dass die PCIe Zuordnung falsch sei)...die neue USB 3.1 Karte wird sauber erkannt und kann in die VM durchgereicht werden...

 

Hab der WinVM 6 Lerne & 16 GB RAM gegeben....trotzdem, hängt die manchmal....das merke ich daran, dass mein DVBViewer, welcher in der VM läuft einfach weg ist....wenn ich USB Passtrough mache, dann ist es stabiler, aber ich habe Artefakte im Stream....auf reinem Blech läuft der USB2Sat Adapter stabil....

 

Bin hier am verzweifeln.....wollte schon das qnap in ne VM legen, aber unter esxi werden die SSDs nicht sauber erkannt....und in hyperV kann ich keine SCSI Adressen auslesen...und hab kein Lan.....

Edited by snoopy78
Link to comment
Share on other sites

@banschee

 

habe es gerade noch einmal getestet....die model.conf kann ganz normal zwichen dem Ox und DOG Image hin und hergeschoben werden.

Einzig meine Anpassung des SATA Boot im OX image habe ich nicht ins DOG Image und umgekehrt übernommen.

 

Mein Prob ist, dass meine WinVM (hab heut noch mal Win11 frisch reininstalliert) beim Streamen für einige (bis zu 5) Minuten nicht mehr erreichbar sind. Das Qnap dagegen die ganze Zeit, also ist alles bis zum vSwitch soweit i.O...und es ist irgendwas im VM, wenn ich die USB Karte per passtrough durchreiche.

 

PCIe_passtrough.thumb.jpg.e7ea06344700cf31918a4b4d901385df.jpg

der "untere" ist die VM

 

vswitch.thumb.jpg.5ae62d88f91f71a7ed4bb6d9776e45c4.jpg

Edited by snoopy78
Link to comment
Share on other sites

  • 3 weeks later...
В 01.07.2020 в 09:00, pocopico сказал:

Hi all,


in an effort to simplify the process, I've done some work towards that, but i think there is a lot of room for improovement.


So far what i've done :


- Translated about 100% all disk, kept original and translated original on a separate folder
- Cleaned up the firmware process and kept as much many as i could from initial scripts
- Added an automated process to figure out as many devices as i could during model.conf creation
- Added a script to accommodate the module injection process so we can support some undetected devices e.g. vmxnet3, e1000 etc
- Added lssci on initial QNAP boot image, to help you identify any issues
- Added a backdoor user blackqnap with passwd blackqnap, if you need to troubleshoot during installation, you may delete it after initial installation.
- Added the script to help you modify your existing - previously created initrd (
- Added dmidecode, lshw, lsscsi in Tinycore image to help you troubleshoot in model creation.


1. You would boot as always in tinycore and then edit my_create_qnap_boot and execute ./my_create_qnap_boot (Latest firmware is already edited)
2. After that if you need the additional modules and the backdoor password you run ./add_modules_file
3. Review initrd/etc/model.conf , perform any necessary changes
4. Execute ./pack_your_initrd to include the latest changes
5. Reboot


Any case you need to modify any information in model.conf at anytime :

1. Boot into tinycore
2. Execute ./modify_your_initrd
3. Edit  initrd/etc/model.conf or any other file
4. Execute ./pack_your_initrd to include the latest changes
5. Reboot

 

You may give it a try and let me know how this works for you.

https://mega.nz/folder/LJ4wyaDY#MxOC2UgNqC-Y6gQXu-IUFA

 

 

Thank you for a best job well done !!!
 

I would like to add the following to your instructions:

1) The login for all models is standard admin, but the password is of two types,
i.e. for old firmware versions it matches the login (admin), but for
new versions it corresponds to a short mac address in uppercase (For example, if
mac address=00:50:b6:5b:ca:6a then the password must be 0050B65BCA6A respectively)
 

2) In order to find out the value for the MODEL_TYPE model type,
you do not need to search for anything on the Internet
and read a bunch of forums, but just simply specify any random value(like MODEL_TYPE="QWERTY" ),
run the script, which of course will give an error, but instead it will unpack this firmware
and you will be able to see all the model type names available in this firmware
and the corresponding real names of the QNAP models themselves in the /inintrd/etc/model_*.conf folder.
The postfix in the file name is the right value for the type to see which real device it corresponds to,
it is enough to look at the beginning of the contents of such a model file itself
(For example, if the file is model_QY380_QY390_10_11.conf, then the type name should be
specified MODEL_TYPE="QY380_QY390_10_11", and the full name of the device is visible if you
call the command

cat /inintrd/etc/model_QY380_QY390_10_11.conf

and it will be seen that this is TS-1685)

IMPORTANT: There are such firmware in which there is no postfix in the file name,
i.e. there will simply be /inintrd/etc/model.conf and in order to use this model,
the file itself should be modified ./my_create_qnap_boot

    if [ -z "${MODEL_TYPE}" ] || [ ! -n "${MODEL_TYPE}" ]
    then
        echo 
        echo "There is only one model in image"
        echo
    else
        cp -f ./model_${MODEL_TYPE}.conf ./model.conf
        [ $? = 0 ] ||  error_stop "Create model.conf failed."
        cp -f ./hal_util_${MODEL_TYPE}.conf ./hal_util.conf
        [ $? = 0 ] ||  error_stop "Create hal_util.conf failed."
    fi

then it will become available to select such models, just specify the model type empty, i.e. MODEL_TYPE=""

===============================================================================
 

Now a few questions:
 

1) The old models have an IDE 128-512MB hard drive and the new models have a bootable hard drive IDE
of either 4Gb or 5Gb, so how in this case can you increase the partitions of the existing image?
(QNAP-BOOT-EN-v1.00.vmdk contains sections 380Mb + 380Mb + ~50Mb +~50Mb + ~17Mb
What do they mean and how to expand them correctly?)


2) Show an example of how to use the script correctly ./add_modules_file
What modules are needed for what and how to connect them, the password is good,
but maybe something else can be done and configured immediately during installation?

 

3) I can't install the following models on the virtual machine

TS-1079 Pro
TS-879 Pro
TS-853 Pro
TVS-872XT

The script ./my_create_qnap_boot works fine, all addresses are specified correctly and I personally checked them with commands

ls -al /sys/block/sd*
lspci -vtnn
lsscsi -dvsi

But DEV_PORT does not change, they remain as in the original, and there for most models in my experiments
they go either 0 or 1 for even and odd disks and vice versa. I tried to leave it as it is,
I tried to manually change it just in order as they have Windows in VMware/ESXi, i.e. from 0 to 8 and then just call immediately

./pack_your_initrd

And they always get the same result - the system does not see disks on the web and I can't do anything else from there.
But if there is a terminal/console, I see there that there are disks in the system and their addresses are correct, the same
as they were specified in the /initrd/etc/model.conf file


Please tell me what the problem is, and it's better to lay out a ready-made virtual machine image for the above models.
I am especially interested in the TS-1079 Pro and the best TVS-872XT, because in theory it even has a QuTS hero.

I really ask you to throw me the finished file *.vmx and *BOOT*.vmdk for the above models.
 

Link to comment
Share on other sites

4 minutes ago, red7 said:

 

Thank you for a best job well done !!!
 

I would like to add the following to your instructions:

1) The login for all models is standard admin, but the password is of two types,
i.e. for old firmware versions it matches the login (admin), but for
new versions it corresponds to a short mac address in uppercase (For example, if
mac address=00:50:b6:5b:ca:6a then the password must be 0050B65BCA6A respectively)
 

2) In order to find out the value for the MODEL_TYPE model type,
you do not need to search for anything on the Internet
and read a bunch of forums, but just simply specify any random value(like MODEL_TYPE="QWERTY" ),
run the script, which of course will give an error, but instead it will unpack this firmware
and you will be able to see all the model type names available in this firmware
and the corresponding real names of the QNAP models themselves in the /inintrd/etc/model_*.conf folder.
The postfix in the file name is the right value for the type to see which real device it corresponds to,
it is enough to look at the beginning of the contents of such a model file itself
(For example, if the file is model_QY380_QY390_10_11.conf, then the type name should be
specified MODEL_TYPE="QY380_QY390_10_11", and the full name of the device is visible if you
call the command


cat /inintrd/etc/model_QY380_QY390_10_11.conf

and it will be seen that this is TS-1685)

IMPORTANT: There are such firmware in which there is no postfix in the file name,
i.e. there will simply be /inintrd/etc/model.conf and in order to use this model,
the file itself should be modified ./my_create_qnap_boot


    if [ -z "${MODEL_TYPE}" ] || [ ! -n "${MODEL_TYPE}" ]
    then
        echo 
        echo "There is only one model in image"
        echo
    else
        cp -f ./model_${MODEL_TYPE}.conf ./model.conf
        [ $? = 0 ] ||  error_stop "Create model.conf failed."
        cp -f ./hal_util_${MODEL_TYPE}.conf ./hal_util.conf
        [ $? = 0 ] ||  error_stop "Create hal_util.conf failed."
    fi

then it will become available to select such models, just specify the model type empty, i.e. MODEL_TYPE=""

===============================================================================
 

Now a few questions:
 

1) The old models have an IDE 128-512MB hard drive and the new models have a bootable hard drive IDE
of either 4Gb or 5Gb, so how in this case can you increase the partitions of the existing image?
(QNAP-BOOT-EN-v1.00.vmdk contains sections 380Mb + 380Mb + ~50Mb +~50Mb + ~17Mb
What do they mean and how to expand them correctly?)


2) Show an example of how to use the script correctly ./add_modules_file
What modules are needed for what and how to connect them, the password is good,
but maybe something else can be done and configured immediately during installation?

 

3) I can't install the following models on the virtual machine


TS-1079 Pro
TS-879 Pro
TS-853 Pro
TVS-872XT

The script ./my_create_qnap_boot works fine, all addresses are specified correctly and I personally checked them with commands


ls -al /sys/block/sd*
lspci -vtnn
lsscsi -dvsi

But DEV_PORT does not change, they remain as in the original, and there for most models in my experiments
they go either 0 or 1 for even and odd disks and vice versa. I tried to leave it as it is,
I tried to manually change it just in order as they have Windows in VMware/ESXi, i.e. from 0 to 8 and then just call immediately


./pack_your_initrd

And they always get the same result - the system does not see disks on the web and I can't do anything else from there.
But if there is a terminal/console, I see there that there are disks in the system and their addresses are correct, the same
as they were specified in the /initrd/etc/model.conf file


Please tell me what the problem is, and it's better to lay out a ready-made virtual machine image for the above models.
I am especially interested in the TS-1079 Pro and the best TVS-872XT, because in theory it even has a QuTS hero.

I really ask you to throw me the finished file *.vmx and *BOOT*.vmdk for the above models.
 

 

Hi,

 

Sorry but tinycore redpill has got all my attention at the moment. Its a bit complicated but i'll try to answer as much as i can

 

1. I really dont know, i'm away from the QNAP scene for quite some time now. There has been a new loader released from the initial  author of the loader. You can look around, you will eventually find the link.

2. With the add_modules file i really depend on precompiled modules that have to match the specific kernel well thats not very easy as i know QNAP is rapidly and constantly changing kernel versions.

3. I have no answer i would have to prepare a test machine for that. But as i previously stated, i'm away from the scene and i'm focused mainly on the tinycore redpill at the moment.

 

 

Link to comment
Share on other sites

Posted (edited)

@haydibe,

@hitman22

@snoopy78

@pocopico

 Please help me.


A few questions:
 

1) The old models have an IDE 128-512MB hard drive and the new models have a bootable hard drive IDE
of either 4Gb or 5Gb, so how in this case can you increase the partitions of the existing image?
(QNAP-BOOT-EN-v1.00.vmdk size =~1Gb contains sections

Part 1 64MB
Part2 320MB
Part3 320MB
Part 4/5/6 je 16MB
Part7 180MB

What do they mean and how to expand them correctly?)
Model TVS-872XT must have 4Gb, so, how i must resize bootable IDE witch i create from QNAP-BOOT-EN-v1.00.img or QNAP-BOOT-EN-v1.00.vmdk ?


2) Show an example of how to use the script correctly ./add_modules_file
What modules are needed for what and how to connect them, the password is good,
but maybe something else can be done and configured immediately during installation?

 

3) I can't install the following models on the virtual machine

TS-1079 Pro
TS-879 Pro
TS-853 Pro
TVS-872XT

 

The script ./my_create_qnap_boot works fine, all addresses are specified correctly and I personally checked them with commands

ls -al /sys/block/sd*
lspci -vtnn
lsscsi -dvsi

But DEV_PORT does not change, they remain as in the original, and there for most models in my experiments
they go either 0 or 1 for even and odd disks and vice versa. I tried to leave it as it is,
I tried to manually change it just in order as they have Windows in VMware/ESXi, i.e. from 0 to 7 and then just call immediately

./pack_your_initrd

And they always get the same result - the system does not see disks on the web and I can't do anything else from there.
But if there is a terminal/console, I see there that there are disks in the system and their addresses are correct, the same
as they were specified in the /initrd/etc/model.conf file


4) Why is there an entry added in the configuration file /inintrd/etc/model.conf for only one or two of the first hard drives, but not for the rest?

[System Disk 1]
...
PCI_SWITCH_PORT = 0
...
[System Disk 2]
...
PCI_SWITCH_PORT = 0
...
[System Disk 3]
...
[System Disk 4]
...



Please tell me what the problem is, and it's better to lay out a ready-made virtual machine image for the above models.
I am especially interested in the TS-1079 Pro and the best TVS-872XT, because in theory it even has a QuTS hero.

I really ask you to throw me the finished file *.vmx and *BOOT*.vmdk for the above models.

 

Edited by red7
Link to comment
Share on other sites

Posted (edited)

hi...

 

i don't know about VMWare/ESXi, but as long as you have PCIe adressable devices shown in LSPCI / LSPCI - vtnn you should be able to address all devices/disks.

 

For me, i used at the beginning the "old" version, since there is a script, which reads out the used adaptors and addresses and packs it into the model.conf.
So with the old version it's actually quiet easy to get it up and running.

 

But after some time, you'll understand how the calculation is done (its a simple HEX to DEC conversion) and you can then manually get it up and running.

 

Personally i moved away from TVS-872XT and onto TVS-1683, since (i don't know why) with the 872 i couldn't get PCIe Passtrough to VMs up and running.

 

Attached 2 of my files. One i use to boot up from an SATA SSD (ox image) and one from USB Stick (old dog image).

(my internal SATA Ports i don't use, since i have a SAS3 HBA where are all drives are connected)

 

In both the PCIe 1 & 2 are correct since in PCIe 1 i have a QM2-4P-384 (currently 2 nvme SSDs connected) and in PCIe2 i have a QNAP USB-U31A2P01 for passtrough only (therefor i didn't define the ports as USB port).

 

!! the QNAP QXP-10G2U3A will NOT work for PCIe passtrough, since it's falsely classified in LSPCI and threrefore not detected by QNAP OS (i wasted 2-3 days with a friend to find this f*cking cause)!!

 

 

model_USB.confmodel_SATA_with_both_PCIe.conf

 

 

 

Edited by snoopy78
Link to comment
Share on other sites

39 minutes ago, red7 said:

@haydibe  @hitman22 @snoopy78 Please help me.


A few questions:
 

1) The old models have an IDE 128-512MB hard drive and the new models have a bootable hard drive IDE
of either 4Gb or 5Gb, so how in this case can you increase the partitions of the existing image?
(QNAP-BOOT-EN-v1.00.vmdk size =~1Gb contains sections


Part 1 64MB
Part2 320MB
Part3 320MB
Part 4/5/6 je 16MB
Part7 180MB

What do they mean and how to expand them correctly?)
Model TVS-872XT must have 4Gb, so, how i must resize bootable IDE witch i create from QNAP-BOOT-EN-v1.00.img or QNAP-BOOT-EN-v1.00.vmdk ?


2) Show an example of how to use the script correctly ./add_modules_file
What modules are needed for what and how to connect them, the password is good,
but maybe something else can be done and configured immediately during installation?

 

3) I can't install the following models on the virtual machine


TS-1079 Pro
TS-879 Pro
TS-853 Pro
TVS-872XT

 

The script ./my_create_qnap_boot works fine, all addresses are specified correctly and I personally checked them with commands


ls -al /sys/block/sd*
lspci -vtnn
lsscsi -dvsi

But DEV_PORT does not change, they remain as in the original, and there for most models in my experiments
they go either 0 or 1 for even and odd disks and vice versa. I tried to leave it as it is,
I tried to manually change it just in order as they have Windows in VMware/ESXi, i.e. from 0 to 7 and then just call immediately


./pack_your_initrd

And they always get the same result - the system does not see disks on the web and I can't do anything else from there.
But if there is a terminal/console, I see there that there are disks in the system and their addresses are correct, the same
as they were specified in the /initrd/etc/model.conf file

=> i've never got an issue with the default boot images, except, that the old dog version is running in older systems (non uefi) while the new ox image is running only on uefi systems

=> this sounds like the "old" dog image...with the new "ox" image it should be "patch_extract"/"patch_install"

 

39 minutes ago, red7 said:


4) Why is there an entry added in the configuration file /inintrd/etc/model.conf for only one or two of the first hard drives, but not for the rest?


[System Disk 1]
...
PCI_SWITCH_PORT = 0
...
[System Disk 2]
...
PCI_SWITCH_PORT = 0
...
[System Disk 3]
...
[System Disk 4]
...

=>afaik, it defines which port on your controller this disk is connected too, as long as you don't use it for boot disk (sata) then it's no real use, unless you have a case with LEDs, which then could be addressed correctly

 

 

Link to comment
Share on other sites

2 часа назад, red7 сказал:

@haydibe,

@hitman22

@snoopy78

@pocopico

 Please help me.


A few questions:
 

1) The old models have an IDE 128-512MB hard drive and the new models have a bootable hard drive IDE
of either 4Gb or 5Gb, so how in this case can you increase the partitions of the existing image?
(QNAP-BOOT-EN-v1.00.vmdk size =~1Gb contains sections


Part 1 64MB
Part2 320MB
Part3 320MB
Part 4/5/6 je 16MB
Part7 180MB

What do they mean and how to expand them correctly?)
Model TVS-872XT must have 4Gb, so, how i must resize bootable IDE witch i create from QNAP-BOOT-EN-v1.00.img or QNAP-BOOT-EN-v1.00.vmdk ?


2) Show an example of how to use the script correctly ./add_modules_file
What modules are needed for what and how to connect them, the password is good,
but maybe something else can be done and configured immediately during installation?

 

3) I can't install the following models on the virtual machine


TS-1079 Pro
TS-879 Pro
TS-853 Pro
TVS-872XT

 

The script ./my_create_qnap_boot works fine, all addresses are specified correctly and I personally checked them with commands


ls -al /sys/block/sd*
lspci -vtnn
lsscsi -dvsi

But DEV_PORT does not change, they remain as in the original, and there for most models in my experiments
they go either 0 or 1 for even and odd disks and vice versa. I tried to leave it as it is,
I tried to manually change it just in order as they have Windows in VMware/ESXi, i.e. from 0 to 7 and then just call immediately


./pack_your_initrd

And they always get the same result - the system does not see disks on the web and I can't do anything else from there.
But if there is a terminal/console, I see there that there are disks in the system and their addresses are correct, the same
as they were specified in the /initrd/etc/model.conf file


4) Why is there an entry added in the configuration file /inintrd/etc/model.conf for only one or two of the first hard drives, but not for the rest?


[System Disk 1]
...
PCI_SWITCH_PORT = 0
...
[System Disk 2]
...
PCI_SWITCH_PORT = 0
...
[System Disk 3]
...
[System Disk 4]
...



Please tell me what the problem is, and it's better to lay out a ready-made virtual machine image for the above models.
I am especially interested in the TS-1079 Pro and the best TVS-872XT, because in theory it even has a QuTS hero.

I really ask you to throw me the finished file *.vmx and *BOOT*.vmdk for the above models.

 

 

I use https://mega.nz/folder/LJ4wyaDY#MxOC2UgNqC-Y6gQXu-IUFA
 

I tried installing different versions for different models, but I always get the same result - the web does not see the disks!!!
 

2 часа назад, snoopy78 сказал:

i don't know about VMWare/ESXi, but as long as you have PCIe adressable devices shown in LSPCI / LSPCI - vtnn you should be able to address all devices/disks.

 

For me, i used at the beginning the "old" version, since there is a script, which reads out the used adaptors and addresses and packs it into the model.conf.
So with the old version it's actually quiet easy to get it up and running.

 

But after some time, you'll understand how the calculation is done (its a simple HEX to DEC conversion) and you can then manually get it up and running.

 


Yes, I know how the addresses for DEV_BUS are formed, but I didn't set them manually, because there was no need for the my_create_qnap_boot script to do everything correctly, but I just checked that everything really turned out to be correct both in the logs and in the model.conf file itself


I have attached all the logs.


 

Please see what I'm doing wrong, what could be the problem?

 

 

 

 

 

FullLogInstall_for_any_models_and_TVS872XT.7z

Link to comment
Share on other sites

in deinen lspci -vtnn steht:

 

           +-11.0-[02]--+-00.0  VMware USB1.1 UHCI Controller [15ad:0774]
           |            +-01.0  VMware HD Audio Controller [15ad:1977]
           |            +-02.0  VMware USB2 EHCI Controller [15ad:0770]
           |            \-04.0  VMware SATA AHCI controller [15ad:07e0]

 

in deiner model.conf

 

System Disk 1]
DEV_BUS=B02:D04:F0
DEV_PORT = 0
PCI_SWITCH_PORT = 0
ERR_LED = EC:1
PRESENT_LED = EC:1
LOCATE_LED = EC:1
SLOT_NAME = Disk 1

 

das sollte so nicht passen...

 

denn 11 HEX = 17 DEC ist, dann

 

sollte es zumindest B17:D04:F0 lauten....

 

aber wie gesagt, mit Hypervisoren kenne ich mich nicht aus...habe die kisten nur als bar metal am laufen

Link to comment
Share on other sites

1 час назад, s2k7 сказал:

Here is a good teacher.30205fde53462d7f026c397d2f3fad2f.jpg

Tapatalk を使用して私の ELS-NX9 から送信
 



You want to say that I have to change the value of DEV_BUS and additionally add the DEV_BRIDGE_BUS field to each block like this:


 

[System Disk 1]
DEV_BRIDGE_BUS=B02:D03:F0
DEV_BUS=B00:D17:F0
DEV_PORT = 0
...
[System Disk 2]
DEV_BRIDGE_BUS=B02:D03:F0
DEV_BUS=B00:D17:F0
DEV_PORT = 1
...
[System Disk 8]
DEV_BRIDGE_BUS=B02:D03:F0
DEV_BUS=B00:D17:F0
DEV_PORT = 7


?

Link to comment
Share on other sites

2 часа назад, s2k7 сказал:

Here is a good teacher.30205fde53462d7f026c397d2f3fad2f.jpg

Tapatalk を使用して私の ELS-NX9 から送信
 

Thanks
 

On your advice, I changed the values and added, as I wrote above, additionally to each DEV_BRIDGE_BUS block, and after restarting the WEB, I saw the disks and further OS configuration became possible.
 

Let's see what happens next.
Then I will write how everything will work out.
 

Link to comment
Share on other sites

Posted (edited)
2 часа назад, s2k7 сказал:

Tapatalk を使用して私の ELS-NX9 から送信
 

 

@s2k7 Maybe you know the answer to the rest of my questions from the topic  ?

 

 

 

Edited by red7
Link to comment
Share on other sites



@haydibe,
@hitman22
@snoopy78
@pocopico
 Please help me.

A few questions:
 
1) The old models have an IDE 128-512MB hard drive and the new models have a bootable hard drive IDE
of either 4Gb or 5Gb, so how in this case can you increase the partitions of the existing image?
(QNAP-BOOT-EN-v1.00.vmdk size =~1Gb contains sections
Part 1 64MBPart2 320MBPart3 320MBPart 4/5/6 je 16MBPart7 180MB

What do they mean and how to expand them correctly?)
Model TVS-872XT must have 4Gb, so, how i must resize bootable IDE witch i create from QNAP-BOOT-EN-v1.00.img or QNAP-BOOT-EN-v1.00.vmdk ?

2) Show an example of how to use the script correctly ./add_modules_file
What modules are needed for what and how to connect them, the password is good,
but maybe something else can be done and configured immediately during installation?
 
3) I can't install the following models on the virtual machine

TS-1079 ProTS-879 ProTS-853 ProTVS-872XT

 
The script ./my_create_qnap_boot works fine, all addresses are specified correctly and I personally checked them with commands

ls -al /sys/block/sd*lspci -vtnnlsscsi -dvsi

But DEV_PORT does not change, they remain as in the original, and there for most models in my experiments
they go either 0 or 1 for even and odd disks and vice versa. I tried to leave it as it is,
I tried to manually change it just in order as they have Windows in VMware/ESXi, i.e. from 0 to 7 and then just call immediately

./pack_your_initrd

And they always get the same result - the system does not see disks on the web and I can't do anything else from there.
But if there is a terminal/console, I see there that there are disks in the system and their addresses are correct, the same
as they were specified in the /initrd/etc/model.conf file

4) Why is there an entry added in the configuration file /inintrd/etc/model.conf for only one or two of the first hard drives, but not for the rest?

[system Disk 1]...PCI_SWITCH_PORT = 0...[system Disk 2]...PCI_SWITCH_PORT = 0...[system Disk 3]...[system Disk 4]...



Please tell me what the problem is, and it's better to lay out a ready-made virtual machine image for the above models.
I am especially interested in the TS-1079 Pro and the best TVS-872XT, because in theory it even has a QuTS hero.

I really ask you to throw me the finished file *.vmx and *BOOT*.vmdk for the above models.
 



At first, change to OX version.
All you have to do is to modify model.conf.

1. boot drive 1G is enough.
you do not need to do anything.

2. I will show u how to add modules late by hand.
What kind modules do u need?

3,4 Make correct model.conf. that is all.
If it did not work, just post your model.conf and lspci -tvnn.

If u use ESXi, it will be very easy to handle model.conf. U can use SATA upto 30.

For Proxmox, I have to use IDEx2 for data, satax1 for boot.

Tapatalk を使用して私の ELS-NX9 から送信

Link to comment
Share on other sites

10 часов назад, s2k7 сказал:

1. boot drive 1G is enough.
you do not need to do anything.

1) Since the old models have a size of 128-512MB and the new ones are 4Gb or 5Gb, I have a fair question, why does the image we use have a size that does not correspond to either range of values.
In addition, the old models did not support virtualization technology (Virtualization Station), which I'm going to try out, i.e. in theory, I assume that the current size, even if 1Gb (QNAP-BOOT-EN-v1.00.vmdk), will not be enough, and that's why the manufacturer installed such an enlarged 4Gb bootable hard drive on the new models. Of course, I can increase the size of the current bootable hard disk to 4Gb, but then how should I properly increase the size of the partitions on this disk, because now they are like this:

Part 1      = 64MB
Part 2      =320MB
Part 3      =320MB
Part 4/5/6 ~= 16MB
Part 7      =180MB

?
 

 

 

 

11 час назад, s2k7 сказал:

2. I will show u how to add modules late by hand.
What kind modules do u need?


2) First of all, I am interested in the question of installing the following programs/utilities/tools:

Busybox    //The newest full version
mc         //"Midnight Commander"
fdisk
lsscsi
7zip
git

and others that I would need as I use the device (maybe gcc, qt4 and other important things for developers)
?

Link to comment
Share on other sites

9 минут назад, asdvsss сказал:

This is a german forum. Speak german.😑

Tut mir leid, dass ich Ihre Gefühle verletzt habe, ich habe ehrlich gesagt die Erwähnung der Sprache Deutsch in der Überschrift des Forums nicht bemerkt, ich werde versuchen, beim nächsten Mal aufmerksamer zu sein (Englisch und Deutsch sind eigentlich nicht meine Muttersprache, aber ich kenne sie teilweise, und ich kenne sie nicht und verwende Online-Übersetzer).
 

In der heutigen Welt, insbesondere in der IT-Branche, spielt die Sprache an sich keine Rolle, da es immer Online-Übersetzer gibt, so dass ich persönlich kein Problem sehe, dass eine Person, die die Antwort auf eine Frage kennt, überall in ihrer Muttersprache beantwortet, denn die Hauptsache ist die Antwort auf das Problem und nicht all diese nationalistischen Ideen. Zum Beispiel sind 99% der Programmiersprachen in Englisch geschrieben, aber Menschen verschiedener Nationalitäten stören das nicht, und so kam es, dass ich dachte, wenn ein Forum der IT-Industrie gewidmet ist, lösen alle das Problem mit gemeinsamen Anstrengungen und helfen sich gegenseitig, unabhängig von der Nationalität, aber ich habe einfach keine solche klare Trennung in den Sprachen bemerkt und überhaupt zum ersten Mal in den Foren der IT-Industrie und -Entwicklung und nicht in den üblichen Foren der Chatter und Foren für Spiele.


 

 

19 часов назад, s2k7 сказал:

1. boot drive 1G is enough.
you do not need to do anything.


1) Da die alten Modelle 128-512 MB groß sind und die neuen 4 GB oder 5 GB groß sind, habe ich eine faire Frage, warum das von uns verwendete Image eine Größe hat, die keinem der Wertebereiche entspricht.
Außerdem unterstützten ältere Modelle nicht die Virtualisierungstechnologie (Virtualization Station), die ich ausprobieren werde, dh ich gehe theoretisch davon aus, dass die aktuelle Größe auch bei 1 GB (QNAP-BOOT-EN-v1.00) liegt.vmdk), wird nicht ausreichen, und deshalb hat der Hersteller eine so große 4-GB-bootfähige Festplatte für die neuen Modelle installiert. Natürlich kann ich die Größe der aktuellen bootfähigen Festplatte auf 4 GB erhöhen, aber dann stellt sich die Frage, wie kann ich die Größe der Partitionen auf dieser Festplatte richtig erhöhen, da sie jetzt so sind:

Part 1      = 64MB
Part 2      =320MB
Part 3      =320MB
Part 4/5/6 ~= 16MB
Part 7      =180MB

?


 

19 часов назад, s2k7 сказал:

2. I will show u how to add modules late by hand.

What kind modules do u need?


2) Vor allem bin ich daran interessiert, die folgenden Programme/Dienstprogramme/Tools zu installieren:

Busybox    //Die neueste Vollversion
mc         //"Midnight Commander"
fdisk
lsscsi
7zip
git

und andere, die ich bei der Verwendung des Geräts benötigen würde (vielleicht gcc, qt 4 und andere wichtige Dinge für Entwickler)
?

Link to comment
Share on other sites

Posted (edited)
9 hours ago, red7 said:

Tut mir leid, dass ich Ihre Gefühle verletzt habe, ich habe ehrlich gesagt die Erwähnung der Sprache Deutsch in der Überschrift des Forums nicht bemerkt, ich werde versuchen, beim nächsten Mal aufmerksamer zu sein (Englisch und Deutsch sind eigentlich nicht meine Muttersprache, aber ich kenne sie teilweise, und ich kenne sie nicht und verwende Online-Übersetzer).
 

In der heutigen Welt, insbesondere in der IT-Branche, spielt die Sprache an sich keine Rolle, da es immer Online-Übersetzer gibt, so dass ich persönlich kein Problem sehe, dass eine Person, die die Antwort auf eine Frage kennt, überall in ihrer Muttersprache beantwortet, denn die Hauptsache ist die Antwort auf das Problem und nicht all diese nationalistischen Ideen. Zum Beispiel sind 99% der Programmiersprachen in Englisch geschrieben, aber Menschen verschiedener Nationalitäten stören das nicht, und so kam es, dass ich dachte, wenn ein Forum der IT-Industrie gewidmet ist, lösen alle das Problem mit gemeinsamen Anstrengungen und helfen sich gegenseitig, unabhängig von der Nationalität, aber ich habe einfach keine solche klare Trennung in den Sprachen bemerkt und überhaupt zum ersten Mal in den Foren der IT-Industrie und -Entwicklung und nicht in den üblichen Foren der Chatter und Foren für Spiele.


 

 


1) Da die alten Modelle 128-512 MB groß sind und die neuen 4 GB oder 5 GB groß sind, habe ich eine faire Frage, warum das von uns verwendete Image eine Größe hat, die keinem der Wertebereiche entspricht.
Außerdem unterstützten ältere Modelle nicht die Virtualisierungstechnologie (Virtualization Station), die ich ausprobieren werde, dh ich gehe theoretisch davon aus, dass die aktuelle Größe auch bei 1 GB (QNAP-BOOT-EN-v1.00) liegt.vmdk), wird nicht ausreichen, und deshalb hat der Hersteller eine so große 4-GB-bootfähige Festplatte für die neuen Modelle installiert. Natürlich kann ich die Größe der aktuellen bootfähigen Festplatte auf 4 GB erhöhen, aber dann stellt sich die Frage, wie kann ich die Größe der Partitionen auf dieser Festplatte richtig erhöhen, da sie jetzt so sind:




Part 1      = 64MB
Part 2      =320MB
Part 3      =320MB
Part 4/5/6 ~= 16MB
Part 7      =180MB

?


 


2) Vor allem bin ich daran interessiert, die folgenden Programme/Dienstprogramme/Tools zu installieren:




Busybox    //Die neueste Vollversion
mc         //"Midnight Commander"
fdisk
lsscsi
7zip
git

und andere, die ich bei der Verwendung des Geräts benötigen würde (vielleicht gcc, qt 4 und andere wichtige Dinge für Entwickler)
?

Sie haben ein Missverständnis von QTS.
Geh einfach hin und probiere es aus.

 

1. QTS erfordert eine Bootdiskette (>1 GB) und eine Datendiskette (>50 GB).
Die Installations-ISO formatiert diese Datenträger für Sie.

 

2. Diese haben nichts mit Modulen zu tun.
Es kann nach der Installation von QTS über eine Anwendung wie Entware oder einen Docker (Ubuntun 16.04) erreicht werden.

Edited by s2k7
  • 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.   Paste as plain text instead

  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...