justinavril

Can PX6-300d or PX4-300d support 7.2?

Same HW, how did you upgrade to DSM 7.2? I'm running DSM 7.1-42661 Update 1 right now.

Just check the vmware site, seems like I cannot take the live snap with system's power-on while direct path IO is configured.

I have done the installation, but still could not take a snap while the VM's running. I used the active backup for business and it returned some useful error message, related to 'direct path IO'. I remember that I have direct path the drives to the ESXi server. So in this scenario, I cannot take the snap?

I will try vm-tools. The dsm version is 'DSM 7.1-42661 Update 1' on 'synology_broadwellnk_3622xs+', so I should install 'open-vm-tools-12_broadwellnk-7.1_12.2.0-1.spk', correct?

I'm using Veeam to backup the syno VM via a vCenter backup job. There're 4 VMs in the backup job. 3 VMs including the syno VM are running and 1 VM is power-off. But only the syno VM backup sub-job failed. I cannot take a live snap while syno VM is power-on. Why it's failed or what makes it different? Thanks!

@Peter Suh I will try the upgrade process on the VM of Gen 8 after taking a snap Just in case~ I assume the process should be the same.

So the steps are: 1. Build the jot mode builder; 2. Boot to the system, use DSM GUI to install 42962 U0 pat file and small updated; 3. Go to menu.sh and run the post update. right?

So after running menu.sh, I should choose 'j' to build jot mode loader and then 'p' to run post update for jot mode, right? Then, I can directly upgrade 'DSM 7.1.1-42962 Update 3' using the pat file via DSM GUI? BTW, I also check the DSM support pages and it says I should upgrade by the sequece. Should I ignore it?

Just check my post about half year ago. My loader should be RedPill DS3622xs v7.1.0-42661. Posted June 24, 2022 - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 5.0-4493 Update 7 as DS3612xs - Loader version and model: RedPill DS3622xs v7.1.0-42661 - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP N54L Gen7 - Additional comments:

Just want to check the upgrade path vi DSM GUI from 'DSM 7.1-42661 Update 1' to 'DSM 7.1.1-42962 Update 3' works fine, right? I should download the pat file and upload it in the DSM GUI to the upgrade. BTW, I have 2 devices, HP Gen7 Bare Metal and VM on HP Gen8 running ESXi. Thanks!

I didn't set VPN in TinyCore, but by hacking the wifi router to OpenWRT.

By using VPN to access github.

What is the model number of LSI HBA? LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072]

How about this: 1. Shut down the machine and plug out all the disks and remember the orders, just in case; 2. Reboot to DSM USB; 3. Use the assistant to find the NAS. Should return no disk error, right? 4. Plug in 1 disk, and retry it in the assitant;

@billat29 Done~

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 5.0-4493 Update 7 as DS3612xs - Loader version and model: RedPill DS3622xs v7.1.0-42661 - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP N54L Gen7 - Additional comments: Thanks for @billat29 & @Peter Suh's great helps! I have fresh installed v7 on Gen7 by using a new USB drive and HDD with DSM v5 data. Make sure 'C1E is disabled in the BIOS' before booting to 'RedPill DS3622xs v7.1.0-42661 Beta (USB, Verbose)' on N54L Gen7. After validating the data on HDD is migrated correctly. I plugin the rest disks back to Gen7 and all the data is back there. For sure, the apps and configurations in v5 should be manually installed/restore in v7, which is very straight-forward.

I have one ix4-200, which is an ARM based CPU. Very old version. I guess probably no chances.

I check it out and there's no .xpenoboot folder under root path. I have put the other 3 disks back and everything is there. But I have to re-install some apps and restore their configurations manually. Now, it's a N54L with v7 installed~ Thanks again! justinwu@JustinSynoNAS:/$ ls -lart total 104 drwxr-xr-x 2 root root 4096 Apr 1 18:01 mnt drwx------ 2 root root 4096 Apr 1 18:01 lost+found drwxr-xr-x 2 root root 4096 Apr 1 18:01 initrd drwxr-xr-x 12 root root 4096 Apr 25 20:15 usr drwxr-xr-x 20 root root 4096 Jun 14 21:49 volume1 drwxr-xr-x 8 root root 4096 Jun 14 21:49 volume2 drwxr-xr-x 9 root root 4096 Jun 14 21:49 volume3 drwxr-xr-x 3 root root 4096 Jun 22 00:47 .syno lrwxrwxrwx 1 root root 7 Jun 22 00:50 bin -> usr/bin lrwxrwxrwx 1 root root 7 Jun 22 00:50 lib64 -> usr/lib lrwxrwxrwx 1 root root 9 Jun 22 00:50 lib32 -> usr/lib32 lrwxrwxrwx 1 root root 7 Jun 22 00:50 lib -> usr/lib lrwxrwxrwx 1 root root 8 Jun 22 00:50 sbin -> usr/sbin drwxr-xr-x 12 root root 4096 Jun 22 00:50 var.defaults -rw------- 1 root root 1024 Jun 22 00:50 .rnd drwxr-xr-x 2 root root 4096 Jun 22 00:51 .old_patch_info drwxr-xr-x 2 root root 4096 Jun 22 00:51 .system_info drwx------ 2 root root 4096 Jun 22 00:56 root dr-xr-xr-x 277 root root 0 Jun 22 22:29 proc drwxr-xr-x 3 root root 4096 Jun 22 22:29 .log.junior drwxr-xr-x 42 root root 4096 Jun 22 22:29 etc.defaults dr-xr-xr-x 12 root root 0 Jun 22 22:29 sys drwxr-xr-x 12 root root 4096 Jun 22 22:30 volume4 drwxr-xr-x 14 root root 4096 Jun 22 22:30 var -rw-r--r-- 1 root root 20480 Jun 22 22:30 SynoUpgrade.tar -rw-r--r-- 1 root root 40 Jun 22 22:30 checksum.syno drwxr-xr-x 7 root root 0 Jun 22 22:30 config drwxr-xr-x 12 root root 14020 Jun 22 22:44 dev drwxr-xr-x 25 root root 4096 Jun 22 22:44 .. drwxr-xr-x 25 root root 4096 Jun 22 22:44 . drwxr-xr-x 47 root root 4096 Jun 22 22:44 etc drwxr-xr-x 40 root root 1940 Jun 22 22:44 run drwxrwxrwt 12 root root 1480 Jun 22 22:45 tmp

Plug out the disks, plug in again and see what's going on?

Just finished the pat installation and the DSM5 data on the disk of slot3 is there with no issue. I guess I will try the reboot process and plug in the extra USB3 cards and NIC of PCIE tomorrow. Then I will plug in the orginial 3 disks.

After I uploading the pat file, or before the uploading?

Got it fixed. 🙏 <--- this means thanks in Chinese.

The post you shared, in 7#, billat29 has the same N54L and we did some chat last week. I posted him the NIC issue and he told me to disable C1E in the BIOS. Now I can see N54L from the Synology Assitant. Thank you for the helps these days! I'll continue the process. Hope no problems～

Would you please go to my post and reply? I will mark it as the solution, so it will help more. Thanks!