Upgraded to stoneburner now raid is missing

miategra · 29. Juni 2016

Hi Guys,

I probably made a mistake by not un-mounting the raid array before upgrading to stoneburner. I made a complete re-install to my ssd system disk but now OMV doesn't see raid array although it sees physical disks.
I'm really in need of help here.

Code

root@OMVmaxi:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md127 : inactive sdb[0] sdd[2] sdc[1]
      8790406536 blocks super 1.2

Code

root@OMVmaxi:~# blkid
/dev/sdc: UUID="27f66ba7-0bf4-a9fd-48f8-2763f7ad8793" UUID_SUB="f7ee4689-fc08-baf4-2cd0-05c11114f104" LABEL="omv2:omv2" TYPE="linux_raid_member"
/dev/sdf: UUID="27f66ba7-0bf4-a9fd-48f8-2763f7ad8793" UUID_SUB="4ce9e842-b7e4-783f-5dfa-ece257681110" LABEL="omv2:omv2" TYPE="linux_raid_member"
/dev/sdb: UUID="27f66ba7-0bf4-a9fd-48f8-2763f7ad8793" UUID_SUB="0679e4eb-b5fb-832d-382f-d597465f55fc" LABEL="omv2:omv2" TYPE="linux_raid_member"
/dev/sde: UUID="27f66ba7-0bf4-a9fd-48f8-2763f7ad8793" UUID_SUB="1256d9c1-a8fa-fdf5-335c-bde3b63400a8" LABEL="omv2:omv2" TYPE="linux_raid_member"
/dev/sdd: UUID="27f66ba7-0bf4-a9fd-48f8-2763f7ad8793" UUID_SUB="05919054-c5eb-d548-8002-a1b658d1c523" LABEL="omv2:omv2" TYPE="linux_raid_member"
/dev/sda1: UUID="f63e4bf3-5f8e-42e8-8884-a4fcec06a9aa" TYPE="ext4"
/dev/sda5: UUID="b7fdbf58-7fcf-4bbd-b9bf-1f3f8569b204" TYPE="swap"

Code

root@OMVmaxi:~# fdisk -l


Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 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: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 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/sde: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 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/sda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000a4e60


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048   112383999    56190976   83  Linux
/dev/sda2       112386046   117229567     2421761    5  Extended
/dev/sda5       112386048   117229567     2421760   82  Linux swap / Solaris


Disk /dev/sdf: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 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/sdd: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 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

Alles anzeigen

Code

root@OMVmaxi:~# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers


# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes


# automatically tag new arrays as belonging to the local system
HOMEHOST <system>


# instruct the monitoring daemon where to send mail alerts
MAILADDR root


# definitions of existing MD arrays


# This file was auto-generated on Mon, 29 Jun 2015 06:41:20 +0000
# by mkconf 3.2.5-5

Alles anzeigen

Code

root@OMVmaxi:~# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers


# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes


# automatically tag new arrays as belonging to the local system
HOMEHOST <system>


# instruct the monitoring daemon where to send mail alerts
MAILADDR root


# definitions of existing MD arrays


# This file was auto-generated on Mon, 29 Jun 2015 06:41:20 +0000
# by mkconf 3.2.5-5
root@OMVmaxi:~# ^C
root@OMVmaxi:~# mdadm --detail --scan --verbose
mdadm: cannot open /dev/md/omv2: No such file or directory
root@OMVmaxi:~#

Alles anzeigen

miategra · 29. Juni 2016

By the way I also tired to install backports but it didn't solve the issue also. Adding some screenshots also.

votdev · 29. Juni 2016

You have to activate your inactive raid, see the mdstats output. Use google how to do that.

miategra · 29. Juni 2016

@votdev
Thanks for your fast replay but sorry to say that I'm really un-experienced on linux. I just get the previous codes from the forum how to check the raid status. I don't want to loose the data on 5 disks. If someone can guide me I will be very glad.

ryecoaaron · 29. Juni 2016

mdadm --stop /dev/md127
mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcdef]
mdadm --examine --scan >> /etc/mdadm.conf
update-initramfs -u

miategra · 29. Juni 2016

@ryecoaaron

Thanks but here it is

Code

root@OMVmaxi:~# mdadm --stop /dev/md127
mdadm: stopped /dev/md127


root@OMVmaxi:~# mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcdef]
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb is identified as a member of /dev/md127, slot 0.
mdadm: /dev/sdc is identified as a member of /dev/md127, slot 1.
mdadm: /dev/sdd is identified as a member of /dev/md127, slot 2.
mdadm: /dev/sde is identified as a member of /dev/md127, slot 3.
mdadm: /dev/sdf is identified as a member of /dev/md127, slot 4.
mdadm: forcing event count in /dev/sdf(4) from 656730 upto 656734
mdadm: clearing FAULTY flag for device 4 in /dev/md127 for /dev/sdf
mdadm: Marking array /dev/md127 as 'clean'
mdadm: added /dev/sdc to /dev/md127 as 1
mdadm: added /dev/sdd to /dev/md127 as 2
mdadm: added /dev/sde to /dev/md127 as 3 (possibly out of date)
mdadm: added /dev/sdf to /dev/md127 as 4
mdadm: added /dev/sdb to /dev/md127 as 0
mdadm: /dev/md127 has been started with 4 drives (out of 5).




root@OMVmaxi:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-3.16.0-0.bpo.4-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.


root@OMVmaxi:~# mdadm --examine --scan >> /etc/mdadm.conf

Alles anzeigen

ryecoaaron · 29. Juni 2016

What is the output of: cat /proc/mdstat

miategra · 30. Juni 2016

Code

root@OMVmaxi:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md127 : active raid5 sdb[0] sdf[4](F) sdd[2] sdc[1]
      11720540160 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/3] [UUU__]


unused devices: <none>

ryecoaaron · 30. Juni 2016

You have one failed drive and the other is missing. Check your connectors. You can't start raid 5 with two missing disks.

miategra · 30. Juni 2016

@ryecoaaron

I know that it looks like that but also can you check the screen shots that I sent before. If there is a connection problem how cam smart monitor can report drives as OK. I'm confused at this point.

ryecoaaron · 30. Juni 2016

Just because smart says it is ok does not mean it is ok. I agree that does probably mean the cable is ok. All I can say is that I help with so many raid issues that I get them mixed up. I am really tired of all these arrays not starting.

What I do know is that mdadm is saying one drive failed and another drive doesn't have array info. With raid 5, that is very bad. If you zero one drive to re-add it to the array, you might lose all data. You need to be able to start the array with four drives and have it working to zero one drive. Because my other command didn't work, there aren't many options left.

I would run longer smart tests on each drive.

miategra · 17. Juli 2016

Sorry for the late replay.
I was out of Country for 14 days and I hadn’t got time to deal with server.
Made self-long tests for the five disks an all completed without error. I have dumb question. Although I’m nearly sure I haven’t done it. Can it be caused by swapped sata cables?

miategra · 19. Juli 2016

Any suggestions ?

Upgraded to stoneburner now raid is missing

Jetzt mitmachen!

Tags