haydibe
-
Posts
705 -
Joined
-
Last visited
-
Days Won
35
Posts posted by haydibe
-
-
On 1/29/2022 at 10:41 AM, haydibe said:
Aus Mangel an Kernel-Sourcen für DSM7 werden die Treiber-Module nach bestem Wissen und Gewissen von pocopico mit entsprechenden vanila Kernel kompiliert.
Syno's Kernel sind ziemlich verbogen (bspw. wilde Patches und Backports die so nicht in den vanila Kerneln vorkommen), so dass Treiber-Module die mit einem vanila Kernel gebaut werden nicht immer zum Syno-Kernel passen.
Afaik gibt es mittlerweile die Kernel-Sourcen für DSM7. Ich würde davon ausgehen das pocopico die Kernel-Sourcen für den Build der Treiber-Module verwendet. Trotzdem bleibt das Problem das Syno's Kernel verbogen sind und damit gebaute Treiber trotzdem nicht richtig funktionieren.
-
1 hour ago, insp said:
und es wird immer das Modell 3615xs bei der Auswahl angezeigt. der DSassisten findet das gerät als DS3615xs aber die Iinstallation kommt mit Fehler ist ja klar
Pack das mal bitte in andere Worte... Vor allem auch in solche die ermöglichen zu verstehen was überhaupt Dein Problem ist.
Erklär mal bitte welchen Sinn es ergibt in Befehl 4 einen DS3515xs Bootloader zu bauen, aber vorher in Befehl 1 für ein anderes Model die Seriennummer generieren zu lassen? Nicht das es eine ungültige Seriennummer die Installation verhindern würde... ich würde nur gerne das warum verstehen.
-
On 3/25/2022 at 8:23 PM, Carl10 said:
tc@box:~$ sudo ./rploader.sh build denverton-7.0.1-42218
parse error: Expected separator between values at line 319, column 28
parse error: Expected separator between values at line 319, column 28
Error : Platform not found
parse error: Expected separator between values at line 319, column 28Something must be off with your user_config.json. Use "jq '.' ~/user_config.json" (of course without quotes) to see wether your json document is valid. Also you might want to generaly check if the structure is still correct (lookout for missing or missplaced comma or curly bracket character(s)?) and the values look similar to those of other platfrom versions.
Another option is to just attach your user_config.json to a post. Make sure to redact the sn and mac addresses.
Update: I should have read the thread to the end. @pocopico the sanity check is missplaced. It needs to be either within "function selectPlatform()" or after it's called the first time. Though, since it sets a global variable, I assume it's safer to place the sanity check it in the function itself.
-
1
-
-
11 hours ago, synoxpe said:
The Console button on the right as you pointed out on the screenshot seems to be the serial port output then?
Unfold the menu by clicking the down-arrow and select xterm.js to see the serial console.
-
1
-
-
Great that you found the post, Orphée! I still find it odd that > even needs to be escapped with \\, even though it shouldn't be necessary in a json value.
It should use zero offset as well, but tbh I am not sure if the offset starts at 0 or 1.
-
1
-
-
4 hours ago, Orphée said:
With Proxmox there is 2 virtual sata controller (I don't know where they are set), the LSI HBA IT card begins at /dev/sdc. I must for this set : SataPortMap=118.
I tried DiskIdxMap=100A00 but it does nothing.
So same as ESXi, with LSI card passthrough the DiskIdxMap settings is ignored.
Odd how a passthrough adapter does that. With a Q35 type PVE machine there are always 2 sata controllers connected, while all virtual disks will be attached to the second. I have no idea why the first even exists. You could use remap to straighten out the drive order, I remember it beeing discussed in this thread. the remap string requires escaping and can be used to straighten out the driver ordering.
-
1
-
-
18 hours ago, synoxpe said:
@haydibe you had inspired me to take the proxmox path 😀 and after a short lived bliss the environment has unfortunately become unusable.
Curious about your proxmox environment. Which version are you using? Can you please share the details?
I started with Proxmox 7.1-0 I think and kept them updated and am now on the latest 7.1-8. I do not have a subscription for any of my 3 nodes. Two nodes use a Xeon E1275v5 and 32gb ram, the third uses a Intel i5-9500T and 32gb ram. All nodes use a Melanox 10gbps nic. I can't say that I experience any issues at all. One of the 1275v2 Nodes has my main DSM VM with a passthough LSI adapter. Before Proxmox, the nodes were operated as vSphere Cluster with a generated serial number - while this didn't bother me in the beginning it did after a while and I was looking for an open source solution. PVE uses KVM under the hood. May cloud solutions (AWS, every OpenStack Cloud) use it to provision and run their compute instances , so it can't be that bad.. can it?
Thus said, what details are you exactly looking for?
-
23 minutes ago, Aigor said:
Is there a sort of math formula to know the meaning of these parameters?
In addition to @jarugut's post, you might want to do into this blog post: https://gugucomputing.wordpress.com/2018/11/11/experiment-on-sata_args-in-grub-cfg/
-
1
-
-
-
Es gibt etwas für 3617xs, allerdings habe ich mir das nie näher angesehen bzw. nur überflogen.
Ich wüsste jetzt auch nicht auf Anhieb wo die entsprechenden Posts dazu zu finden sind, vor allem den Post zum Thema "wie baue ich mir selber eine pat-Datei für die Update Versionen".
Diesem Forum fehlt leider eine Art persönliches Wiki/Blog, in dem man bspw. Tipps & Tricks und nützliche Links sammeln könnte und aktuell halten könnte. In so einem Bereich hätte ich solche Links festgehalten, da die Threads hier teilweise hunderte von Seiten haben, die keiner mehr wirklich durchblicken kann.
-
1
-
-
It's possible that the virtio driver is not detected by listmods now - I am not sure, as I made my first PVE installation before listmods now was even implemented. It worked like a charm without adding any additional extension.
... and it shouldn't matter if the virtio driver is not detected, unless the maintainer of the redpill-load repo you choose in your global_config.json or custom_config.json removed the virtio extension from the bundled-exts.json file.
For instance, jumkey's repos still has the virtio driver as one of the default extensions, see: https://github.com/jumkey/redpill-load/blob/develop/bundled-exts.json.
Thus said, you might want to check the repo used for the specific platform and version, then check the bundled-exts.json to verify wether virtio is still included or not. Ever maintainer is free to modify the bundles-exts.json according their needs. So better doublecheck if the virtio extensions are still present and if not, just add the extension using "ext add" yourself.
On PVE you don't need to add any extension, unless the redpill-load repo removed it from bundled-exts.json or you passthrough pci-e cards and require drivers for them to be added to the bootloader.
-
4 hours ago, alvink said:
I have also tried the various virtual adapters (Virtio, RealTek, e1000) and DS models on SATA boot.
Virtio, USB-Boot should work fine with when the vm is created from the cli with the commands I provide in my signature.
As long as the hardware is properly detected on the hypervisor level, the pysical hardware shouldn't matter. Proxmox (and every other hypervisor) emulate the same set of virtual hardware component for vm's regardless of the physical compoentnes the Proxmox server is run on.
4 hours ago, alvink said:Found Ethernet Interface : pciid 1af4d00001000 Required Extension :
No matching extensionThis is with a Virtio vnic?!
4 hours ago, alvink said:I cannot get a DHCP IP lease and thus the DiskStation cannot be found (DS918+/DS3615xs)
Are you sure you are connected to the correct bridge? Since it's working with TC, I would assume to work identicaly with DMS7. In every of my installations on three different hosts, it was always the case.
-
19 minutes ago, synoxpe said:
@haydibeDo you get the link speed displayed on DSM?
Neither is the link speed shown, nor is it possible to select a mtu > 1500.
-
4 hours ago, synoxpe said:
Thoughts? Maybe master @haydibe
The output difference is because of the `-f G` parameter.
What I see on my systems:
me@dsm1:~$ iperf3 -c 192.168.200.11 # DSM -> PVE Connecting to host 192.168.200.11, port 5201 [ 5] local 192.168.200.18 port 37910 connected to 192.168.200.11 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 3.96 GBytes 34.0 Gbits/sec 0 2.27 MBytes [ 5] 1.00-2.00 sec 3.93 GBytes 33.8 Gbits/sec 0 2.45 MBytes [ 5] 2.00-3.00 sec 3.91 GBytes 33.6 Gbits/sec 0 2.58 MBytes [ 5] 3.00-4.00 sec 3.70 GBytes 31.8 Gbits/sec 0 3.04 MBytes [ 5] 4.00-5.00 sec 3.66 GBytes 31.4 Gbits/sec 0 3.04 MBytes [ 5] 5.00-6.00 sec 3.90 GBytes 33.5 Gbits/sec 0 3.04 MBytes [ 5] 6.00-7.00 sec 3.90 GBytes 33.5 Gbits/sec 0 3.04 MBytes [ 5] 7.00-8.00 sec 3.49 GBytes 30.0 Gbits/sec 0 3.04 MBytes [ 5] 8.00-9.00 sec 3.66 GBytes 31.4 Gbits/sec 0 3.04 MBytes [ 5] 9.00-10.00 sec 3.76 GBytes 32.3 Gbits/sec 0 3.04 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 37.9 GBytes 32.5 Gbits/sec 0 sender [ 5] 0.00-10.04 sec 37.9 GBytes 32.4 Gbits/sec receiver iperf Done. me@dsm1:~$ iperf3 -c 192.168.200.11 -R # reverse sender/receiver role, PVE -> DSM Connecting to host 192.168.200.11, port 5201 Reverse mode, remote host 192.168.200.11 is sending [ 5] local 192.168.200.18 port 37914 connected to 192.168.200.11 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 2.33 GBytes 20.0 Gbits/sec [ 5] 1.00-2.00 sec 2.36 GBytes 20.3 Gbits/sec [ 5] 2.00-3.00 sec 2.45 GBytes 21.0 Gbits/sec [ 5] 3.00-4.00 sec 2.51 GBytes 21.6 Gbits/sec [ 5] 4.00-5.00 sec 2.35 GBytes 20.2 Gbits/sec [ 5] 5.00-6.00 sec 2.28 GBytes 19.6 Gbits/sec [ 5] 6.00-7.00 sec 2.38 GBytes 20.5 Gbits/sec [ 5] 7.00-8.00 sec 2.28 GBytes 19.6 Gbits/sec [ 5] 8.00-9.00 sec 2.43 GBytes 20.9 Gbits/sec [ 5] 9.00-10.00 sec 2.45 GBytes 21.1 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.04 sec 23.8 GBytes 20.4 Gbits/sec 698 sender [ 5] 0.00-10.00 sec 23.8 GBytes 20.5 Gbits/sec receiver iperf Done.From a 2nd PVE host transfer speeds to the dsm vm are ~ 9.3 Gbps in both directions.
I am not realy sure what causes the retransmits, but it appears they are more likely to happen from pve to dsm, then from dsm to pve.
-
8 hours ago, blu001 said:
Is there any known problem with Microserver gen8 embedded ethernet adapter?
This question is only relevant for the hypervisor. The guest vm uses vnics provided by the hypervervisor, unless a physical nic is used in passthrough mode. Redpill works ootb with with a Virtio vnic.
Since you are able to access tc over the network, it is safe to assume that the ethernet adapter works properly on the hypervisor level, otherwise it would be impossible to access tc.
-
9 hours ago, Redjewel said:
Was hat es eigentlich mit den Modulen
Apollolake 4.4.180 (DSM7) modules : https://github.com/pocopico/4.4.180plus-modules Apollolake 4.4.59 (DSM6) modules : https://github.com/pocopico/4.4.59plus-modules Bromollow 3.10.108 (DSM7) modules : https://github.com/pocopico/3.10.108-modules Bromollow 3.10.105 (DSM6) modules : https://github.com/pocopico/3.10.105-modulesvon Picopoco auf sich?
Durch die Kernel Module werden die Geräte-Treiber bereitgestellt, die nicht schon in den Kernel fest eingebaken sind.
9 hours ago, Redjewel said:tc@box:~$ lsscsi -Hv [0] ahci dir: /sys/class/scsi_host//host0 device dir: /sys/devices/pci0000:00/0000:00:13.0/ata1/host0 [1] ahci dir: /sys/class/scsi_host//host1 device dir: /sys/devices/pci0000:00/0000:00:13.0/ata2/host1 [2] usb-storage dir: /sys/class/scsi_host//host2 device dir: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host2
In der Tat 1 Controller mit 2 Ports. Das ist wieder einer dieser "schrägen" Fälle. AHCI braucht keine zusätzlichen Kernel Module.
Mit SataPortMap wird definiert wieviele Ports die Controller haben - das sollte erstmal nichts mit der Anzahl der angeschlossenen Festplatten zu tun haben.
In meinen Proxmox Installationen habe ich zwei Controller a 6 Ports in meinem VMs und kann unabhängig von der Anzahl angeschlossener Platten den Wert SataPortMap=66 verwenden.
Ich bin gespannt ob es bei dir jemals mit 2 Platten klappen wird... In die Tüte gesponnen, ich könnte mir vorstellen, dass das Weglassen von SataPortMap vielleicht funktionieren könnte. Ich hab "leider" keine Systeme die das Problem haben, so dass ich nicht überprüfen kann, ob es so überhaupt funktionieren würde.
-
21 hours ago, Redjewel said:
DSM zäher ???
Ich kann mir kaum vorstellen das die Oberfläche zügig ist. Letzendlich ist das aber auch egal, solange man die Kiste nur als Datentopf verwenden will und die Datenrate passt.
Geräte für die es keine Treiber gibt laufen einfach "nur nicht" - solange es nicht Netzwerkkarte, Storage und ggf. USB-Treiber betrifft ist alles andere eigentlich kein Partybreaker.
Damit siehst du zumindest welchen Kernel-Treiber Tinycore verwendet: lspci -nnqk
Dein VID:PID kommt durch "./rploader.sh identifyusb now" und deine Sata Konfiguration durch "./rploader.sh satamap now"?
Ansonsten find ich "lsscsi -Hv" noch interessant, ABER: manchmal führen selbst vermeintlich richtige Einstellungen zu Probleme die nicht so wirklich zu verstehen sind. Der Original-Post ist voll von solchen Posts, wo Leute dann plötzliche anfangen irgendwelchen willkürlichen Kram auszuprobieren, nur weil sie gesehen haben das andere (mit völlig anderen Systemen) mit den Werten Erfolg hatten..
-
57 minutes ago, Redjewel said:
Als Modell wird mir DS918+ und als CPU INTEL Celeron J3455 angezeig
Dann hast Du gerade DS918+ installiert. Die CPU und die Details dazu sind fest hinterlegte Zeichenketten.. da wird nichts dynamischen von der echten CPU ausgelesen. Das ist ootb normal.
57 minutes ago, Redjewel said:Habe einmal die Auflistung gemacht, da ich immer wieder von "Treiber von Hand nachinstallieren" gelesen habe.
Meinst Du damit die Auflistung deiner Schnittstellen je Interface? Hier hilft es nur die exakte Gerätebezeichnung und ihre entsprechende VID:PID zu kennen.
57 minutes ago, Redjewel said:Frage: Ist es mit meiner CPU überhaupt möglich 7.x aufzuspielen?
Ich würde empfehlen mit pocopico's tinycore Installer zu arbeiten, da der viele Treiber erkennen kann.
Was die Variante des DS-Models angeht ist man mit Bromolow auf der sichereren Seite. Zumal dort eine GPU der 7ten Generation verbaut ist und die Funktionalität für hardwarebeschleunigtes Video-Encoding/-Decoding nicht besitzt. Apollolake hat eine GPU der 9ten Generation, die entsprechende Funktionalität mitbringt.
Die Pentium N3540 CPU hat einen Passmark von 1217, die Celeron J3455 CPU hat einen Passmark von 2219. Das DSM etwas zäher funktioniert wirst Du ja sicherlich auch schon unter DSM6.2 gewohnt gewesen sein. Dein System sollte nicht weniger als 2GB RAM haben, idealerweise >= 3GB.
Ich würde dir empfehlen eine Testinstallation zu machen, bei der Du Deine alten Platten abklemmst und versuchsweise eine alte Platte mit mehr als 10GB anklemmst und schaust ob alles funktioniert (Installation zuende bringen und Volume anlegen!). Erst wenn das sauber durchläuft würde ich empfehlen eine Migration mit den aktuell unter 6.2.x verwendeten Platten zu machen. Wenn schon bei dem Versuch etwas schiefgeht, dann kann man sich die Rückwärtsmigration zu 6.2.x sparen - die wäre nur mit Bastelei zu bewerkstelligen.
-
4 hours ago, recoco said:
I'm using vm in Proxmox. NIC is e1000.
If you deperatly want to use an intel vnic, you will have to use the e1000e, which can not be configured from the ui.
If you want to walk down that road, you will have to dig deeper into proxmox or the vm configuration (either from the serial console or using ssh):
- either by manualy adding the nic in the "args" value of the vm config - this one is cumbursom to archive
- by patching some promox files to "unlock" the e1000e in the ui - this one is not recommended as any PVE update will undo the changes.
Google consulting should provide plenty of examples on how its done - the forum search might reveil hits about this as well.
Though, why are you not just using virtio? I am using it on Proxmox 7.x with bromolow/apollolake DSM7.x -> works like a charme.
-
3 hours ago, synoxpe said:
You could have setup the vm with way less effort...
If you use the command sequence from this post, the tinycore image would be pulled, a vm using the tinycore image as usb boot would be created + a 100gb disk + serial ports for boot logs. This vm can be booted right away without changes - or further customized, like adding more disk for instance. Just make sure to not mess arround with any other parameter that you have seen in any random tutorial... they might break the perfectly fine pre-configuration.
Once tinycore is booted, you run the usual commands to detect the sata settings and take care of the serial number + network.
Before you run the actual build you just need to configure the SataPortMap + DiskIdxMap in the user_config.json according the settings from this post and your setup is complete - of course having additional controllers added as passthrough will require different SataPortMap and DiskIdxMap, but for a default vm "this is the way!"
If at one point you mess up the tinycore image and want to start from scratch, you just have to power off the vm, re-execute this command sequenc
id=930 gzip --decompress /var/lib/vz/images/${id}/tinycore-redpill.img.gz --keepStart the vm again and you will start with a clean slate, without having to worry about anything else. There is no need to remove the vm, unless you want to get rid of the data on the attached 100gb data disk as well...
It doesn't get less painfree than that
-
1
-
-
Normaly this should be fixable from the storage manager overview. It should display a banner regarding the failed system partition and provide a "repair" link, that actualy initiates the repair. A couple of seconds later the system should be healthy again.
I had it a couple of times with DSM6 and the repair always fixed it.
Your data is on /dev/md5. As long as it's working, everything else can be fixed without complication. Even problems on /dev/md5 usualy can be fixed manualy and do not neceissarily have to result in full dataloss.
-
Aus Mangel an Kernel-Sourcen für DSM7 werden die Treiber-Module nach bestem Wissen und Gewissen von pocopico mit entsprechenden vanila Kernel kompiliert.
Syno's Kernel sind ziemlich verbogen (bspw. wilde Patches und Backports die so nicht in den vanila Kerneln vorkommen), so dass Treiber-Module die mit einem vanila Kernel gebaut werden nicht immer zum Syno-Kernel passen.
-
2
-
-
1 hour ago, ikky_phoenix said:
"sata_remap": "24\\>2:25\\>3:26\\>10:27\\>11:28\\>12:29\\>13"
This realy works? So it just needed some good old escaping? Thanks for sharing!
-
4 hours ago, jarugut said:
I've executed all that you recommend, the test executed correctly.
Seems okay to me. Even though I forget to add "build" in the rploader command.
On a 2nd though the jq error was merly cosmetic, as the values it failed to parse aren't used anywhere. the existance of "add_extensions": [] does not influence the build.
Thats why your last and previous build had the same result...
when I try to passthrough the IGD to dsm . it startup with kernel panic.
in Developer Discussion Room
Posted
What is an IGD?
For PCI-E passthrough, make sure to follow this guide https://pve.proxmox.com/wiki/PCI(e)_Passthrough and configure your vm to use the q35 chipset.