Error creating Raid 5

Re: Error creating Raid 5

Postby Jocko » Tue Apr 21, 2015 8:48 pm

If in mdstat, you have the recovery line, then it will be ok...
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Error creating Raid 5

Postby b1gnas » Tue Apr 21, 2015 8:56 pm

mmmh

Code: Select all
root@fvdwsl-base:/ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sde8[4](F) sdd8[2] sdc8[5](F) sdb8[0]
      2920423872 blocks level 5, 64k chunk, algorithm 2 [4/2] [U_U_]
     
unused devices: <none>
b1gnas
 
Posts: 145
Joined: Fri Apr 17, 2015 8:11 am

Re: Error creating Raid 5

Postby Jocko » Tue Apr 21, 2015 9:11 pm

:hairpull
What said mke2fs ?

and
Code: Select all
 mdadm --detail /dev/md0
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Error creating Raid 5

Postby b1gnas » Wed Apr 22, 2015 6:35 am

tried a second time. When i rebooted i had 2 red disk led on the back

mke2fs is blocked here

Code: Select all
root@fvdwsl-base:/ # mke2fs -t ext3 -j -m 1 /dev/md0
mke2fs 1.42.11 (09-Jul-2014)
Creating filesystem with 730105968 4k blocks and 182534144 inodes
Filesystem UUID: a5b99f53-ed61-4faf-9090-05856974c08f
Superblock backups stored on blocks:
   32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
   4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
   102400000, 214990848, 512000000, 550731776, 644972544

Allocating group tables: done                           
Writing inode tables: done                           
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information:           
b1gnas
 
Posts: 145
Joined: Fri Apr 17, 2015 8:11 am

Re: Error creating Raid 5

Postby b1gnas » Wed Apr 22, 2015 6:50 am

deleted the raid and rebooted, but i always have two red disk led sda and sdd i suppose
b1gnas
 
Posts: 145
Joined: Fri Apr 17, 2015 8:11 am

Re: Error creating Raid 5

Postby fvdw » Wed Apr 22, 2015 7:13 am

probably yes, but looking from the back which led is red ?
why don't you post the output of
Code: Select all
mdadm --detail /dev/md0

?

ps mke2fs can take a while to finish

To see if the kernel has seen all your diks please gain once more the output of dmesg command
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Error creating Raid 5

Postby Jocko » Wed Apr 22, 2015 7:25 am

After setting a raid, when you reboot if a disk has a fail status, the related RED LED is on.

Note: and when the raid has a recovery status, all LED of the related disks are blinking red/blue.

So with your previous posts, I think it is right to have two red LED.

Note2: to get a raid5 you need at least to have 3 clean devices. Currently, your raid status is 2 clean devices and 2 fail devices. It is why your raid don't have the recovery status and you can not format it (it fails to save the superblocks in the root directory of the file system)

With your last trial, the two fail disks still are they the Hitachi disks ?
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Error creating Raid 5

Postby b1gnas » Wed Apr 22, 2015 1:58 pm

redone all from the beginnig, deleted all partitions, repartioned all 4 disks, so all back led was blue.

Now creating again the raid, formatting and it is blocked here

Code: Select all
root@fvdwsl-base:/ # mdadm --create /dev/md0 --level=5 --assume-clean --raid-dev
ices=4 /dev/sdb8 /dev/sdc8 /dev/sdd8 /dev/sde8
mdadm: /dev/sdb8 appears to contain an ext2fs file system
    size=973474740K  mtime=Wed Apr 22 17:24:38 2015
mdadm: /dev/sdc8 appears to contain an ext2fs file system
    size=973474740K  mtime=Wed Apr 22 17:24:38 2015
mdadm: /dev/sdd8 appears to contain an ext2fs file system
    size=973474740K  mtime=Wed Apr 22 17:24:38 2015
mdadm: /dev/sde8 appears to contain an ext2fs file system
    size=973474740K  mtime=Wed Apr 22 17:24:38 2015
Continue creating array? y
mdadm: array /dev/md0 started.
root@fvdwsl-base:/ # cat /etc/mdadm.0 > /etc/mdadm.conf
root@fvdwsl-base:/ # mdadm --detail --scan >> /etc/mdadm.conf
root@fvdwsl-base:/ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sde8[3] sdd8[2] sdc8[1] sdb8[0]
      2920423872 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
     
unused devices: <none>
root@fvdwsl-base:/ # mke2fs -t ext3 -j -m 1 /dev/md0
mke2fs 1.42.11 (09-Jul-2014)
/dev/md0 contains a ext3 file system
   last mounted on Wed Apr 22 17:24:38 2015
Proceed anyway? (y,n) y
Creating filesystem with 730105968 4k blocks and 182534144 inodes
Filesystem UUID: 4d10ab1a-9807-4906-bdfe-c9a85309e575
Superblock backups stored on blocks:
   32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
   4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
   102400000, 214990848, 512000000, 550731776, 644972544

Allocating group tables: done                           
Writing inode tables: done                           
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information:         


In the while from another ssh session

Code: Select all
root@fvdwsl-base:/ # mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90.03
  Creation Time : Wed Apr 22 17:32:04 2015
     Raid Level : raid5
     Array Size : 2920423872 (2785.13 GiB 2990.51 GB)
    Device Size : 973474624 (928.38 GiB 996.84 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Wed Apr 22 17:33:33 2015
          State : active, degraded
 Active Devices : 2
Working Devices : 2
 Failed Devices : 2
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

           UUID : cacb412e:2042a25e:dffee99d:ebaa035e
         Events : 0.4

    Number   Major   Minor   RaidDevice State
       0       8       56        0      active sync   /dev/sdb8
       1       0        0        1      removed
       2       0        0        2      removed
       3       8        8        3      active sync   /dev/sde8

       4       8       24        -      faulty spare   /dev/sdd8
       5       8       40        -      faulty spare   /dev/sdc8


sdc and sdd are the hitachi disks

dmeg is full of these errors, i can't post all the output

Code: Select all
root@fvdwsl-base:/ # dmesg
lost page write due to I/O error on md0
quiet_error: 68597 callbacks suppressed
Buffer I/O error on device md0, logical block 314572942
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 314572926
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 314572943
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 314572927
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 314572928
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 314572929
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 314572930
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 314572931
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 314572932
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 314572933
lost page write due to I/O error on md0
quiet_error: 68743 callbacks suppressed
Buffer I/O error on device md0, logical block 318963983
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 318963984
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 318964000
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 318964016
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 318963985
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 318964001
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 318964017
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 318963986
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 318964002
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 318964018
lost page write due to I/O error on md0
quiet_error: 68895 callbacks suppressed
Buffer I/O error on device md0, logical block 323387464
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 323387448
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 323387465
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 323387449
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 323387466
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 323387450
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 323387467
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 323387451
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 323387468
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 323387452
lost page write due to I/O error on md0
quiet_error: 68606 callbacks suppressed
Buffer I/O error on device md0, logical block 327778368
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 327778384
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 327778400
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 327778369
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 327778385
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 327778401
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 327778370
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 327778386
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 327778402
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 327778371
lost page write due to I/O error on md0
quiet_error: 67905 callbacks suppressed
Buffer I/O error on device md0, logical block 332104075
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 332104076
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 332104077
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 332104078
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 332104079
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 332104080
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 332104096
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 332104112
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 332104081
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 332104097
lost page write due to I/O error on md0
quiet_error: 68457 callbacks suppressed
Buffer I/O error on device md0, logical block 336494862
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 336494878
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 336494846
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 336494863
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 336494879
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 336494847
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 336494848
lost page write due to I/O error on md0


This time all leds are blue
b1gnas
 
Posts: 145
Joined: Fri Apr 17, 2015 8:11 am

Re: Error creating Raid 5

Postby Jocko » Wed Apr 22, 2015 2:53 pm

Thank for this posts.
b1gnas wrote:This time all leds are blue
It is normal because the raid monitor is not running (need to reboot to start it) and so the LED status is not yet updated.

b1gnas wrote:sdc and sdd are the hitachi disks
As at the beginning it was already these disks which have a failure status, I am more and more convinced that your issue is these disks even if SMART returns no error about them.

if you are able to use another disk even with a small size we can check it.

To do it create a partition table on it and replace one Hitachi disk. Then try to create a raid5 with 3 devices : 2 Seagate disks and with new disk.

If you can do it then that means that there is an issue with these 2 disks and need to find how to repair them.
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Error creating Raid 5

Postby fvdw » Wed Apr 22, 2015 9:09 pm

seems those hitachi disks have a problem

I suggest that you format the partitions in ext3 and then run fsck on them and see what it mentions

fsck /dev/sdd8
fsck /dev/sdc8

(the partitions should be unmounted first before formatting and running fsck)

ps instead of raid5 you could try if you succeed to build a raid1 array of these 4 disks
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

PreviousNext

Return to Lacie 5Big Network vs1

Who is online

Users browsing this forum: No registered users and 7 guests