OMV Missing RAID 5 filesystem after broken drive
-
- gelöst
- Pahikainen
-
-
chente
Hat das Thema freigeschaltet. -
Versio that Im using is openmediavault_4.1.3
This is EOL current version is v7
After drive failed on RAID 5 im lost. Replaced drive with same size disk but Raid file system says its missing, and options are greyd out
This is probably where it went wrong, mdadm (software raid) is not plug and play it has to told what to do in a specific order
ssh into omv as root and run the following two commands and post the output in a code box, this symbol </> on the forum menu bar, makes it easier to read.
cat /proc/mdstat
blkid
-
I Think before swapping drive it said missing filesystem before that. I still have the faulty drive but it just clicks all the time when powered. Hardware where Im running this OMV is old lacie 5big and it was blinking red on backside.
Geaves thanks for the help I got the following output from these commadsCode
Alles anzeigenlogin as: root root@192.168.1.185's password: Linux NAS 4.18.0-0.bpo.1-amd64 #1 SMP Debian 4.18.6-1~bpo9+1 (2018-09-13) x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Sun Mar 24 07:17:45 2024 from 127.0.0.1 root@NAS:~# cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : inactive sde[0](S) sdc[2](S) sdb[3](S) 5860150536 blocks super 1.2 unused devices: <none> root@NAS:~# Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] -bash: Personalities: command not found root@NAS:~# md0 : inactive sde[0](S) sdc[2](S) sdb[3](S) -bash: syntax error near unexpected token `(' root@NAS:~# 5860150536 blocks super 1.2 -bash: 5860150536: command not found root@NAS:~# root@NAS:~# unused devices: <none> -bash: syntax error near unexpected token `newline' root@NAS:~# root@NAS:~# -bash: root@NAS:~#: command not found root@NAS:~# blkid /dev/sda1: UUID="1d70a63e-ebac-4550-a0a2-25c439cb7b49" TYPE="ext4" PARTUUID="759466f9-01" /dev/sda5: UUID="84481ae1-1f44-4dad-8d80-e1d27b4fd8bf" TYPE="swap" PARTUUID="759466f9-05" /dev/sdc: UUID="3c2c744c-3a25-6b38-e367-e4134e154b2a" UUID_SUB="0ab35f5d-5d76-87f8-3ed7-d1d7dbc1d662" LABEL="openmediavault:0" TYPE="linux_raid_member" /dev/sdb: UUID="3c2c744c-3a25-6b38-e367-e4134e154b2a" UUID_SUB="b6758de4-8177-f40e-2fc6-e404ca914e6f" LABEL="openmediavault:0" TYPE="linux_raid_member" /dev/sde: UUID="3c2c744c-3a25-6b38-e367-e4134e154b2a" UUID_SUB="71e4cdd0-888e-06a8-e901-fb38328bcc79" LABEL="openmediavault:0" TYPE="linux_raid_member" /dev/sdd1: UUID="1d1ede5f-bec9-4546-800d-38524b9a03cb" TYPE="ext4" PARTUUID="b48ef6b3-3fbb-49a3-8ca3-fcfe2bc68e80" root@NAS:~#
-
The array is inactive, and it's showing 3 drives available in the array, to get it started run ->
mdadm --stop /dev/md0 wait for the output, then ->
mdadm --assemble --force --verbose /dev/md0 /dev/sd[bce] this should assemble the array, wait for the rebuild/sync to complete
is /dev/sdd1 the new drive that you attempted to add/wanted to add to the array to replace the failed one?
-
Yes dev/sdd1 is the replaced drive and sda wouls be the drive where OMV is installed. Btw does omv always consume whole drive where installed? Or can OMV drive be partitioned
Thank you this made it accessible. Is there way to add sdd1 as part of the array or is it rebuilding now?Code
Alles anzeigenroot@NAS:~# mdadm --stop /dev/md0 mdadm: stopped /dev/md0 root@NAS:~# mdadm --assemble --force --verbose /dev/md0 /dev/sd[bce] mdadm: looking for devices for /dev/md0 mdadm: /dev/sdb is identified as a member of /dev/md0, slot 3. mdadm: /dev/sdc is identified as a member of /dev/md0, slot 2. mdadm: /dev/sde is identified as a member of /dev/md0, slot 0. mdadm: no uptodate device for slot 1 of /dev/md0 mdadm: added /dev/sdc to /dev/md0 as 2 mdadm: added /dev/sdb to /dev/md0 as 3 mdadm: added /dev/sde to /dev/md0 as 0 mdadm: /dev/md0 has been started with 3 drives (out of 4).
-
Btw does omv always consume whole drive where installed
Yes, what you did with /dev/sdd was to format it, then you tried to add it to the existing array, with OMV this will not work you need to add the blank drive to the array this ensures that the metadata etc is the same across the array.
What you will need to do, Storage -> Wipe, select /dev/sdd, from the menu select wipe, then select secure, when finished ->
Raid Management -> now the menu there is an option to add a drive, you are using V4, I can't remember if the option is restore or rebuild it's certainly not grow, from the dialog box select the drive and click ok, this will add the drive to the array.
or is it rebuilding now
I don't know the image you are showing is the file system which is initially irrelevant, Raid Management will show that information or from the cli cat /proc/mdstat
-
Thank you now that this is corrected and I got back the data I might experiment something and install OMV 7. Thank you so much for you time.
-
macom
Hat das Label gelöst hinzugefügt.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!