RAID 6 gone, physical drives visible

Hello,

had big troubles after a thunderstorm - power was cut and some strange things started :

the system i use Raid 6 123x3TB worked for about 4 or 5 days quite normally then after i rebootet the system i found the following situation ;

the raid was gone and in the FS section the raid was mentioned by name but n/a and N/V entries were shown ....

after another reboot the above mentioned FS entry for the raid part was gone for good.

the physical drives are all visible ....

so i installed OMV on another hdd and re-connected the raid drives - same result ..

any ideas - and if possible a solution within the web gui or detailed instructions for any kind of shell usage ...

cheers ahab666

i would have but it was disabled - not clickable - after the raid entry in the FS section was gone another thing occured - even though all 12 HDDs are physically available, i dont see any one of them in the raid building window ... i am a little stressed out atm b3ecause i might have lost like 16 TB of data ...

thx ahab666

hello thx for your "condolences" - but yes i am sure. i just use a 16 port LSI sas/sata controller without any HW-Raid functionality.
and yes - the system worked (no raid degarde even) for 4 or 5 days after the surge and all the discs are shown in the phyical disk section of the OMV Web Gui. i will use spinrite soon to check the disks soon ....

hello wastlJ :

the requestet blkid output :

/dev/sda1: UUID="6ac66484-42b3-48ad-8430-072852de03ab" TYPE="ext4"
/dev/sda5: UUID="6edd6d3a-11b9-4188-848c-0c2f2c9a73fa" TYPE="swap"
/dev/sdb: UUID="6230a09b-2bd2-f0af-b6f7-2e1946e3b8b3" UUID_SUB="46407afa-b56c-6c a7-79f4-f3497240040d" LABEL="OMV:OMV" TYPE="linux_raid_member"
/dev/sdd: UUID="6230a09b-2bd2-f0af-b6f7-2e1946e3b8b3" UUID_SUB="eca180cd-b1e6-78 0a-8c0b-669a5e2b4c43" LABEL="OMV:OMV" TYPE="linux_raid_member"
/dev/sdc: UUID="6230a09b-2bd2-f0af-b6f7-2e1946e3b8b3" UUID_SUB="76ccce05-7b75-2f 60-1a1c-e8394aabaede" LABEL="OMV:OMV" TYPE="linux_raid_member"
/dev/sde: UUID="6230a09b-2bd2-f0af-b6f7-2e1946e3b8b3" UUID_SUB="45ad475e-4fbc-af 93-722d-499caad9dbe8" LABEL="OMV:OMV" TYPE="linux_raid_member"
/dev/sdf: UUID="6230a09b-2bd2-f0af-b6f7-2e1946e3b8b3" UUID_SUB="c6856d1d-314f-d2 35-60e0-0af84c0150ec" LABEL="OMV:OMV" TYPE="linux_raid_member"
/dev/sdg: UUID="6230a09b-2bd2-f0af-b6f7-2e1946e3b8b3" UUID_SUB="f98d325f-913e-75 cb-adcd-8fb3fdc053b4" LABEL="OMV:OMV" TYPE="linux_raid_member"
/dev/sdh: UUID="6230a09b-2bd2-f0af-b6f7-2e1946e3b8b3" UUID_SUB="d7c2bfc6-fcbf-4c f5-f507-e22db1e8ce30" LABEL="OMV:OMV" TYPE="linux_raid_member"
/dev/sdi: UUID="6230a09b-2bd2-f0af-b6f7-2e1946e3b8b3" UUID_SUB="51b73ff6-4016-84 14-9899-8b25da11f007" LABEL="OMV:OMV" TYPE="linux_raid_member"
/dev/sdk: UUID="6230a09b-2bd2-f0af-b6f7-2e1946e3b8b3" UUID_SUB="8bdeee4f-18de-aa a5-a65f-148f57c581f0" LABEL="OMV:OMV" TYPE="linux_raid_member"
/dev/sdl: UUID="6230a09b-2bd2-f0af-b6f7-2e1946e3b8b3" UUID_SUB="32752f25-7f1e-0c f4-1363-440f59911248" LABEL="OMV:OMV" TYPE="linux_raid_member"
/dev/sdm: UUID="6230a09b-2bd2-f0af-b6f7-2e1946e3b8b3" UUID_SUB="7baee838-006e-d0 ae-d087-1beea06b7dc3" LABEL="OMV:OMV" TYPE="linux_raid_member"
/dev/sdj: UUID="6230a09b-2bd2-f0af-b6f7-2e1946e3b8b3" UUID_SUB="29fcb9ac-b1f4-17 94-bd3b-07d441ac6f1b" LABEL="OMV:OMV" TYPE="linux_raid_member"

looks like the harddisks still have their raid ids ....

Zitat von WastlJ

Code

cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
unused devices: <none>
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=6ac66484-42b3-48ad-8430-072852de03ab /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=6edd6d3a-11b9-4188-848c-0c2f2c9a73fa none            swap    sw              0       0
/dev/sdb1       /media/usb0     auto    rw,user,noauto  0       0

Alles anzeigen

i'd like to mention that i never used raid 5 on any of my data discs ...

Zitat von WastlJ

Looks like you do not even have a raid.

mdadm --assemble /dev/md127 /dev/sd[bcdefghijklm] --verbose --force --level=6

root@OMV:~# mdadm --assemble /dev/md127 /dev/sd[bcdefghijklm] --verbose --force                                                   --level=6
mdadm:option --level not valid in assemble mode

strage indeed ....

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 5.
mdadm: /dev/sdg is identified as a member of /dev/md127, slot 4.
mdadm: /dev/sdh is identified as a member of /dev/md127, slot 6.
mdadm: /dev/sdi is identified as a member of /dev/md127, slot 8.
mdadm: /dev/sdj is identified as a member of /dev/md127, slot 7.
mdadm: /dev/sdk is identified as a member of /dev/md127, slot 9.
mdadm: /dev/sdl is identified as a member of /dev/md127, slot 10.
mdadm: /dev/sdm is identified as a member of /dev/md127, slot 11.
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
mdadm: added /dev/sdg to /dev/md127 as 4
mdadm: added /dev/sdf to /dev/md127 as 5
mdadm: added /dev/sdh to /dev/md127 as 6
mdadm: added /dev/sdj to /dev/md127 as 7 (possibly out of date)
mdadm: added /dev/sdi to /dev/md127 as 8
mdadm: added /dev/sdk to /dev/md127 as 9
mdadm: added /dev/sdl to /dev/md127 as 10
mdadm: added /dev/sdm to /dev/md127 as 11
mdadm: added /dev/sdb to /dev/md127 as 0
mdadm: /dev/md127 has been started with 11 drives (out of 12).

out of date ???
mounted the file system - worked - but was unreferenced in the beginning - now it is referenced - will start a rebuild run to see if the degraded status will clean ...

thx for your efforts - alex aka ahab666

during rebuild i got a server connection error - after rebooting the server all changes i made mount FS and start raid rebuild were gone - the raid and FS entries are gone as well and with the
mdadm --assemble /dev/md127 /dev/sd[bcdefghijklm] --verbose --force
command i get this :

mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb is busy - skipping
mdadm: /dev/sdc is busy - skipping
mdadm: /dev/sdd is busy - skipping
mdadm: /dev/sde is busy - skipping
mdadm: /dev/sdf is busy - skipping
mdadm: /dev/sdg is busy - skipping
mdadm: /dev/sdh is busy - skipping
mdadm: /dev/sdi is busy - skipping
mdadm: /dev/sdj is busy - skipping
mdadm: /dev/sdk is busy - skipping
mdadm: /dev/sdl is busy - skipping
mdadm: /dev/md127 is already in use.

any ideas ? and how to fix that ???

Personalities : [raid6] [raid5] [raid4]
md127 : inactive sdb[0] sdl[11] sdk[10] sdj[9] sdi[12] sdh[6] sdf[5] sdg[4] sde[3] sdd[2] sdc[1]
32231490632 blocks super 1.2

Personalities : [raid6] [raid5] [raid4]
md127 : inactive sdb[0] sdl[11] sdk[10] sdj[9] sdi[12] sdh[6] sdf[5] sdg[4] sde[3] sdd[2] sdc[1]
32231490632 blocks super 1.2