I have also tried mount -a to no avail
OMV OS Drive Failed, How to recover RAID
-
-
root@snowdon:/# cat /etc/fstab | grep md
root@snowdon:/# -
not sure if this helps
# /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=38f45487-8693-4b71-ad79-eb3d2797380b / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=e853670d-1950-4a3a-bff8-79afe94905b2 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
# >>> [openmediavault]
# <<< [openmediavault]
root@snowdon:/# -
That is why it isn't mounting. Does the filesystem show up in the Filesystems tab? If so, you probably need to click mount.
-
Hi no it doesn't show up in this tab
-
@ryecoaaron look in blkid output at the Fs signature of md0
-
@ryecoaaron look in blkid output at the Fs signature of md0
I just looked at it again but it doesn't make sense. No filesystem listed. I don't know how an array can be a member of itself. I know an array can be a member of another array but that isn't what it is showing. /proc/mdstat says the array is fine. No idea what is going on. -
well if it ha you guys stumped I have no idea what to do next
-
root@snowdon:/# blkid
/dev/sdb: UUID="5400d348-9300-2dd3-89c8-5e22c933904c" UUID_SUB="3ba9adbf-131c-907a-c765-ced561cac6b3" LABEL="snowdon:Nixdy" TYPE="linux_raid_member"
/dev/sdd: UUID="5400d348-9300-2dd3-89c8-5e22c933904c" UUID_SUB="a082aebb-868f-a1fb-34a2-4ad00d3433fa" LABEL="snowdon:Nixdy" TYPE="linux_raid_member"
/dev/sda1: UUID="38f45487-8693-4b71-ad79-eb3d2797380b" TYPE="ext4" PARTUUID="00096f5f-01"
/dev/sda5: UUID="e853670d-1950-4a3a-bff8-79afe94905b2" TYPE="swap" PARTUUID="00096f5f-05"
/dev/sdc: UUID="5400d348-9300-2dd3-89c8-5e22c933904c" UUID_SUB="4814b415-3105-bae1-fe1b-6e83251226e6" LABEL="snowdon:Nixdy" TYPE="linux_raid_member"
/dev/md0: UUID="9261963a-f8e3-8fdc-c858-ef5936b06251" UUID_SUB="90d7d666-3d12-4884-cc83-6e0a86f82099" LABEL="snowdon:Nixdy" TYPE="linux_raid_member" -
Post the output of the following:
mdadm --stop /dev/md0
blkid -
root@snowdon:/# mdadm --stop /dev/md0
mdadm: stopped /dev/md0
root@snowdon:/#
root@snowdon:/# blkid
/dev/sdb: UUID="5400d348-9300-2dd3-89c8-5e22c933904c" UUID_SUB="3ba9adbf-131c-907a-c765-ced561cac6b3" LABEL="snowdon:Nixdy" TYPE="linux_raid_member"
/dev/sdd: UUID="5400d348-9300-2dd3-89c8-5e22c933904c" UUID_SUB="a082aebb-868f-a1fb-34a2-4ad00d3433fa" LABEL="snowdon:Nixdy" TYPE="linux_raid_member"
/dev/sda1: UUID="38f45487-8693-4b71-ad79-eb3d2797380b" TYPE="ext4" PARTUUID="00096f5f-01"
/dev/sda5: UUID="e853670d-1950-4a3a-bff8-79afe94905b2" TYPE="swap" PARTUUID="00096f5f-05"
/dev/sdc: UUID="5400d348-9300-2dd3-89c8-5e22c933904c" UUID_SUB="4814b415-3105-bae1-fe1b-6e83251226e6" LABEL="snowdon:Nixdy" TYPE="linux_raid_member"
root@snowdon:/# -
so in stopping this I can't see the raid in Raid Management now. not sure if this helps
-
ok. Now try:
mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcd]
blkid -
root@snowdon:/# mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcd]
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb is identified as a member of /dev/md127, slot 2.
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 0.
mdadm: added /dev/sdc to /dev/md127 as 1
mdadm: added /dev/sdb to /dev/md127 as 2
mdadm: added /dev/sdd to /dev/md127 as 0
mdadm: /dev/md127 has been started with 3 drives.
root@snowdon:/# blkid
/dev/sdb: UUID="5400d348-9300-2dd3-89c8-5e22c933904c" UUID_SUB="3ba9adbf-131c-907a-c765-ced561cac6b3" LABEL="snowdon:Nixdy" TYPE="linux_raid_member"
/dev/sdd: UUID="5400d348-9300-2dd3-89c8-5e22c933904c" UUID_SUB="a082aebb-868f-a1fb-34a2-4ad00d3433fa" LABEL="snowdon:Nixdy" TYPE="linux_raid_member"
/dev/sda1: UUID="38f45487-8693-4b71-ad79-eb3d2797380b" TYPE="ext4" PARTUUID="00096f5f-01"
/dev/sda5: UUID="e853670d-1950-4a3a-bff8-79afe94905b2" TYPE="swap" PARTUUID="00096f5f-05"
/dev/sdc: UUID="5400d348-9300-2dd3-89c8-5e22c933904c" UUID_SUB="4814b415-3105-bae1-fe1b-6e83251226e6" LABEL="snowdon:Nixdy" TYPE="linux_raid_member"
/dev/md127: UUID="9261963a-f8e3-8fdc-c858-ef5936b06251" UUID_SUB="90d7d666-3d12-4884-cc83-6e0a86f82099" LABEL="snowdon:Nixdy" TYPE="linux_raid_member"
root@snowdon:/# -
How important is the data? I have never tried what I would recommend:
mdadm --remove /dev/md127 /dev/md127
cat /proc/mdstat
blkid -
pretty important but to be honest i'm willing to try anything at this moment in time. should it be /dev/md0 and not /dev/md127?
-
root@snowdon:/# mdadm --remove /dev/md127 /dev/md127
mdadm: hot remove failed for /dev/md127: No such device or address -
root@snowdon:/# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md127 : active (auto-read-only) raid5 sdd[0] sdb[2] sdc[1]
3906766848 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
bitmap: 0/15 pages [0KB], 65536KB chunk -
Ok. The array itself shouldn't have a superblock on it - each drive should. So:
mdadm --zero-superblock /dev/md127
-
root@snowdon:/# mdadm --zero-superblock /dev/md127
root@snowdon:/# blkid
/dev/sdb: UUID="5400d348-9300-2dd3-89c8-5e22c933904c" UUID_SUB="3ba9adbf-131c-907a-c765-ced561cac6b3" LABEL="snowdon:Nixdy" TYPE="linux_raid_member"
/dev/sdd: UUID="5400d348-9300-2dd3-89c8-5e22c933904c" UUID_SUB="a082aebb-868f-a1fb-34a2-4ad00d3433fa" LABEL="snowdon:Nixdy" TYPE="linux_raid_member"
/dev/sda1: UUID="38f45487-8693-4b71-ad79-eb3d2797380b" TYPE="ext4" PARTUUID="00096f5f-01"
/dev/sda5: UUID="e853670d-1950-4a3a-bff8-79afe94905b2" TYPE="swap" PARTUUID="00096f5f-05"
/dev/sdc: UUID="5400d348-9300-2dd3-89c8-5e22c933904c" UUID_SUB="4814b415-3105-bae1-fe1b-6e83251226e6" LABEL="snowdon:Nixdy" TYPE="linux_raid_member"
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!