Defective RAID

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,
my name is Axel. I added my address to the list because I think I did something terribly wrong.
Several pages in the internet show not so good hints to reassemble a raid I think.
Now I need help from people, who know what they are doing.

The story:
I have a mdadm-RAID 5 with four disks. I chose a fantec usb/esata case which seemed to do what I wanted.
But sometimes the fantec device just switched itself off. Regardless i fit was connected to ESata or USB. Not quite a problem. I switched it back on and it ran for another couple of weeks.
Then one drive failed. I replaced ist with standard commands with no problem.

About two weeks ago the drive again stopped working. Switched off itself. I turned it back on, but mdadm would not start /dev/md0.
I tought the fantec is defective. So I took the four drives out of it and put them in my pc.
But mdadm did not assemble it automatically.
So I assembled it manually
Mdadm -assemble -scan.
Did not work.
Mdadm -assemble /md1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
Did not work either.
I read a howto where one wrote I should recreate the raid:
Mdadm -create --level=5 --raid-devices=4 /dev/md1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
That did it, but I could not mount it.
I realized, that the raid was marked degraded and tried to recover by writing to /dev /sde1.
I paniced, because all drives appeared ok (AAAA) when I scaned them so I stopped the RAID.
Then I reassembled them with the three devices but never managed to mount it.
I read that the order of the drives is important.
Is hat true?
Did I destroy the RAID?


mdadm --assemble  /dev/md1 /dev/sdd1 /dev/sdc1 /dev/sdb1
mdadm: /dev/md1 has been started with 3 drives (out of 4).
root@debian-t4:~# mount /dev/md1 /srv/test1/
mount: /srv/test1: wrong fs type, bad option, bad superblock on /dev/md1, missing codepage or helper program, or other error.
root@debian-t4:~# fsck.ext4 -n /dev/md1
e2fsck 1.44.2 (14-May-2018)
/dev/md1 besitzt nicht unterstützte Eigenschaft(en): FEATURE_C16 FEATURE_C17 FEATURE_C18 FEATURE_C19 FEATURE_C21 FEATURE_C22 FEATURE_C23 FEATURE_C25 FEATURE_C27 FEATURE_C28 FEATURE_I29 FEATURE_R29
e2fsck: Neuere Version von e2fsck benötigt!

What should I do next?


At the beginning all devices had (AAAA).
Now it looks like this:


root@debian-t4:~# mdadm -Evvvvs
/dev/sdc1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 27845ebe:8b19b4e1:e589d777:1bcea933
           Name : debian-t4:1  (local to host debian-t4)
  Creation Time : Mon May 21 15:15:22 2018
     Raid Level : raid5
   Raid Devices : 4

Avail Dev Size : 3906764800 (1862.89 GiB 2000.26 GB)
     Array Size : 5860147200 (5588.67 GiB 6000.79 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
   Unused Space : before=262056 sectors, after=0 sectors
          State : clean
    Device UUID : 44f8e4c7:aadd0fc2:07d599b5:dbd4d46a

Internal Bitmap : 8 sectors from superblock
    Update Time : Mon May 21 15:15:22 2018
  Bad Block Log : 512 entries available at offset 72 sectors
       Checksum : 4ae643d - correct
         Events : 0

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 1
   Array State : AAA. ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdc:
   MBR Magic : aa55
Partition[0] :   3907029167 sectors at            1 (type ee)
/dev/sde1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x3
     Array UUID : d87ebe37:95c10d7f:d4570046:134acc4d
           Name : debian-t4:1  (local to host debian-t4)
  Creation Time : Mon May 21 14:53:14 2018
     Raid Level : raid5
   Raid Devices : 4

Avail Dev Size : 3906764800 (1862.89 GiB 2000.26 GB)
     Array Size : 5860147200 (5588.67 GiB 6000.79 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
Recovery Offset : 308671456 sectors
   Unused Space : before=262056 sectors, after=0 sectors
          State : clean
    Device UUID : e1a702e3:6b8889aa:53609ad3:8591f761

Internal Bitmap : 8 sectors from superblock
    Update Time : Mon May 21 15:13:12 2018
  Bad Block Log : 512 entries available at offset 72 sectors
       Checksum : 2e93e216 - correct
         Events : 234

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 3
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sde:
   MBR Magic : aa55
Partition[0] :   3907029167 sectors at            1 (type ee)
/dev/sdd1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 27845ebe:8b19b4e1:e589d777:1bcea933
           Name : debian-t4:1  (local to host debian-t4)
  Creation Time : Mon May 21 15:15:22 2018
     Raid Level : raid5
   Raid Devices : 4

Avail Dev Size : 3906764800 (1862.89 GiB 2000.26 GB)
     Array Size : 5860147200 (5588.67 GiB 6000.79 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
   Unused Space : before=262056 sectors, after=0 sectors
          State : clean
    Device UUID : 3ca80292:e292b9ae:bcbdb0d0:04947062

Internal Bitmap : 8 sectors from superblock
    Update Time : Mon May 21 15:15:22 2018
  Bad Block Log : 512 entries available at offset 72 sectors
       Checksum : ce28714b - correct
         Events : 0

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 2
   Array State : AAA. ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdd:
   MBR Magic : aa55
Partition[0] :   3907029167 sectors at            1 (type ee)
/dev/sdb1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 27845ebe:8b19b4e1:e589d777:1bcea933
           Name : debian-t4:1  (local to host debian-t4)
  Creation Time : Mon May 21 15:15:22 2018
     Raid Level : raid5
   Raid Devices : 4

Avail Dev Size : 3906764800 (1862.89 GiB 2000.26 GB)
     Array Size : 5860147200 (5588.67 GiB 6000.79 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
   Unused Space : before=262056 sectors, after=0 sectors
          State : clean
    Device UUID : 6e00eaa3:2121171b:57e225f9:246f4712

Internal Bitmap : 8 sectors from superblock
    Update Time : Mon May 21 15:15:22 2018
  Bad Block Log : 512 entries available at offset 72 sectors
       Checksum : 24b95775 - correct
         Events : 0

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 0
   Array State : AAA. ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdb:
   MBR Magic : aa55
Partition[0] :   3907029167 sectors at            1 (type ee)
mdadm: No md superblock detected on /dev/sda5.
/dev/sda2:
   MBR Magic : aa55
Partition[0] :      7301120 sectors at            2 (type 82)
mdadm: No md superblock detected on /dev/sda1.
/dev/sda:
   MBR Magic : aa55
Partition[0] :   3899723776 sectors at         2048 (type 83)
Partition[1] :      7301122 sectors at   3899727870 (type 05)
root@debian-t4:~#

-- 
Mit freundlichem Gruß,
Axel Spallek
Dipl.-Ing. FH IE
Hochdorfer Straße 34
88477 Schönebürg
Mobil: 01577 7929886
E-Mail: mailto:axel@xxxxxxxxxxx
Bankverbindung:
Volksbank Schwendi
IBAN: DE20654913200095195009
BIC: GENODES1VBL
Steuernummer: 5433840045
UST.-ID.:     DE290536647


--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux