Guess in that case, you won't have anything else to do but upgrade to a newer model or get a replacement part.
Noted and thanks for advice.
Anyway to recover my data? I have try "
DiskStation Manager - Knowledge Base | Synology Inc." but not successful. Below are the step that i do.
ubuntu@ubuntu:~$ sudo -i
root@ubuntu:~# apt-get update
Ign:1 cdrom://Ubuntu 20.04.2.0 LTS _Focal Fossa_ - Release amd64 (20210209.1) focal InRelease
Hit:2 cdrom://Ubuntu 20.04.2.0 LTS _Focal Fossa_ - Release amd64 (20210209.1) focal Release
Hit:4
Index of /ubuntu focal InRelease
Hit:5
Index of /ubuntu focal-security InRelease
Hit:6
Index of /ubuntu focal-updates InRelease
Reading package lists... Done
root@ubuntu:~# apt-get install -y mdadm lvm2
Reading package lists... Done
Building dependency tree
Reading state information... Done
lvm2 is already the newest version (2.03.07-1ubuntu1).
Suggested packages:
default-mta | mail-transport-agent dracut-core
The following NEW packages will be installed:
mdadm
0 upgraded, 1 newly installed, 0 to remove and 219 not upgraded.
Need to get 417 kB of archives.
After this operation, 1,255 kB of additional disk space will be used.
Get:1
Index of /ubuntu focal-updates/main amd64 mdadm amd64 4.1-5ubuntu1.2 [417 kB]
Fetched 417 kB in 3s (162 kB/s)
Preconfiguring packages ...
Selecting previously unselected package mdadm.
(Reading database ... 189770 files and directories currently installed.)
Preparing to unpack .../mdadm_4.1-5ubuntu1.2_amd64.deb ...
Unpacking mdadm (4.1-5ubuntu1.2) ...
Setting up mdadm (4.1-5ubuntu1.2) ...
Generating mdadm.conf... done.
update-initramfs is disabled since running on read-only media
/usr/sbin/grub-probe: error: failed to get canonical path of `/cow'.
Created symlink /etc/systemd/system/mdmonitor.service.wants/mdcheck_continue.timer → /lib/systemd/system/mdcheck_continue.timer.
Created symlink /etc/systemd/system/mdmonitor.service.wants/mdcheck_start.timer → /lib/systemd/system/mdcheck_start.timer.
Created symlink /etc/systemd/system/mdmonitor.service.wants/mdmonitor-oneshot.timer → /lib/systemd/system/mdmonitor-oneshot.timer.
Processing triggers for man-db (2.9.1-1) ...
root@ubuntu:~# mdadm -Asf && vgchange -ay
mdadm: /dev/md/2 has been started with 3 drives.
2 logical volume(s) in volume group "vg1" now active
root@ubuntu:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md2 : active raid5 sda5[0] sdc5[2] sdb5[1]
5850870912 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU]
unused devices: <none>
root@ubuntu:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
syno_vg_reserved_area vg1 -wi-a----- 12.00m
volume_1 vg1 -wi-a----- <5.45t
root@ubuntu:~# mount /dev/vg1/volume_1 /home/ubuntu/test -o ro
mount: /home/ubuntu/test: wrong fs type, bad option, bad superblock on /dev/mapper/vg1-volume_1, missing codepage or helper program, or other error.
root@ubuntu:~# pvscan
PV /dev/md2 VG vg1 lvm2 [<5.45 TiB / 0 free]
Total: 1 [<5.45 TiB] / in use: 1 [<5.45 TiB] / in no VG: 0 [0 ]
root@ubuntu:~#
I getting "mount: /home/ubuntu/test: wrong fs type, bad option, bad superblock on /dev/mapper/vg1-volume_1, missing codepage or helper program, or other error."
What can i do?
Thank you.