Jump to content
XPEnology Community

valix

Member
  • Posts

    53
  • Joined

  • Last visited

Everything posted by valix

  1. Hi, what do you want to know? The solution is in my earlier post above / the one you quoted.
  2. Ok, I found a way to get further with SA6400 or any AMD based other RR-Loader, and I don't really know why, but maybe I have an idea. Obviously the Intel NICs are shared with the BMC NIC. Therefore I can access the BMC via the Intel NIC and its dedicated NIC. And the BMC NIC is a Realtek 8211E Chip. Idk if this is the one Realtek, which wouldn't work with DSM or if it is just coincidence. The solution was, not to use the onboard NICs and to install the Aquatia Atlantic 107 10 GbE NIC I wanted to install anyway. Now, only the actual BMC NIC and the Aquatia NIC are connected and SA6400 setups fine.
  3. Thank you. I just tested SA6400 and at least I got further a little bit. little by little the bird builds its nest. After booting the sa6400 loader I was able to reach the intial setup webpage and install the latest PAT-File (I chose "download from Synology"). But after the first "10 minutes" reboot nothing worked any more 😕 Edit: I forgot to mention something. Actually the web interface is in a "reboot loop". Every ten minutes, after the countdown timer reached 0, the web interface say "Error - try again" and the installation progress percentage starts again vom 0% to 100% with the reboot information and aber the reboot count down is again bei 0:00 it all starts again. But actually - according to the display outbput, the machine never reboots. If I do that via reset button, DSM is broken.
  4. Hi, I hope some of you have got an idea. I get no network connection after booting the DSM. No mac address propagated. My build: - AMD Ryzen 5 Pro 5650G - Gigabyte MC12-LE0 - 2x 16 GB ECC RAM - 2x 1 TB NVMe via Bifurcation adapter - 2x Intel i210 GbE (onboard) - Aspeed 2500 BMC - SATA SSD for testing purposes - Loader: RR (aka arpl-i18n) 24.1.3 several models (1621+, 3622xs+, 923+), with "all" modules - DSM: 7.2.1 I tested my hardware with a Windows 10 Installation, therefore I assume everything works basically fine. The USB stick also boots fine. Since I made good experiences with RR Loader (currently running AMD Carizzo (923+), Intel Skylake (3622+), Intel Ivy Bridge (3622+) setups), I chose it again for my latest project. But unfortunately it doesn't work after building and booting the loader. From the console, everything looks fine, but I get no mac address. I also switched from UEFI Boot to Legacy Boot. Removed the mac1 and mac2 entry from config file. The BMC (ASPEED 2500) is connected to switch port 6 and the the prod interface to switchport GE3, but there is no mac address visible.
  5. Outcome of the update: SUCCESSFUL DSM version prior update: DSM 7.2-69057 update-3 Loader version and model: RR 23.11.10 on / DS3622xs+ Installation type: BAREMETAL - Fujitsu D3417-B2 (Xeon E3 1225v5), Aquantia AQtion AQC107 NIC -> chosen Matching Modules Additional comments: Manual update via DSM Control Panel Outcome of the update: SUCCESSFUL DSM version prior update: DSM 7.2-69057 update-3 Loader version and model: RR 23.11.10 on / DS923+ Installation type: BAREMETAL - Biostar A10N-8800E (AMD FX-8800P Processor)-> chosen Matching Modules Additional comments: Manual update via DSM Control Panel
  6. Outcome of the update: SUCCESSFUL DSM version prior update: DSM 7.2-69057 update-3 Loader version and model: RR 24.1.2 on / DS3622xs+ Installation type: BAREMETAL - HPE Microserver Gen8 (Xeon E3 1220Lv2), Aquantia AQtion AQC107 NIC -> chosen Matching Modules Additional comments: After applying update the loader boot to RR, just hit "boot loader" and boot operation proceeded
  7. https://www.synology.com/en-global/releaseNote/DSM
  8. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Update 3 (DS918+) - DSM version after update: DSM 7.2.1 69057 - Update 1 (DS923+) - Loader version and model: Juns Loader 1.03b -> ARPL-i18n v23.10.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - BIOSTAR A10-8800E (AMD FX-8800P Processor -> Carrizo), ASMedia 1064 SATA Controller -> chosen all Modules - Additional comments: Didn't startup completely with DS3622XS+ Loader and also didn't startup with DS918+ Loader. It hang somewhere during the DSM launch, not during loading the ARPL loader.. Then I tested the AMD Loader fir 923+ and it worked like a charm. And the CPU Recognition Addon doesn't work. It still claims to have a R1600.
  9. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2 64570 Update 3 (3622xs+) - Loader version and model: arpl-i18n v23.8.5 -> v23.10.0 - Using custom extra.lzma: NO - Installation type: BAREMETAL - Fujitsu D3417-A1x w/ Xeon E3-1225v5, Aquantia AQtion AQC107 NIC, NVMe RW-Cache -> chosen all Modules - Additional comments: Update Menu, Rebuilt flash; model 3622xs+; Active Backup for Business needed a new activation
  10. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2 64570 Update 3 (3622xs+) - Loader version and model: arpl-i18n v23.8.5 -> v23.9.7 - Using custom extra.lzma: NO - Installation type: BAREMETAL - HPE Microserver Gen8 (Xeon E3 1220Lv2), Aquantia AQtion AQC107 NIC -> chosen Matching Modules - Additional comments: Rebuilt flash; model 3622xs+; Active Backup for Business needed a new activation.
  11. I faced similar issues some years ago. This were my conclusions: Have you tried to enter the ip address of the device directly into your browser? http://<ip.of.your.xpenology>:5000 that is the way I usually setup my Xpenologys Have you chosen the right option in the boot menu ("Install")? You should connect a display and a keyboard for the first startup Why are you running DSM 6.1? DSM 6.2.3 works also fine with Jun's latest loaders. Only beyond 6.2.3 you need to be careful and add / create a new bootloader. Or you may be facing a network driver issue, that the driver is included in the loader but not loaded DSM. I had this issue with a 918+ bootloader and the onboard Realtek NIC of my HP MS Gen8. Therefore I switched back to 3615xs
  12. I wonder if it is necessary to replace also rd.gz and zImage from the original .pat file. I just replaced the extra.lzma itself and it worked (Juns 1.03b 3615xs loader + DSM 6.2.3U3 un HP MS Gen8 Baremetal) for me. My 10 Gig Asus NIC (Aquantia 107) is recoginzed. Thanks for the driver package. Edit. Somehow I have 41% Packetlos (480 pings send), when die Aquantia NIC is running on 1 Gbps. I haven't tried another link speed, since my switch isn't upgraded yet. But my current switch has no raising error counters. No matter if I set the interface to 100 Mb FD or 1000 Mb FD. No issues with the onboard Broadcom NICs. Argh - call myself idiot. Accidentially a provided two different NIC of two different Xpenologies with the same MAC. Shame on me.
  13. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: Jun's v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP ProLiant Microserver Gen8 (Xeon 1220Lv2) - Additional comment: To avoid custom extra.lzma, I already installed in 2019 an Intel e1000e Dual-Nic (HP NC360T) to go for 6.2, and disabled the onboard NICs in BIOS. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: Jun's v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Fujitsu D3417-B1 C236 Chipset w/ Xeon 1220v5 - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: Jun's v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Biostar A10N-8800E (Carizzo), 8 GB DDR4 2133, Inline 76617d 4x SATA controller
  14. @hoppler it worked like a charm on my 918+ config!
  15. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 4 - Loader version and model: Jun's v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP ProLiant Microserver Gen8 (Xeon 1220Lv2) - - Additional comment: To avoid custom extra.lzma, I already installed in 2019 an Intel e1000e Dual-Nic (HP NC360T) to go for 6.2, and disabled the onboard NICs in BIOS. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 4 - Loader version and model: Jun's v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Fujitsu D3417-B1 C236 Chipset w/ Xeon 1220v5 - Comments: -/- - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 4 - Loader version and model: Jun's v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Biostar A10N-8800E (Carizzo), 8 GB DDR4 2133, Inline 76617d 4x SATA controller - Comments:-/-
  16. I tested the Power Plan on the HP Powerserver Gen 8 I also have. It worked in a restricted way. It cannot determine between the week days, each day is today for booting up, setting up to boot e.g. only on saturdays results in a boot every day. I assume an issue I have to live with - and I lived with it since 2015 or 2014. A nice to have, but on the other hand, Xpenology is no comercial product.
  17. Loader version and type: 1.04b DS918+ DSM version in use (including critical update): 6.2.2-24922-4 Using custom modules/ramdisk?: no Hardware details: Biostar A10N-8800E Ver. V6.1 (AMD FX-8800P Carrizo Processor), 4 GB DDR4 2400@2133 LAN: Realtek RTL8111H Gigabit SATA: 2x via SoC and 4x via Inline 76617D Add-In Card (Marvell 88SE9230 Chipset), S.M.A.R.T is supported for both Comments: clean install, used DSM_DS918+_24922.pat, perfect, CPU FAN replaced by Noctua 60 mm 3 Pin Fan, GPU clock reduced to minimum Loader version and type: 1.04b DS918+ DSM version in use (including critical update): 6.2.2-24922-4 Using custom modules/ramdisk?: no Hardware details: Fujitsu D3417-B1 w/ Intel Xeon 1220v5, 8 GB DDR4 ECC 2133 LAN: Intel I219-LM Gigabit SATA: 6x onboard Comments: clean install, used DSM_DS918+_24922.pat, perfect
  18. This are my test settings for DSM And the device shut down as usual correctly as planned, but even as usual nothing happend at 18:12 - no start up. This are the power settings in BIOS: I could set a wake up date in BIOS but it couldn't be controlled from DSM GUI. DSM 6.2.2 on Biostar A10N-8800. But I hat the same experience with my HPE Microserver Gen8 and a Fujitsu D3417-B1 Board.
  19. Of course I did. As I wrote it works perfectly for shutdown but not for startup. And I tested this with all my current and former Xpenology NAS (AMD Kabini, Intel Haswell, Intel Skylake, Intel Ivy Bridge, AMD Carizzo platforms). It never worked for startup. I give you one task: Set a shutdown time and 30 minutes later a startup time and please let me know if it worked for you.
  20. Hi there, I ask myself if it wouldn't be great if the power schedule would work to boot and shutdown the NAS at a certain time. Shutdown works so far without any change for me at all my NAS but what about booting? Of course I could set a wakeup-timer in the BIOS but it is no very dynamic and has often poor possibilities and since the NAS is running headless I wouldn't always attach and detach a monitor and keyboard to change the BIOS settings - very annoying. Does anybody have a clue how to setup a working startup timer?
  21. Alright, after replacing the currently used usb stick by another one it works fine. Obviously Hardware fault.
  22. Hi there. I need some support to get on with my new NAS build. (This is supposed to be my 5th Xpenology NAS). This time I switched from Intel based systems to an AMD based system. When I install the image (no matter which 6.2.2) image with a 1.04 918+ bootloader, the installation process stops suddenly at 57% or 58 % depending on the 6.2.2 release with the error message " File could not be installed. The file is propably damaged. (13)". I found nothing suitable to this error message. I tested to install the current image from the internet and from a local file - no success. My hardware: Biostar A10N-8800E Ver. 6.1 (Carrizo), Realtek NIC onboard Inline 76617d SATA Controller (Marvell 88SE9230) 1 WD Red 1 TB 2,5" HDD connected to the Biostar MB 1 Seagate Ironwolf 8 TB also connectro to the MB 1 WD Red 3 TB HDD, connected to the Marvell controller all drive are recognized correctly by the controllers (BIOS view) I made no changes on the BIOS except the fan control, and disabled the serial I/O header, because I don't need it. I changed the file grub.cfg of the connected usb drive. The change lines are: VID, PID, changed the last 6 numbers of the SN and MAC section, and changed the SataPortMap to 24 (2x SATA onboard 4x SATA of the controller add-in card) Any ideas? Ps: The Inline Controller Card worked already perfectly on a AMD Kabini NAS build in 2016 with DSM 5.2
  23. Sorry for the late answer. I m still running 6.1.x.... In November I took the latest loader from the link list: And I double checked it again - it was 1.03b That I used - the file is still on my computer. Right, in some kind I was in the wrong sub topic regarding the version - but the fault was the same. Nevertheless I remain sticking to 6.1. as long as possible, perhaps some day a new loader is available. And I am aware that this Xpenology porject is a project of voltuneers ...
×
×
  • Create New...