turbolars
-
Posts
4 -
Joined
-
Last visited
Posts posted by turbolars
-
-
- Outcome of the update: SUCCESSFUL
- DSM version prior update: DSM 7.1.1-42962 Update 5
- Loader version and model: TinyCore RedPill v0.9.4.6 with Friend - DS3622xs+
- Using custom extra.lzma: NO
- Installation type: Vmware ESXi 8.0- Additional comments: updated from tinycore 09.4.3, replaced rp image in vmconfig, rebuild, start, dsm detected move nas, pat install, done.
-
18 hours ago, dodo-dk said:
@turbolars do you use acpid (powerbutton) on 3617? I have test it and it don't work with Proxmox. Or I do something wrong. on 918 and 3615 it works.
Ah ******* I notice that now I rarely use powerdown or restart on the esxi host but indeed, Power off and restart via esxi does not work. Power down in xpenology no problemo. will add this to known issues
I installed open-vm-tools from open-vm-tools 7.0.1 found that one on openos.org
that is the only one that actually works. but it doesnt solve the power down / restart issue in esxi.
16 hours ago, john_matrix said:Thanks for the feeback
Is it still required to disable Internet connection during the installation/migration?
Yes I did disconnect the nic via esxi when dsm installing started and waited for 5 minutes. However there is currently no update available so i really cant say if it's necessary or not. I just thought better safe then sorry will test on a new machine next week or so.
-
1
-
1
-
-
Finally got a 3617 (broadwell) running prod on Vmware esxi 7 using multiple vlans, hyperb,synodrive, dns, vpn, smb
Lessons learned and experience.
Disk write issues -> Needed to convert the vmdk with v2v in order to make it sata writable (without convert only readable via IDE interface esxi config could not be written strange errors and disk failure when installing dsm.)
After disks reassignment in esxi and assignment in synology had to “repair” them, which went very fast and without issues.
SMB issues -> users got access denied on smb shares. Synology added the SMB service as an application for access. The group users didn’t had default access on SMB. (my other synology boxes updated via control panel to dms7 did give default user group access to SMB) this issues costed
Config restore issues – Couldn’t get my packages back, had to redownload on dsm7, but import setting successful, network interfaces on different numbers but in esxi in the same order. Restore config didn’t restore all settings, Just check all your settings!
Synodrive had to upload all files to my other synology devices like they had been changed after the migration but done with success.
So, running for a couple of days stable …. thanks pocopico ! for creating such an easy working loader. Never got the redpill from thor working because of issues and time.
DSM 7.2-64570 Update 2
in DSM Updates Reporting
Posted
https://www.synology.com/en-us/releaseNote/DSM?model=DS3622xs%2B
Version: 7.2-64570 Update 2
(2023-07-24)
Important notes
Your Synology NAS may not notify you of this DSM update because of the following reasons. If you want to update your DSM to this version now, please click here to update it manually.
Your DSM is working fine without having to update. The system evaluates service statuses and system settings to determine whether it needs to update to this version.
Depending on your Synology NAS model, this update will restart the device.
Fixed Issues
1. Fixed an issue where deleting snapshots through Snapshot Replication on the destination server might cause unused memory to not be released properly.
2. Fixed an issue where certain models might experience unsuccessful replication with Snapshot Replication after updating to DSM 7.2.
3. Fixed an issue where users signing in to DSM through Synology SSO might be unable to open Synology Office files.
4. Fixed an issue where the system might be unable to send test emails when Synology Account is configured to receive notifications.
5. Adjusted the suggestions generated by Western Digital Device Analytics (WDDA).
6. Fixed an issue where certain models might not display the corresponding storage pool after creating a volume.
7. Fixed an issue where the warning for checksum mismatch did not provide the file path for the files containing the error.
8. Fixed a security vulnerability regarding Ghostscript (CVE-2023-36664).
Notes:
This version is released in a staged rollout.