+-Serie wiederholter volume-crash bei DS710+ mit DX510 Expansionseinheit

Alle Geräte der +-Serie. Geräte für kleinere und mittlere Unternehmen.
Status
Für weitere Antworten geschlossen.

PaddyKN

Benutzer
Mitglied seit
28. Sep 2009
Beiträge
13
Punkte für Reaktionen
0
Punkte
1
Hallo zusammen,

ich betreibe eine DS710+ und habe das System nun mit einer DX510 erweitert. Leider habe ich hier arge Probleme. Ich habe eben ein Ticket an den Synology support geschrieben aber evtl. hat hier ja jemand ebenfalls eine Idee oder ähnliche Erfahrungen gemacht. Für Ratschläge wäre ich dankbar:

Folgendes Problem liegt vor:

The DX510 is connected to a DS710+ unit. Volume 1 is installed on the DS710+ (Raid1 mode) and runs perfectly fine. I created two more volumes on the DX510. Volume 2 runs in Raid 5 mode (=4x Western Digital WD20EARS-07MVWB0; 2TB each; slot 2-5), volume 3 runs in basic mode (WD10EADS-00L5B1; 1TB; slot1).

I was experiencing problems since the beginning. After creating the volumes (including checking of the HDDs) I started to copy data on the two volumes, which was not problematic. The problems started, after rebooting the system. I attached a screenshot. The Diskstation was not able to correctly initialize volume 2 and 3 (volumes on DX510). The protocol says the volumes were removed and then inserted again. Then the volumes crashed. Volume 1 (DS710+ still works perfectly fine).

After a reboot of the system there are always two possiblilities:
a) problem as desribed above; volume 2+3 are still in status "crashed".
b) the system works fine and all three volumes are detected and operational. After another restart there is a 50:50 chance that the system crashs again or works fine.

I repeated these system reboots several times now and the connection to the DX510 is just not stable (sometimes volume 2+3 crash, sometimes not). The eSATA cable does not hang loose. The SMART status says there are no problems with the HDDs.

I now tested another eSATA cable (eSATA II; 3 Gbit/s). The DX510 did not automatically startup and needed to be started manually. The DX510 was then correctly detected as an external drive and the data of volume 2 and 3 (formerly crashed) were accessable again (raid 5 testing for consistency). The "eSATA LED" of the DS710+ was not blinking. I assume there is something special about the Synology eSATa cable which enables the Diskstation to better communicate with the DX510 expansion unit?

However, my best guess is that there is something wrong about the Synology eSATA cable (cable defect) which results in an instable connection between the two devices.


Anhang anzeigen 7109
 

PaddyKN

Benutzer
Mitglied seit
28. Sep 2009
Beiträge
13
Punkte für Reaktionen
0
Punkte
1
Log file

Jan 2 11:27:14 syslogd started: BusyBox v1.16.1
Jan 2 11:27:17 kernel: [ 150.453690] md: md2: set sda3 to auto_remap [0]
Jan 2 11:27:17 kernel: [ 150.458345] md: md2: set sdb3 to auto_remap [0]
Jan 2 11:27:17 kernel: [ 150.551664] md: md4: set sdga3 to auto_remap [0]
Jan 2 11:27:17 kernel: [ 150.698569] md: md3: set sdgb5 to auto_remap [0]
Jan 2 11:27:17 kernel: [ 150.703474] md: md3: set sdge5 to auto_remap [0]
Jan 2 11:27:17 kernel: [ 150.708270] md: md3: set sdgd5 to auto_remap [0]
Jan 2 11:27:17 kernel: [ 150.713039] md: md3: set sdgc5 to auto_remap [0]
Jan 2 11:27:17 kernel: [ 150.753101] 0: w=1 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
Jan 2 11:27:17 kernel: [ 150.758245] 3: w=2 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
Jan 2 11:27:17 kernel: [ 150.763383] 2: w=3 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
Jan 2 11:27:17 kernel: [ 150.768531] 1: w=4 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
Jan 2 11:27:17 kernel: [ 150.773671] raid5: raid level 5 set md3 active with 4 out of 4 devices, algorithm 2
Jan 2 11:27:17 kernel: [ 150.781576] RAID5 conf printout:
Jan 2 11:27:17 kernel: [ 150.784904] --- rd:4 wd:4
Jan 2 11:27:17 kernel: [ 150.787718] disk 0, o:1, dev:sdgb5
Jan 2 11:27:17 kernel: [ 150.799407] disk 1, o:1, dev:sdgc5
Jan 2 11:27:17 kernel: [ 150.803014] disk 2, o:1, dev:sdgd5
Jan 2 11:27:17 kernel: [ 150.806620] disk 3, o:1, dev:sdge5
Jan 2 11:27:18 spacetool: spacetool.c:2201 [Info] Old vg path: [/dev/vg1000], New vg path: [/dev/vg1000], UUID: [nWU1tW-ViWx-RG3S-o1Gd-Kzgk-QHdA-J2jmjy]
Jan 2 11:27:18 spacetool: spacetool.c:2208 [Info] Activate all VG
Jan 2 11:27:18 spacetool: spacetool.c:2219 Activate LVM [/dev/vg1000]
Jan 2 11:27:26 scemd: scemd.c:127 fan_type=6, raid_type=1, led_type=1, thermal_type=1, fanctrl_type=1, auto_poweron_type=1, dual_power_type=1, usbcopy_type=1, fan_number=1, ebox_type=0, pis_type=1, rtc_type=3
Jan 2 11:27:26 scemd: modules/fan_speed_adjust_common.c:117 Type: INTERNAL Fan Mode: LOW
Jan 2 11:27:26 kernel: [ 159.817076] ata7: illegal qc_active transition (80000000->00000001)
Jan 2 11:27:26 kernel: [ 159.823804] ata7.01: failed to read SCR 1 (Emask=0x100)
Jan 2 11:27:26 kernel: [ 159.829184] ata7.02: failed to read SCR 1 (Emask=0x40)
Jan 2 11:27:26 kernel: [ 159.834499] ata7.03: failed to read SCR 1 (Emask=0x40)
Jan 2 11:27:26 kernel: [ 159.839811] ata7.04: failed to read SCR 1 (Emask=0x40)
Jan 2 11:27:26 kernel: [ 159.845114] ata7.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 2 11:27:26 kernel: [ 159.852548] ata7.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 2 11:27:26 kernel: [ 159.860004] ata7.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 2 11:27:26 kernel: [ 159.867527] ata7.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 2 11:27:29 kernel: [ 162.014709] ata7.15: PMP revalidation failed (errno=-19)
Jan 2 11:27:33 kernel: [ 166.216472] ata7.15: PMP revalidation failed (errno=-19)
Jan 2 11:27:37 kernel: [ 170.367312] ata7: illegal qc_active transition (80000000->00000001)
Jan 2 11:27:37 kernel: [ 170.373788] ata7.15: failed to read PMP GSCR[1] (Emask=0x100)
Jan 2 11:27:44 kernel: [ 177.388006] ata7.15: PMP revalidation failed (errno=-5)
Jan 2 11:27:44 kernel: [ 177.393400] ata7.15: failed to recover PMP after 3 tries, giving up
Jan 2 11:27:44 kernel: [ 177.404484] ata7.00: disabled
Jan 2 11:27:44 kernel: [ 177.407495] ata7.01: disabled
Jan 2 11:27:44 kernel: [ 177.410552] ata7.02: disabled
Jan 2 11:27:44 kernel: [ 177.413640] ata7.03: disabled
Jan 2 11:27:44 kernel: [ 177.416725] ata7.04: disabled
Jan 2 11:27:44 kernel: [ 177.419779] ata7.00: disabled
Jan 2 11:27:52 kernel: [ 185.073564] sd 6:1:0:0: rejecting I/O to offline device
Jan 2 11:27:52 kernel: [ 185.074438] sd 6:1:0:0: rejecting I/O to offline device
Jan 2 11:27:52 kernel: [ 185.074438] sd 6:1:0:0: rejecting I/O to offline device
Jan 2 11:27:52 kernel: [ 185.074438] end_request: I/O error, dev sdgb, sector 9453288
Jan 2 11:27:52 kernel: [ 185.074438] md: super_written gets error=-5, uptodate=0
Jan 2 11:27:52 kernel: [ 185.074438] raid5: Disk failure on sdgb5, disabling device. Operation continuing on 3 devices
Jan 2 11:27:52 kernel: [ 185.109833] sd 6:4:0:0: rejecting I/O to offline device
Jan 2 11:27:52 kernel: [ 185.110817] sd 6:4:0:0: rejecting I/O to offline device
Jan 2 11:27:52 kernel: [ 185.110817] sd 6:4:0:0: rejecting I/O to offline device
Jan 2 11:27:52 kernel: [ 185.110817] end_request: I/O error, dev sdge, sector 9453288
Jan 2 11:27:52 kernel: [ 185.110817] md: super_written gets error=-5, uptodate=0
Jan 2 11:27:52 kernel: [ 185.110817] raid5: Disk failure on sdge5, disabling device. Operation continuing on 2 devices
Jan 2 11:27:52 kernel: [ 185.145912] sd 6:3:0:0: rejecting I/O to offline device
Jan 2 11:27:52 kernel: [ 185.147664] sd 6:3:0:0: rejecting I/O to offline device
Jan 2 11:27:52 kernel: [ 185.147664] sd 6:3:0:0: rejecting I/O to offline device
Jan 2 11:27:52 kernel: [ 185.147664] end_request: I/O error, dev sdgd, sector 9453288
Jan 2 11:27:52 kernel: [ 185.147664] md: super_written gets error=-5, uptodate=0
Jan 2 11:27:52 kernel: [ 185.147664] raid5: Disk failure on sdgd5, disabling device. Operation continuing on 1 devices
Jan 2 11:27:52 kernel: [ 185.182015] sd 6:2:0:0: rejecting I/O to offline device
Jan 2 11:27:52 kernel: [ 185.182994] sd 6:2:0:0: rejecting I/O to offline device
Jan 2 11:27:52 kernel: [ 185.182994] sd 6:2:0:0: rejecting I/O to offline device
Jan 2 11:27:52 kernel: [ 185.182994] end_request: I/O error, dev sdgc, sector 9453288
Jan 2 11:27:52 kernel: [ 185.182994] md: super_written gets error=-5, uptodate=0
Jan 2 11:27:52 kernel: [ 185.182994] raid5: Disk failure on sdgc5, disabling device. Operation continuing on 0 devices
Jan 2 11:27:52 kernel: [ 185.218178] RAID5 conf printout:
Jan 2 11:27:52 kernel: [ 185.221547] --- rd:4 wd:0
Jan 2 11:27:52 kernel: [ 185.224312] disk 0, o:0, dev:sdgb5
Jan 2 11:27:52 kernel: [ 185.227892] disk 1, o:0, dev:sdgc5
Jan 2 11:27:52 kernel: [ 185.231496] disk 2, o:0, dev:sdgd5
Jan 2 11:27:52 kernel: [ 185.235131] disk 3, o:0, dev:sdge5
Jan 2 11:27:52 kernel: [ 185.241481] RAID5 conf printout:
Jan 2 11:27:52 kernel: [ 185.244818] --- rd:4 wd:0
Jan 2 11:27:52 kernel: [ 185.247648] disk 1, o:0, dev:sdgc5
Jan 2 11:27:52 kernel: [ 185.251234] disk 2, o:0, dev:sdgd5
Jan 2 11:27:52 kernel: [ 185.254825] disk 3, o:0, dev:sdge5
Jan 2 11:27:52 kernel: [ 185.258459] RAID5 conf printout:
Jan 2 11:27:52 kernel: [ 185.261819] --- rd:4 wd:0
Jan 2 11:27:52 kernel: [ 185.264628] disk 1, o:0, dev:sdgc5
Jan 2 11:27:52 kernel: [ 185.268253] disk 2, o:0, dev:sdgd5
Jan 2 11:27:52 kernel: [ 185.271874] disk 3, o:0, dev:sdge5
Jan 2 11:27:52 kernel: [ 185.277484] RAID5 conf printout:
Jan 2 11:27:52 kernel: [ 185.280801] --- rd:4 wd:0
Jan 2 11:27:52 kernel: [ 185.283614] disk 1, o:0, dev:sdgc5
Jan 2 11:27:52 kernel: [ 185.287199] disk 2, o:0, dev:sdgd5
Jan 2 11:27:52 kernel: [ 185.290811] RAID5 conf printout:
Jan 2 11:27:52 kernel: [ 185.294117] --- rd:4 wd:0
Jan 2 11:27:52 kernel: [ 185.296902] disk 1, o:0, dev:sdgc5
Jan 2 11:27:52 kernel: [ 185.300506] disk 2, o:0, dev:sdgd5
Jan 2 11:27:52 kernel: [ 185.306490] RAID5 conf printout:
Jan 2 11:27:52 kernel: [ 185.309816] --- rd:4 wd:0
Jan 2 11:27:52 kernel: [ 185.312610] disk 1, o:0, dev:sdgc5
Jan 2 11:27:52 kernel: [ 185.316184] RAID5 conf printout:
Jan 2 11:27:52 kernel: [ 185.319527] --- rd:4 wd:0
Jan 2 11:27:52 kernel: [ 185.322326] disk 1, o:0, dev:sdgc5
Jan 2 11:27:52 kernel: [ 185.328494] RAID5 conf printout:
Jan 2 11:27:52 kernel: [ 185.331808] --- rd:4 wd:0
Jan 2 11:27:52 kernel: [ 185.334645] Buffer I/O error on device dm-0, logical block 0
Jan 2 11:27:52 kernel: [ 185.340451] lost page write due to I/O error on dm-0
Jan 2 11:27:54 kernel: [ 187.295962] sd 6:0:0:0: rejecting I/O to offline device
Jan 2 11:27:54 kernel: [ 187.296866] sd 6:0:0:0: rejecting I/O to offline device
Jan 2 11:27:54 kernel: [ 187.296866] sd 6:0:0:0: rejecting I/O to offline device
Jan 2 11:27:54 kernel: [ 187.296866] end_request: I/O error, dev sdga, sector 9437192
Jan 2 11:27:54 kernel: [ 187.296866] md: super_written gets error=-5, uptodate=0
Jan 2 11:27:54 kernel: [ 187.296866] raid1: Disk failure on sdga3, disabling device.
Jan 2 11:27:54 kernel: [ 187.296866] Operation continuing on 0 devices
Jan 2 11:27:54 kernel: [ 187.333851] RAID1 conf printout:
Jan 2 11:27:54 kernel: [ 187.337161] --- wd:0 rd:1
Jan 2 11:27:54 kernel: [ 187.339958] disk 0, wo:1, o:0, dev:sdga3
Jan 2 11:27:54 kernel: [ 187.346887] RAID1 conf printout:
Jan 2 11:27:54 kernel: [ 187.350228] --- wd:0 rd:1
Jan 2 11:27:54 kernel: [ 187.695990] ata7: softreset failed (timeout)
Jan 2 11:28:00 kernel: [ 193.563118] ata7: controller in dubious state, performing PORT_RST
Jan 2 11:28:05 kernel: [ 198.247019] ata7: softreset failed (timeout)
Jan 2 11:28:05 kernel: [ 198.255194] ata7: controller in dubious state, performing PORT_RST

etc....das geht noch seitenlang so weiter
 

Tommi2day

Benutzer
Mitglied seit
24. Aug 2011
Beiträge
1.165
Punkte für Reaktionen
63
Punkte
68
sieht aus, als ob der interne Controler der Erweiterungseinheit nicht angesteuert werden kann. Ich vermute mal, das PMP auf ata7.15 genau das ist, was da fehlgeschlagen ist, da die Platten ja nur ata7.00-04 haben können. Wenn die DX510 neu ist, hat sie evtl. einen Schaden. Aber genau kann das wirklich nur der Support sagen. Meine DX geht auch nur mit dem mitgelieferten Kabel, was mir eigentlich zu kurz ist.
 
Status
Für weitere Antworten geschlossen.
 

Kaffeautomat

Wenn du das Forum hilfreich findest oder uns unterstützen möchtest, dann gib uns doch einfach einen Kaffee aus.

Als Dankeschön schalten wir deinen Account werbefrei.

:coffee:

Hier gehts zum Kaffeeautomat