DSM 5.2-5644.5 error


Recommended Posts

I am using DSM5.2-5644.5. When 1 HDD cracked. I changed and repaired. But cannot open storage manager. System had problem

 

26559561956_0fe84aa549_b.jpg

 

After that i uninstall everything. Scrubbing data, run a file system check. System has still error "File system error was found on volume [1]". Volume is normal, but ask run a file system check.

 

Please help. Thanks everybody.

Link to post
Share on other sites
did you run the e2fsck process? What were the result?

have you tried mounting the file system using Ubuntu?

Do you have a data backup?

 

Thanks. I don't have data backup. My computer knowledge limited. I've read a lot of comment. I did as directed. And result, you saw. I don't know to using Ubuntu. Could you help me please? Thank a lot.

Link to post
Share on other sites
This is the guidance from Synology to mount volumes using ubuntu.

 

https://www.synology.com/en-uk/knowledg ... using_a_PC

 

Thanks. And result, i didn't connect to volume

 

root@ubuntu:~# mdadm -Asf && vgchange -ay

mdadm: /dev/md/2 has been started with 6 drives.

/run/lvm/lvmetad.socket: connect failed: No such file or directory

WARNING: Failed to connect to lvmetad. Falling back to internal scanning.

1 logical volume(s) in volume group "vg1000" now active

 

Can i recuse my data?

When i click volume, it notify

 

Unable to access “1.42.6-5644”

Error mounting /dev/dm-0 at /media/ubuntu/1.42.6-5644: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/dm-0" "/media/ubuntu/1.42.6-5644"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/mapper/vg1000-lv,

missing codepage or helper program, or other error

 

In some cases useful info is found in syslog - try

dmesg | tail or so.

Link to post
Share on other sites

> cat /proc/mdstat

Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]

md2 : active raid5 sdb5[0] sdf5[5] sde5[4] sdd5[3] sdc5[2] sda5[6]

9743376960 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [uUUUUU]

 

md1 : active raid1 sdf2[5] sde2[4] sdd2[3] sdc2[2] sdb2[1] sda2[0]

2097088 blocks [12/6] [uUUUUU______]

 

md0 : active raid1 sda1[1] sdb1[0] sdc1[2] sdd1[3] sde1[4] sdf1[5]

2490176 blocks [12/6] [uUUUUU______]

 

unused devices:

 

> mdadm --detail /dev/md2

/dev/md2:

Version : 1.2

Creation Time : Tue Feb 9 13:48:38 2016

Raid Level : raid5

Array Size : 9743376960 (9292.01 GiB 9977.22 GB)

Used Dev Size : 1948675392 (1858.40 GiB 1995.44 GB)

Raid Devices : 6

Total Devices : 6

Persistence : Superblock is persistent

 

Update Time : Mon May 2 13:20:32 2016

State : clean

Active Devices : 6

Working Devices : 6

Failed Devices : 0

Spare Devices : 0

 

Layout : left-symmetric

Chunk Size : 64K

 

Name : LONGA:2 (local to host LONGA)

UUID : 4d6fcde3:e172ef03:8baef73c:f06c4bf7

Events : 8521

 

Number Major Minor RaidDevice State

0 8 21 0 active sync /dev/sdb5

6 8 5 1 active sync /dev/sda5

2 8 37 2 active sync /dev/sdc5

3 8 53 3 active sync /dev/sdd5

4 8 69 4 active sync /dev/sde5

5 8 85 5 active sync /dev/sdf5

 

> mount | grep "vol\|md\|vg"

/dev/sdu1 on /volumeUSB2/usbshare type vfat (utf8,umask=000,shortname=mixed,uid=1024,gid=100,quiet)

 

> vgchange -ay

1 logical volume(s) in volume group "vg1000" now active

 

> mount /dev/vg1000/lv /volume1

mount: mounting /dev/vg1000/lv on /volume1 failed: No such device

 

> lvm vgscan

Reading all physical volumes. This may take a while...

Found volume group "vg1000" using metadata type lvm2

 

> lvm 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 0

Max PV 0

Cur PV 1

Act PV 1

VG Size 9.07 TB

PE Size 4.00 MB

Total PE 2378754

Alloc PE / Size 2378754 / 9.07 TB

Free PE / Size 0 / 0

VG UUID sNYq8b-M28N-fiI4-e7ud-QT4z-R3I6-YBg5fM

 

 

> fdisk -l

 

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes

255 heads, 63 sectors/track, 243201 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

Device Boot Start End Blocks Id System

/dev/sda1 1 311 2490240 fd Linux raid autodetect

Partition 1 does not end on cylinder boundary

/dev/sda2 311 572 2097152 fd Linux raid autodetect

Partition 2 does not end on cylinder boundary

/dev/sda3 588 243201 1948788912 f Win95 Ext'd (LBA)

/dev/sda5 589 243188 1948676448 fd Linux raid autodetect

 

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes

255 heads, 63 sectors/track, 243201 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

Device Boot Start End Blocks Id System

/dev/sdb1 1 311 2490240 fd Linux raid autodetect

Partition 1 does not end on cylinder boundary

/dev/sdb2 311 572 2097152 fd Linux raid autodetect

Partition 2 does not end on cylinder boundary

/dev/sdb3 588 243201 1948788912 f Win95 Ext'd (LBA)

/dev/sdb5 589 243188 1948676448 fd Linux raid autodetect

 

Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes

255 heads, 63 sectors/track, 243201 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

Device Boot Start End Blocks Id System

/dev/sdc1 1 311 2490240 fd Linux raid autodetect

Partition 1 does not end on cylinder boundary

/dev/sdc2 311 572 2097152 fd Linux raid autodetect

Partition 2 does not end on cylinder boundary

/dev/sdc3 588 243201 1948788912 f Win95 Ext'd (LBA)

/dev/sdc5 589 243188 1948676448 fd Linux raid autodetect

 

Disk /dev/sdd: 2000.3 GB, 2000397852160 bytes

255 heads, 63 sectors/track, 243201 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

Device Boot Start End Blocks Id System

/dev/sdd1 1 311 2490240 fd Linux raid autodetect

Partition 1 does not end on cylinder boundary

/dev/sdd2 311 572 2097152 fd Linux raid autodetect

Partition 2 does not end on cylinder boundary

/dev/sdd3 588 243201 1948788912 f Win95 Ext'd (LBA)

/dev/sdd5 589 243188 1948676448 fd Linux raid autodetect

 

Disk /dev/sde: 2000.3 GB, 2000398934016 bytes

255 heads, 63 sectors/track, 243201 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

Device Boot Start End Blocks Id System

/dev/sde1 1 311 2490240 fd Linux raid autodetect

Partition 1 does not end on cylinder boundary

/dev/sde2 311 572 2097152 fd Linux raid autodetect

Partition 2 does not end on cylinder boundary

/dev/sde3 588 243201 1948788912 f Win95 Ext'd (LBA)

/dev/sde5 589 243188 1948676448 fd Linux raid autodetect

 

Disk /dev/sdf: 2000.3 GB, 2000398934016 bytes

255 heads, 63 sectors/track, 243201 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

Device Boot Start End Blocks Id System

/dev/sdf1 1 311 2490240 fd Linux raid autodetect

Partition 1 does not end on cylinder boundary

/dev/sdf2 311 572 2097152 fd Linux raid autodetect

Partition 2 does not end on cylinder boundary

/dev/sdf3 588 243201 1948788912 f Win95 Ext'd (LBA)

/dev/sdf5 589 243188 1948676448 fd Linux raid autodetect

 

Disk /dev/sdg: 2000.3 GB, 2000397852160 bytes

255 heads, 63 sectors/track, 243201 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

Device Boot Start End Blocks Id System

/dev/sdg1 * 1 122785 986267573+ 83 Linux

/dev/sdg2 122785 243202 967243777 5 Extended

/dev/sdg5 242696 243202 4058112 82 Linux swap

/dev/sdg6 122785 242696 963185664 83 Linux

 

Partition table entries are not in disk order

 

Disk /dev/sdu: 8097 MB, 8097103872 bytes

4 heads, 32 sectors/track, 123552 cylinders

Units = cylinders of 128 * 512 = 65536 bytes

 

Device Boot Start End Blocks Id System

/dev/sdu1 * 1 384 24544+ e Win95 FAT16 (LBA)

LONGA>

LONGA> /dev/md2:

Used Dev Size : 1948675392 (1858.40 GiB 1995.44 GB)

Raid Devices : 6

Total Devices : 6

Persistence : Superblock is persistent

 

Update Time : Mon May 2 13:20:32 2016

State : clean

Active Devices : 6

-ash: Working Devices : 6

Fa/dev/md2:: not foundiled Devices : 0

Spare Devices

: 0

 

Layout : left-symmetric

Chunk Size : 64K

 

 

 

Anybody know, please help. Thanks

Link to post
Share on other sites