The you'll need to run omv-mkconf mdadm
Done, without any issues.
Going back to your post 7 running mdadm --readwrite /dev/md127 should have brought the array back up as active.
Done after but the result is:
root@openmediavault:~# mdadm --readwrite /dev/md127
mdadm: failed to set writable for /dev/md127: Device or resource busy
Now the second drive weren't recognized.
I feel like a noob right now !
I feel like a noob right now !
Nah, all been there, OK mdadm --stop /dev/md127 then run the command
Nah, all been there, OK mdadm --stop /dev/md127 then run the command
Done.
root@openmediavault:~# mdadm --stop /dev/md127
mdadm: stopped /dev/md127
root@openmediavault:~# omv-mkconf mdadm
update-initramfs: Generating /boot/initrd.img-4.19.0-0.bpo.4-amd64
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
root@openmediavault:~#
What the problem is, I don't know. No step forward, no solution. I'm getting desperate.
omv-mkconf mdadm should only be run after you have a working array. I would mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc] (not sure about the drives). If it is fine, then run the omv-mkconf command. If it is auto read only, run the readwrite command.
The second drive still unrecognized.
OK you didn't follow @ryecoaaron output mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc] you should have assembled with both drives not one
Checked and now the second drive is now recognized.
Output of;
cat /proc/mdstat
cat /etc/mdadm/mdadm.conf
mdadm --detail --scan --verbose
nothing else please.
cat /proc/mdstat
root@openmediavault:~# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md127 : active (auto-read-only) raid1 sdc[0]
1953383360 blocks super 1.2 [2/1] [U_]
unused devices: <none>
root@openmediavault:~#
cat /etc/mdadm/mdadm.conf
root@openmediavault:~# cat /etc/mdadm/mdadm.conf
# 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/md127 metadata=1.2 name=openmediavault:Raid1 UUID=6f6bc262:bb6c50ca:ca2f7080:3ec12977
root@openmediavault:~#
mdadm --detail --scan --verbose
root@openmediavault:~# cat /etc/mdadm/mdadm.conf
# 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/md127 metadata=1.2 name=openmediavault:Raid1 UUID=6f6bc262:bb6c50ca:ca2f7080:3ec12977
root@openmediavault:~# ^C
root@openmediavault:~# mdadm --detail --scan --verbose
ARRAY /dev/md127 level=raid1 num-devices=2 metadata=1.2 name=openmediavault:Raid1 UUID=6f6bc262:bb6c50ca:ca2f7080:3ec12977
devices=/dev/sdc
root@openmediavault:~#
Ahmmm, I think posting only once is enough.
Everytime I tried to post I got an "Fatal Error" Warning.
If that happens just refresh the page.
Ok, back to the problem, we appear to back at the beginning 
Two steps only;
1. mdadm --stop /dev/md127
2. mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]
Just execute each on in turn, please doing else.
mdadm --stop /dev/md127
root@openmediavault:~# mdadm --stop /dev/md127
mdadm: stopped /dev/md127
mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]
root@openmediavault:~# mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb is identified as a member of /dev/md127, slot 1.
mdadm: /dev/sdc is identified as a member of /dev/md127, slot 0.
mdadm: added /dev/sdb to /dev/md127 as 1 (possibly out of date)
mdadm: added /dev/sdc to /dev/md127 as 0
mdadm: /dev/md127 has been started with 1 drive (out of 2).
root@openmediavault:~#
mdadm --stop /dev/md127
mdadm --zero-superblock /dev/sdb
mdadm --add /dev/md127 /dev/sdb
The raid should now rebuild, to check;
cat /proc/mdstat
mdadm --stop /dev/md127
mdadm --zero-superblock /dev/sdb
mdadm --add /dev/md127 /dev/sdb
root@openmediavault:~# mdadm --stop /dev/md127
mdadm: stopped /dev/md127
root@openmediavault:~# mdadm --zero-superblock /dev/sdb
root@openmediavault:~# mdadm --add /dev/md127 /dev/sdb
mdadm: Cannot get array info for /dev/md127
root@openmediavault:~#
By the way. Many thanks to everybody for helping me. I really appricate it.
mdadm: Cannot get array info for /dev/md127
That I assume was after trying to add the drive, the output implies it's looking at/for mdadm.conf
If the raid is till stopped, which it should be try this again mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]
Need to get it back together before creating the config file.
BTW, does it show as clean/degraded in the GUI
mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]
root@openmediavault:~# mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]
mdadm: looking for devices for /dev/md127
mdadm: no recogniseable superblock on /dev/sdb
mdadm: /dev/sdb has no superblock - assembly aborted
root@openmediavault:~#
The WebGUI shows 3 drives the system drive (sda), and the two raid drives (sdb + sdc).
If I try to create a raid only sdb is shown. Don't know what went wrong.
Under raid management is there no raid displayed at all.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
