Re: Problems with raid after reboot.

[Robin Hill <robin@robinhill.me.uk>]

[-- Attachment #1: Type: text/plain, Size: 2616 bytes --]

On Mon Jul 25, 2011 at 03:55:02PM -0600, Matthew Tice wrote:

> So now it's syncing:
> # mdadm --detail /dev/md0
> /dev/md0:
>         Version : 00.90
>   Creation Time : Sat Mar 12 21:22:34 2011
>      Raid Level : raid5
>      Array Size : 2197723392 (2095.91 GiB 2250.47 GB)
>   Used Dev Size : 732574464 (698.64 GiB 750.16 GB)
>    Raid Devices : 4
>   Total Devices : 4
> Preferred Minor : 0
>     Persistence : Superblock is persistent
> 
>     Update Time : Mon Jul 25 15:52:29 2011
>           State : clean, degraded, recovering
>  Active Devices : 3
> Working Devices : 4
>  Failed Devices : 0
>   Spare Devices : 1
> 
>          Layout : left-symmetric
>      Chunk Size : 64K
> 
>  Rebuild Status : 0% complete
> 
>            UUID : daf06d5a:b80528b1:2e29483d:f114274d (local to host storage)
>          Events : 0.5599
> 
>     Number   Major   Minor   RaidDevice State
>        4       8       64        0      spare rebuilding   /dev/sde
>        1       8       48        1      active sync   /dev/sdd
>        2       8       32        2      active sync   /dev/sdc
>        3       8       16        3      active sync   /dev/sdb
> 
> # cat /proc/mdstat
> Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5]
> [raid4] [raid10]
> md0 : active raid5 sde[4] sdd[1] sdb[3] sdc[2]
>       2197723392 blocks level 5, 64k chunk, algorithm 2 [4/3] [_UUU]
>       [>....................]  recovery =  0.4% (3470464/732574464)
> finish=365.0min speed=33284K/sec
> 
> unused devices: <none>
> 
> 
> However, it's still failing an fsck - so does order matter when I
> re-assemble the array?  I see conflicting answers online.
> 
No, order only matters if you're recreating the array (which is a
last-ditch option for if assembly fails). The metadata on each drive
indicates where it should be in the array, so the assembly will use that
to order the drives.

The fsck errors would look to be genuine issues with the filesystem. Was
the array shut down cleanly before you moved it? You did have to force
the assembly initially, which would suggest not (and could point to some
minor corruption). I'm not sure you have much of an option other than to
go through with a fsck & repair any issues now though (if you've got the
space then I'd suggest imaging the array as a backup though). 

Cheers,
    Robin
-- 
     ___        
    ( ' }     |       Robin Hill        <robin@robinhill.me.uk> |
   / / )      | Little Jim says ....                            |
  // !!       |      "He fallen in de water !!"                 |

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]