Jump to content
XPEnology Community

Automated RedPill Loader (ARPL)


fbelavenuto

Recommended Posts

@fbelavenuto Got the new HBA card and finally in DSM and detecting all disks! Seriously, is there any way to donate for this project? 

The only question I have left, is that I see this message over and over in the serial output once booted in DSM. I am guessing that it is detecting the USB that it's booting off of? Is this normal and can be ignored?

 

Spoiler


[  352.200535] usb-storage 2-2:1.0: USB Mass Storage device detected
[  352.201336] scsi host262: usb-storage 2-2:1.0
[  353.052394] usb 2-1: reset SuperSpeed USB device number 15 using xhci_hcd
[  353.066860] usb 2-1: device firmware changed
[  353.067313] usb usb2-port1: logical disconnect on port 1 []
[  353.089087] usb 2-1: USB disconnect, device number 15
[  353.385112] usb 2-1: new SuperSpeed USB device number 17 using xhci_hcd
[  354.563191] xhci_hcd 0000:01:1b.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  354.686282] usb 2-2: reset SuperSpeed USB device number 16 using xhci_hcd
[  354.700684] usb 2-2: device firmware changed
[  354.700933] usb usb2-port2: logical disconnect on port 2 [usb-storage]
[  359.564207] usb 2-1: unable to read config index 0 descriptor/start: -110
[  359.564854] usb 2-1: can't read configurations, error -110
[  359.860271] usb 2-1: new SuperSpeed USB device number 18 using xhci_hcd
[  359.877443] usb-storage 2-1:1.0: USB Mass Storage device detected
[  359.878224] scsi host263: usb-storage 2-1:1.0
[  359.878595] usb 2-2: USB disconnect, device number 16
[  360.152134] usb 2-2: new SuperSpeed USB device number 19 using xhci_hcd
[  360.168823] drivers/usb/core/hub.c (2943) Same device found. Change serial to 09GZW5GW22S0HUR0 
[  360.192330] usb-storage 2-2:1.0: USB Mass Storage device detected
[  360.193050] scsi host264: usb-storage 2-2:1.0
[  361.187369] usb 2-1: reset SuperSpeed USB device number 18 using xhci_hcd
[  361.200407] usb 2-1: device firmware changed
[  361.377540] usb usb2-port1: logical disconnect on port 1 [usb-storage]
[  361.400087] usb 2-1: USB disconnect, device number 18
[  361.500167] usb 2-2: reset SuperSpeed USB device number 19 using xhci_hcd
[  362.222776] xhci_hcd 0000:01:1b.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  362.345276] usb 2-1: new SuperSpeed USB device number 20 using xhci_hcd
[  362.363099] usb-storage 2-1:1.0: USB Mass Storage device detected
[  362.363794] scsi host265: usb-storage 2-1:1.0
[  363.625999] scsi 265:0:0:0: Direct-Access     JetFlash Transcend 8GB            1100 PQ: 0 ANSI: 6
[  363.626751] sd 265:0:0:0: Attached scsi generic sg25 type 0
[  363.628463] sd 265:0:0:0: [synoboot] 14761984 512-byte logical blocks: (7.56 GB/7.04 GiB)
[  363.630143] sd 265:0:0:0: [synoboot] Write Protect is off
[  363.630506] sd 265:0:0:0: [synoboot] Mode Sense: 43 00 00 00
[  363.631895] sd 265:0:0:0: [synoboot] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  363.639189]  synoboot: synoboot1 synoboot2 synoboot3
[  363.643181] sd 265:0:0:0: [synoboot] Attached SCSI removable disk
[  367.223147] usb 2-2: device firmware changed
[  367.223488] usb usb2-port2: logical disconnect on port 2 [usb-storage]
[  367.245133] usb 2-2: USB disconnect, device number 19
[  367.628154] usb 2-2: new SuperSpeed USB device number 21 using xhci_hcd
[  367.645415] drivers/usb/core/hub.c (2943) Same device found. Change serial to 09GZW5GW22S0HUR0 
[  367.668512] usb-storage 2-2:1.0: USB Mass Storage device detected
[  367.669286] scsi host266: usb-storage 2-2:1.0
[  368.388236] usb 2-1: reset SuperSpeed USB device number 20 using xhci_hcd
[  368.401460] usb 2-1: device firmware changed
[  368.401706] usb usb2-port1: logical disconnect on port 1 []
[  368.423202] usb 2-1: USB disconnect, device number 20
[  368.721132] usb 2-1: new SuperSpeed USB device number 22 using xhci_hcd
[  369.880411] xhci_hcd 0000:01:1b.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  370.002213] usb 2-2: reset SuperSpeed USB device number 21 using xhci_hcd
[  370.016589] usb 2-2: device firmware changed
[  370.016836] usb usb2-port2: logical disconnect on port 2 [@usb-storage]
[  374.882301] usb 2-1: unable to read config index 0 descriptor/start: -110
[  374.882823] usb 2-1: can't read configurations, error -110
[  375.181179] usb 2-1: new SuperSpeed USB device number 23 using xhci_hcd
[  375.198228] usb-storage 2-1:1.0: USB Mass Storage device detected
[  375.198836] scsi host267: usb-storage 2-1:1.0
[  375.199235] usb 2-2: USB disconnect, device number 21
[  375.472129] usb 2-2: new SuperSpeed USB device number 24 using xhci_hcd
[  375.488813] drivers/usb/core/hub.c (2943) Same device found. Change serial to 09GZW5GW22S0HUR0 
[  375.504326] usb-storage 2-2:1.0: USB Mass Storage device detected
[  375.505129] scsi host268: usb-storage 2-2:1.0
[  376.507338] usb 2-1: reset SuperSpeed USB device number 23 using xhci_hcd
[  376.520996] usb 2-1: device firmware changed
[  376.697233] usb usb2-port1: logical disconnect on port 1 [@usb-storage]
[  376.718089] usb 2-1: USB disconnect, device number 23
[  376.820198] usb 2-2: reset SuperSpeed USB device number 24 using xhci_hcd
[  377.510663] xhci_hcd 0000:01:1b.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  377.633256] usb 2-1: new SuperSpeed USB device number 25 using xhci_hcd
[  377.651413] usb-storage 2-1:1.0: USB Mass Storage device detected
[  377.652399] scsi host269: usb-storage 2-1:1.0
[  378.914440] scsi 269:0:0:0: Direct-Access     JetFlash Transcend 8GB            1100 PQ: 0 ANSI: 6
[  378.915275] sd 269:0:0:0: Attached scsi generic sg25 type 0
[  378.916659] sd 269:0:0:0: [synoboot] 14761984 512-byte logical blocks: (7.56 GB/7.04 GiB)
[  378.918326] sd 269:0:0:0: [synoboot] Write Protect is off
[  378.918905] sd 269:0:0:0: [synoboot] Mode Sense: 43 00 00 00
[  378.920537] sd 269:0:0:0: [synoboot] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  378.927807]  synoboot: synoboot1 synoboot2 synoboot3
[  378.931807] sd 269:0:0:0: [synoboot] Attached SCSI removable disk
[  382.514203] usb 2-2: device firmware changed
[  382.514612] usb usb2-port2: logical disconnect on port 2 [@usb-storage]
[  382.536249] usb 2-2: USB disconnect, device number 24
[  382.920157] usb 2-2: new SuperSpeed USB device number 26 using xhci_hcd
[  382.937020] drivers/usb/core/hub.c (2943) Same device found. Change serial to 09GZW5GW22S0HUR0 
[  382.952533] usb-storage 2-2:1.0: USB Mass Storage device detected
[  382.953323] scsi host270: usb-storage 2-2:1.0
[  383.760343] usb 2-1: reset SuperSpeed USB device number 25 using xhci_hcd
[  383.773466] usb 2-1: device firmware changed
[  383.773776] usb usb2-port1: logical disconnect on port 1 []
[  383.795191] usb 2-1: USB disconnect, device number 25
[  384.092151] usb 2-1: new SuperSpeed USB device number 27 using xhci_hcd
[  385.252015] xhci_hcd 0000:01:1b.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  385.374244] usb 2-2: reset SuperSpeed USB device number 26 using xhci_hcd
[  385.388694] usb 2-2: device firmware changed
[  385.388943] usb usb2-port2: logical disconnect on port 2 [Susb-storage]
[  390.254287] usb 2-1: unable to read config index 0 descriptor/start: -110
[  390.254782] usb 2-1: can't read configurations, error -110
[  390.553261] usb 2-1: new SuperSpeed USB device number 28 using xhci_hcd
[  390.570987] usb-storage 2-1:1.0: USB Mass Storage device detected
[  390.572184] scsi host271: usb-storage 2-1:1.0
[  390.572635] usb 2-2: USB disconnect, device number 26
[  390.828144] usb 2-2: new SuperSpeed USB device number 29 using xhci_hcd
[  390.844819] drivers/usb/core/hub.c (2943) Same device found. Change serial to 09GZW5GW22S0HUR0 
[  390.864267] usb-storage 2-2:1.0: USB Mass Storage device detected
[  390.864954] scsi host272: usb-storage 2-2:1.0
[  391.879319] usb 2-1: reset SuperSpeed USB device number 28 using xhci_hcd
[  391.892388] usb 2-1: device firmware changed
[  392.069112] usb usb2-port1: logical disconnect on port 1 [@usb-storage]
[  392.090258] usb 2-1: USB disconnect, device number 28
[  392.191171] usb 2-2: reset SuperSpeed USB device number 29 using xhci_hcd
[  392.867626] xhci_hcd 0000:01:1b.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  392.989174] usb 2-1: new SuperSpeed USB device number 30 using xhci_hcd
[  393.006632] usb-storage 2-1:1.0: USB Mass Storage device detected
[  393.007364] scsi host273: usb-storage 2-1:1.0
[  394.268059] scsi 273:0:0:0: Direct-Access     JetFlash Transcend 8GB            1100 PQ: 0 ANSI: 6
[  394.268930] sd 273:0:0:0: Attached scsi generic sg25 type 0
[  394.270383] sd 273:0:0:0: [synoboot] 14761984 512-byte logical blocks: (7.56 GB/7.04 GiB)
[  394.271934] sd 273:0:0:0: [synoboot] Write Protect is off
[  394.272367] sd 273:0:0:0: [synoboot] Mode Sense: 43 00 00 00
[  394.273643] sd 273:0:0:0: [synoboot] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  394.280699]  synoboot: synoboot1 synoboot2 synoboot3
[  394.284560] sd 273:0:0:0: [synoboot] Attached SCSI removable disk
[  397.867480] usb 2-2: device firmware changed
[  397.867812] usb usb2-port2: logical disconnect on port 2 []
[  397.889116] usb 2-2: USB disconnect, device number 29
[  398.272163] usb 2-2: new SuperSpeed USB device number 31 using xhci_hcd
[  398.288906] drivers/usb/core/hub.c (2943) Same device found. Change serial to 09GZW5GW22S0HUR0 

 

And this keeps popping up in DSM: 

image.png.c22e5a58503325dd7245720f3e9d7634.png

Edited by jrac86
Link to comment
Share on other sites

Hi do you known please if these modules are already there or not yet implemented? I am not able to see DS3622xs+ with network driver VMXNET3 but with driver E1000e in esxi its not a problem.

 

Do you plan to support these modules in near future?
Extension Name: "vmw_pvscsi" Description : "Adds VMware PVSCSI driver Support"
Extension Name: "vmxnet3" Description : "Adds VMware vmxnet3 virtual NIC driver Support"

 

Thanks for reply and your work.

Link to comment
Share on other sites

38 minutes ago, jrac86 said:

@fbelavenuto Got the new HBA card and finally in DSM and detecting all disks! Seriously, is there any way to donate for this project? 

The only question I have left, is that I see this message over and over in the serial output once booted in DSM. I am guessing that it is detecting the USB that it's booting off of? Is this normal and can be ignored?

 

  Serial (Reveal hidden contents)


[  352.200535] usb-storage 2-2:1.0: USB Mass Storage device detected
[  352.201336] scsi host262: usb-storage 2-2:1.0
[  353.052394] usb 2-1: reset SuperSpeed USB device number 15 using xhci_hcd
[  353.066860] usb 2-1: device firmware changed
[  353.067313] usb usb2-port1: logical disconnect on port 1 []
[  353.089087] usb 2-1: USB disconnect, device number 15
[  353.385112] usb 2-1: new SuperSpeed USB device number 17 using xhci_hcd
[  354.563191] xhci_hcd 0000:01:1b.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  354.686282] usb 2-2: reset SuperSpeed USB device number 16 using xhci_hcd
[  354.700684] usb 2-2: device firmware changed
[  354.700933] usb usb2-port2: logical disconnect on port 2 [usb-storage]
[  359.564207] usb 2-1: unable to read config index 0 descriptor/start: -110
[  359.564854] usb 2-1: can't read configurations, error -110
[  359.860271] usb 2-1: new SuperSpeed USB device number 18 using xhci_hcd
[  359.877443] usb-storage 2-1:1.0: USB Mass Storage device detected
[  359.878224] scsi host263: usb-storage 2-1:1.0
[  359.878595] usb 2-2: USB disconnect, device number 16
[  360.152134] usb 2-2: new SuperSpeed USB device number 19 using xhci_hcd
[  360.168823] drivers/usb/core/hub.c (2943) Same device found. Change serial to 09GZW5GW22S0HUR0 
[  360.192330] usb-storage 2-2:1.0: USB Mass Storage device detected
[  360.193050] scsi host264: usb-storage 2-2:1.0
[  361.187369] usb 2-1: reset SuperSpeed USB device number 18 using xhci_hcd
[  361.200407] usb 2-1: device firmware changed
[  361.377540] usb usb2-port1: logical disconnect on port 1 [usb-storage]
[  361.400087] usb 2-1: USB disconnect, device number 18
[  361.500167] usb 2-2: reset SuperSpeed USB device number 19 using xhci_hcd
[  362.222776] xhci_hcd 0000:01:1b.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  362.345276] usb 2-1: new SuperSpeed USB device number 20 using xhci_hcd
[  362.363099] usb-storage 2-1:1.0: USB Mass Storage device detected
[  362.363794] scsi host265: usb-storage 2-1:1.0
[  363.625999] scsi 265:0:0:0: Direct-Access     JetFlash Transcend 8GB            1100 PQ: 0 ANSI: 6
[  363.626751] sd 265:0:0:0: Attached scsi generic sg25 type 0
[  363.628463] sd 265:0:0:0: [synoboot] 14761984 512-byte logical blocks: (7.56 GB/7.04 GiB)
[  363.630143] sd 265:0:0:0: [synoboot] Write Protect is off
[  363.630506] sd 265:0:0:0: [synoboot] Mode Sense: 43 00 00 00
[  363.631895] sd 265:0:0:0: [synoboot] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  363.639189]  synoboot: synoboot1 synoboot2 synoboot3
[  363.643181] sd 265:0:0:0: [synoboot] Attached SCSI removable disk
[  367.223147] usb 2-2: device firmware changed
[  367.223488] usb usb2-port2: logical disconnect on port 2 [usb-storage]
[  367.245133] usb 2-2: USB disconnect, device number 19
[  367.628154] usb 2-2: new SuperSpeed USB device number 21 using xhci_hcd
[  367.645415] drivers/usb/core/hub.c (2943) Same device found. Change serial to 09GZW5GW22S0HUR0 
[  367.668512] usb-storage 2-2:1.0: USB Mass Storage device detected
[  367.669286] scsi host266: usb-storage 2-2:1.0
[  368.388236] usb 2-1: reset SuperSpeed USB device number 20 using xhci_hcd
[  368.401460] usb 2-1: device firmware changed
[  368.401706] usb usb2-port1: logical disconnect on port 1 []
[  368.423202] usb 2-1: USB disconnect, device number 20
[  368.721132] usb 2-1: new SuperSpeed USB device number 22 using xhci_hcd
[  369.880411] xhci_hcd 0000:01:1b.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  370.002213] usb 2-2: reset SuperSpeed USB device number 21 using xhci_hcd
[  370.016589] usb 2-2: device firmware changed
[  370.016836] usb usb2-port2: logical disconnect on port 2 [@usb-storage]
[  374.882301] usb 2-1: unable to read config index 0 descriptor/start: -110
[  374.882823] usb 2-1: can't read configurations, error -110
[  375.181179] usb 2-1: new SuperSpeed USB device number 23 using xhci_hcd
[  375.198228] usb-storage 2-1:1.0: USB Mass Storage device detected
[  375.198836] scsi host267: usb-storage 2-1:1.0
[  375.199235] usb 2-2: USB disconnect, device number 21
[  375.472129] usb 2-2: new SuperSpeed USB device number 24 using xhci_hcd
[  375.488813] drivers/usb/core/hub.c (2943) Same device found. Change serial to 09GZW5GW22S0HUR0 
[  375.504326] usb-storage 2-2:1.0: USB Mass Storage device detected
[  375.505129] scsi host268: usb-storage 2-2:1.0
[  376.507338] usb 2-1: reset SuperSpeed USB device number 23 using xhci_hcd
[  376.520996] usb 2-1: device firmware changed
[  376.697233] usb usb2-port1: logical disconnect on port 1 [@usb-storage]
[  376.718089] usb 2-1: USB disconnect, device number 23
[  376.820198] usb 2-2: reset SuperSpeed USB device number 24 using xhci_hcd
[  377.510663] xhci_hcd 0000:01:1b.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  377.633256] usb 2-1: new SuperSpeed USB device number 25 using xhci_hcd
[  377.651413] usb-storage 2-1:1.0: USB Mass Storage device detected
[  377.652399] scsi host269: usb-storage 2-1:1.0
[  378.914440] scsi 269:0:0:0: Direct-Access     JetFlash Transcend 8GB            1100 PQ: 0 ANSI: 6
[  378.915275] sd 269:0:0:0: Attached scsi generic sg25 type 0
[  378.916659] sd 269:0:0:0: [synoboot] 14761984 512-byte logical blocks: (7.56 GB/7.04 GiB)
[  378.918326] sd 269:0:0:0: [synoboot] Write Protect is off
[  378.918905] sd 269:0:0:0: [synoboot] Mode Sense: 43 00 00 00
[  378.920537] sd 269:0:0:0: [synoboot] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  378.927807]  synoboot: synoboot1 synoboot2 synoboot3
[  378.931807] sd 269:0:0:0: [synoboot] Attached SCSI removable disk
[  382.514203] usb 2-2: device firmware changed
[  382.514612] usb usb2-port2: logical disconnect on port 2 [@usb-storage]
[  382.536249] usb 2-2: USB disconnect, device number 24
[  382.920157] usb 2-2: new SuperSpeed USB device number 26 using xhci_hcd
[  382.937020] drivers/usb/core/hub.c (2943) Same device found. Change serial to 09GZW5GW22S0HUR0 
[  382.952533] usb-storage 2-2:1.0: USB Mass Storage device detected
[  382.953323] scsi host270: usb-storage 2-2:1.0
[  383.760343] usb 2-1: reset SuperSpeed USB device number 25 using xhci_hcd
[  383.773466] usb 2-1: device firmware changed
[  383.773776] usb usb2-port1: logical disconnect on port 1 []
[  383.795191] usb 2-1: USB disconnect, device number 25
[  384.092151] usb 2-1: new SuperSpeed USB device number 27 using xhci_hcd
[  385.252015] xhci_hcd 0000:01:1b.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  385.374244] usb 2-2: reset SuperSpeed USB device number 26 using xhci_hcd
[  385.388694] usb 2-2: device firmware changed
[  385.388943] usb usb2-port2: logical disconnect on port 2 [Susb-storage]
[  390.254287] usb 2-1: unable to read config index 0 descriptor/start: -110
[  390.254782] usb 2-1: can't read configurations, error -110
[  390.553261] usb 2-1: new SuperSpeed USB device number 28 using xhci_hcd
[  390.570987] usb-storage 2-1:1.0: USB Mass Storage device detected
[  390.572184] scsi host271: usb-storage 2-1:1.0
[  390.572635] usb 2-2: USB disconnect, device number 26
[  390.828144] usb 2-2: new SuperSpeed USB device number 29 using xhci_hcd
[  390.844819] drivers/usb/core/hub.c (2943) Same device found. Change serial to 09GZW5GW22S0HUR0 
[  390.864267] usb-storage 2-2:1.0: USB Mass Storage device detected
[  390.864954] scsi host272: usb-storage 2-2:1.0
[  391.879319] usb 2-1: reset SuperSpeed USB device number 28 using xhci_hcd
[  391.892388] usb 2-1: device firmware changed
[  392.069112] usb usb2-port1: logical disconnect on port 1 [@usb-storage]
[  392.090258] usb 2-1: USB disconnect, device number 28
[  392.191171] usb 2-2: reset SuperSpeed USB device number 29 using xhci_hcd
[  392.867626] xhci_hcd 0000:01:1b.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  392.989174] usb 2-1: new SuperSpeed USB device number 30 using xhci_hcd
[  393.006632] usb-storage 2-1:1.0: USB Mass Storage device detected
[  393.007364] scsi host273: usb-storage 2-1:1.0
[  394.268059] scsi 273:0:0:0: Direct-Access     JetFlash Transcend 8GB            1100 PQ: 0 ANSI: 6
[  394.268930] sd 273:0:0:0: Attached scsi generic sg25 type 0
[  394.270383] sd 273:0:0:0: [synoboot] 14761984 512-byte logical blocks: (7.56 GB/7.04 GiB)
[  394.271934] sd 273:0:0:0: [synoboot] Write Protect is off
[  394.272367] sd 273:0:0:0: [synoboot] Mode Sense: 43 00 00 00
[  394.273643] sd 273:0:0:0: [synoboot] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  394.280699]  synoboot: synoboot1 synoboot2 synoboot3
[  394.284560] sd 273:0:0:0: [synoboot] Attached SCSI removable disk
[  397.867480] usb 2-2: device firmware changed
[  397.867812] usb usb2-port2: logical disconnect on port 2 []
[  397.889116] usb 2-2: USB disconnect, device number 29
[  398.272163] usb 2-2: new SuperSpeed USB device number 31 using xhci_hcd
[  398.288906] drivers/usb/core/hub.c (2943) Same device found. Change serial to 09GZW5GW22S0HUR0 

 

And this keeps popping up in DSM: 

image.png.c22e5a58503325dd7245720f3e9d7634.png

 

Very good!!!!! I thank you for donations, my paypal: belavenuto@gmail.com

This problem is with the loader flash drive! Please test on another USB port on your PC.

 

Link to comment
Share on other sites

7 minutes ago, Hydrael said:

Hi do you known please if these modules are already there or not yet implemented? I am not able to see DS3622xs+ with network driver VMXNET3 but with driver E1000e in esxi its not a problem.

 

Do you plan to support these modules in near future?
Extension Name: "vmw_pvscsi" Description : "Adds VMware PVSCSI driver Support"
Extension Name: "vmxnet3" Description : "Adds VMware vmxnet3 virtual NIC driver Support"

 

Thanks for reply and your work.

Hello, these modules already exist, they should work (be loaded automatically)!
Could you send the serial log?

 

Link to comment
Share on other sites

11 minutes ago, fbelavenuto said:

 

Very good!!!!! I thank you for donations, my paypal: belavenuto@gmail.com

This problem is with the loader flash drive! Please test on another USB port on your PC.

 

Donation sent! Will try a new usb port and report back

  • Thanks 1
Link to comment
Share on other sites

So here is my question, I build a loader months ago using rploader for my bare metal  Supermicro X10SDV-6C+-TLN4F mobo which has integrated 10gb ports everything work , also using a LSI HBA card , no issues running DSM 7.0.1-42218

 

Everything I have tried since with the new loaders either doesn't recognize the HBA card or the network card

 

How did we digress to this state?

 

I am by no means complaining, but if it worked back then why is so hard to get it to work now?

 

I'm also running a vm on unraid using the same img , something I'm yet to accomplish with the new stuff

 

 

 

 

Link to comment
Share on other sites

5 hours ago, fbelavenuto said:

 

Very good!!!!! I thank you for donations, my paypal: belavenuto@gmail.com

This problem is with the loader flash drive! Please test on another USB port on your PC.

 

All working now. Thanks again for all the assistance!

  • Thanks 1
Link to comment
Share on other sites

1 hour ago, NooL said:

@fbelavenuto Any chance you have a guide on how to build a system using this on Proxmox? :) 

 

I built mine on proxmox... I don't have a guide, but can try to assist. Doing most of this from memory since my DSM array is being built.

 

I created a usb boot drive using balena etcher and the arpl .img file. For the VM, leave the machine as 1440fx (if you pick q35, it will create dummy controllers which for me was making the setup more complicated). I used the VirtIO for network and removed both the vm disk and cd drive. Also attach a serial socket - this will allow you to see the output during the DSM boot process and can report issues here with the output. Then I added the usb to the vm and set that as the boot drive. If you have a disk shelf then you will need to passthrough the HBA card (LSI 9200-8e is what I used). If you just have drives attached to our motherboard, you can passthrough the individual sata drives (proxmox only allows 6 sata drives to be passed through).

 

If you are passing through a hba card, you need to follow the following guide: https://pve.proxmox.com/wiki/PCI(e)_Passthrough. The other thing to know, is that passing through hardware is done in groups (called iommu). For example, if your pcie slot is in the same iommu group as a usb controller, you will passthrough both to the vm. This may be a deal breaker depending on what hardware is in your iommu groups. The guide above explains this as well as this (it is for a gpu passthrough, but similar principles) https://www.reddit.com/r/Proxmox/comments/mib3u6/a_guide_to_how_i_got_nvidia_gpu_passthrough_to_a/

 

 

Once you do that, you can start the VM. You will need to go to the web gui with the ip and port 7681 (http://xx.xx.xx.xx:7681) and then follow the steps. I used the DS3622xs and the older build version, but you may need to try several (the DS2422 one did not work for me). Generate the serial, install the modules that are detected, and set the max disks to whatever value you need. Once you build and then boot the bootloader, you can then go to find.synology.com and it should detect the instance.

 

Again, I'm doing this off memory, but without knowing your exact hardware or setup, can't really give any more useful devices. If you run into any issues, post here and we can try to assist further. Good luck!

 

  • Like 2
Link to comment
Share on other sites

@jrac86 Thanks a bunch. 

 

I played around in the meantime with a bit different approach just to see if i could get something working. 

 

1. Converted the VMDK to QCOW 2 and imported it to a newly created VM with a secondary 32gb disk, changed the unused disk type from IDE to SATA 

2. Booted and selected model and version (920+ and latest 42661)

3. Built the loader and went through the install process. 

 

It worked, surprisingly enough: 

 

image.thumb.png.3eb43b3ac78fc6916d69928afb55927e.png

 

 

Now to play around a bit 

 

Awesome work with the loader :) 

Link to comment
Share on other sites

On 7/11/2022 at 7:32 AM, fbelavenuto said:

Sorry for delay. In the proxmox console, type this:

 

dd if="/dev/zero" of="/var/lib/vz/images/arpl.img" bs=1M seek=4096 count=0

 

1M * 4096 = 4GB. Adjust values for your need.

 

For the record, I quickly tested DVA1622 using arpl03-a3 in proxmox. I did use the above command to expand the arpl image to 4gb. I used the same method for settin up proxmox for arpl as I did for tcrp @pocopico release of my DS3622xs+ build, those detailed instructions are linked in my signature with pictures and can easily be used as a guide to install arpl on proxmox... the only difference (obviously) was I used the arpl image instead of the tcrp image, and again I expanded the img.  I booted the VM logged into the ip:7681, added the hw misc and acpid from the list, built the loader and rebooted the vm and successfully booted into DVA1622 and completed dsm install 42661-U3. It was painless and super fast to build the loader. pretty cool.  I could not test the AI as my proxmox server is running a Xeon E3-1270v2 without graphics :( but I did have all 8 SS licenses. Great job @fbelavenuto

 

FYI: the acpid doesn't work, as I tried to click shutdown of the vm in proxmox and opened the console to watch dsm process shutdown, and it did not shutdown. After about 4-5 mins I manually shutdown the dsm instance. So, whichever acpid is shown does not actually work on DVA1622.

Link to comment
Share on other sites

I just found a problem when using alpha3, the IP displayed by arpl can only be the actual IP of the device. the IP address assigned to my device now is: 192.168.5.133, if I set the custom MAC address, the IP of the DSM system will become: 192.168.5.134, but arpl still shows: 192.168 .5.133. I can only use Synology Assistant to find the correct IP address.

 

DS920.jpg

  • Like 1
Link to comment
Share on other sites

@jrac86 @NooL there is no need to use a real USB key with Proxmox or convert vmdk ...

 

You just need to create your VM, delete default drive and cd-rom.

Then copy IMG file with scp transfert into proxmox system.

then import IMG in proxmox VM config with :

 

qm importdisk 101 /var/lib/vz/dump/orphee/tinycore-redpill.v0.8.0.0.img local-lvm

of course adapt values with your VM number, etc...

 

Then your IMG will be unused available disk in Proxmox GUI, you will be able to set it to SATA0 and go in VM option to set it to "boot order"

 

If you choose q35 machine, you will have a dummy/unused controller so your SataPortMap will have to be SataPortMap="1X" and DiskIdxMap="10XX" in my case : SataPortMap="18" DiskIdxMap="1000"

Your disks in DSM will start at sdb and will see first disk slot unsused.

 

You can choose i440fx and you will not need to play with this unused controller.

 

 

You will also add a serial socket to your VM with :

qm set 101 -serial0 socket

 

I choosed to not passthrough my HBA card to DSM because with HP Gen8, Proxmox passthrough is quite tricky, you must patch the kernel to enable iommu...

 

So I added SATA drives to the VM directly with :

qm set 101 -sata1 /dev/disk/by-id/ata-ST4000VN008-2DR166_XXXXXXXA
qm set 101 -sata2 /dev/disk/by-id/ata-ST4000VN008-2DR166_XXXXXXXB
qm set 101 -sata3 /dev/disk/by-id/ata-ST4000VN008-2DR166_XXXXXXXC
qm set 101 -sata4 /dev/disk/by-id/ata-ST4000VN008-2DR166_XXXXXXXD

 

My actual VM Proxmox conf :

image.png.d08ec979bf67ebb2cda3149a609ade52.thumb.png.de026a9423149cec6f748e2680b27bd0.png

 

Edit : Bonus

If you install kpartx on Proxmox (apt install ...)

You are able to mount IMG partition and edit file from proxmox SSH console in case needed :

 

image.png.f857e6d26cb6dc7d169532ff4712a342.png

 

Edit 2 : If you need more info about GPU passthrough you can have a look at my post in DVA3221 development thread

 

Edited by Orphée
  • Like 3
  • Thanks 1
Link to comment
Share on other sites

@Orphée Thanks for taking the time to reply :) 

 

I think we did almost the same way, except that i had the vmdk to qcow step, nice to know that can be skipped :) Glad to hear I wasnt completely wrong hehe :) 

 

For the first and most basic try, this was my setup: 

 

image.thumb.png.1bfa83de1c27a30dfa483e3dae4e35fc.png

 

Thanks again for replying, first time using proxmox after using Baremetal build for years. so its a bit new :) 

Link to comment
Share on other sites

@fbelavenuto Can you please explain the process of the module loading  ? I understand that the modules are now all in one bundle. Where the decision for loading or not takes place ? Is it based on the modules that are loaded in buildroot ? What if the modules are not included in buildroot ?

 

I think the most efficient way would be to use a yml file that will include PCIID and module so that it can be decided based to that. "modinfo" displays a list of device aliases, and the module name so there you have all your information.

 

Thats how the following is created.

https://github.com/pocopico/tinycore-redpill/blob/main/modules.alias.4.json.gz?raw=true

 

 

  • Like 1
Link to comment
Share on other sites

13 minutes ago, NooL said:

@Orphée Thanks for taking the time to reply :) 

 

I think we did almost the same way, except that i had the vmdk to qcow step, nice to know that can be skipped :) Glad to hear I wasnt completely wrong hehe :) 

 

For the first and most basic try, this was my setup: 

 

image.thumb.png.1bfa83de1c27a30dfa483e3dae4e35fc.png

 

Thanks again for replying, first time using proxmox after using Baremetal build for years. so its a bit new :) 

You may want to change core numbers if you want features like Synology Photo face detection work.

 

Edit :

It seems i440fx does not handle pci-e. I would suggest to use q35 if you do PCI-e passthrough... (but I may be wrong)

Edited by Orphée
Link to comment
Share on other sites

5 minutes ago, Orphée said:

You may want to change core numbers if you want features like Synology Photo face detection work.

 

Gotcha - This was just a proof of concept to see how it worked compared to the old Jun loader 6.2.3 on Baremetal which I was coming from :) 

 

Later today I will try again with a more proper build, and try passing through the Sata controller. - Hopefully all goes smooth again, otherwise I might quote you hehe :P 

 

Thanks again :) 

Link to comment
Share on other sites

@fbelavenuto Also one thing that worries me is the change in the partition scheme of the loader.P1 and P2 are always the same size even on original syno boxes.

 

Since we dont really know what scemd does and how it checks now or in the future for hardware integrity, i would keep the original loader scheme, move all required files to P3 and increase that size.

 

 

  • Like 2
Link to comment
Share on other sites

6 hours ago, Orphée said:

@jrac86 @NooL there is no need to use a real USB key with Proxmox or convert vmdk ...

 

You just need to create your VM, delete default drive and cd-rom.

Then copy IMG file with scp transfert into proxmox system.

then import IMG in proxmox VM config with :

 

qm importdisk 101 /var/lib/vz/dump/orphee/tinycore-redpill.v0.8.0.0.img local-lvm

of course adapt values with your VM number, etc...

 

Then your IMG will be unused available disk in Proxmox GUI, you will be able to set it to SATA0 and go in VM option to set it to "boot order"

 

If you choose q35 machine, you will have a dummy/unused controller so your SataPortMap will have to be SataPortMap="1X" and DiskIdxMap="10XX" in my case : SataPortMap="18" DiskIdxMap="1000"

Your disks in DSM will start at sdb and will see first disk slot unsused.

 

You can choose i440fx and you will not need to play with this unused controller.

 

 

You will also add a serial socket to your VM with :

qm set 101 -serial0 socket

 

I choosed to not passthrough my HBA card to DSM because with HP Gen8, Proxmox passthrough is quite tricky, you must patch the kernel to enable iommu...

 

So I added SATA drives to the VM directly with :

qm set 101 -sata1 /dev/disk/by-id/ata-ST4000VN008-2DR166_XXXXXXXA
qm set 101 -sata2 /dev/disk/by-id/ata-ST4000VN008-2DR166_XXXXXXXB
qm set 101 -sata3 /dev/disk/by-id/ata-ST4000VN008-2DR166_XXXXXXXC
qm set 101 -sata4 /dev/disk/by-id/ata-ST4000VN008-2DR166_XXXXXXXD

 

My actual VM Proxmox conf :

image.png.d08ec979bf67ebb2cda3149a609ade52.thumb.png.de026a9423149cec6f748e2680b27bd0.png

 

Edit : Bonus

If you install kpartx on Proxmox (apt install ...)

You are able to mount IMG partition and edit file from proxmox SSH console in case needed :

 

image.png.f857e6d26cb6dc7d169532ff4712a342.png

 

Edit 2 : If you need more info about GPU passthrough you can have a look at my post in DVA3221 development thread

 

Awesome info! Ill be moving off the usb to a virtual disk then.

 

I had to passthrough the HBA card bc proxmox has a limit of 6 passed through sata drives for a vm.

Link to comment
Share on other sites

9 hours ago, kekylin said:

I just found a problem when using alpha3, the IP displayed by arpl can only be the actual IP of the device. the IP address assigned to my device now is: 192.168.5.133, if I set the custom MAC address, the IP of the DSM system will become: 192.168.5.134, but arpl still shows: 192.168 .5.133. I can only use Synology Assistant to find the correct IP address.

 

DS920.jpg

 

I've noticed that after the initial install the IP always moved one digit forward. No matter what loader you are using.

 

In the next reboot it should be fixed.

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

9 minutes ago, jrac86 said:

Awesome info! Ill be moving off the usb to a virtual disk then.

 

I had to passthrough the HBA card bc proxmox has a limit of 6 passed through sata drives for a vm.

From what i've read on internet pci-e passthrough require q35 machine conf. (remember Dummy Sata Map conf with it)

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