Hostilian

Can't edit the above. Looks like it's RESTARTING after the Shutdown. So it is shutting down on schedule - and then coming back up again. 🙄 There is no startup schedule at all, so I am not sure why it's starting up again!! Any ideas?

Anyone having issues with Scheduled Shutdown? Hardware and Power - Power Schedule - and create some shutdown tasks. They they appear in Task Scheduler. However, they do not shut down the server! Any ideas please?? Do I need to do this via Script instead? ARPL rr-23.11.7 (think it's that one) on Bare Metal. Previous versions (and 2a) worked fine. Thanks

Surprise surprise, it's now worked..

If anyone else is interested. I tried to clean up my system partition - and cleaned up a lot of logs (almost every log archive marked .xz) and other files. df -h (putty) showed I had a total system partition size of only 2.5GB. With free space only about 500MB. Doesn't sound like an awful lot.. Tried again with the newest loader. Didn't work. Just said there was an issue with the download - corrupt or whatever. I KNOW that it works on this sytem, as I had tested it with a new single SSD. Installed fine. Put in my original loader USB drive and rebooted. Said I needed to reinstall DSM. Oh sh*t. It said that it formatted the system partition - and continued to install the old DSM version that I used to have installed. Thankfully the data was fine. I restored a configuration backup and all is good. Checked the system partition again (after the system partition was reformatted) and now it's 7.9GB.. Basically tripled in size. So I guess any upgrades will work fine now.. 😜

I've been back in and cleaned up a LOT of log archives, any obvious system image files (for the updates) - and it's got some more room on the system partition. What I don't know is where any not so obvious files would be placed - and how far I can go when it comes to cleaning stuff out..

I can't get into DSM apart from at the limited install menu, SSH using putty or at the server itself. In /Addons I can find some large tgz files. Are these OK to remove? They look like old versions (with the exception of 7.2). eudev-7.2.tgz eudev-7.1.tgz eudev-6.2.tgz I can't see anything in /root (says 'for system use only'). Is this the loader Im conneted to? Loader has 'syno_hdd_detect=0' - not sure if that's relevant? edit. I've plugged back in my previous loader USB drive and I'm back in again to my DS3615. It didn't change anything. I'll try a more thorough cleanup before attempting this again. Motherboard is Asus H87i plus. Anyone any success with this - 6 HDDs - with ARPL 18i?

Hey guys Update of my system using a new ARPL loader - i18 latest version. 4th gen i3 CPU. Trying to build 2422, have booted file and connect to web interface. Selected to migrate my disks and information. It downloads the PAT file but then comes up with the error above "Available system space is insufficient" I was prepping the machine yesterday in advance of this. Had issues with system space when installing Packages, so I cleaned up a lot of logs. Rebooted fine and was working OK. Obviously not enough stuff has been cleared out of System... I tried the 3622 first (think it was that one - as was coming from ds3615), but that didn't work. Not sure if it's got the PAT file sitting on the system partition? Questions. How do I clean up my system partition please? I can Putty into the server, can connect to the web interface and obviously have the console direct to the server.. Many thanks!

Hi. I've had a look and the 10.5 update is only from 23.10.4 to 23.10.5 (so the script says). The other doesn't look to have any 'update' information. One of my boxes is on the 23.7.1 loader. I can't see notes for updating on the vast majority of the release pages, which is why I am asking. There's just that update.zip file present. It's not a big issue, just wondering whether there was a simple upgrade path. If not, I'll just replace the loader and reconfigure as I've been doing.

Would also like some pointers for this. I've previously just rebuilt the loader on another flash drive and then let the 'new' system recognise the drives etc - then import the configuration. There is an update.zip on the ARPL 18n github page, but I can't see any guides on what to do with it - and whether you can easily update?!

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1 U3, I think. - Loader version and model: ARPL-i18n 23.7.1 / DS920+ - Using custom extra.lzma: NO - Installation type: VMware ESXi 7 U3 - Additional comments: OK so I didn't realise that the old ARPL loader no longer worked. Tried that. Failed. It was a VM and I had copied and snapshotted everything, so wasn't too bothered. Used the new loader by attaching the image as a new disk, replacing the old loader disk. Booted and configured it again. Rebooted and it migrated data and settings "to the new server" and was back up again. Working well!

Check the MAC address hasn't changed in the Network Interface.

You shouldn't lose data. I've done a few of them with no data loss (6.2.3 to 7.1.1). One lost the DSM config, but no actual data loss at all. Back up your data and configuration, just in case! I'd go with the same model and then you can choose whether to try changing the model once you've upgraded to the latest DSM - it'll think you've moved the disks to a new model! Yeah, latest ARPL, build loader (after selecting model, serial etc) and give it a go. If it doesn't work and you need any addons, choose them before building the loader. You can always recreate the loader and try again (I did one of mine a few times) without data loss.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3 - Loader version and model: ARPL 1.0 Beta 2 - Using custom extra.lzma: NO - Installation type: DS220. Bare Metal upgrade from Jun's loader. ASRock J3455 integrated cpu. Integrated realtek NIC. - Additional comments: Took a very long time to get a usable IP address. Install of DSM failed with 'failed to connect' and when the IP was pingable again it said that I needed to reinstall DSM. Did the same again, but no joy. Tried DS218 install. Same issue. Reinstalled DSM 220 and after waiting for about 30 minutes, I got a pingable IP address and could access the console. Success, this time round. It lost my previous DSM configuration info but kept the files..

Anyone any luck getting this to work with an ASROCK J3455-ITX board? Tested with DS920 and despite finding an IP via DHCP, it's not appearing via the web interface (or ping). Then tried DS918 and I was able to get to the web console to install DSM, but it had an error, then lost connectivity for a while after reboot. Not able to connect to the console. Then it came back saying I needed to format and install DSM again (hopefully just DSM, rather than the files - though they're backed up). Another DSM install didn't work either.. edit. a few minutes later.. DS220 Just started pinging after about 10 minutes sitting there doing nothing. Will see what happens after another DSM Install... Well. It failed again and after trying to reconnect, said it needed to format the system partition and re-install DSM.. Another reinstall, then a very long wait and it looks to be working. It must have been 30 minutes before it came back online - Kept the files, but it lost the configuration though.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3 DS3615 - Loader version and model: ARPL 1.0 Beta 2 - Using custom extra.lzma: NO - Installation type: Bare Metal upgrade from Jun's loader. 4th Gen i3 CPU, intel Dual port NIC and onboard NIC. - Additional comments: Created loader on NAS, rebooted. Didn't get IP initially, but got one after waiting for a minute or two. Went to URL to install DSM. Detected previous install (I went for same DS3615) and chose latest 7.1.1. Downloaded and updated automaticaly. Took 5-10 mins then reboot. No issues so far. Data has been retained and confirmation too..