cferra Posted January 25 Share #5076 Posted January 25 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. Quote Link to comment Share on other sites More sharing options...
sobig11 Posted January 25 Share #5077 Posted January 25 i posted this some days ago, but obviously in the wrong Thread.. so please help me Hi .. i'am trying install my HP Microserver Gen 10 which ran before wirh DSM 6.1.3 with the redPill Loader... but i stuck at teh first step... i boot from the internal USB-Port as well as i did with DSM but first came error messages, that VGA and VESA Files could not be found, then the menu comes up in normal size...with just one entry if i try to build the loader the the script couldn't find the kernel file after "Loading Linux...." ERROR disk "hd0 ' msdos" not found .......... where can i change it or change the script to find it at the correct place... using Redpil "tinycore-redpill-uefi.v0.10.0.0.img" Thnak you Quote Link to comment Share on other sites More sharing options...
cferra Posted February 10 Share #5078 Posted February 10 (edited) 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. Edited February 10 by cferra Quote Link to comment Share on other sites More sharing options...
Captainfingerbang Posted February 12 Share #5079 Posted February 12 Could someone just remind me what this means when having issues with the advanced codec install? (hevc etc) "Failed to play or display music or videos due to a codec activation error. To fix this issue, check your Internet connection." I can go and find what to do, just need reminder. Installed to new hardware today with no REAL serial/mac so.. There's a great fix for these things over here for dsm 7.2 , https://github.com/darknebular/Wrapper_VideoStation but not quite sure if that's what i need yet. Thanks! Quote Link to comment Share on other sites More sharing options...
Owen Posted February 12 Share #5080 Posted February 12 (edited) 9 hours ago, Captainfingerbang said: Could someone just remind me what this means when having issues with the advanced codec install? (hevc etc) "Failed to play or display music or videos due to a codec activation error. To fix this issue, check your Internet connection." I can go and find what to do, just need reminder. Installed to new hardware today with no REAL serial/mac so.. There's a great fix for these things over here for dsm 7.2 , https://github.com/darknebular/Wrapper_VideoStation but not quite sure if that's what i need yet. Thanks! I haven't followed the xpenology project for a while but I think the error is no real MAC/Serial and therefore license is not activated in AME - run through the install of the Wrapper - if you are <7.2, if 7.2+ sounds like you will have to fix the serial: https://github.com/darknebular/Wrapper_VideoStation#now-the-installer-has-the-ames-license-fix Edited February 12 by Owen Quote Link to comment Share on other sites More sharing options...
Captainfingerbang Posted February 12 Share #5081 Posted February 12 9 minutes ago, Owen said: I haven't followed the xpenology project for a while but I think the error is no real MAC/Serial and therefore license is not activated in AME - run through the install of the Wrapper - if you are <7.2, if 7.2+ sounds like you will have to fix the serial: https://github.com/darknebular/Wrapper_VideoStation#now-the-installer-has-the-ames-license-fix Wow, so full reinstall for codec? Those Chinese are really startin ta squeeze our lemons. Maybe if they put out some better, more exciting hardware with some real man balls to it, they wouldnt have to pinch all these pennies from us with buying their brand drives etc stupid people Quote Link to comment Share on other sites More sharing options...
Owen Posted February 12 Share #5082 Posted February 12 20 minutes ago, Captainfingerbang said: Wow, so full reinstall for codec? Those Chinese are really startin ta squeeze our lemons. Maybe if they put out some better, more exciting hardware with some real man balls to it, they wouldnt have to pinch all these pennies from us with buying their brand drives etc stupid people It may be possible to fix the codec without a full re-install, not sure! In the worst case - can't most things be imported/migrated from existing data or a backup? Quote Link to comment Share on other sites More sharing options...
cferra Posted February 16 Share #5083 Posted February 16 (edited) 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_name I'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_name It 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? Edited February 16 by cferra Quote Link to comment Share on other sites More sharing options...
alirz1 Posted February 18 Share #5084 Posted February 18 On 2/12/2024 at 10:32 AM, Owen said: It may be possible to fix the codec without a full re-install, not sure! In the worst case - can't most things be imported/migrated from existing data or a backup? I recall I have done this by just changing the Mac and serial in the grub.cfg and then I was able install the AME pack. Quote Link to comment Share on other sites More sharing options...
Hackaro1 Posted March 6 Share #5085 Posted March 6 Hi all, @Peter Suh a friend of mine trying to build his 1st Xpenology had a problem with DS3622XS model and ACPI daemon. It was installed the DSM 7.2.1-69057 Update 3 on my pc with DS3622xs+ via your M Shell for tinycore-redpill v.1.0.1.0. Everything's fine except for the power off via power button. Checking acpid.service: root@ALAMO_Test_1:~# systemctl status acpid.service -l ● acpid.service - ACPI Daemon Loaded: loaded (/usr/lib/systemd/system/acpid.service; static; vendor preset: disabled) Active: active (running) since Wed 2024-01-31 18:02:25 CET; 9min ago Main PID: 25027 (acpid) CGroup: /system.slice/acpid.service └─25027 /usr/sbin/acpid -f Jan 31 18:02:25 ALAMO_Test_1 systemd[1]: Started ACPI Daemon. Jan 31 18:02:25 ALAMO_Test_1 systemd[1]: Starting ACPI Daemon... Jan 31 18:02:25 ALAMO_Test_1 acpid[25027]: cannot open input layer Jan 31 18:02:25 ALAMO_Test_1 acpid[25027]: inotify_add_watch() failed: No such file or directory (2) Jan 31 18:02:25 ALAMO_Test_1 acpid[25027]: starting up with netlink and the input layer Jan 31 18:02:25 ALAMO_Test_1 acpid[25027]: 1 rule loaded Jan 31 18:02:25 ALAMO_Test_1 acpid[25027]: waiting for events: event logging is off any hint? Thanks in advance! Quote Link to comment Share on other sites More sharing options...
cferra Posted March 6 Share #5086 Posted March 6 What board? Latest bios version? Clear bios to factory defaults. Quote Link to comment Share on other sites More sharing options...
Hackaro1 Posted March 7 Share #5087 Posted March 7 On 3/6/2024 at 2:26 PM, cferra said: What board? Latest bios version? Clear bios to factory defaults. Asus z370a , yes latest bios available, and already cleared to factory defaults but nothing changed. Quote Link to comment Share on other sites More sharing options...
nadiva Posted March 18 Share #5088 Posted March 18 On 12/20/2023 at 2:38 AM, Peter Suh said: Also, here is additional information about the detailed chipset of Synology's genuine Ethernet. E10G17-F2 : Mellanox ConnectX-3 Pro CX312B E10G18-T1 : Aquantia AQC107-B1 E10G18-T2: Marvell QL41102 (MAC) + BCM84886 (PHY) E10M20-T1: Aquantia AQC107 (built-in PLX PCIe switch and 2EA M.2 slots) E10G21-F2: Intel X710 E25G21-F2: Intel XXV710 (estimated) E10G22-T1-Mini : Aquantia AQC107 E10G30-T2: Broadcom BCM57416 (estimated) E25G30-F2: Broadcom BCM57414 (estimated) Model name - If it starts with T, it is 10GBASE-T (RJ45), if it starts with F, it is SFP+ or SFP28, and the last number is the number of ports. Hello is there a reason ice driver is not included in kernel 5? I tried SA6400 and it brings IGPU to Intel CPU, but without NICs. lspci -vv | egrep Ethernet Product Name: Intel(R) Ethernet Network Adapter E810-XXVDA2 lsmod|grep ice dmesg|grep Ethernet Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted March 19 Share #5089 Posted March 19 (edited) 12 hours ago, nadiva said: Hello is there a reason ice driver is not included in kernel 5? I tried SA6400 and it brings IGPU to Intel CPU, but without NICs. lspci -vv | egrep Ethernet Product Name: Intel(R) Ethernet Network Adapter E810-XXVDA2 lsmod|grep ice dmesg|grep Ethernet A little while ago, I compiled and distributed a version that included the missing sa6400 ice.ko. Rebuild the loader of tcrp-mshell and try it. https://github.com/PeterSuh-Q3/arpl-modules/tree/main/epyc7002-7.2-5.10.55 https://github.com/PeterSuh-Q3/arpl-modules/releases/tag/24.3.19 Edited March 19 by Peter Suh 1 Quote Link to comment Share on other sites More sharing options...
ivan9ef Posted March 23 Share #5090 Posted March 23 (edited) What do I need get my n6000 motherbord to work as SA6400? gpu (at least photo recognition) doesn't work. I tried different loadrers like arc, RR, etc. What am I doing wrong?????????? 😭😭😭 Edited March 23 by ivan9ef Quote Link to comment Share on other sites More sharing options...
tomydu69 Posted April 5 Share #5091 Posted April 5 Hello everybody, I come back after years without having touched my server and I am totally lost. I am currently in version 7.1-42661 update 1. It suggests I upgrade to version 7.1.1-42962 but this does not seem to be the latest possible version. Do you have to go through this update? If so, which loader should I use on my key? my key is in RedPill V0.9.4.9 Or can I directly update DSM 7.2.1 69057-Update 4? also with which loader? Thank you very much for your help please Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.