RAID6 herstellen.

[shinger]

Hallo jongens,

Op mijn NAS heb ik van de 5 hardeschijven 4 in de RAID6 opstelling. Deze werkten helemaal goed, maar sinds 2 dagen geleden nadat door 1 lamp van mij stroomgroep uit viel, ging mijn NAS ook op onjuiste manier uit.

Normaal zou ik het opnieuw hebben gestart en alles zou weer het oude zijn. Alleen ik met mijn domme hoofd had paar weken geleden IN REALTIME geexperimenteerd met opzetten van een PXE Boot server. Dit helaas niet gelukt, maar hierdoor veel instellingen verandert. Afgelopen 2 dagen ben ik veel bezig geweest om instellingen terug te draaien, alleen bij het terugdraaien van instellingen was één van mijn hardeschijven die behoorde in RAID6 opstelling gemount op USB =_=!. Deze heb ik verwijdert in de fstab file en vervolgens de mdadm bestand ook aangepast.

Hij hoort hoe die moet horen. RAID6 (md0) bestaat gewoon, maar is niet geactiveerd. Ik probeer via webmin mijn hardeschijven aan toe te voegen, maar ik krijg volgende foutmelding.

Code: [Selecteer]

mdadm in --manage --add mode failed : mdadm: cannot get array info for /dev/md0
fstab bestand:

Code: [Selecteer]

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sda1 during installation
UUID=e0212cc8-d084-47a9-9ebf-21ecefea7df3 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
/dev/sda5 none            swap    sw              0       0

#Raid6 (Harde schijven nr. 2,3,4,5)
/dev/md0 /mnt/RAID6 ext4 defaults 0 0
#RAID1 (Hardeschijf nr. 1)
UUID=2a14d6e3-203a-43c9-a4e0-16afcff17cca /media/RAID1 ext4 defaults 0 0



mdadm bestand:

Code: [Selecteer]

DEVICE /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
ARRAY /dev/md0 level=raid6 devices=/dev/sdc1,/dev/sdd1,/dev/sde1,/dev/sdf1
MAILADDR root
cat /proc/mdstat:

Code: [Selecteer]

shinger@NAS:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : inactive sdf1[3](S) sdd1[1](S) sde1[2](S) sdc1[0](S)
      7813529600 blocks super 1.2
       
unused devices: <none>

[shinger]

sdc1

Code: [Selecteer]

shinger@NAS:~$ sudo mdadm --examine /dev/sdc1
/dev/sdc1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : aac0715d:c270f071:b4d7a663:e8b8f1bc
           Name : NAS:0  (local to host NAS)
  Creation Time : Wed Sep 26 15:34:54 2012
     Raid Level : -unknown-
   Raid Devices : 0

 Avail Dev Size : 3906764800 (1862.89 GiB 2000.26 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : active
    Device UUID : 65ed9cb4:525282e9:947037a8:7e304db1

    Update Time : Wed Sep 25 14:44:57 2013
       Checksum : 6a1e297b - correct
         Events : 1


   Device Role : spare
   Array State :  ('A' == active, '.' == missing)
sdd1

Code: [Selecteer]

shinger@NAS:~$ sudo mdadm --examine /dev/sdd1
/dev/sdd1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : aac0715d:c270f071:b4d7a663:e8b8f1bc
           Name : NAS:0  (local to host NAS)
  Creation Time : Wed Sep 26 15:34:54 2012
     Raid Level : -unknown-
   Raid Devices : 0

 Avail Dev Size : 3906764800 (1862.89 GiB 2000.26 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : active
    Device UUID : bf6b236d:3a4f115f:87bb897b:c666dabc

    Update Time : Wed Sep 25 14:50:42 2013
       Checksum : 7715274f - correct
         Events : 1


   Device Role : spare
   Array State :  ('A' == active, '.' == missing)

sde1

Code: [Selecteer]

shinger@Koerdistan-NAS:~$ sudo mdadm --examine /dev/sde1
/dev/sde1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : aac0715d:c270f071:b4d7a663:e8b8f1bc
           Name : Koerdistan-NAS:0  (local to host Koerdistan-NAS)
  Creation Time : Wed Sep 26 15:34:54 2012
     Raid Level : -unknown-
   Raid Devices : 0

 Avail Dev Size : 3906764800 (1862.89 GiB 2000.26 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : active
    Device UUID : 3793f216:7438924c:0890d754:65236b47

    Update Time : Wed Sep 25 14:44:57 2013
       Checksum : 7241c7ca - correct
         Events : 1


   Device Role : spare
   Array State :  ('A' == active, '.' == missing)
sdf1

Code: [Selecteer]

shinger@Koerdistan-NAS:~$ sudo mdadm --examine /dev/sdf1
/dev/sdf1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : aac0715d:c270f071:b4d7a663:e8b8f1bc
           Name : Koerdistan-NAS:0  (local to host Koerdistan-NAS)
  Creation Time : Wed Sep 26 15:34:54 2012
     Raid Level : -unknown-
   Raid Devices : 0

 Avail Dev Size : 3906764800 (1862.89 GiB 2000.26 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : active
    Device UUID : 35e0959c:357da956:486a7181:689cc596

    Update Time : Wed Sep 25 14:50:42 2013
       Checksum : 7df2ae25 - correct
         Events : 1


   Device Role : spare
   Array State :  ('A' == active, '.' == missing)

[shinger]

Code: [Selecteer]

shinger@Koerdistan-NAS:~$ sudo mdadm --stop /dev/md0
mdadm: stopped /dev/md0
shinger@Koerdistan-NAS:~$ sudo mdadm --assemble --scan
mdadm: device 1 in /dev/md/0 has wrong state in superblock, but /dev/sdd1 seems ok
mdadm: device 3 in /dev/md/0 has wrong state in superblock, but /dev/sdf1 seems ok
mdadm: /dev/md/0 assembled from 0 drives and 4 spares - not enough to start the array.

[shinger]

Ik merk trouwen dat als ik een usb-stick erin doe, dan veranderen de schijven van device. D wordt E, E wordt f, f wordt G. C blijft het zelfde.

[Johan van Dijk]

Probeer dit eens:

Code: [Selecteer]

sudo mdadm --assemble --force /dev/md0 /dev/sd[c-f]1
(Ik ga er dan wel van uit dat je RAID-schijven /dev/sdc tot /dev/sdf zijn)

[shinger]

Probeer dit eens:

Code: [Selecteer]

sudo mdadm --assemble --force /dev/md0 /dev/sd[c-f]1
(Ik ga er dan wel van uit dat je RAID-schijven /dev/sdc tot /dev/sdf zijn)

Dit is wat ik krijg daar uit.

Code: [Selecteer]

shinger@KOERDISTAN-NAS:~$ sudo mdadm --assemble --force /dev/md0 /dev/sd[c-f]1
mdadm: /dev/sdc1 is busy - skipping
mdadm: /dev/sdd1 is busy - skipping
mdadm: /dev/sde1 is busy - skipping
mdadm: /dev/sdf1 is busy - skipping

[Johan van Dijk]

Doe dan eerst eens sudo mdadm --stop /dev/md0 en probeer het daarna nog eens.

[shinger]

Doe dan eerst eens sudo mdadm --stop /dev/md0 en probeer het daarna nog eens.

Ik heb het gestopt en opnieuw gedaan.. hier onder de output.

Code: [Selecteer]

shinger@KOERDISTAN-NAS:~$ sudo mdadm --stop /dev/md0
mdadm: stopped /dev/md0
shinger@KOERDISTAN-NAS:~$ sudo mdadm --assemble --force /dev/md0 /dev/sd[c-f]1
mdadm: /dev/md0 assembled from 0 drives and 4 spares - not enough to start the array.

[Johan van Dijk]

Het enige wat ik nog kan bedenken is het opnieuw aanmaken van de array met de --assume-clean optie. Voor zover ik kan zien in de data die je gaf is er maar een klein verschil in writes tussen de verschillende schijven (events in de --examine resultaten) dus zou je bestandssysteem nog in redelijke staat moeten zijn.

Dit is wel op eigen risico, ik garandeer helemaal niets. Niet of het lukt en ook niet of je data beschadigd raakt of helemaal opgegeten wordt.

Als je RAID-schijven nog steeds sdc tot sdf zijn, dan kan je dit proberen:

Code: [Selecteer]

sudo mdadm --stop /dev/md0
sudo mdadm --create --assume-clean --level=6 --raid-devices=4 --chunk=64 /dev/md0 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
sudo mdadm --readonly /dev/md0
Verloopt dit zonder problemen, dan zou ik de array fsck-en in read-only modus:

Code: [Selecteer]

sudo fsck -n /dev/md0

Verloopt dit zonder duizenden errors, dan heb je de volgorde van je schijven goed ingevuld in het --create commando. Je array moet nu weer beschikbaar zijn.
Zo niet, dan moet je het --create commando proberen met een andere volgorde van je schijven net zo lang tot het weer werkt.

Hierna moet je nog een normale fsck doen om er zeker van te zijn dat er geen fouten meer zijn en dat de paar fouten die er toch zijn opgelost worden.

Als laatste moet je mdadm nog een check laten doen of alles nog in sync is:

Code: [Selecteer]

sudo /usr/share/mdadm/checkarray -saf
Dit kan wel een paar uur duren.


Werkt het allemaal weer, dan zou ik nog een paar zaken controleren/aanpassen:

/etc/mdadm/mdadm.conf:
De DEVICE regel zou ik weghalen of een comment van maken.
In de ARRAY regel zou alleen je UUID moeten staan, dit om veranderende namen (sda->sdb enz.).
Zo dus:

Code: [Selecteer]

ARRAY /dev/md0 UUID=aac0715d:c270f071:b4d7a663:e8b8f1bc
Edit: nadat je dat bestand aangepast hebt moet je ook nog dit commando uitvoeren:

Code: [Selecteer]

sudo update-initramfs -u -k all


[shinger]

Ik durft niet verder te gaan .

Code: [Selecteer]

[sudo] password for shinger:
mdadm: stopped /dev/md0
shinger@Koerdistan-NAS:~$ sudo mdadm --create --assume-clean --level=6 --raid-devices=4 --chunk=64 /dev/md0 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
mdadm: /dev/sdc1 appears to be part of a raid array:
    level=-unknown- devices=0 ctime=Wed Sep 26 15:34:54 2012
mdadm: /dev/sdd1 appears to be part of a raid array:
    level=-unknown- devices=0 ctime=Wed Sep 26 15:34:54 2012
mdadm: /dev/sde1 appears to be part of a raid array:
    level=-unknown- devices=0 ctime=Wed Sep 26 15:34:54 2012
mdadm: /dev/sdf1 appears to be part of a raid array:
    level=-unknown- devices=0 ctime=Wed Sep 26 15:34:54 2012
Continue creating array?

[Johan van Dijk]

Dat is volgens mij nog normaal, want in principe maak je nu een nieuwe RAID array. En omdat je de --assume-clean optie hebt meegegeven gaat mdadm geen rebuild doen. Alle data zou bewaard moeten blijven.

[shinger]

De errors .. ik kon niet alles kopiëren. Hier hield de terminal op.

Code: [Selecteer]

Error writing block 81 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 82 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 83 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 84 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 85 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 86 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 87 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 88 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 89 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 90 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 91 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 92 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 93 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 94 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 95 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 96 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 97 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 98 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 99 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 100 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 101 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 102 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 103 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 104 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 105 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 106 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 107 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 108 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 109 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 110 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 111 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 112 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 113 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 114 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 115 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 116 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 117 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 118 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 119 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 120 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 121 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 122 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 123 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 124 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 125 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 126 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 127 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 128 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 129 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 130 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 131 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 132 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 133 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 134 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 135 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 136 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 137 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 138 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 139 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 140 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 141 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 142 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 143 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 144 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 145 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 146 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 147 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 148 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 149 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 150 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 151 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 152 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 153 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 154 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 155 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 156 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 157 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 158 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 159 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 160 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 161 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 162 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 163 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 164 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 165 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 166 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 167 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 168 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 169 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 170 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 171 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 172 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 173 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 174 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 175 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 176 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 177 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 178 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 179 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 180 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 181 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 182 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 183 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 184 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 185 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 186 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 187 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 188 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 189 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 190 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 191 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 192 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 193 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 194 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 195 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 196 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 197 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 198 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 199 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 200 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 201 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 202 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 203 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 204 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 205 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 206 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 207 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 208 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 209 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 210 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 211 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 212 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 213 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 214 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 215 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 216 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 217 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 218 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 219 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 220 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 221 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 222 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 223 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 224 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 225 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 233 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 226 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 227 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 228 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 229 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 230 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 231 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 232 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 233 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 226 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 227 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 228 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 229 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 230 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 231 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 232 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 233 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 226 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 227 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 228 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 229 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 230 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 231 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

Error writing block 232 (Attempt to write block to filesystem resulted in short write).  Ignore error? no

fsck.ext4: Device or resource busy while trying to open /dev/md0
Filesystem mounted or opened exclusively by another program?


[Johan van Dijk]

Dan is de volgorde niet goed denk ik zo.
Stop md0 en maak hem opnieuw aan met een andere volgorde van schijven.

[shinger]

Dan is de volgorde niet goed denk ik zo.
Stop md0 en maak hem opnieuw aan met een andere volgorde van schijven.

Volgens mij had ik een foutje gedaan. Dat was de filesystemscheck die al die errors gaf.

[shinger]

Ik heb de mdadm bestand gewijzigd en inderdaad, met UUID moet mij minder stress gaan geven.

Code: [Selecteer]

shinger@Koerdistan-NAS:/mnt$ sudo update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-3.8.0-30-generic
W: mdadm: the array /dev/md0 with UUID ee49bca8:25595e39:2d933e82:06174e4d
W: mdadm: is currently active, but it is not listed in mdadm.conf. if
W: mdadm: it is needed for boot, then YOUR SYSTEM IS NOW UNBOOTABLE!
W: mdadm: please inspect the output of /usr/share/mdadm/mkconf, compare
W: mdadm: it to /etc/mdadm/mdadm.conf, and make the necessary changes.
update-initramfs: Generating /boot/initrd.img-3.8.0-29-generic
W: mdadm: the array /dev/md0 with UUID ee49bca8:25595e39:2d933e82:06174e4d
W: mdadm: is currently active, but it is not listed in mdadm.conf. if
W: mdadm: it is needed for boot, then YOUR SYSTEM IS NOW UNBOOTABLE!
W: mdadm: please inspect the output of /usr/share/mdadm/mkconf, compare
W: mdadm: it to /etc/mdadm/mdadm.conf, and make the necessary changes.

Code: [Selecteer]

shinger@Koerdistan-NAS:/mnt$ sudo /usr/share/mdadm/checkarray -saf
md0: idle


Code: [Selecteer]

shinger@Koerdistan-NAS:/mnt$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid6 sdf1[3] sde1[2] sdd1[1] sdc1[0]
      3906764416 blocks super 1.2 level 6, 64k chunk, algorithm 2 [4/4] [UUUU]
     
unused devices: <none>

[Johan van Dijk]

Werkt het nu weer? Het is me niet helemaal duidelijk wat je precies gedaan hebt en of je weer bij je data kan.
Het is wel belangrijk om te wachten met de checkarray tot hij weer werkt. Anders synct hij misschien wel verkeerd en ben je alsnog je data kwijt.
Kan je md0 mounten en zie je dan je bestanden weer?

Verder moet je waarschijnlijk de UUID even updaten in /etc/mdadm/mdadm.conf. De UUID kan je vinden door sudo mdadm -D /dev/md0 te doen. Hierna weer het update-initramfs commando.

[Johan van Dijk]

En nog een toevoeging: ik zie net dat je bij het checkarray commando de -s optie weg moet laten:
sudo /usr/share/mdadm/checkarray  -af moet het dus zijn.

Wil je daarna de voortgang van dat commando in de gaten houden, dan is dit wel een handig commando (afbreken met control-c):

Code: [Selecteer]

watch cat /proc/mdstat


[shinger]

En nog een toevoeging: ik zie net dat je bij het checkarray commando de -s optie weg moet laten:
sudo /usr/share/mdadm/checkarray  -af moet het dus zijn.

Wil je daarna de voortgang van dat commando in de gaten houden, dan is dit wel een handig commando (afbreken met control-c):

Code: [Selecteer]

watch cat /proc/mdstat


Ik kan het niet mounten of laten syncen. 

Code: [Selecteer]

shinger@Koerdistan-NAS:~$ sudo fsck -n /dev/md0
fsck from util-linux 2.20.1
e2fsck 1.42 (29-Nov-2011)
fsck.ext4: No such file or directory while trying to open /dev/md0
Possibly non-existent device?

Code: [Selecteer]

shinger@Koerdistan-NAS:~$ sudo /usr/share/mdadm/checkarray -af
checkarray: W: array md127 in auto-read-only state, skipping...

[shinger]

En nog een toevoeging: ik zie net dat je bij het checkarray commando de -s optie weg moet laten:
sudo /usr/share/mdadm/checkarray  -af moet het dus zijn.

Wil je daarna de voortgang van dat commando in de gaten houden, dan is dit wel een handig commando (afbreken met control-c):

Code: [Selecteer]

watch cat /proc/mdstat


Ik kan het niet mounten of laten syncen. 

Code: [Selecteer]

shinger@Koerdistan-NAS:~$ sudo fsck -n /dev/md0
fsck from util-linux 2.20.1
e2fsck 1.42 (29-Nov-2011)
fsck.ext4: No such file or directory while trying to open /dev/md0
Possibly non-existent device?

Code: [Selecteer]

shinger@Koerdistan-NAS:~$ sudo /usr/share/mdadm/checkarray -af
checkarray: W: array md127 in auto-read-only state, skipping...

Edit: Ik had hem net op nieuwe opgestart en hij is van md0 naar md127 gegaan. Dus verandert naar md127.

[shinger]

Fstab is nu anders:

Code: [Selecteer]

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sda1 during installation
UUID=c65edbe5-4219-4d82-a8f2-2057240e2dfe /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=d3de6a30-3503-4e89-8cc1-154cabcb508b none            swap    sw              0       0

#RAID1 (Hardeschijf nr. 1)
UUID=2a14d6e3-203a-43c9-a4e0-16afcff17cca       /media/RAID1    ext4    defaults        0       0

#Raid6 (Harde schijven nr. 2,3,4,5)
/dev/md127      /mnt/RAID6      ext4    defaults        0       0
mdadm.conf:

Code: [Selecteer]

#DEVICE /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
MAILADDR root
ARRAY /dev/md127 metadata=1.2 UUID=ee49bca8:25595e39:2d933e82:06174e4d name=Koerdistan-NAS:0
   spares=4

[shinger]

Fstab is nu anders:

Code: [Selecteer]

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sda1 during installation
UUID=c65edbe5-4219-4d82-a8f2-2057240e2dfe /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=d3de6a30-3503-4e89-8cc1-154cabcb508b none            swap    sw              0       0

#RAID1 (Hardeschijf nr. 1)
UUID=2a14d6e3-203a-43c9-a4e0-16afcff17cca       /media/RAID1    ext4    defaults        0       0

#Raid6 (Harde schijven nr. 2,3,4,5)
/dev/md127      /mnt/RAID6      ext4    defaults        0       0
mdadm.conf:

Code: [Selecteer]

#DEVICE /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
MAILADDR root
ARRAY /dev/md127 metadata=1.2 UUID=ee49bca8:25595e39:2d933e82:06174e4d name=Koerdistan-NAS:0
   spares=4

sudo mdadm -D /dev/md127

Code: [Selecteer]

shinger@Koerdistan-NAS:~$  sudo mdadm -D /dev/md127
/dev/md127:
        Version : 1.2
  Creation Time : Wed Sep 25 20:08:04 2013
     Raid Level : raid6
     Array Size : 3906764416 (3725.78 GiB 4000.53 GB)
  Used Dev Size : 1953382208 (1862.89 GiB 2000.26 GB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent

    Update Time : Wed Sep 25 20:16:25 2013
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

           Name : Koerdistan-NAS:0  (local to host Koerdistan-NAS)
           UUID : ee49bca8:25595e39:2d933e82:06174e4d
         Events : 2

    Number   Major   Minor   RaidDevice State
       0       8       33        0      active sync   /dev/sdc1
       1       8       49        1      active sync   /dev/sdd1
       2       8       65        2      active sync   /dev/sde1
       3       8       81        3      active sync   /dev/sdf1

Ik ga even niks meer typen/doen, want ik heb nu ongelofelijk veel rotzooi hier gepost.. waardoor jij volgens mij geen overzicht meer hebt en ik zelf geen overzicht meer heb.

[Johan van Dijk]

Ok...
Weer even vanaf het begin:
Wat zegt cat /proc/mdstat

Kan je md0 (of md127) mounten en gebruiken?
Zo niet, wat zegt sudo mdadm -D /dev/md0
(of /dev/md127...)

[shinger]

cat /proc/mdstat

Code: [Selecteer]

shinger@Koerdistan-NAS:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : active (auto-read-only) raid6 sdf1[3] sdc1[0] sde1[2] sdd1[1]
      3906764416 blocks super 1.2 level 6, 64k chunk, algorithm 2 [4/4] [UUUU]
     
unused devices: <none>
sudo mdadm -D /dev/md127

Code: [Selecteer]

shinger@Koerdistan-NAS:~$ sudo mdadm -D /dev/md127
/dev/md127:
        Version : 1.2
  Creation Time : Wed Sep 25 20:08:04 2013
     Raid Level : raid6
     Array Size : 3906764416 (3725.78 GiB 4000.53 GB)
  Used Dev Size : 1953382208 (1862.89 GiB 2000.26 GB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent

    Update Time : Wed Sep 25 20:16:25 2013
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

           Name : Koerdistan-NAS:0  (local to host Koerdistan-NAS)
           UUID : ee49bca8:25595e39:2d933e82:06174e4d
         Events : 2

    Number   Major   Minor   RaidDevice State
       0       8       33        0      active sync   /dev/sdc1
       1       8       49        1      active sync   /dev/sdd1
       2       8       65        2      active sync   /dev/sde1
       3       8       81        3      active sync   /dev/sdf1
sudo mount -a

Code: [Selecteer]

shinger@Koerdistan-NAS:~$ sudo mount -a
mount: wrong fs type, bad option, bad superblock on /dev/md127,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

[Johan van Dijk]

Dan zal je de instructies uit antwoord #8 nog eens moeten proberen, maar dan met md127 ipv md0.
De volgorde van je schijven klopt nog niet en daarom werkt het niet.

En pas wanneer de fsck zonder grote problemen verloopt en je md127 kan mounten (als read-only!) moet je verder gaan met resyncen en andere aanpassingen.

Zo niet, dan klopt de volgorde nog niet en moet je het weer proberen. Het zijn 24 mogelijkheden, dus je moet er gewoon een aantal proberen...

Edit: zie ook hier: https://raid.wiki.kernel.org/index.php/RAID_Recovery
Je kan het perl-script dat gelinkt is nog proberen, dat zal wel sneller zijn dan handmatig alles nalopen. Kom je er dan nog steeds niet uit, dan is hulp vragen via de mailinglijst die ook gelinkt is de laatste optie.

[shinger]

Ik krijg constant dit als ik andere volgordes probeer bij het filesystemcheck.

Code: [Selecteer]

fsck from util-linux 2.20.1
The filesystem revision is apparently too high for this version of e2fsck.
(Or the filesystem superblock is corrupt)


The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
Alleen bij c, d, e, f krijg ik dit.


shinger@Koerdistan-NAS:~$ sudo fsck -n /dev/md0 >> test3.status
e2fsck 1.42 (29-Nov-2011)
fsck.ext4: Device or resource busy while trying to open /dev/md0

Output van fsck (test3.status) <zie bijlage>.. teveel regels.. waardoor 20.000 karakters overschreden worden..

Edit: Ik vroeg mij overigens ook af, is de chunk size misschien niet te groot of te klein?