RAID5 Grow (failed?) - device removed??!

microdots · 13. November 2013

Hey!

I tried to grow my RAID5 with the built-in grow function. It took around 16-17 hours and now the RAID is just clean, degraded. (http://d.pr/i/qbFr) ... it states now the 7,28TB (instead of 5,4TB before). But ...

Code

mdadm --misc --detail /dev/md0
/dev/md0:
        Version : 1.2
  Creation Time : Wed Apr  3 22:52:27 2013
     Raid Level : raid5
     Array Size : 7814051840 (7452.06 GiB 8001.59 GB)
  Used Dev Size : 1953512960 (1863.02 GiB 2000.40 GB)
   Raid Devices : 5
  Total Devices : 4
    Persistence : Superblock is persistent


    Update Time : Wed Nov 13 11:47:02 2013
          State : active, degraded
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0


         Layout : left-symmetric
     Chunk Size : 512K


           Name : openmediavault:HOLORAID
           UUID : ce5ef9ad:519fcb80:51a665e4:9b98483c
         Events : 24093


    Number   Major   Minor   RaidDevice State
       0       8       48        0      active sync   /dev/sdd
       1       8       64        1      active sync   /dev/sde
       2       0        0        2      removed
       3       8       32        3      active sync   /dev/sdc
       4       8       16        4      active sync   /dev/sdb

Alles anzeigen

Last time I did this there was in the last row a "faulty spare". So /dev/sdb is the added HDD for the RAID5: http://d.pr/i/5STZ

I already clicked (unfortunately a few times since I thought ...nothing would happen) in the resize button here http://d.pr/i/j9Ur then I noticed this message in /var/log/messages:

Code

Nov 13 11:40:52 HOLONAS kernel: [  228.010971] EXT4-fs warning (device md0): ext4_group_extend: multiple resizers run on filesystem!

Is everything fine? I see the Filesystem is now becoming larger... that is a good sign, isn't it?? I am a bit afraid something went wrong. What would be my next step (besides waiting for the resize to be done)?

Will the 5th drive be added on its own (which is now 'removed' - but that drive was never removed - that is what makes me concerned... I can access the RAID over afp though... so everything is still there.

Hope someone knows how to handle this!

edit:

output from fdisk -l

Code

fdisk -l


Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e8146


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       29490   236876800   83  Linux
/dev/sda2           29491       30402     7319553    5  Extended
/dev/sda5           29491       30402     7319552   82  Linux swap / Solaris


Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


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


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


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


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


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


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


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


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


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


Disk /dev/md0: 8001.6 GB, 8001589084160 bytes
2 heads, 4 sectors/track, 1953512960 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 2097152 bytes
Disk identifier: 0x00000000


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

Alles anzeigen

Output from /proc/mdstat

Code

cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sdd[0] sdb[4] sdc[3] sde[1]
      7814051840 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/4] [UU_UU]


unused devices: <none>

Output from mount:

Code

mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw)
/dev/md0 on /media/05617d64-3b86-46a5-a058-dacbb21a0f2e type ext4 (rw,noexec,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0)

ryecoaaron · 13. November 2013

Did you have a drive going bad before adding the new one by any chance? Was the array clean/active before you added? I would try rebooting. If that doesn't add it, try as root:

mdadm --add /dev/md0 /dev/sdf

If that doesn't complete it, then

mdadm --grow /dev/md0 --raid-devices=5

microdots · 13. November 2013

Everything was clean when I started. I added /dev/sdf now and it's recovering ... hopefully that won't take too long. Guess next time I don't use the GUI for growing.

Code

Version : 1.2
  Creation Time : Wed Apr  3 22:52:27 2013
     Raid Level : raid5
     Array Size : 7814051840 (7452.06 GiB 8001.59 GB)
  Used Dev Size : 1953512960 (1863.02 GiB 2000.40 GB)
   Raid Devices : 5
  Total Devices : 5
    Persistence : Superblock is persistent


    Update Time : Wed Nov 13 16:32:45 2013
          State : clean, degraded, recovering
 Active Devices : 4
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 1


         Layout : left-symmetric
     Chunk Size : 512K


 Rebuild Status : 0% complete


           Name : openmediavault:HOLORAID
           UUID : ce5ef9ad:519fcb80:51a665e4:9b98483c
         Events : 25158


    Number   Major   Minor   RaidDevice State
       0       8       48        0      active sync   /dev/sdd
       1       8       64        1      active sync   /dev/sde
       2       8       80        2      spare rebuilding   /dev/sdf
       3       8       32        3      active sync   /dev/sdc
       4       8       16        4      active sync   /dev/sdb

Alles anzeigen

Does this look right now? Space device...?

ryecoaaron · 13. November 2013

The gui is what I use for growing. It shouldn't be a spare but when you reboot it might add it automatically. Otherwise, we can try a couple more things.

microdots · 18. November 2013

Hey ryeocaaron,

it worked somehow after all. But now the Raid5 seems to be quite slow - I often get disconnects over AFP and SMB andiTunes DAAP. OMV says the RAID is clean. How could I approach this? The newly added HDD is on another SATA lane - could that be the reason?

Cheers!

ryecoaaron · 18. November 2013

If you are using daapd with iTunes, it is known issue with the older version of forked-daapd. AFP and samba shouldn't be disconnecting though. Anything in the Messages log?

Jetzt mitmachen!