Error creating Raid 5

[Jocko]

Hi b1gnas,

In addition with fvdw's post to test the kernel:
- untar the modules file in the folder /lib/modules/3.18.21
- do not write the kernel image on sda6 but use fvdw-sl console to load this new version (load external kernel option). So store the uimage file in the folder tftp/5big1.

if the nas boots then you can overwrite 3.14.2 by this one on sda6.

[b1gnas]

Hi Jocko,

using load external kernel option all back leds become red and frontal led is red and blinking

[fvdw]

you must use the u-boot console of the fvdw-sl console to load the kernel with the parameters set to enable netconsole
It is the only way to find out what is going on when loading this kernel

viewtopic.php?f=30&t=2168&start=250#p20536

[b1gnas]

Code: Select all

provided by fvdw
waiting for u-boot..
starting u-boot net console click on window and press enter


Marvell>> setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@$
{serverip}/ root=/dev/sda7
setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}
/ root=/dev/sda7
Marvell>> printenv bootargs
printenv bootargs
bootargs=console=ttyS0,115200 netconsole=6666@192.168.188.30/,6666@192.168.188.2
0/ root=/dev/sda7
Marvell>> ide reset
ide reset

Reset IDE:
Marvell Serial ATA Adapter
Found adapter at bus 1, device 7 ... Scanning channels
Error - Failed initializing(SRST) drive on channel 0
Failed initializing storage deivce connected to SATA channel 0
Error - Failed initializing(SRST) drive on channel 1
Failed initializing storage deivce connected to SATA channel 1
  Device 2: OK
Model: ST1000DM003-1ER162                       Firm: CC45     Ser#:
 W4Y0QLDA
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
  Device 3: OK
Model: ST1000DM003-1ER162                       Firm: CC45     Ser#:
 W4Y0RF1K
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
Error - Failed initializing(SRST) drive on channel 4
Failed initializing storage deivce connected to SATA channel 4

Marvell>> tftpboot 0x400000 UIMAGE-31821-5BIG1-7
tftpboot 0x400000 UIMAGE-31821-5BIG1-7
Using egiga0 device
TFTP from server 192.168.188.20; our IP address is 192.168.188.30
Filename 'UIMAGE-31821-5BIG1-7'.
Load address: 0x400000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #########
done
Bytes transferred = 2040240 (1f21b0 hex)
Marvell>> bootm
bootm
## Booting image at 00400000 ...
   Image Name:   Linux-3.18.21
   Created:      2015-10-10  22:02:50 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2040176 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...




Something went wrong.... 3 disks failed

and if i start the nas normally there's always red leds and the nas doesn't boot anymore :hairpull

[fvdw]

the kernel doesn't do anything to the disks.
The problem already exist when we perform a ide reset, u-boot doesn't find three disks and the kernel then will fail as well as it cannot find disk sda (device 4)
So even before the kernel is loaded the disk are not detected

That is also the reason why the nas won't boot normally anymore as it doesn't find a system disk.
The red flashing indicates this error

The reason is now why is this happening
What you could do is the following, turn of take out all disks. Then only put back disk sda and put it in slot 1, then open the u-boot console of the fvdw-sl console and at marvell prompt give command

Code: Select all

ide reset

to see if now the disk is found
if that works then give command

ide part

that should show partition info
If that works ok then try again to load the new kernel in the u-boot console

seem your ata controller may have a an issue (hardware issue) and give erratic behavior

[b1gnas]

What you could do is the following, turn of take out all disks. Then only put back disk sda and put it in slot 1, then open the u-boot console of the fvdw-sl console and at marvell prompt give command

Code: Select all

ide reset

to see if now the disk is found

Code: Select all

provided by fvdw
waiting for u-boot..
starting u-boot net console click on window and press enter



Marvell>> ide reset
ide reset

Reset IDE:
Marvell Serial ATA Adapter
Found adapter at bus 1, device 7 ... Scanning channels
Error - Failed initializing(SRST) drive on channel 4
Failed initializing storage deivce connected to SATA channel 4

Marvell>>

[fvdw]

Your hard disk doesn't want to communicate properly with u-boot

Are there any jumpers on the drive you use for setting it to master ,slave or cable select ?
If so put it to cable select and try again

[b1gnas]

No jumpers

Now after some switch off/switch on, blue leds are blinking but i don't know what it's doing...

[b1gnas]

Now the nas booted but i have a problem with the raid

Code: Select all

root@fvdwsl-base:/ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sdb8[0] sda8[4] sde8[3] sdc8[1]
      3893898496 blocks level 5, 64k chunk, algorithm 2 [5/4] [UU_UU]
     
unused devices: <none>
root@fvdwsl-base:/ # mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90.03
  Creation Time : Wed Nov 16 13:22:21 2011
     Raid Level : raid5
     Array Size : 3893898496 (3713.51 GiB 3987.35 GB)
    Device Size : 973474624 (928.38 GiB 996.84 GB)
   Raid Devices : 5
  Total Devices : 4
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Mon Oct 12 19:53:34 2015
          State : clean, degraded
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

           UUID : fa58a2b1:a56fc1c1:2a5b9325:5626151a
         Events : 0.12790

    Number   Major   Minor   RaidDevice State
       0       8       56        0      active sync   /dev/sdb8
       1       8       40        1      active sync   /dev/sdc8
       2       0        0        2      removed
       3       8        8        3      active sync   /dev/sde8
       4       8       72        4      active sync   /dev/sda8
root@fvdwsl-base:/ #


[Jocko]

Hi b1gnas,

check if sdd is detected

Code: Select all

fdisk -l /dev/sdd

If yes you can tried to add it in the raid

Code: Select all

mdadm --manage /dev/md0 --re-add /dev/sdd8