Hi. I am having a situation that I never had bevore and I am clueles. I am running a virtual RS4021xs on ESX for a while now. I have 12 SSD Drives connected as RDMs and forming 3 raid5 arrays. All volumes are BTRS formated volumes. Disk 1 is the "satadom". Disk 2 is a 50GB VMDK which is volume4.
I am running ARC loader version 23.11.30 and DSM 7.2.1-69057 Update 3
If I force DSM reinstallation, the DSM boots normaly, I cann logon and all volumes are mounted and all apps are fine. Looks all good.
But if I reboot the DSM, it looks to me like the boot process does not finish.
Telneting on the virtual serial port I can see that is stops "to early" at logon prompt. If I try to logon to the GUI it says "system is getting ready...". But I cann logon via telnet or ssh.
My /etc/fstab only shows this two entries:
none /proc proc defaults 0 0
/dev/root / ext4 defaults 1 1
It should be:
none /proc proc defaults 0 0
/dev/root / ext4 defaults 1 1
/dev/mapper/cachedev_0 /volume4 btrfs auto_reclaim_space,ssd,synoacl,relatime,nodev 0 0
/dev/mapper/cachedev_3 /volume1 btrfs auto_reclaim_space,ssd,synoacl,relatime,nodev 0 0
/dev/mapper/cachedev_2 /volume2 btrfs auto_reclaim_space,ssd,synoacl,relatime,nodev 0 0
/dev/mapper/cachedev_1 /volume3 btrfs auto_reclaim_space,ssd,synoacl,relatime,nodev 0 0
The commands
cat /proc/mdstat
lvdisplay
vgdisplay
do not seam to show any abnormal situation. I can manually mount my volumes without a problem.
If I execute
synobootseq --set-boot-done
synobootseq --is-ready
I am able to logon to the GUI. But the apps are missing.
At the momemt the only way I know how to help my self is to force DSM reinstallation via ARC Loader. After reinstallation and first boot, all works perfectly again. Till next reboot.
If someone has an idea what could be the reason and how to solve it, I realy would apreciate the help.
BTW: I have backup of the complete NAS on a second baremetal XPEnology runing with spinning disks. I don't think that restoring it will fix my problem. I am afraid the issue will be restored as well. It's not the restore time that I'm afraid of, but rather the reconfiguration time.