golge13

root@ubuntu:~# vgdisplay -v Using volume group(s) on command line. --- Volume group --- VG Name vg1000 System ID Format lvm2 Metadata Areas 4 Metadata Sequence No 15 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1 Open LV 1 Max PV 0 Cur PV 4 Act PV 4 VG Size 9.98 TiB PE Size 4.00 MiB Total PE 2617331 Alloc PE / Size 2617331 / 9.98 TiB Free PE / Size 0 / 0 VG UUID 0mJfTu-HpKa-N00X-ecjA-ZWmh-nIsT-i7bDo2 --- Logical volume --- LV Path /dev/vg1000/lv LV Name lv VG Name vg1000 LV UUID SQcxkP-D3DV-cxNj-Zkr2-RZ5k-EmfX-Zcy9vq LV Write Access read/write LV Creation host, time , LV Status available # open 1 LV Size 9.98 TiB Current LE 2617331 Segments 9 Allocation inherit Read ahead sectors auto - currently set to 1280 Block device 253:0 --- Physical volumes --- PV Name /dev/md2 PV UUID UaZBcq-yq6p-UQk7-HKwn-t53m-WiyO-ST7XfK PV Status allocatable Total PE / Free PE 1186557 / 0 PV Name /dev/md3 PV UUID 2MCtMR-GdSF-UufZ-m16o-Fx7c-c4GU-687R78 PV Status allocatable Total PE / Free PE 715387 / 0 PV Name /dev/md4 PV UUID tUpwsB-N0ue-Pk1q-VTe0-MJwF-Pt8U-O2wFMl PV Status allocatable Total PE / Free PE 476925 / 0 PV Name /dev/md5 PV UUID RBUtMK-zd4z-cNns-i8c5-jOoL-k8kx-vwfSuk PV Status allocatable Total PE / Free PE 238462 / 0 I removed insignificant items from the log file and uploaded it below. I see that I tried to fix the disk more times than I remember. synosys.log avskalad.rtf

Thank you for a detailed answer! 1. The original disk was also 1 TB 2. First I tried to repair with the same disk. maybe went 30-40% before it was disconnected. Then I tried with a new 10TB disk, but it did not even initialize the disk before it became completely useless. (crc-error or something, got a new one on warranty).I did not want to chance with one other 10TB so I bought a new 1TB. Then it worked well to repair. But the files were already gone. 3. Now I was unsure I'll be back to check if I can see it in the log file 4. Now mdstat says everything is okay, but I checked in the DiskStation when I had it and I attached the picture here. I do not know if it will look like that in md0 and md1. What I think it means is that I had 12 slots in 3612xs and that I only used 6 but I'm definitely not sure. I can not see md0 and md1 in ubuntu? root@ubuntu:~# cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md2 : active raid5 sda5[0] sdd5[6] sdc5[5] sdf5[3] sde5[7] sdb5[1] 4860138240 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU] md5 : active raid5 sdd8[0] sdc8[1] 976742784 blocks super 1.2 level 5, 64k chunk, algorithm 2 [2/2] [UU] md4 : active raid5 sdc7[0] sdd7[2] sdb7[1] 1953485568 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU] md3 : active raid5 sdb6[0] sdd6[3] sdc6[2] sda6[1] 2930228352 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU] unused devices: <none> 5. No I do not think so.

Hi! One of my six hard drives gave up and the volume became degraded. I swapped the broken HDD and started repairing the volume. But the new hddn broke down in the meantime, now I see that an entire folder is missing. On the volume itself, the space is still the same as before but some files are gone. (Can`t see them). After I had repair the device, the files still missing. I run on DSM 5.0-4493 update 5 on a HP n54l. Shr-1 raid with 6 HDD I happened to do a factory reset in panic so I'm using an ubuntu live stick, as well as a Windows 10 live stick with UFS Explorer. I apologize for my bad computer skills and English. I have saved the space_history_ logfiles when the volume was degraded and now. it seems that the partitions have moved a little bit there. Is there anyone who could help me fix my problem? I would be very grateful! space_history_20171224_131310.xml space_history_20180306_181156.xml