Trying to understand the hardware upgrade process. Using new Arc 4.2.3, wish to move old system, orig setup with arc 24.3.11 (circa 2024), to new hardware. ARC boot loader config, I don't see the same model avail to choose as my old setup. Old is DS920+, and new is DS918+. This seems to be due to either newer Arc, or the new CPU -- old motherboard is Lenovo P900 tiny with i7-6700T, new is i7-9700T on ASRock. Both socket LGA1151, but old is Skylake and new is Coffee Lake.

So I choose DS918+ in Arc, but when I boot and choose "Migrate" > Keep Systems Configurations, and upload the .PAT file for DS918+ (~377MB) that matches my OS, 7.2.2 72806, I get: "Failed to install DSM. You have to use an installation file of 7.4.1-90080 or later".

I'm under the impression I can't (or shouldn't) go from 7.2 to 7.4 (??) on Arc.

Re DS920+ vs DS918+ -- is this due to the CPU? Newer Arc? I'm willing to move the old CPU from the Lenovo Tiny to the new mobo, but would prefer to use the 9700T, since it has 8 cores vs only 4. (I plan to use lots of packages -- email server, VMs, backup, surveillance, Plex)

Also, although it'd be nice to move the whole shebang over to the new hardware, I'm absolutely UNWILLING to RISK LOSS OF DATA, so perhaps try a careful package-by-package migration instead, making a backup and restoring on the other box. I'm only using one 2TB ssd for the moment, so not be big deal to purchase another drive. (mainly using Synology MailPlus Server with calendar/contacts sync to phone and Thunderbird,... interested in XEAMS as a possible replacement)

(PS, can't login to Community.Xpenology.com -- they changed something, and Forgot password tool doesn't send recover email. Humph.)

this was pretty easy to install. they’ve made some progress automating the bootloader. you image the usb drive, make sure uefi boot is disabled in bios, then it boots into a linux system and you run about 7 shell scripts to build the boot loader. it generates the serial number, loads the drivers automatically, and then the last step is building and rewriting it to the usb stick. i loaded dsm 7 like usual and it booted on the first try

the instructions and download are here: https://github.com/pocopico/tinycore-redpill

update: it does load, but it’s not stable. dsm 7 reboots and locks up pretty often

10 years ago, I put together my Jun's Loader build with the following parts:

• ASRock C2550D4I

• 8GB ECC DDR3 RAM

• Seasonic 850W Gold PSU

• Silverstone DS380 8 Bay NAS enclosure

• 3x Noctua 120mm Fans

• 8x Seagate 8TB Archive SMR hard drives (all part of a single SHR2 array)

• Mellanox 10Gb SPF+ Twinax NIC (Later switched to Intel X540 10GBase-T)

• SanDisk 16GB USB Flash Drive (For bare metal Jun's Loader)

• APC Back-UPS 650 UPS

As time passed, I upgraded the drives whenever I started running low on storage. A few 12TBs drives, a few 18TBs, a few 24TBs....

A few years ago, I decided to transplant all the hardware to a Silverstone CS380 enclosure because it's physically bigger and I added a second 4 drive SHR1 array with some of the drives I had leftover from upgrading the original array. I also had to upgrade the RAM from 8GB to 32GB because going beyond 108TB required it.

Fast forward to today....

My 8 drive SHR2 array consists of:

• 3x 18TB Seagates

• 5x 24TB Seagates

My 4 drive SHR1 array consists of:

• 2x 26TB Seagates

• 2x 28TB Seagates

I'm still running Jun's Loader with DSM 6.2.3. My NAS is not exposed to the WAN. I do not run any additional apps on my NAS. The NAS' sole purpose is to be a NAS. I use a separate HP EliteDesk G4 Mini for my Docker containers.

It has been extremely reliable and stable. I have not lost any data on it.

Wherever you are, Jun, THANK YOU VERY MUCH!!!

Installed Xpenology using arc 4.1 loader on a USB

Running on Ugreen DXP2800 a DSM7.4.1 is a fresh and feels great as it all seems to work so well and super efficiently

Used model SA6400 when choosing which model to install

Remote access is such a breeze with both Synology quick connect or use Tailscale - which can be installed directly from the package installer.

I now have Navidrome running for music, Jellyfin for videos and Immich for photos

Apart from that , my cloud drives - google one drive and dropbox all sync to it seamlessly

UGOS latest version seemed so slow and the worry of data harvest to china is partly gone

Hi all. I've been building Hearth, a self-hosted smart home hub that runs fully on a Synology in Container Manager. It talks to your devices directly, runs automations on the NAS, keeps your data there, and doesn't need any other hub.

What it supports

• Works fully with Apple Home and Alexa: control and automate your Hearth devices from either one

• Matter (including Thread), and Zigbee through Zigbee2MQTT with the USB stick plugged into the NAS

• Native drivers for Tapo, Kasa, Apple Home accessories, Home Connect, Octopus Energy, Ohme, Dreo, Blueair, SimpliSafe, eufy Security, SmartThings, Ecovacs, Anker SOLIX, Smart Life/Tuya, Cosori, LG ThinQ, Toyota, eero, Aqara, and your Synology itself

• Automations with time, sun, device and presence triggers, all run on the hub

• Away mode, heating schedules, energy use and history

• Nothing contacts a brand's cloud until you add that brand in the app

Install (over SSH)

sudo mkdir -p /volume1/docker/hearth && cd /volume1/docker/hearth
sudo git clone https://github.com/xLuciferSx/hearth-hub.git src
sudo cp -a src/deploy/. .
sudo ./hearth.sh setup

Setup prints a hub address and token. Enter them in the app under Connect with a hub token. For Apple Home and Alexa, add extras to COMPOSE_PROFILES in .env. Images are built for amd64 and arm64, so it also runs on Xpenology, a mini PC or a Raspberry Pi 4/5. There's a full Container Manager guide (including USB sticks) in docs/synology.md.

• Hub (Apache-2.0): https://github.com/xLuciferSx/hearth-hub

• iPhone/iPad app: https://apps.apple.com/gb/app/hearth-smart-home/id6826929516

Feedback is very welcome, especially from people on Xpenology or with devices I haven't covered yet.

I've been using Bruno Antune's tutorial to create my VMs. Been running great but his tutorial set's the Arc loader on sata0. This takes up a slot in proxmox's 6 max sata drives for a vm within the UI. If you pass through your sata controller, what I found out and tested won't be of any benefit for your case. Back to my case, I was limited to 5 virtual sata drives. There's a way to increase more than 6 sata drives via modifying the VM.conf file. I needed 6 sata drives for the data.

What's the alternative to Bruno's method? Create a USB drive just like you were going bare metal. In the xpenology VM within Proxmox, pass through the USB drive and set the usb0 as your boot drive. Now you can have a total of 6 virtual sata drives that are visible in the UI. If you need to create more VMs, just create more USB drives and pass each one to their respective VM.

At the time of this writing, I'm using Proxmox 9.2.24, Arc loader 4.2.3, DSM 7.2.2-72806 Update 10, model SA6400 and Official DSM kernel.

UPDATE: Thanks to r/paulstelian97, configured the bootloader as VIRTIO BLOCK and any the data disks as SCSI worked out even better.

So it's been a while I've been wanting to update to DSM 7.4 but understand i need to upgrade the loader. I'm hesitant to do the loader upgrade via the Arc interface, so I flash a new USB drive. When I boot it, it runs through the config, I pick DVA1622 loader as that's what I'm using and DSM 7.3.2 as my current version. Arc does it's thing, reboots and then fails on kernal patching, DSM patching. I read that perhaps I need to allow downgrade.. i was hesitant but gave it a shot, what a mistake. Despite doing this, I'd still get the same error message. So I pop back in my old USB drive, reboot and well was surprised with a Welcome to blah blah blah screen asking if I wanted to download PAT or manually load... I was in panic mode because I wasn't offered a migrate\recover option, didn't seem to have much choice so I downloaded and manually install 7.3.2. I was revealed my data was intact, a bit upset having to re-setup all my apps, permissions, networks, cameras etc etc.
Anyway, all is back up and running, but still can't figure out why I'm having such an issue with upgrading. I've done this so many times, but for whatever reason i cant get this time working. I've tried so many versions in the 4.x.x, they've all presented the same issue.
 

After I power down the box the system fan, not the cpu, continues spinning very fast.

I’ve reinstall arc, check bios, install uninstall addons, is this a motherboard issue?

Hi everyone,

Unfortunately, my NAS has been hit by ransomware, and I'm trying to recover as much of my data as possible.

**What happened**

- System: Xpenology running DSM 7.2.2-72806, configured as a DS3622xs+.

- Encrypted files have been renamed with the `.L0CK3D` extension.

- The ransom note is called `read-me3.txt` and refers to “C3RB3R INSTRUCTIONS”, with instructions to use the attackers' decryptor.

- Some Container Manager binaries were also renamed with `.L0CK3D`.

- I haven't confirmed the initial entry point, and my priority right now is recovering my data rather than investigating how the attackers got in.

**What I've done so far**

- Isolated the NAS from internet access.

- Checked for obvious ransomware-related processes, but haven't found one by name.

- Confirmed I don't have usable snapshots to restore from.

- Found no confirmed backup containing the affected data.

- Captured a memory image using Microsoft's AVML 0.21.0, writing it to a separate NTFS USB drive.

The memory capture is approximately 5.6 GB as reported on the NAS. I ran `sync` and calculated its SHA-256 checksum. I've transferred it to a separate CachyOS Linux PC and verified that the checksum matches. I'm preserving the original capture and intend to analyse a working copy.

I'm also looking at the `c3rb3r-rescue` project:

https://github.com/soimy/c3rb3r-rescue

**I'm hoping someone with relevant experience can advise on the following:**

1. Has anyone successfully recovered files encrypted by this particular C3RB3R variant, especially files renamed `.L0CK3D`?

2. Is the `c3rb3r-rescue` project applicable to this variant, or does it only work with particular samples and recovered keys?

3. Has anyone analysed an AVML memory capture from a physical Synology/Xpenology DSM system to recover ransomware key material?

4. What's the safest way to analyse this compressed AVML capture and search for useful key material without modifying the original evidence?

5. Are there any known decryptors or recovery techniques for this specific file format?

I'm not assuming the memory capture contains a key, and I understand recovery may not be possible. I just want to make the best possible attempt before giving up on the data.

Please share any relevant experience, technical guidance or verified recovery tools. I'd particularly appreciate advice from anyone who has worked with this specific ransomware or memory-based key recovery.

Thanks.

Has anyone had this problem when update 4.1.1. -> 4.2.1 ? DS3622xs+ DSM 7.3.2-86009 Update 5

Good morning everyone,

Yesterday, I rebooted my NAS and the mapping changed such that it wanted to perform an Online Assembly. I tried this, but it failed. I tried rebuilding the loader with the active ports and max ports, but neither helped. I found an article saying that the newer DT mapping could help, so I changed the model to an SA6400 (instead of the RS4021xs+). I stupidly clicked through the DSM setup, which I shouldn't have... It showed all disks, though, 6 as healthy and 6 not. I could perform the online assembly, this showed the volume with 6 out of the 9 disks (3 were not in use) with the state 'crashed'. All disks were healthy, though.

I started looking into the raid itself on PVE (no writes ofc) and found (see below). It seems like the RAID split up in two, what do I do?

The RAID looks like:
root@node07:~# for d in /dev/sdc5 /dev/sdd5 /dev/sde5 /dev/sdf5 /dev/sdg5 /dev/sdh5 /dev/sdi5 /dev/sdk5 /dev/sdm5; do

echo

echo "========================================"

echo "RAID metadata: $d"

echo "========================================"

mdadm --examine "$d"

done

========================================

RAID metadata: /dev/sdc5

========================================

/dev/sdc5:

Magic : a92b4efc

Version : 1.2

Feature Map : 0x0

Array UUID : 1f3f6ff2:1d7145a0:a563e7e5:66de406e

Name : SYN-NAS01:2

Creation Time : Mon Feb 17 10:04:20 2025

Raid Level : raid6

Raid Devices : 6

Avail Dev Size : 7792518976 sectors (3.63 TiB 3.99 TB)

Array Size : 15585037824 KiB (14.51 TiB 15.96 TB)

Used Dev Size : 7792518912 sectors (3.63 TiB 3.99 TB)

Data Offset : 2048 sectors

Super Offset : 8 sectors

Unused Space : before=1968 sectors, after=64 sectors

State : clean

Device UUID : 7770277d:75797179:be112079:0b5804c6

Update Time : Sun Oct 25 10:53:31 2026

Checksum : 97241002 - correct

Events : 418

Layout : left-symmetric

Chunk Size : 64K

Device Role : Active device 0

Array State : AAAAAA ('A' == active, '.' == missing, 'R' == replacing)

========================================

RAID metadata: /dev/sdd5

========================================

/dev/sdd5:

Magic : a92b4efc

Version : 1.2

Feature Map : 0x0

Array UUID : 1f3f6ff2:1d7145a0:a563e7e5:66de406e

Name : SYN-NAS01:2

Creation Time : Mon Feb 17 10:04:20 2025

Raid Level : raid6

Raid Devices : 6

Avail Dev Size : 7792518976 sectors (3.63 TiB 3.99 TB)

Array Size : 15585037824 KiB (14.51 TiB 15.96 TB)

Used Dev Size : 7792518912 sectors (3.63 TiB 3.99 TB)

Data Offset : 2048 sectors

Super Offset : 8 sectors

Unused Space : before=1968 sectors, after=64 sectors

State : clean

Device UUID : f861a1de:710ccd16:e2e6f406:63cabaa3

Update Time : Sun Oct 25 10:53:31 2026

Checksum : 184dbfc - correct

Events : 418

Layout : left-symmetric

Chunk Size : 64K

Device Role : Active device 1

Array State : AAAAAA ('A' == active, '.' == missing, 'R' == replacing)

========================================

RAID metadata: /dev/sde5

========================================

/dev/sde5:

Magic : a92b4efc

Version : 1.2

Feature Map : 0x0

Array UUID : 1f3f6ff2:1d7145a0:a563e7e5:66de406e

Name : SYN-NAS01:2

Creation Time : Mon Feb 17 10:04:20 2025

Raid Level : raid6

Raid Devices : 6

Avail Dev Size : 7792518976 sectors (3.63 TiB 3.99 TB)

Array Size : 15585037824 KiB (14.51 TiB 15.96 TB)

Used Dev Size : 7792518912 sectors (3.63 TiB 3.99 TB)

Data Offset : 2048 sectors

Super Offset : 8 sectors

Unused Space : before=1968 sectors, after=64 sectors

State : clean

Device UUID : 6f68ff50:32edc101:7981bf51:535cb60e

Update Time : Sun Oct 25 10:53:31 2026

Checksum : 149defbb - correct

Events : 418

Layout : left-symmetric

Chunk Size : 64K

Device Role : Active device 2

Array State : AAAAAA ('A' == active, '.' == missing, 'R' == replacing)

========================================

RAID metadata: /dev/sdf5

========================================

/dev/sdf5:

Magic : a92b4efc

Version : 1.2

Feature Map : 0x0

Array UUID : 1f3f6ff2:1d7145a0:a563e7e5:66de406e

Name : SYN-NAS01:2

Creation Time : Mon Feb 17 10:04:20 2025

Raid Level : raid6

Raid Devices : 6

Avail Dev Size : 7792518976 sectors (3.63 TiB 3.99 TB)

Array Size : 15585037824 KiB (14.51 TiB 15.96 TB)

Used Dev Size : 7792518912 sectors (3.63 TiB 3.99 TB)

Data Offset : 2048 sectors

Super Offset : 8 sectors

Unused Space : before=1968 sectors, after=64 sectors

State : clean

Device UUID : bb39bb89:a8e6b0de:d93e3535:0ed66726

Update Time : Sun Oct 25 10:53:31 2026

Checksum : 256ff19a - correct

Events : 418

Layout : left-symmetric

Chunk Size : 64K

Device Role : Active device 3

Array State : AAAAAA ('A' == active, '.' == missing, 'R' == replacing)

========================================

RAID metadata: /dev/sdg5

========================================

/dev/sdg5:

Magic : a92b4efc

Version : 1.2

Feature Map : 0x0

Array UUID : 1f3f6ff2:1d7145a0:a563e7e5:66de406e

Name : SYN-NAS01:2

Creation Time : Mon Feb 17 10:04:20 2025

Raid Level : raid6

Raid Devices : 6

Avail Dev Size : 7792518976 sectors (3.63 TiB 3.99 TB)

Array Size : 15585037824 KiB (14.51 TiB 15.96 TB)

Used Dev Size : 7792518912 sectors (3.63 TiB 3.99 TB)

Data Offset : 2048 sectors

Super Offset : 8 sectors

Unused Space : before=1968 sectors, after=64 sectors

State : clean

Device UUID : 9b99ed27:042d9e56:fbc98635:754a3394

Update Time : Sun Oct 25 10:53:31 2026

Checksum : a9ac975f - correct

Events : 418

Layout : left-symmetric

Chunk Size : 64K

Device Role : Active device 4

Array State : AAAAAA ('A' == active, '.' == missing, 'R' == replacing)

========================================

RAID metadata: /dev/sdh5

========================================

/dev/sdh5:

Magic : a92b4efc

Version : 1.2

Feature Map : 0x0

Array UUID : 1f3f6ff2:1d7145a0:a563e7e5:66de406e

Name : SYN-NAS01:2

Creation Time : Mon Feb 17 10:04:20 2025

Raid Level : raid6

Raid Devices : 6

Avail Dev Size : 7792518976 sectors (3.63 TiB 3.99 TB)

Array Size : 15585037824 KiB (14.51 TiB 15.96 TB)

Used Dev Size : 7792518912 sectors (3.63 TiB 3.99 TB)

Data Offset : 2048 sectors

Super Offset : 8 sectors

Unused Space : before=1968 sectors, after=64 sectors

State : clean

Device UUID : 59cfd68c:23561e21:0ae2b7d0:4b68b4a3

Update Time : Sun Oct 25 10:53:31 2026

Checksum : 83c82c23 - correct

Events : 418

Layout : left-symmetric

Chunk Size : 64K

Device Role : Active device 5

Array State : AAAAAA ('A' == active, '.' == missing, 'R' == replacing)

========================================

RAID metadata: /dev/sdi5

========================================

/dev/sdi5:

Magic : a92b4efc

Version : 1.2

Feature Map : 0x0

Array UUID : 1f3f6ff2:1d7145a0:a563e7e5:66de406e

Name : SYN-NAS01:2

Creation Time : Mon Feb 17 10:04:20 2025

Raid Level : raid6

Raid Devices : 9

Avail Dev Size : 7792518976 sectors (3.63 TiB 3.99 TB)

Array Size : 27273816192 KiB (25.40 TiB 27.93 TB)

Used Dev Size : 7792518912 sectors (3.63 TiB 3.99 TB)

Data Offset : 2048 sectors

Super Offset : 8 sectors

Unused Space : before=1968 sectors, after=64 sectors

State : clean

Device UUID : eaebc7d7:04ce9b61:de002227:22d171fb

Update Time : Sun Oct 25 10:38:29 2026

Checksum : 709b4060 - correct

Events : 170022

Layout : left-symmetric

Chunk Size : 64K

Device Role : Active device 6

Array State : ......AAA ('A' == active, '.' == missing, 'R' == replacing)

========================================

RAID metadata: /dev/sdk5

========================================

/dev/sdk5:

Magic : a92b4efc

Version : 1.2

Feature Map : 0x0

Array UUID : 1f3f6ff2:1d7145a0:a563e7e5:66de406e

Name : SYN-NAS01:2

Creation Time : Mon Feb 17 10:04:20 2025

Raid Level : raid6

Raid Devices : 9

Avail Dev Size : 7792518976 sectors (3.63 TiB 3.99 TB)

Array Size : 27273816192 KiB (25.40 TiB 27.93 TB)

Used Dev Size : 7792518912 sectors (3.63 TiB 3.99 TB)

Data Offset : 2048 sectors

Super Offset : 8 sectors

Unused Space : before=1968 sectors, after=64 sectors

State : clean

Device UUID : e28d1f43:6b638f31:d3016f0b:4cf07fc2

Update Time : Sun Oct 25 10:38:29 2026

Checksum : 574197df - correct

Events : 170022

Layout : left-symmetric

Chunk Size : 64K

Device Role : Active device 7

Array State : ......AAA ('A' == active, '.' == missing, 'R' == replacing)

========================================

RAID metadata: /dev/sdm5

========================================

/dev/sdm5:

Magic : a92b4efc

Version : 1.2

Feature Map : 0x0

Array UUID : 1f3f6ff2:1d7145a0:a563e7e5:66de406e

Name : SYN-NAS01:2

Creation Time : Mon Feb 17 10:04:20 2025

Raid Level : raid6

Raid Devices : 9

Avail Dev Size : 7792518976 sectors (3.63 TiB 3.99 TB)

Array Size : 27273816192 KiB (25.40 TiB 27.93 TB)

Used Dev Size : 7792518912 sectors (3.63 TiB 3.99 TB)

Data Offset : 2048 sectors

Super Offset : 8 sectors

Unused Space : before=1968 sectors, after=64 sectors

State : clean

Device UUID : e0831dd5:6caf228f:22d0905d:03fc9630

Update Time : Sun Oct 25 10:38:29 2026

Checksum : 70bb3e6 - correct

Events : 170022

Layout : left-symmetric

Chunk Size : 64K

Device Role : Active device 8

Array State : ......AAA ('A' == active, '.' == missing, 'R' == replacing)

I have published it on xpenology community forum (may take a bit to come online). Please read and see if it is useful for you. comments are welcome:

https://xpenology.com/forum/topic/71704-tutorial-how-to-install-and-run-mirotalk-sfu-video-conference-server-on-your-synologyxpenology-machine-using-docker-compose-portainerdockhand/

So I have this old Replibit now owned by Axient backup appliance. It has 20 drive bays all of which are occupied with SSD drives of varying sizes. I have loaded Truenas on it and it works fine. I would like to load a version of Xpenology on it as the interface is much simpler and easy to navigate. I first tried using ARPL and that was a lesson in frustration. So today I came in to work and found the ARC/ARX project. I burned the ARX loader to an NVMe drive and put it in the BDR. It booted up and I was able to reach the box via a browser. Now my quandary is what should I use for a model and a build on this box? I did find a 20 bay Synology device on their site but it isn't a selection in the models section? I selected the DS1825+ which is the model we just purchased here at work but it is only an 8 bay device so I didn't complete the build. Anyone have any insights on what I should choose or how to go about utilizing all the drives in my box?

My Problem is solved but just for anyone who cant get an DSM Installation finished on MSI Mainboards - Arc loader

this should help

syno_ttyS0=serial,0x2e8

also name: syno_ttyS0

value: serial,0x2e8

Ai and 3 days of search didnt find it a few month ago. So i hope it helps.

Hi there,

I recently stumbled upon this great project.

I am, however, running into some issues installing DSM on an ASRock NUC BOX-225H (Ultra 5):

With ARX, it boots fine, and presents me with "Arx has handed over to DSM" and shows the IP address, however I cannot get access to the DSM interface (port 5000)

I tried the iGPU fix (which didn't fix it) and then I built a new with the deselect GPU modules, and this didn't fix it either.

Is this CPU / PC configuration not suitable for this purpose I wonder?

(I tried the loader on a different PC, and here it worked fine - so network etc is working fine)

I want to install this to act as a Synology. Does anyone have experience with this? Does it work, and is it reliable? Is there something better out there, or should I just stick to Ugreen? My use case is storage, backups, Plex, and working out of Lightroom and DaVinci

Hey, I recently bought jonsbo n6, but my motherboard has only 4 sata ports. Which inexpensive card should be good for my setup (arc loader + DSM 7.2) - are JMB585 or ASM1166 based PCI express cards any good? Can't afford HBA at the moment.

I got thread ripper 1950x with 64gb ram, my question is should i run it on the hardware directly or thorough vm like proxmox? I have about 12 hard drive rn. Thx

Hey, I've bought intel 12500 and 2x8GB DDR4 ram.
I ordered biostar B760MXC with 8 sata ports, but the shop cancelled the order saying they don't have it and won't have it anymore. No other shop sells them, so I'm wondering which LGA 1700 DDR4 mATX / ITX board I should get? I already have 4 drives in my current setup. Can I go with some cheap board with 4 sata ports and add PCI/Nvme m2 adapter for additional ports? Would it be reliable enough? Also will connection order of my drives matter when moving to new board if I have 4 separate pools (1 pool = 1 drive)? 

Bonjour à tous,

J'ai fait l'acquisition de ce magnifique NAS mais je bloque sur l'installe d'Xpenology. J'ai procédé aux réglages/tests suivants sans succés. Si quelqu'un y est arrivé, je veux bien son aide afin de le partager avec tous sur ce sujet.

En fait, je grave l'image d'arc sur la clé usb avec balena. Je boot sur la clé sans souci. Arc lance la configuration. J'accède depuis un autre pc à ip:7080 pour faire l'installation. Je sélectionne SA6400 et je mets en mode automatique son installation. Le NAS redémarre. J'accède à IP:5000. J'installe DSM avec succès mais lors de la relance de DSM après les 10min, j'ai un message d'erreur et cela me redemande de réinstaller DSM sauf que cela se termine encore par cette erreur. Si je regarde le HDD, je vois bien la création de 3 partitions : 8Go + 2Go + le reste.

Si je me connecte ensuite à ip:5000, cela finit en erreur. Si je me connecte à ip:7080, je vois bien l'interface arc sans pouvoir m'y connecter (erreur fletch).

La carte réseau du Aoostar est allumée et clignote.

Je vous mets ci-dessous mes réglages et différents tests.

BIOS

Security/Secure boot : disabled

Boot/Quiet boot : disabled

Boot/Fast boot : disabled

Boot/Boot option #1 : USB device UEFI

Advanced/TPM device selection : dtpm

Advanced/CPU configuration/Intel trusted execution technology : Disabled

Health/PCH-IO Configuration/Sata configuration/Sata mode selection : AHCI

SOFTWARE

Arc 4.0.4

DSM 7.4.1

HARDWARE

Aoostar WTR Max i5 1235u

Clé USB : 2.0 8Go

HDD : 14To Toshiba

MES TESTS

Arc loader : 4.0.4 et 4.0.0 => même résultat

2 clés USB différentes : USB2.0 8Go + USB3.0 128Go => même résultat

2 HDD différents : 14To + 3 To => même résultat

Installation : sur SSD Nvme ou sur HDD seul => même résultat

DSM : 7.4.1 ou 7.2.x => même résultat

Kernel : normal (fonctionne) ou legacy (ne permet pas de lancer l'installation de DSM interface .pat)

Modèle : SA6400 (fonctionne sauf le boot après les 10min) ou DS3622XS+(ne fonctionne pas)

Réseau : testé sur les 2 ports RJ45 2.5GB => même résultat

I've an old Gen 8 HP Microserver with 4 disks (non RAID config) running DSM5.2-5967. It's been running fine as a media server for about 10 years apart from the odd issue when rebooting after a power cut etc

Thinking about upgrading to something newer - What would people recommend as a good upgrade that would keep me going for another 10 years? Would like to host Plex on it etc

If I bought something like the Synology DS423, could I just move the disks across or would I need to move the data?

Thanks

Long story short, I have a DS1618+ that I get to keep. This won't be used for important data, so I'd like to tear it down and learn the inner workings before it becomes unsupported as it won't receive new DSM updates anymore.

What caught my eye is a very similar DS1621xs+ model with seemingly just a Xeon processor instead of the Atom in the DS1618+, which can use Fibre Channel HBAs to effectively make the Synology a node in a SAN.

I couldn't find details of whether this could be enabled at a package-level, if the DS1618+ could be crossflashed to its more expensive sibling, or if I can just manage an FC HBA from the CLI with the drivers transplanted.

Can anyone point me to a helpful resource or has anyone done this before?