Search the Community

Showing results for tags '6.2.2-24922'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN
    • CHINESE
    • HUNGARIAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 3 results

  1. Hello everyone, I'm running NUTS with my virtual Synology running on vMWare ESXI 6.7 A few months ago, I started to work with the loader on a HP ML350 G5 server. It was brilliant. I've added multiple volumes, one from the SAS 2.5 RAID bay and some other volumes from regular SATA HDD connected directly on the mainboard. It was working fine. I was able to make some backups on the basic volumes. I started the server a few weeks later and I was able to backup again. But yesterday, after a few months with the server shut down, I needed to do another backup. So I boote
  2. Hello, Did some of you found how to get the DSM (6.2.2+) restart and shutdown functions to work correctly? Is there something related to BIOS version(s) or settings? Or the issue is in the DSM software itself? I've updated successfully to 6.2.2-24922-3 on bare-metal systems (both with 1.03b bootloader & DS3615xs and additional HP NC365T Quad Gigabit Intel NIC): HP Microserver G8 with latest BIOS (04/2019). Tried No C-States setting at CPU power management, but behavior is the same HP Microserver G7 N54L with modded BIOS 041 (2013, Kamzata version).
  3. Hallo, erst einmal zur Vorstellung meines Servers: H370m-itx - i5-8400 8GB RAM 6xWD Red 3TB Raid 5 AQ107C von ASUS (Aquantia 10G NIC) Intel 211 und 219 NIC (219V nicht betriebsbereit) Läuft super und gut mit der 6.1.7 unter Zuhilfenahme von Loader 1.02b mit extra.lzma (AQ107 dann funktional) als DS3617xs Nun zum Problem: Sobald ich Loader 1.03b oder 1.04b (1.03b dann als 3617xs, 1.04b als 918+) einrichte und booten will als Test-Setup, kann ich nur booten, wenn ich keine extra.lzma austausche, aber dann funktioniert meine Asus 1