cferra
-
Posts
177 -
Joined
-
Last visited
-
Days Won
1
Posts posted by cferra
-
-
13 hours ago, afaroz61 said:
Hi. I have X10SLH-N6-ST031 (onboard INTEL x540 AT2 - 6x 10gbe) I am using ARC loader. I cannot connect 2.5g and 10g. The connection always shows gigabit. The cable is solid. When I connect the computer with a cable, I can establish a 2.5g connection. I tried 918+ - 920 - 3622xs. Can you help me?
Ixgbe Linux drivers do not support 2.5gb - it’s either 1 or 10.
-
1 hour ago, Captainfingerbang said:
Wow thats great. Your always on top of things Peter.
I havent gotten my 3008 card yet though. Postal service said "weather problems" yet there is no bad weather within 500 miles of here!
Thank you will do
By the way im getting too old, or smoking too much funny grass, but what does "rr" mean again? Release date etc?
RR is the new name for ARPL
-
With rr 24.2.0 I am still unable to get hotplug to work, the out of the box dts file looked correct when comparing to syno_block_info so I'm not sure what's up there. There is also a repeating error in the logs:
2024-02-15T21:57:19-05:00 MediaVaultXL synostgd-disk[31748]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sata15/device/../../scsi_host/host*/proc_name
2024-02-15T21:57:19-05:00 MediaVaultXL synostgd-disk[31750]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sata16/device/../../scsi_host/host*/proc_name
2024-02-15T21:57:19-05:00 MediaVaultXL synostgd-disk[31750]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sata16/device/../../scsi_host/host*/proc_name
Maybe I'm doing something wrong with the dts file or missing clarity on what to do.
I have 40 disks populated and it sees all of them and works with them without issue aside from the hotplugging.
-
On 9/2/2023 at 10:30 AM, killseeker said:
@Peter Suh I've tried to find some more information about what is happening under the hood in Synology regarding these messages:
2023-09-03T00:06:32+10:00 Beast synostgd-disk[9340]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdl/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9340]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdl/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9335]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdk/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9335]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdk/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9348]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdm/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9348]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdm/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9354]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdn/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9354]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdn/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9357]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdo/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9357]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdo/device/../../scsi_host/host*/proc_nameI've tracked them to the "systemctl status synostoraged.service":
● synostoraged.service - Synology daemon for monitoring space/disk/cache status Loaded: loaded (/usr/lib/systemd/system/synostoraged.service; static; vendor preset: disabled) Active: active (running) since Sat 2023-09-02 23:39:31 AEST; 33min ago Main PID: 16670 (synostoraged) CGroup: /syno_dsm_storage_manager.slice/synostoraged.service ├─16670 synostoraged ├─16673 synostgd-disk ├─16675 synostgd-space ├─16677 synostgd-cache ├─16678 synostgd-volume └─16680 synostgd-external-volume Sep 03 00:12:32 Beast [3825]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdk/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3825]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdk/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3828]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdl/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3828]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdl/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3831]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdm/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3831]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdm/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3834]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdn/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3834]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdn/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3836]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdo/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3836]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdo/device/../../scsi_host/host*/proc_nameIt would be specifically coming from this process: synostgd-disk which seems to run every minute in the background.
I am kind of at a loss of where else to check. My unix knowledge and troubleshooting skills are not that advanced, so I am unsure how else to help out here sorry.
Do you think we need to modify the synostgd-disk service and the tell it to use the mtp3sas driver to do its queries and checks as opposed to the mv1475_driver or mv_soc_driver? Or is this not how it works or not possible?
Even though I see these messages, my Storage manager appears healthy and happy:
Disks are also all visible, and shows serial numbers and all SMART information:
@Peter Suh @killseeker @pocopico I am seeing the same thing with my SA6400 build. I am using a 9305-24i and a 9305-16e - these errors are flooding the log, has there been any fix for this? Anything that I can do?
-
seeing this in the logs for sa6400 - any thoughts?
2024-02-15T21:57:19-05:00 MediaVaultXL synostgd-disk[31748]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sata15/device/../../scsi_host/host*/proc_name
2024-02-15T21:57:19-05:00 MediaVaultXL synostgd-disk[31750]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sata16/device/../../scsi_host/host*/proc_name
2024-02-15T21:57:19-05:00 MediaVaultXL synostgd-disk[31750]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sata16/device/../../scsi_host/host*/proc_name -
9 minutes ago, Captainfingerbang said:
Hello i have a very specific question. I only have Serial/Mac for Ds918 and always used intel but running into problems
Would it be possible to use this loader and use ds918+ on 7.1+ using a 5900x and b550 motherboard and use all 24 threads?
Are you looking for gpu hardware encoding?
-
Got it. Sorry for the confusion
-
-
I am out of my depth completely so if I’m not making sense - I’m more than happy to shut up haha
-
1
-
-
-
From what you posted - it seems pretty related but I could be wrong.
-
21 minutes ago, Peter Suh said:
What is it about? Please tell me the specific link so I can take a look.
https://dortania.github.io/Getting-Started-With-ACPI/Manual/dump.html
https://www.insanelymac.com/forum/topic/278170-dsdt-—-what-is-it-and-how-do-i-get-it/
https://elitemacx86.com/threads/how-to-install-dsdt-ssdt-clover-opencore.31/
https://dortania.github.io/OpenCore-Install-Guide/
let me know what you think, I’m a bit out of my depth in the development side of things.
-
Can we leverage what they do in the hackintosh community to work around device tree issues?
-
13 minutes ago, Peter Suh said:
You seem to be talking about Hot PlugIn for SATA disks or SAS disks.
Device-Tree based models such as SA6400 do not seem to support Hot PlugIn disk mapping.
Newly added disks will only have new mappings processed through the reboot process.
In a genuine Synology, this process is probably unnecessary.
Makes sense - 3622 I was unable to build the array though for some reason - instant error when attempting. Using 14 10tb SAS disks.
SA6400 this worked with no issue.
is SA3600 better for a large build out? Or even something being with testing?
-
@Peter Suh on SA6400 Is it a known issue that connecting new drives while being turned on when LSI hba cards is not working?
im able to see drives when I reboot the machine but not if I add drives when the machine is on.
LSI 9305 series cards.
-
is there a trick to getting LSI controllers to detect new drives being added on the SA6400 image? I was able to boot on the ds3622 image but I was having difficulty creating new volumes, which seems to work better on the SA6400 build. Just need new drive detection to work. Any thoughts?
For context the LSI controllers are 9305-24i and 9305-16e - both are running the latest firmware for UEFI and legacy - and are non-raid HBA cards.
The system sees the drives attached when booting up but when adding drives when the machine is on, the drive is not detected until reboot.
-
On 12/31/2023 at 7:33 AM, DomZ said:
RIght now, my xpenology VM has been installed using a vmdk image that was already set, and loader is embed in the VM image (I suppose).
I have used this youtube toturial :
What you propose is to redo the image from scratch right ?
Looks like synology is going crazy copyright striking everything on youtube.
-
Is there an update step by step doc to go from prefriend - 7.1.1 to withfriend and latest Dsm? I’ve kinda fallen behind the times…
-
1
-
-
4 minutes ago, Peter Suh said:
Thank you for answer.
Successful cases have also been confirmed with the usual built-in M.2 slot.
https://xpenology.com/forum/topic/53817-redpill-tinycore-loader/?do=findComment&comment=344524I followed the nvme guide in the forum - added my results there
-
On 9/28/2022 at 11:38 PM, Peter Suh said:
As a result of my testing, there were two cases where NMVe cache worked in TCRP friends even on baremetal.
The NVMe cache of the onboard internal M.2 slot did not work,
In the case of using the M.2 PCIE extension adapter, it worked for me as well.
May I know which of the two is the case?
I’m using a super micro x10slh board with bifurcation enabled and a dual nvme adapter
-
28 minutes ago, Peter Suh said:
Virtualbox also supports PCIE type NVMe.
So I also tried to enable NVMe on the VM.
As you can see, in the same way as in DS3622xs+ baremetal.
I modified /etc.defaults/extensionPorts but it didn't work.
I don't think I've ever heard any reports of successful NVMe caching in VMs.
Once it can be activated from DSM, it can be extended to the test of TCRP friends, but it seems impossible at the moment.
I think we should focus on baremetal.
Yeah it works on Baremetal. I’ve got that going now.
-
@pocopico Ok got it - how can I help test?
-
@pocopicoSo i feel out of the loop a bit, what does friend allow us to do? Direct updates from synology? More? Color me intrigued - willing to test but a bit confused.
how can I help?
-
I’m trying to remove an extension from the build - but I can’t seem to figure out the commands
I do ./rploader.sh ext broadwellnk-7.1.1-42962 remove pocopico.mlx4_core
it seems to generate permission denied entries when attempting this so I manually delete the directory
when I run build the driver downloads again, I’m jumping back in so I might be missing a step or doing the wrong command.
TinyCore RedPill Loader (TCRP)
in Loaders
Posted
What board? Latest bios version? Clear bios to factory defaults.