Nieuws:

Welkom, Gast. Alsjeblieft inloggen of registreren.
Heb je de activerings-mail niet ontvangen?

Auteur Topic: RAID6 configuratie gewist.  (gelezen 1514 keer)

RAID6 configuratie gewist.
« Gepost op: 2012/09/24, 18:05:02 »
Hallo jongens,

Door het updaten van Ubuntu heb ik mijn NAS met Ubuntu 12.04.1 LTS 32bit een reboot gegeven, maar ik denk dat één van de updates mijn RAID configuratie heeft gewist.

Wat heel raar is, is dat hij de JBOD partitie niks aangedaan heeft. Alleen mijn RAID6 configuratie is verdwenen. Ik ben nu heel bang voor data verlies, aangezien ik express voor Dual redundant had gekozen.

Hier de output van sommige commandos:

cat /proc/mdstat: (Ik heb hem nu OPNIEUW in RAID6 moeten zetten. Hij is hier nu aan het syncen.

shinger@Koerdistan-NAS:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid6 sdf1[3] sde1[2] sdd1[1] sdc1[0]
      3906761584 blocks super 1.2 level 6, 4k chunk, algorithm 2 [4/4] [UUUU]
      [>....................]  resync =  0.6% (12673120/1953380792) finish=1225.9min speed=26383K/sec
     
unused devices: <none>

output: sudo mdadm --detail /dev/md0:
shinger@Koerdistan-NAS:~$ sudo mdadm --detail /dev/md0
/dev/md0:
        Version : 1.2
  Creation Time : Mon Sep 24 17:50:12 2012
     Raid Level : raid6
     Array Size : 3906761584 (3725.78 GiB 4000.52 GB)
  Used Dev Size : 1953380792 (1862.89 GiB 2000.26 GB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent

    Update Time : Mon Sep 24 17:50:15 2012
          State : active, resyncing
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 4K

  Resync Status : 0% complete

           Name : Koerdistan-NAS:0  (local to host Koerdistan-NAS)
           UUID : 5d067bee:73a70ef6:a580f1e7:82b59d49
         Events : 1

    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

Output: sudo mdadm --examine /dev/sdc1
shinger@Koerdistan-NAS:~$ sudo mdadm --examine /dev/sdc1
/dev/sdc1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 5d067bee:73a70ef6:a580f1e7:82b59d49
           Name : Koerdistan-NAS:0  (local to host Koerdistan-NAS)
  Creation Time : Mon Sep 24 17:50:12 2012
     Raid Level : raid6
   Raid Devices : 4

 Avail Dev Size : 3906761858 (1862.89 GiB 2000.26 GB)
     Array Size : 3906761584 (3725.78 GiB 4000.52 GB)
  Used Dev Size : 3906761584 (1862.89 GiB 2000.26 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : active
    Device UUID : 12ec0911:c55927d5:9fdc9dc8:12bbede8

    Update Time : Mon Sep 24 17:50:15 2012
       Checksum : 2e859595 - correct
         Events : 1

         Layout : left-symmetric
     Chunk Size : 4K

   Device Role : Active device 0
   Array State : AAAA ('A' == active, '.' == missing)

Output: sudo mdadm --examine /dev/sdd1

shinger@Koerdistan-NAS:~$ sudo mdadm --examine /dev/sdd1
/dev/sdd1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 5d067bee:73a70ef6:a580f1e7:82b59d49
           Name : Koerdistan-NAS:0  (local to host Koerdistan-NAS)
  Creation Time : Mon Sep 24 17:50:12 2012
     Raid Level : raid6
   Raid Devices : 4

 Avail Dev Size : 3906761858 (1862.89 GiB 2000.26 GB)
     Array Size : 3906761584 (3725.78 GiB 4000.52 GB)
  Used Dev Size : 3906761584 (1862.89 GiB 2000.26 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : active
    Device UUID : 284ee8ac:2620ccef:72c30978:9d354587

    Update Time : Mon Sep 24 17:50:15 2012
       Checksum : 32cc1f6b - correct
         Events : 1

         Layout : left-symmetric
     Chunk Size : 4K

   Device Role : Active device 1
   Array State : AAAA ('A' == active, '.' == missing)

Output: sudo mdadm --examine /dev/sde1
shinger@Koerdistan-NAS:~$ sudo mdadm --examine /dev/sde1
/dev/sde1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 5d067bee:73a70ef6:a580f1e7:82b59d49
           Name : Koerdistan-NAS:0  (local to host Koerdistan-NAS)
  Creation Time : Mon Sep 24 17:50:12 2012
     Raid Level : raid6
   Raid Devices : 4

 Avail Dev Size : 3906761858 (1862.89 GiB 2000.26 GB)
     Array Size : 3906761584 (3725.78 GiB 4000.52 GB)
  Used Dev Size : 3906761584 (1862.89 GiB 2000.26 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : active
    Device UUID : fba99bb9:35662d95:891c77fb:58356017

    Update Time : Mon Sep 24 17:50:15 2012
       Checksum : f8691a1f - correct
         Events : 1

         Layout : left-symmetric
     Chunk Size : 4K

   Device Role : Active device 2
   Array State : AAAA ('A' == active, '.' == missing)

Output: sudo mdadm --examine /dev/sdf1
shinger@Koerdistan-NAS:~$ sudo mdadm --examine /dev/sdf1
/dev/sdf1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 5d067bee:73a70ef6:a580f1e7:82b59d49
           Name : Koerdistan-NAS:0  (local to host Koerdistan-NAS)
  Creation Time : Mon Sep 24 17:50:12 2012
     Raid Level : raid6
   Raid Devices : 4

 Avail Dev Size : 3906761858 (1862.89 GiB 2000.26 GB)
     Array Size : 3906761584 (3725.78 GiB 4000.52 GB)
  Used Dev Size : 3906761584 (1862.89 GiB 2000.26 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : active
    Device UUID : d9cac08f:9e43787c:9bd46b73:88f3d69b

    Update Time : Mon Sep 24 17:50:15 2012
       Checksum : b2448ea9 - correct
         Events : 1

         Layout : left-symmetric
     Chunk Size : 4K

   Device Role : Active device 3
   Array State : AAAA ('A' == active, '.' == missing)

Re: RAID6 configuratie gewist.
« Reactie #1 Gepost op: 2012/09/24, 18:55:35 »
Houdt ons op de hoogte.

Re: RAID6 configuratie gewist.
« Reactie #2 Gepost op: 2012/09/24, 19:23:54 »
Als alles gesynced is, dan zal ik opnieuw even alles proberen en de output van de mount posten.

Re: RAID6 configuratie gewist.
« Reactie #3 Gepost op: 2012/09/25, 23:56:08 »
Oké, ik heb hem nu helemaal gesynct. Hieronder output van sommige commands.
Als ik het nu probeer te mounten, dan krijg ik het volgende.

Failed to save mount : Mount failed :
mount: wrong fs type, bad option, bad superblock on /dev/md0,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

Output: dmesg | tail
shinger@Koerdistan-NAS:~$ dmesg | tail
[84886.720060] ata5: EH complete
[84983.413375] ata5: limiting SATA link speed to 1.5 Gbps
[84983.413382] ata5: exception Emask 0x10 SAct 0x0 SErr 0x10002 action 0xe frozen
[84983.413457] ata5: edma_err_cause=00000008 pp_flags=00000000, dev disconnect
[84983.413521] ata5: SError: { RecovComm PHYRdyChg }
[84983.413569] ata5: hard resetting link
[84984.292043] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[84984.324053] ata5.00: configured for UDMA/133
[84984.324061] ata5: EH complete
[108461.485168] EXT4-fs (md0): VFS: Can't find ext4 filesystem

output:  sudo mount /dev/md0 /media/RAID6
shinger@Koerdistan-NAS:~$ sudo mount /dev/md0 /media/RAID6
mount: unknown filesystem type 'LVM2_member'

Hieronder in 1 van de outputs fdisk, zegt hij dat filesystem onbekend is, maar toen ik mijn RAID6 aanmaakte had ik ext4 gekozen. Waarom die het nu niet ziet weet ik echt niet. Kan iemand mij hiermee helpen??

Output: cat /proc/mdstat

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

Output: sudo sudo fdisk -l

shinger@Koerdistan-NAS:~$ sudo fdisk -l
[sudo] password for shinger:

Disk /dev/sda: 8019 MB, 8019099648 bytes
255 heads, 63 sectors/track, 974 cylinders, total 15662304 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00038013

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048    13584383     6791168   83  Linux
/dev/sda2        13586430    15661055     1037313    5  Extended
/dev/sda5        13586432    15661055     1037312   82  Linux swap / Solaris

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00055513

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63  1953520064   976760001   83  Linux

Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d203e

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1              63  3907024064  1953512001   83  Linux

Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00054c42

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1              63  3907024064  1953512001   83  Linux

Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0008623b

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1              63  3907024064  1953512001   83  Linux

Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0007ae2b

   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1              63  3907024064  1953512001   83  Linux

Disk /dev/md0: 4000.5 GB, 4000523862016 bytes
2 heads, 4 sectors/track, 976690396 cylinders, total 7813523168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 8192 bytes
Disk identifier: 0x00000000

Disk /dev/md0 doesn't contain a valid partition table

output: sudo mdadm --detail /dev/md0:
shinger@Koerdistan-NAS:~$ sudo mdadm --detail /dev/md0
/dev/md0:
        Version : 1.2
  Creation Time : Mon Sep 24 17:50:12 2012
     Raid Level : raid6
     Array Size : 3906761584 (3725.78 GiB 4000.52 GB)
  Used Dev Size : 1953380792 (1862.89 GiB 2000.26 GB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent

    Update Time : Tue Sep 25 14:30:06 2012
          State : active
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 4K

           Name : Koerdistan-NAS:0  (local to host Koerdistan-NAS)
           UUID : 5d067bee:73a70ef6:a580f1e7:82b59d49
         Events : 18

    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

Output: sudo mdadm --examine /dev/sdc1

shinger@Koerdistan-NAS:~$ sudo mdadm --examine /dev/sdc1
/dev/sdc1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 5d067bee:73a70ef6:a580f1e7:82b59d49
           Name : Koerdistan-NAS:0  (local to host Koerdistan-NAS)
  Creation Time : Mon Sep 24 17:50:12 2012
     Raid Level : raid6
   Raid Devices : 4

 Avail Dev Size : 3906761858 (1862.89 GiB 2000.26 GB)
     Array Size : 3906761584 (3725.78 GiB 4000.52 GB)
  Used Dev Size : 3906761584 (1862.89 GiB 2000.26 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : active
    Device UUID : 12ec0911:c55927d5:9fdc9dc8:12bbede8

    Update Time : Tue Sep 25 14:30:06 2012
       Checksum : 2e86b83d - correct
         Events : 18

         Layout : left-symmetric
     Chunk Size : 4K

   Device Role : Active device 0
   Array State : AAAA ('A' == active, '.' == missing)

Output: sudo mdadm --examine /dev/sdd1

shinger@Koerdistan-NAS:~$ sudo mdadm --examine /dev/sdd1
/dev/sdd1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 5d067bee:73a70ef6:a580f1e7:82b59d49
           Name : Koerdistan-NAS:0  (local to host Koerdistan-NAS)
  Creation Time : Mon Sep 24 17:50:12 2012
     Raid Level : raid6
   Raid Devices : 4

 Avail Dev Size : 3906761858 (1862.89 GiB 2000.26 GB)
     Array Size : 3906761584 (3725.78 GiB 4000.52 GB)
  Used Dev Size : 3906761584 (1862.89 GiB 2000.26 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : active
    Device UUID : 284ee8ac:2620ccef:72c30978:9d354587

    Update Time : Tue Sep 25 14:30:06 2012
       Checksum : 32cd4213 - correct
         Events : 18

         Layout : left-symmetric
     Chunk Size : 4K

   Device Role : Active device 1
   Array State : AAAA ('A' == active, '.' == missing)

Output: sudo mdadm --examine /dev/sde1

shinger@Koerdistan-NAS:~$ sudo mdadm --examine /dev/sde1
/dev/sde1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 5d067bee:73a70ef6:a580f1e7:82b59d49
           Name : Koerdistan-NAS:0  (local to host Koerdistan-NAS)
  Creation Time : Mon Sep 24 17:50:12 2012
     Raid Level : raid6
   Raid Devices : 4

 Avail Dev Size : 3906761858 (1862.89 GiB 2000.26 GB)
     Array Size : 3906761584 (3725.78 GiB 4000.52 GB)
  Used Dev Size : 3906761584 (1862.89 GiB 2000.26 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : active
    Device UUID : fba99bb9:35662d95:891c77fb:58356017

    Update Time : Tue Sep 25 14:30:06 2012
       Checksum : f86a3cc7 - correct
         Events : 18

         Layout : left-symmetric
     Chunk Size : 4K

   Device Role : Active device 2
   Array State : AAAA ('A' == active, '.' == missing)

Output: sudo mdadm --examine /dev/sdf1

shinger@Koerdistan-NAS:~$ sudo mdadm --examine /dev/sdf1
/dev/sdf1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 5d067bee:73a70ef6:a580f1e7:82b59d49
           Name : Koerdistan-NAS:0  (local to host Koerdistan-NAS)
  Creation Time : Mon Sep 24 17:50:12 2012
     Raid Level : raid6
   Raid Devices : 4

 Avail Dev Size : 3906761858 (1862.89 GiB 2000.26 GB)
     Array Size : 3906761584 (3725.78 GiB 4000.52 GB)
  Used Dev Size : 3906761584 (1862.89 GiB 2000.26 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : active
    Device UUID : d9cac08f:9e43787c:9bd46b73:88f3d69b

    Update Time : Tue Sep 25 14:30:06 2012
       Checksum : b245b151 - correct
         Events : 18

         Layout : left-symmetric
     Chunk Size : 4K

   Device Role : Active device 3
   Array State : AAAA ('A' == active, '.' == missing)
« Laatst bewerkt op: 2012/09/26, 00:02:10 door shinger »

Offline Johan van Dijk

  • Administrator
    • johanvandijk
Re: RAID6 configuratie gewist.
« Reactie #4 Gepost op: 2012/09/26, 00:06:42 »
Volgens de uitvoer van dmesg is er iets stuk, dat zijn namelijk meldingen dat Linux de SATA verbindingen reset om een bepaalde reden. Kijk dus even of alle kabeltjes goed vast zitten, probeer het evt. met andere kabeltjes, enz.

Kijk ook eens naar de SMART waarden van je schijven (pakket smartmontools, commando smartctl).

Re: RAID6 configuratie gewist.
« Reactie #5 Gepost op: 2012/09/26, 11:24:08 »
Volgens de uitvoer van dmesg is er iets stuk, dat zijn namelijk meldingen dat Linux de SATA verbindingen reset om een bepaalde reden. Kijk dus even of alle kabeltjes goed vast zitten, probeer het evt. met andere kabeltjes, enz.

Kijk ook eens naar de SMART waarden van je schijven (pakket smartmontools, commando smartctl).

In de dmesg had hij het over ata5 en dit bleek dus de middelste hardeschijf te zijn.
http://img.hexus.net/v2/news/misc/thecus5200pro.jpg
Ik heb vervolgens mijn NAS uitgezet en alles even goedschoongemaakt en gecheckt of alles weer goed inzat.

Na reboot heb ik de volgende output van de dmesg commando.

shinger@Koerdistan-NAS:~$ dmesg | tail
[   33.176535] init: failsafe main process (848) killed by TERM signal
[   33.391506] type=1400 audit(1348657539.264:5): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=911 comm="apparmor_parser"
[   33.393182] type=1400 audit(1348657539.268:6): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=911 comm="apparmor_parser"
[   33.393699] type=1400 audit(1348657539.268:7): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=911 comm="apparmor_parser"
[   33.403049] type=1400 audit(1348657539.276:8): apparmor="STATUS" operation="profile_load" name="/usr/sbin/mysqld" pid=912 comm="apparmor_parser"
[   33.427830] type=1400 audit(1348657539.300:9): apparmor="STATUS" operation="profile_load" name="/usr/sbin/slapd" pid=914 comm="apparmor_parser"
[   33.446717] type=1400 audit(1348657539.320:10): apparmor="STATUS" operation="profile_load" name="/usr/sbin/tcpdump" pid=915 comm="apparmor_parser"
[   33.806207] type=1400 audit(1348657539.680:11): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=993 comm="apparmor_parser"
[   33.811012] init: whoopsie main process (984) terminated with status 1
[   33.811046] init: whoopsie main process ended, respawning

De output van smartctl commando's.

Output: sudo smartctl -a /dev/sdc1

shinger@Koerdistan-NAS:~$ sudo smartctl -a /dev/sdc1
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.2.0-31-generic-pae] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green (Adv. Format)
Device Model:     WDC WD20EARS-00MVWB0
Serial Number:    WD-WCAZA5535910
LU WWN Device Id: 5 0014ee 25afc7f85
Firmware Version: 51.0AB51
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Wed Sep 26 11:17:00 2012 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (36600) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: (   2) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
Conveyance self-test routine
recommended polling time: (   5) minutes.
SCT capabilities:        (0x3035) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   253   253   021    Pre-fail  Always       -       991
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       42
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   086   086   000    Old_age   Always       -       10605
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       40
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       16
193 Load_Cycle_Count        0x0032   197   197   000    Old_age   Always       -       9702
194 Temperature_Celsius     0x0022   117   093   000    Old_age   Always       -       33
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Output: sudo smartctl -a /dev/sdd1

shinger@Koerdistan-NAS:~$ sudo smartctl -a /dev/sdd1
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.2.0-31-generic-pae] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green (Adv. Format)
Device Model:     WDC WD20EARS-00MVWB0
Serial Number:    WD-WCAZA5103391
LU WWN Device Id: 5 0014ee 25af2527b
Firmware Version: 51.0AB51
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Wed Sep 26 11:18:04 2012 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (38100) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: (   2) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
Conveyance self-test routine
recommended polling time: (   5) minutes.
SCT capabilities:        (0x3035) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   253   253   021    Pre-fail  Always       -       1008
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       40
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   086   086   000    Old_age   Always       -       10579
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       38
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       16
193 Load_Cycle_Count        0x0032   197   197   000    Old_age   Always       -       10135
194 Temperature_Celsius     0x0022   118   098   000    Old_age   Always       -       32
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.







Re: RAID6 configuratie gewist.
« Reactie #6 Gepost op: 2012/09/26, 11:24:22 »
Output: sudo smartctl -a /dev/sde1

shinger@Koerdistan-NAS:~$ sudo smartctl -a /dev/sde1
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.2.0-31-generic-pae] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green (Adv. Format)
Device Model:     WDC WD20EARS-00MVWB0
Serial Number:    WD-WCAZA5535694
LU WWN Device Id: 5 0014ee 205a754c9
Firmware Version: 51.0AB51
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Wed Sep 26 11:18:47 2012 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (36960) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: (   2) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
Conveyance self-test routine
recommended polling time: (   5) minutes.
SCT capabilities:        (0x3035) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   253   253   021    Pre-fail  Always       -       966
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       40
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   086   086   000    Old_age   Always       -       10578
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       38
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       17
193 Load_Cycle_Count        0x0032   197   197   000    Old_age   Always       -       10265
194 Temperature_Celsius     0x0022   118   102   000    Old_age   Always       -       32
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       150

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Output: sudo smartctl -a /dev/sdf1
shinger@Koerdistan-NAS:~$ sudo smartctl -a /dev/sdf1
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.2.0-31-generic-pae] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green (Adv. Format)
Device Model:     WDC WD20EARS-00MVWB0
Serial Number:    WD-WCAZA5528638
LU WWN Device Id: 5 0014ee 205a71d2b
Firmware Version: 51.0AB51
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Wed Sep 26 11:19:51 2012 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (37560) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: (   2) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
Conveyance self-test routine
recommended polling time: (   5) minutes.
SCT capabilities:        (0x3035) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   253   253   021    Pre-fail  Always       -       1000
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       39
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   086   086   000    Old_age   Always       -       10410
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       37
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       19
193 Load_Cycle_Count        0x0032   197   197   000    Old_age   Always       -       10392
194 Temperature_Celsius     0x0022   119   106   000    Old_age   Always       -       31
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Re: RAID6 configuratie gewist.
« Reactie #7 Gepost op: 2012/09/26, 11:26:47 »
mdadm.conf
shinger@Koerdistan-NAS:~$ cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions /dev/sdc2 /dev/sdd2 /dev/sde2

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
#ARRAY /dev/md1 level=linear num-devices=1 UUID=129b326d:66b87cb6:b4bfb7ea:d19d5d7e
#ARRAY /dev/md2 level=raid6 num-devices=4 UUID=7545bd22:48a70794:79e98ea1:50f79eb9

# This file was auto-generated on Mon, 26 Jul 2010 00:55:54 +0200
# by mkconf $Id$
DEVICE /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
ARRAY /dev/md0 level=raid6 devices=/dev/sdc1,/dev/sdd1,/dev/sde1,/dev/sdf1

fstab:
shinger@Koerdistan-NAS:~$ cat /etc/fstab
# /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
#USB (Voor het mounten van externe usbapparaten)
/dev/sdg1  /media/usb  vfat  noauto  0  0
#Raid6 (Harde schijven nr. 2,3,4,5)
#/dev/md0 /media/RAID6 ext4 user 0 0
#RAID1 (Hardeschijf nr. 1)
UUID=2a14d6e3-203a-43c9-a4e0-16afcff17cca  /media/RAID1  ext4  defaults  0  0
#/dev/RAID6/LV0 /media/RAID6 ext4 defaults 0 0

Offline Johan van Dijk

  • Administrator
    • johanvandijk
Re: RAID6 configuratie gewist.
« Reactie #8 Gepost op: 2012/09/26, 13:24:57 »
In je mdadm.conf kan je beter geen directe verwijzingen naar schijven doen. Bij veel systemen verandert de volgorde van /dev/sda, /dev/sdb enz. nog wel eens. In zo'n geval komt je array niet meer op.

Wat je nodig hebt in mdadm.conf:
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md0 UUID=7d4b6bba:enz
ARRAY /dev/md2 UUID=6e20bf45:enz
ARRAY /dev/md1 UUID=cc343e39:enz
ARRAY /dev/md3 UUID=af418e97:enz

De UUID's kan je opvragen via sudo mdadm --detail /dev/md0


Verder: ik zie net dat je waarschijnlijk voor een indeling met LVM hebt gekozen.
In dat geval zal je eerst met pvscan en lvscan moeten bepalen of hij alle volumes wel ziet en zo ja dan moet je ze activeren.

Vervolgens moet je niet /dev/md0 mounten, maar het volume /dev/md0/LV0
Tenminste, dat haal ik uit de weggecommente regel in fstab.

Re: RAID6 configuratie gewist.
« Reactie #9 Gepost op: 2012/09/26, 14:23:13 »
In je mdadm.conf kan je beter geen directe verwijzingen naar schijven doen. Bij veel systemen verandert de volgorde van /dev/sda, /dev/sdb enz. nog wel eens. In zo'n geval komt je array niet meer op.

Wat je nodig hebt in mdadm.conf:
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md0 UUID=7d4b6bba:enz
ARRAY /dev/md2 UUID=6e20bf45:enz
ARRAY /dev/md1 UUID=cc343e39:enz
ARRAY /dev/md3 UUID=af418e97:enz

De UUID's kan je opvragen via sudo mdadm --detail /dev/md0


Verder: ik zie net dat je waarschijnlijk voor een indeling met LVM hebt gekozen.
In dat geval zal je eerst met pvscan en lvscan moeten bepalen of hij alle volumes wel ziet en zo ja dan moet je ze activeren.

Vervolgens moet je niet /dev/md0 mounten, maar het volume /dev/md0/LV0
Tenminste, dat haal ik uit de weggecommente regel in fstab.

Ik kan mij nog herinneren dat ik een 1 grote Logical Volume had. Ik heb zelf webmin geinstalleerd en bij de 3de tab (logical Volume) kan ik een filesystem aan de Logical volume toewijzen die ik net even heb gemaakt.

Hij zegt alleen:Select a filesystem type and click this button to create a new filesystem on this logical volume. This will erase any data currently on the volume.
Wil dit zeggen dat ik dan AL mijn data kwijt raak wat ik op mijn RAID6 heb staan??

Output: sudo pvscan

shinger@Koerdistan-NAS:~$ sudo pvscan
  PV /dev/md0   VG RAID6   lvm2 [3.64 TiB / 796.00 MiB free]
  Total: 1 [3.64 TiB] / in use: 1 [3.64 TiB] / in no VG: 0 [0   ]

Output: sudo lvscan
shinger@Koerdistan-NAS:~$ sudo lvscan
  ACTIVE            '/dev/RAID6/RAID6' [3.64 TiB] inherit
« Laatst bewerkt op: 2012/09/26, 14:27:23 door shinger »

Re: RAID6 configuratie gewist.
« Reactie #10 Gepost op: 2012/09/26, 15:01:02 »
Johan, dank je wel voor de moeite, maar ik ben gewoon ALLES kwijt. tegen de 2 TB aan data. F*$&$#&!*@#$(!!!!

Ik ga nu de RAID6 vanaf het begin weer maken en dit keer goed, al was die vorige keer ook goed. Nou ja, je ziet hoe..*$#&$#(* het leven af en toe kan zijn.

Offline Johan van Dijk

  • Administrator
    • johanvandijk
Re: RAID6 configuratie gewist.
« Reactie #11 Gepost op: 2012/09/26, 15:27:58 »
Hij ziet wel de LVM volumes, dus dat zou wel goed moeten zijn.
Misschien dat iemand anders je nog kan helpen met alles weer aan de gang krijgen? Ik heb niet zoveel ervaring met LVM. Het is nog best mogelijk dat je niets kwijt bent, maar dan zal je wel dat LVM gebeuren weer aan de gang moeten krijgen.


Overigens zou ik voor zo'n data array helemaal geen LVM gebruiken. Je kan de RAID direct op de paritites zetten of zelfs op de schijven zelf zonder partities. En dan kan je op de RAID array direct je filesystem maken.