Dragsdal

I'm afraid I haven't got a backup of the package configuration. 😕 Most of my apps was running as docker containers anyway, and the folder containing all the config-folders for my docker containers is saved, so I guess it's just a matter of creating all the containers again and linking the corresponding config-folder to each. The image in danish basically says that all disks are OK, but warns that I need to run an optimization (data scrubbing ) to ensure data consistency. I kind of feel confident that it won't ruin anything as all the data on storage pool 1 is intact. So yea, it appear to be fixed as far as recovering the data. I just need to reestablish the DSM OS (packaged, docker, etc.). Sincerely, Dragsdal

Hi Peter, Thank you so much for your reply. Following your guide, I am able to update from DSM 7.2.1-69057 to DSM 7.2.2-72806 (This was possible with RR as well to be fair). The problem is however, that it boots right into the DSM 7.2.2-72806 enviroment and does not recognize that I came from a running system on 7.2.1-69057. But there is some good news: the harddrives no longer registers af "System partition failed" but are now all "Healthy". Even more good news is that all my data seems to be avaliable from disk station. The major issue now is, that the entire DMS OS is back to factory default, so all apps (Docker, Resillio Sync, Survelliance Station, etc.) are gone. It's not the worst problem, as I am able to configure everything back again - it's just a time consuming task I'd rather wish I hadn't do. If you or other know a way of recovering the OS configuration I'd appreciate it. But a big thanks to you Peter for helping me out so far. I owe you a beer! Sincerely, Dragsdal

Hi guys, I think I've might have destroyed my installation trying to update, and need some advise. I had DSM 7.2.1 69057-Update 5 running on a HPE ProLiant MicroServer N40L with TCRP 0.10.0 as loader. I previously had succes manually updating through all the updates from DSM control panel, and was comfortable trying that once more as I saw DSM 7.2.2-72806 was avaliable. The update seemed to go fine, but i ran into the infamous infinite recovery loop, which I had experienced before. At the previous time, all I had to do was update the loader, and it usually did the trick. This time there wasn't any update to TCRP so I did some reading and saw that someone had success updating a N40L to DSM 7.2.2-72806 with the RR loader, so I downloaded and flashed it (24.10.3). The upgrade seemed to go fine, but to my horror I wasn't presented with the migrate option, but the "new install process" instead (naming the system, admin user, etc.) When I finally got into DSM it was a brand new setup. Everything was back to factory default, and none of my apps/programs was there. In the drive settings I could see the hard drives, bur each of them is having "System partition failed" as status...! I'm being presented with the option to do a data scrubbing to ensure data consistency but I dare not do it, as I fear of erasing every single hard drive. Can anyone please help, as I'm at the ropes here... Sincerely, Dragsdal

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2.1 69057-Update 4 - DSM version AFTER update: DSM 7.2.1 69057-Update 5 - Loader version and model prior to update: ARC v24.2.21 / DS3622xs+ - Loader version and model before update: ARC v24.2.21 / DS3622xs+ - Using custom extra.lzma: No - Installation type: BAREMETAL – HPE ProLiant MicroServer Turion II Neo, L2 N40L Dual-Core - 16GB RAM - Additional comments: Downloaded manually and updated via DSM Control Panel. No issues.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.0.1-42218 Update 3 - Loader version and model: Tinycore-Redpill v0.9.2.7 (DS3615xs) - Using custom extra.lzma: No - Installation type: Baremetal - HP Proliant Microserver N40L - Additional comments: My previous loader was Tinycore-Redpill 0.4.6 and I initially tried using Automated Redpill Loader 0.5 Alpha 1, but it threw me into an endless booting loop. Nearly having a heartattack thinking my HDDs were wiped/unavaliable, I then tried upgrading to Tinycore-Redpill v0.9.2.7. Luckily that worked.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: Tinycore-Redpill 0.4.6 (ds3615xs) - Using custom extra.lzma: No - Installation type: Baremetal - HP Proliant Microserver N40L - Additional comments: None

Nevermind... The issue seems to have solved itself. Of no apparent reason (no reboot or the sort) all icons suddenly blinked into existence. 🤔

Hej guys, I have a two Xpenology instances running: VMware® Workstation 16 (Virtual) DS918+ DSM 6.2.3-25426 Update 3 Jun's Mod V1.04 HPE Proliant N40L (Bare metal) DS3615xs DSM 6.2.3-25426 Update 3 Jun's Mod V1.03 I have noticed a small but odd difference in how the programs installed from package center are integrated in the main tray menu. For example as shown in the image below, Jackett, Sonarr and Radarr have a shortcut on the 918+, but on the 3615xs they don't. It seems to be the case with all programs that have a webbased UI out of the synology enviroment. I guess the difference could relate to the difference in synology versions, but I think it's odd since they run the same version of DSM. Has anyone an idea why this is, and perhaps a workaround to get these shortcuts in the menu? (I know it's an abysmally small matter, but it really annoys me. ) Thanks! Menu from DS918+ on VMware:

I think it may already have... I found info here: https://xpenology.club/enable-shr-in-dsm-6/

Hi @bearcat! Thank you for a lightning fast response! I feel somewhat stupid as that visual calculator clearly explains why... I should have done my research better before asking. 😳 I'm just glad I posted it in "The Noob Lounge", so I can use that excuse. Thanks again.

Hey guys, First of all thanks for a brilliant forum. I'm pretty new to Xpenology, but in the last few weeks I have learned a great deal about it and have sucessfully run a DSM 6.2.3-25426 with Update 3 on ESXi. I recently accuired a HPE Proliant MicroServer N40L at a bargain, and have sucessfully installed a bare metal DSM 6.2.3-25426 using Jun's Mod V1.03. Initially I had some trouble figuring out how to enable SHR, as it apparently has been deprecated by Synology. After enabling it, the configuration of discs was pretty straightforward, but one thing makes me wonder: Why on earth is the Storage Pool unable to use 34% of the available HDD capacity? (See picture below) I'm aware what some discspace is reserved for the system itself, but seriously: nearly 2TB? Can anybody shed some light? Thanks!