Hi All, I've posted this on the Synology forums but it can't hurt to post it here as well. Thanks everyone. "my brother's DS212J is claiming that DSM isn't installed following a house move. My only guess is that the installation has become corrupt? I am looking to reinstall DSM but don't want to lose the data on the drives (Raid1). I was going down the safe option and trying to backup the data before running an installation as Synology Assistant claims "you will lose all your data" etc. I've removed a hard drive and have connected it to a W10 PC. Drive Management can see the hard drive but I was unable to assign a drive letter to actually view the files. I then used EX2 Volume Manager which allowed me to assign a letter and view the file structure. I'm a bit lost from here. I can't see anywhere obvious that the files are stored. Can a backup be done this way or am I barking up the wrong tree? Could someone point me in the right direction? I don't have access to a linux system. Any help much appreciated. Cheers, Will."
Synology DSM has Linux LVM on top of Linux mdraid. So you need Linux ideally. RAID arrays on my DS216j : Code: # cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md2 : active raid1 sda5[0] sdb5[1] 3902187456 blocks super 1.2 [2/2] [UU] md1 : active raid1 sda2[0] sdb2[1] 2097088 blocks [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 2490176 blocks [2/2] [UU] Which then maps to LVM physical volume : Code: #pvdisplay --- Physical volume --- PV Name /dev/md2 VG Name vg1000 PV Size 3.63 TiB / not usable 1.94 MiB Allocatable yes (but full) PE Size 4.00 MiB Total PE 952682 Free PE 0 Allocated PE 952682 PV UUID crypticID Which then maps to LVM volume group : Code: # vgdisplay --- Volume group --- VG Name vg1000 System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 2 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1 Open LV 1 Max PV 0 Cur PV 1 Act PV 1 VG Size 3.63 TiB PE Size 4.00 MiB Total PE 952682 Alloc PE / Size 952682 / 3.63 TiB Free PE / Size 0 / 0 VG UUID anotherCrypticID Which then finally maps to LVM logical volume : Code: # lvdisplay --- Logical volume --- LV Path /dev/vg1000/lv LV Name lv VG Name vg1000 LV UUID lastCrypticID LV Write Access read/write LV Creation host, time , LV Status available # open 1 LV Size 3.63 TiB Current LE 952682 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 512 Block device 253:0 And this logical volume is then mapped to /volumeNumber in the filesystem : Code: /dev/mapper/vg1000-lv on /volume1 type ext4 (rw,relatime,journal_checksum,synoacl,data=writeback,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group) So if you managed to get around this in Windows, good for you - and at this moment you should see the folders for shares he defined, plus few folders and files with @ in front of them - like @eaDir, @iSCSI, @appstore etc. His files should be in the non-@ folders. If you see something else (like folders bin,dev, etc,root,usr and so on), you mounted /dev/md0, which is the system ext4 RAID1 partition - you are not interested in this one. There is also /dev/md1, which is the swap partition. Official guide to recovery using Ubuntu : https://www.synology.com/en-global/...I_recover_data_from_my_DiskStation_using_a_PC
I know it sound silly but did you check the drives? We get this all the time with these units, even just taking on our selves up the road to a customer (not even posting) the drive came loose and corrupted the OS. Norm just get the end user to reseat all the drives, reboot and it comes back.
