Raid regraded and split in two

DiskMan · 10. Mai 2015

hi guys,
i can not tell if this has happen while upgrade to 2.06 from 1.8 or has happen before but what i can say is that it has happen.
as you can see on the screenshot one of my raid 1 has degraded and split into two raids.
both are degraded but still seen as one mountpoint and its working fine so far.....
normaly i did not see it because the system work very stable but last night was a little bit boring and i clicked around so i can't really say when this was happen.

maybe volker you can help me and tell what i can do without loosing my data....which is very importent for me.

also in german if you want.

disk

DiskMan · 12. Mai 2015

and after another reboot i can' see and mount my raid one anymore.

if i hit mount:

Page

of 1

1 - 6 von 6 angezeigt

Failed to mount 'd86b7aca-64dc-4000-8c20-304562129aac': mount: wrong fs type, bad option, bad superblock on /dev/md127,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Fehler #6000:
exception 'OMVException' with message 'Failed to mount 'd86b7aca-64dc-4000-8c20-304562129aac': mount: wrong fs type, bad option, bad superblock on /dev/md127,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:906
Stack trace:
#0 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('mount', Array, Array)
#3 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'mount', Array, Array, 1)
#4 {main}

DiskMan · 15. Mai 2015

help ?

ryecoaaron · 15. Mai 2015

See this thread.

DiskMan · 15. Mai 2015

Code

= Linux Software RAID
================================================================================
md126 : active raid5 sdc[6] sdh[5] sdg[4] sdf[9] sde[8] sdd[7]
md127 : active raid1 sdk[2] sdb[0]
Personalities : [raid1] [raid6] [raid5] [raid4]
md126 : active raid5 sdc[6] sdh[5] sdg[4] sdf[9] sde[8] sdd[7]
      14651325440 blocks super 1.2 level 5, 512k chunk, algorithm 2 [6/6] [UUUUUU]


md127 : active raid1 sdk[2] sdb[0]
      1465137424 blocks super 1.2 [2/1] [U_]
      [=========>...........]  recovery = 45.1% (661557376/1465137424) finish=181.6min speed=73745K/sec


unused devices: <none>
--------------------------------------------------------------------------------
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions


# 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>


# definitions of existing MD arrays
ARRAY /dev/md/Privat metadata=1.2 spares=1 name=OMVServer:Privat UUID=7ee2af3f:5a87c1bd:461145ec:5b989a0d
ARRAY /dev/md/Raid metadata=1.2 name=openmediavault:Raid UUID=b06379cb:18e05f6f:63d21922:713798b3


================================================================================
= Block device attributes
================================================================================
/dev/sdb: UUID="7ee2af3f-5a87-c1bd-4611-45ec5b989a0d" LABEL="OMVServer:Privat" TYPE="linux_raid_member" UUID_SUB="25c1cceb-80cd-9b90-32fd-bedf4d16f43c"
/dev/sda1: UUID="b0a951a1-ff12-458d-89e3-272cbbf217bf" TYPE="ext4"
/dev/sda5: UUID="a80b7e37-6c56-4101-ba52-c53b17169b45" TYPE="swap"
/dev/sdd: UUID="b06379cb-18e0-5f6f-63d2-1922713798b3" LABEL="openmediavault:Raid" TYPE="linux_raid_member" UUID_SUB="dc58c185-8053-1695-3a2c-143405462ff7"
/dev/sde: UUID="b06379cb-18e0-5f6f-63d2-1922713798b3" LABEL="openmediavault:Raid" TYPE="linux_raid_member" UUID_SUB="e6881bdb-0aaa-da25-1c50-b35d97f0dc4b"
/dev/sdf: UUID="b06379cb-18e0-5f6f-63d2-1922713798b3" LABEL="openmediavault:Raid" TYPE="linux_raid_member" UUID_SUB="184e3b2a-5acc-f4a0-55cb-ca9bd5c9026c"
/dev/sdg: UUID="b06379cb-18e0-5f6f-63d2-1922713798b3" LABEL="openmediavault:Raid" TYPE="linux_raid_member" UUID_SUB="bf7d8a85-dc07-d37e-cafd-0cbaf0332652"
/dev/sdc: UUID="b06379cb-18e0-5f6f-63d2-1922713798b3" LABEL="openmediavault:Raid" TYPE="linux_raid_member" UUID_SUB="7b5921d8-1c36-bf44-f474-37bc6cd02897"
/dev/sdh: UUID="b06379cb-18e0-5f6f-63d2-1922713798b3" LABEL="openmediavault:Raid" TYPE="linux_raid_member" UUID_SUB="64884854-34f2-3c1d-f6eb-c2c214498019"
/dev/sdj1: LABEL="Upload" UUID="614562c9-27d6-466b-9b18-2af225b53bd3" TYPE="ext4"
/dev/md126: LABEL="Raid" UUID="70bb0626-74ae-4e06-bb5f-c40dd7cf22fa" TYPE="ext4"
/dev/sdi1: LABEL="4000" UUID="3de4ebbf-d9df-493d-92f1-5ab11eebbd88" TYPE="ext4"
/dev/sdk: UUID="7ee2af3f-5a87-c1bd-4611-45ec5b989a0d" UUID_SUB="bc4d4e3e-e8aa-521a-f2a4-b1ef983ce3e5" LABEL="OMVServer:Privat" TYPE="linux_raid_member"
/dev/md127: LABEL="Privat" UUID="3b63297f-cf67-4fc3-9b31-5c48c6914334" TYPE="ext4"

Alles anzeigen

also i can't remove the old entry and also not mount the new one :o(

DiskMan · 16. Mai 2015

and happy birthday ....now it is even not booting any more and i can recreate my whole sytem......crap

Dennis · 16. Mai 2015

Zitat von diskman

....now it is even not booting any more

I'm sorry about that. I can't help you, because it's a RAID-Topic and I don't use RAID for good reason.

Zitat von diskman

help me and tell what i can do without loosing my data....which is very importent for me.

May I ask, because I don't get that: Why is your data important when you're are using a testing-release?

DiskMan · 6. Juni 2015

and i can't delete this one on top

now i have the raid clean but if i try to mount it i get:

File contains invalid JSON (filename=/var/lib/openmediavault/fstab_tasks.json):

Fehler #6000:
exception 'OMVException' with message 'File contains invalid JSON (filename=/var/lib/openmediavault/fstab_tasks.json): ' in /usr/share/php/openmediavault/util.inc:274
Stack trace:
#0 /usr/share/php/openmediavault/module.inc(141): OMVJsonFile->read()
#1 /usr/share/openmediavault/engined/module/fstab.inc(52): OMVModuleAbstract->execTasks('delete')
#2 /usr/share/openmediavault/engined/rpc/config.inc(164): OMVModuleFsTab->stopService()
#3 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#4 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#5 /usr/share/php/openmediavault/rpcservice.inc(158): OMVRpcServiceAbstract->callMethod('applyChanges', Array, Array)
#6 /usr/share/openmediavault/engined/rpc/config.inc(224): OMVRpcServiceAbstract->callMethodBg('applyChanges', Array, Array)
#7 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
#8 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#9 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('applyChangesBg', Array, Array)
#10 /usr/sbin/omv-engined(500): OMVRpc::exec('Config', 'applyChangesBg', Array, Array, 1)
#11 {main}

Jetzt mitmachen!