Synology-Forum.nl
Firmware => Synology DSM algemeen => Topic gestart door: drnizeguy op 03 april 2014, 18:23:53
-
Ik had bepaalde problemen met instellingen die bleven hangen. Al is eerder gehad en alleen het opnieuw installeren van DSM kon dit verhelpen.
Dit heb ik nu dus weer gedaan, nieuwe firmware geïnstalleerd zoals het hoort (en natuurlijk er voor gekozen om GEEN nieuwe raid volume aan te maken).
De nas start weer op, ik log in: geen volume. Niks. Diskstation status is ok, maar geen volume. Kan wel een nieuwe aanmaken, maar niets om te restoren oid.
Een schijf nog eruit gehad, opnieuw gestart (misschien constateert dsm dan een foutieve raid configuratie) maar dat bood ook geen soelaas.
Ik heb al een ticket aangemaakt bij Synology maar dat duurt 4 dagen (ze hebben het druk). Weet iemand nog een oplossing?
-
laat eens wat screenshots zien van je opslag (volume, hdd,...)
-
[attach=2]
[attach=3]
en dit zegt fdisk
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
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
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
Disk /dev/sdd: 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/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
Disk /dev/synoboot: 128 MB, 128450560 bytes
255 heads, 63 sectors/track, 15 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/synoboot1 1 16 125439+ ee EFI GPT
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 1) logical=(0, 0, 2)
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(15, 157, 14)
Dat de 1e twee schijven niet geïnitialiseerd zijn klopt, deze heb ik er uit gehad, in de hoop dat de array corrupt werd en zich opnieuw ging rebuilden (dit heeft wel eens geholpen,maar nu dus niet).
en als ik mdadm doe op de schijven komt dit eruit
ds> mdadm --misc --examine /dev/sda1
/dev/sda1:
Magic : a92b4efc
Version : 0.90.00
UUID : ebc1bf6a:a445dd83:b36848ba:e3c877f2 (local to host ds)
Creation Time : Sat Jan 1 01:00:06 2000
Raid Level : raid1
Used Dev Size : 2490176 (2.37 GiB 2.55 GB)
Array Size : 2490176 (2.37 GiB 2.55 GB)
Raid Devices : 4
Total Devices : 3
Preferred Minor : 0
Update Time : Thu Apr 3 17:51:23 2014
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 1
Spare Devices : 0
Checksum : 5c347b4d - correct
Events : 948
Number Major Minor RaidDevice State
this 0 8 1 0 active sync /dev/hda1
0 0 8 1 0 active sync /dev/hda1
1 1 0 0 1 faulty removed
2 2 8 33 2 active sync /dev/hdc1
3 3 8 49 3 active sync /dev/hdd1
ds> mdadm --misc --examine /dev/sdb1
/dev/sdb1:
Magic : a92b4efc
Version : 0.90.00
UUID : ebc1bf6a:a445dd83:b36848ba:e3c877f2 (local to host ds)
Creation Time : Sat Jan 1 01:00:06 2000
Raid Level : raid1
Used Dev Size : 2490176 (2.37 GiB 2.55 GB)
Array Size : 2490176 (2.37 GiB 2.55 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Update Time : Thu Apr 3 16:08:55 2014
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : 5c345c33 - correct
Events : 20
Number Major Minor RaidDevice State
this 1 8 17 1 active sync /dev/hdb1
0 0 8 1 0 active sync /dev/hda1
1 1 8 17 1 active sync /dev/hdb1
2 2 8 33 2 active sync /dev/hdc1
3 3 8 49 3 active sync /dev/hdd1
ds> mdadm --misc --examine /dev/sdc1
/dev/sdc1:
Magic : a92b4efc
Version : 0.90.00
UUID : ebc1bf6a:a445dd83:b36848ba:e3c877f2 (local to host ds)
Creation Time : Sat Jan 1 01:00:06 2000
Raid Level : raid1
Used Dev Size : 2490176 (2.37 GiB 2.55 GB)
Array Size : 2490176 (2.37 GiB 2.55 GB)
Raid Devices : 4
Total Devices : 2
Preferred Minor : 0
Update Time : Thu Apr 3 19:52:55 2014
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 1
Spare Devices : 0
Checksum : 5c34a1e7 - correct
Events : 2230
Number Major Minor RaidDevice State
this 2 8 33 2 active sync /dev/hdc1
0 0 0 0 0 removed
1 1 0 0 1 faulty removed
2 2 8 33 2 active sync /dev/hdc1
3 3 8 49 3 active sync /dev/hdd1
ds> mdadm --misc --examine /dev/sdd1
/dev/sdd1:
Magic : a92b4efc
Version : 0.90.00
UUID : ebc1bf6a:a445dd83:b36848ba:e3c877f2 (local to host ds)
Creation Time : Sat Jan 1 01:00:06 2000
Raid Level : raid1
Used Dev Size : 2490176 (2.37 GiB 2.55 GB)
Array Size : 2490176 (2.37 GiB 2.55 GB)
Raid Devices : 4
Total Devices : 2
Preferred Minor : 0
Update Time : Thu Apr 3 19:52:55 2014
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 1
Spare Devices : 0
Checksum : 5c34a1f9 - correct
Events : 2230
Number Major Minor RaidDevice State
this 3 8 49 3 active sync /dev/hdd1
0 0 0 0 0 removed
1 1 0 0 1 faulty removed
2 2 8 33 2 active sync /dev/hdc1
3 3 8 49 3 active sync /dev/hdd1
ds> mdadm --misc --examine /dev/sdd2
/dev/sdd2:
Magic : a92b4efc
Version : 0.90.00
UUID : c5806afa:a3af72b2:b36848ba:e3c877f2 (local to host ds)
Creation Time : Thu Apr 3 19:34:29 2014
Raid Level : raid1
Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
Array Size : 2097088 (2048.28 MiB 2147.42 MB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 1
Update Time : Thu Apr 3 19:35:21 2014
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : 50272607 - correct
Events : 19
Number Major Minor RaidDevice State
this 3 8 50 3 active sync /dev/sdd2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/hdb2
2 2 8 34 2 active sync /dev/hdc2
3 3 8 50 3 active sync /dev/sdd2
ds> mdadm --misc --examine /dev/sda2
/dev/sda2:
Magic : a92b4efc
Version : 0.90.00
UUID : c5806afa:a3af72b2:b36848ba:e3c877f2 (local to host ds)
Creation Time : Thu Apr 3 19:34:29 2014
Raid Level : raid1
Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
Array Size : 2097088 (2048.28 MiB 2147.42 MB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 1
Update Time : Thu Apr 3 19:35:21 2014
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : 502725d1 - correct
Events : 19
Number Major Minor RaidDevice State
this 0 8 2 0 active sync /dev/sda2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/hdb2
2 2 8 34 2 active sync /dev/hdc2
3 3 8 50 3 active sync /dev/sdd2
ds> mdadm --misc --examine /dev/sdb2
/dev/sdb2:
Magic : a92b4efc
Version : 0.90.00
UUID : c5806afa:a3af72b2:b36848ba:e3c877f2 (local to host ds)
Creation Time : Thu Apr 3 19:34:29 2014
Raid Level : raid1
Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
Array Size : 2097088 (2048.28 MiB 2147.42 MB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 1
Update Time : Thu Apr 3 19:35:21 2014
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : 502725e3 - correct
Events : 19
Number Major Minor RaidDevice State
this 1 8 18 1 active sync /dev/hdb2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/hdb2
2 2 8 34 2 active sync /dev/hdc2
3 3 8 50 3 active sync /dev/sdd2
ds> mdadm --misc --examine /dev/sdc2
/dev/sdc2:
Magic : a92b4efc
Version : 0.90.00
UUID : c5806afa:a3af72b2:b36848ba:e3c877f2 (local to host ds)
Creation Time : Thu Apr 3 19:34:29 2014
Raid Level : raid1
Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
Array Size : 2097088 (2048.28 MiB 2147.42 MB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 1
Update Time : Thu Apr 3 19:35:21 2014
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : 502725f5 - correct
Events : 19
Number Major Minor RaidDevice State
this 2 8 34 2 active sync /dev/hdc2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/hdb2
2 2 8 34 2 active sync /dev/hdc2
3 3 8 50 3 active sync /dev/sdd2
-
Wat dat betreft is de service die Synology levert echt top.
Een ticket aangemaakt en een Taiwanees heeft op afstand het volume weer terug gekregen.
Ik vroeg nog wat 'ie gedaan had; via mdadm de partitie opnieuw aangemaakt. Op de vraag hoe ik dat zelf kan doen: "google it". :P
In ieder geval, problem solved.
-
Ah......deze dus:
http://serverfault.com/questions/568166/how-to-recover-an-mdadm-array-on-synology-nas-with-drive-in-e-state