Status - media - error in RRD::

1

Hello!

How can i remove this error?

ERROR
ERROR1920×1040 127 KB 

[root@wrouter ~]# cat /proc/partitions
major minor  #blocks  name

   1        0      16384 ram0
   1        1      16384 ram1
   1        2      16384 ram2
   1        3      16384 ram3
   1        4      16384 ram4
   1        5      16384 ram5
   1        6      16384 ram6
   1        7      16384 ram7
   1        8      16384 ram8
   1        9      16384 ram9
   1       10      16384 ram10
   1       11      16384 ram11
   1       12      16384 ram12
   1       13      16384 ram13
   1       14      16384 ram14
   1       15      16384 ram15
   8        0  250059096 sda
   8        1     131072 sda1
   8        2      32768 sda2
   8        3    1048576 sda3
   8        4  248844632 sda4
   8       16 5860522584 sdb
   8       32 5860522584 sdc
   9      126 11721039872 md126
 259        0 11721038831 md126p1
2

What sort of device is md127?
Can you see it with ls -1 /sys/block ( the method media.cgi determines the disk devices )?
( maybe ll /sys/block enlightens more )

3

The top graph is looking for raid array md126 but smartctl is looking for raid array md127 which doesn’t exist.

What was being done on the IPFire system just before this message was seen.

Were there two raid arrays installed on IPFire, both md126 and md127, or just md126.

4 
    [root@wrouter ~]# ls -1 /sys/block
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
md126
md127
ram0
ram1
ram10
ram11
ram12
ram13
ram14
ram15
ram2
ram3
ram4
ram5
ram6
ram7
ram8
ram9
sda
sdb
sdc
5

When I installed ipfire there was an ntfs filesystem on this raid array.
I completely deleted everything from the raid array and created a logical partition and formatted it to ext4

6 
[root@wrouter ~]# ls -l1 /sys/block
total 0
lrwxrwxrwx 1 root root 0 May 31 18:20 loop0 -> ../devices/virtual/block/loop0
lrwxrwxrwx 1 root root 0 May 31 18:20 loop1 -> ../devices/virtual/block/loop1
lrwxrwxrwx 1 root root 0 May 31 18:20 loop2 -> ../devices/virtual/block/loop2
lrwxrwxrwx 1 root root 0 May 31 21:43 loop3 -> ../devices/virtual/block/loop3
lrwxrwxrwx 1 root root 0 May 31 18:20 loop4 -> ../devices/virtual/block/loop4
lrwxrwxrwx 1 root root 0 May 31 21:43 loop5 -> ../devices/virtual/block/loop5
lrwxrwxrwx 1 root root 0 May 31 18:20 loop6 -> ../devices/virtual/block/loop6
lrwxrwxrwx 1 root root 0 May 31 18:20 loop7 -> ../devices/virtual/block/loop7
lrwxrwxrwx 1 root root 0 May 31 18:17 md126 -> ../devices/virtual/block/md126
lrwxrwxrwx 1 root root 0 May 31 18:17 md127 -> ../devices/virtual/block/md127
lrwxrwxrwx 1 root root 0 May 31 18:20 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx 1 root root 0 May 31 18:20 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx 1 root root 0 May 31 18:20 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx 1 root root 0 May 31 21:43 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx 1 root root 0 May 31 18:20 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx 1 root root 0 May 31 21:43 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx 1 root root 0 May 31 18:20 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx 1 root root 0 May 31 18:20 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx 1 root root 0 May 31 18:20 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx 1 root root 0 May 31 18:20 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx 1 root root 0 May 31 21:43 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx 1 root root 0 May 31 18:20 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx 1 root root 0 May 31 21:43 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx 1 root root 0 May 31 18:20 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx 1 root root 0 May 31 21:43 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx 1 root root 0 May 31 18:20 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx 1 root root 0 May 31 18:17 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 May 31 18:17 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb
lrwxrwxrwx 1 root root 0 May 31 18:17 sdc -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc
7

Do you have one or two RAID arrays?

8

one raid array.

/dev/sda - 250gb Samsung SSD
/dev/sdb - 6TB WD HDD
/dev/sdc - 6TB WD HDD

SDB and SDC = RAID0

9

What shows up on the menu Services - ExtraHD

10

MD127
MD1271920×1040 92.1 KB

it looks like md127 but i don’t know what to do with it.

11 
[root@wrouter ~]# cat /proc/mdstat
Personalities : [raid0]
md126 : active raid0 sdb[1] sdc[0]
      11721039872 blocks super external:/md127/0 128k chunks

md127 : inactive sdb[1](S) sdc[0](S)
      5296 blocks super external:imsm
12

The combination of external:/md… on one raid array and external:imsm on the second raid array I have found to be mentioned as related to when proc/mdstat breaks its parsing when dealing with Intel bios Raid

Was your original raid with the ntfs system based on Intel bios Raid? If no then I have no idea why mdstat is showing what it is showing.

From what I have read, Intel bios Raid has created md127 as a container. The actual raid array created inside md127 is md126.

From what I have read mdadm status programme mdstat can’t parse the Intel bios Raid containers properly so you get this inactive raid container showing up.

Either way my suggestion, if you have not stored any data yet on the sdb/sdc raid array, would be to stop the array, remove the individual drives from it and then clear the superblocks from sdb and sdc and start over with creating the raid array using the mdadm commands, maybe even going back to setting the partitions up on sdb and adc with fdisk as fresh Linux raid partitions before creating the raid arrays.

13

I have found that mdadm has three superblock formats that can be used. The standard mdadm superblock format, DDF (Disk Data Format) and IMSM (Intel Matrix Storage Manager).

It looks like your raid drive is using the Intel IMSM format which creates raid arrays inside containers. DDF also creates raid arrays inside containers.

Was the raid array with the ntfs filesystem on it working with IPFire. What I am not familiar enough about is if IPFire can recognise this raid array inside containers structure or not.

All my raid array experience is with the basic mdadm v0.9 and v1.2 superblock format approach and I have not used raid on IPFire.