Jump to content
XPEnology Community

Develop and refine the DS3622xs+ loader


yanjun

Recommended Posts

10 minutes ago, p33ps said:

 

Hey, can you please explain what build did you use to get it working in HP Gen8?

if baremetal just add this extension to the loader and also update the loader with ./rploader.sh update now :

https://raw.githubusercontent.com/jimmyGALLAND/redpill-ext/master/acpid/rpext-index.json

 

if VM, just update and rebuild : ./rploader.sh update now

 

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

Hi everyone, I am currently trying to solve the following problem (important and urgent):

 

1, On my machine, once the data scrub is run manually, the btrfs scrub start of the first step takes roughly a few hours and works fine, while the second step of resyncing the array causes a memory overflow after roughly 10 minutes (I give dsm allocated 38G of memory). After that, it will cause a restart. I tested it twice. Although there is no data overflow, it has laid a hidden danger for data recovery after an error occurs. For detailed logs, see messages-oom-killer.txt

 

2. When you mix sata controller and mpt3sas-driven LSI card, you can't mix sata controller's hard disk and lsi card's hard disk to create raid1, normally not many people will create raid1, so I need to clarify Now, this bug will cause the startup of md0 to fail. Once you mix the two hard disks, it will fail to enter junior mode when the system starts for the second time. The phenomenon on the webui is to prompt you to install the system. I personally think that there is still a problem with the mpt3sas driver.

599850536_GDU0OLYDD@H5XQK.thumb.png.b9deb6231f26570d663a0e152f8ec6a8.png

messages-oom-killer.txt

 

 

@IG-88 @buggy25200 @pocopico 

Link to comment
Share on other sites

3 minutes ago, flyride said:

 

The default behavior of DSM is to RAID1 over all available devices for /dev/md0 (Linux OS) and /dev/md1 (Linux swap).  I assume we all know this but just to clarify.

Yes, I also observed that each HDD is in RAID1 of md0 and md1, but if the mpt3sas-driven HDD and the ahci-driven HDD are rebooted, the system will not boot normally and enter install mode.

 

2099419445_P(V4DV5EL6YOG@PZD4BE.thumb.jpg.095fbced61786960236eaba91f743233.jpg 

Link to comment
Share on other sites

1 hour ago, yanjun said:

2. When you mix sata controller and mpt3sas-driven LSI card, you can't mix sata controller's hard disk and lsi card's hard disk to create raid1, normally not many people will create raid1, so I need to clarify Now, this bug will cause the startup of md0 to fail. Once you mix the two hard disks, it will fail to enter junior mode when the system starts for the second time. The phenomenon on the webui is to prompt you to install the system. I personally think that there is still a problem with the mpt3sas driver.



Good New:  this issue has been fixed.

I tried to replace the source code of mpt3sas, which is from the driver download page of Broadcom's latest device. https://www.broadcom.com/products/storage/host-bus-adapters/sas-nvme-9500-16i Validated on both of my LSI devices (SAS2308 PCI-Express Fusion-MPT SAS-2 and SAS3416 Fusion-MPT Tri-Mode I/O Controller Chip (IOC)). The packaged mpt3sas driver module address is as follows.

https://github.com/dogodefi/mpt3sas/blob/offical/rpext-index.json

 

@pocopico hope you can refer to my experience.

@IG-88 Hope to hear your advice on this issue.

  • Like 1
Link to comment
Share on other sites

15 minutes ago, yanjun said:



Good New:  this issue has been fixed.

I tried to replace the source code of mpt3sas, which is from the driver download page of Broadcom's latest device. https://www.broadcom.com/products/storage/host-bus-adapters/sas-nvme-9500-16i Validated on both of my LSI devices (SAS2308 PCI-Express Fusion-MPT SAS-2 and SAS3416 Fusion-MPT Tri-Mode I/O Controller Chip (IOC)). The packaged mpt3sas driver module address is as follows.

https://github.com/dogodefi/mpt3sas/blob/offical/rpext-index.json

 

@pocopico hope you can refer to my experience.

@IG-88 Hope to hear your advice on this issue.

 

 

So what was the solution ? Was it related to the mpt3sas version of the driver ? Was this related to your HBA firmware level ? 

 

Link to comment
Share on other sites

2 minutes ago, pocopico said:

 

 

So what was the solution ? Was it related to the mpt3sas version of the driver ? Was this related to your HBA firmware level ? 

 

I personally think that the Drive Version of MPT3SAS is related to my two models of LSI devices, there is the same ISSUE. My solution is to update the driver, use MPT3SAS-40.00.00.00-src.tar.gz, included in Linux_Driver-rhel7-8_sles12-15_gen35_phase_21.0_nvme.

  • Like 1
Link to comment
Share on other sites

2 hours ago, yanjun said:

Hi everyone, I am currently trying to solve the following problem (important and urgent):

 

1, On my machine, once the data scrub is run manually, the btrfs scrub start of the first step takes roughly a few hours and works fine, while the second step of resyncing the array causes a memory overflow after roughly 10 minutes (I give dsm allocated 38G of memory). After that, it will cause a restart. I tested it twice. Although there is no data overflow, it has laid a hidden danger for data recovery after an error occurs. For detailed logs, see messages-oom-killer.txt

 

2. When you mix sata controller and mpt3sas-driven LSI card, you can't mix sata controller's hard disk and lsi card's hard disk to create raid1, normally not many people will create raid1, so I need to clarify Now, this bug will cause the startup of md0 to fail. Once you mix the two hard disks, it will fail to enter junior mode when the system starts for the second time. The phenomenon on the webui is to prompt you to install the system. I personally think that there is still a problem with the mpt3sas driver.

599850536_GDU0OLYDD@H5XQK.thumb.png.b9deb6231f26570d663a0e152f8ec6a8.png

messages-oom-killer.txt 160.86 kB · 1 download

 

 

@IG-88 @buggy25200 @pocopico 

I think the same happens with mpt3sas on 918+ as well. I installed and then immediately got a critical os error on first boot and it prompts me to put in a support ticket - no option to repair system partition - after that when i reboot it wants to install DSM again. 

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

1 minute ago, cferra said:

I think the same happens with mpt3sas on 918+ as well. I installed and then immediately got a critical os error on first boot and it prompts me to put in a support ticket - after that when i reboot it wants to install DSM again. 

If you need, I can make 918 mpt3sas MPT3SAS-40.00.00.00 extension for you.

Link to comment
Share on other sites

I think it would be good to do as a driver pack - i think I want to migrate to the 22xs - i couldn’t get the drivers to work at all with tc and 3617 so i tried with 918, they worked there but I ran into that issue.  
 

for right now I had to fall back to jun’s 6.3.2 3617 

Link to comment
Share on other sites

13 minutes ago, cferra said:

While I have no data on the array I have some ability to experiment too so if I could be useful in that regard let me know. 
 

i have a x10srl-f board with a v4 xeon and an lsi 9305-24i card. 

Whether you want to test 3622xs + or 918+, just convert the address of the MPT3SAS driver package as follows:

 

https://raw.githubusercontent.com/dogodefi/mpt3sas/offical/rpext-index.json

  • Like 1
Link to comment
Share on other sites

Join the conversation

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

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

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

×   Your previous content has been restored.   Clear editor

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

×
×
  • Create New...