Hello everyone,
my raid configuration get lost on each restart of my server and have to configure it again.
I am mirroring 2 harddisk.
Thanks
Hello everyone,
my raid configuration get lost on each restart of my server and have to configure it again.
I am mirroring 2 harddisk.
Thanks
Re,
can you explain a little bit more, what "have to configure it again." in detail means?
- What did you do exactly?
- Which hardware do you use?
Sc0rp
1. Created a software raid through the admin menu
2. Hardware:
It worked well with my old hardware with the same harddisks.
Re,
hmm, i did not get the glue about this behavior ... normally should the raid being autodetected on boot.
Hardware issues don't fit in this case ... may be some UEFI magic?
Did you checked your logs?
Sc0rp
Which log should log shall I check?
And where can I find the correct mdadm.conf?
In the following folder /etc/mdadm/mdadm.conf I cannot see the configured harddrives.
Try.
sudo mdadm --assemble --force --verbose /dev/md0 /dev/sd[ab]
try to look in my topic too.
Also I suggest you to search for mdadm, I found various different solution (sadly none of them worked for me)
I got the following result.
root@NAS:~# sudo mdadm --assemble --force --verbose /dev/md0 /dev/sdf /dev/sdg
mdadm: looking for devices for /dev/md0
mdadm: Cannot assemble mbr metadata on /dev/sdf
mdadm: /dev/sdf has no superblock - assembly aborted
Maybe I should say, that I created the raid with my old hardware and wanted to reuse it with my new one.
Maybe I should say, that I created the raid with my old hardware and wanted to reuse it with my new one.
What was your old hardware?
What is your new?
What are your physical disks named in the OMV GUI?
I could find now the following message at boot:
[Depend] Dependency failed for/srv/dev-disk-by-label/PrivateData
[Depend] Dependency failed for File System Check on /dev-disk-by-label/PrivateData
Hardware
old: Core 2 Quad
new: Intel i7 4770
Hi,
In the following folder /etc/mdadm/mdadm.conf I cannot see the configured harddrives.
Yeah, since you use "superblock auto-detect" by default, there is nothing written down ...
mdadm: /dev/sdf has no superblock - assembly aborted
Seems to be no raid-member, try
blkid first ...
Sc0rp
Seems that you used the disks in your array before
1. Created a software raid through the admin menu
2. Hardware:
- Asrock Z87 EXTREME4 Mainboard Sockel LGA 1150
- Intel i7 4770
- 2 WD 3tb Red
It worked well with my old hardware with the same harddisks.
Did you wipe the disks before using them in your new rig? I assume you didn't...
I had the very similiar problem because I used my disks in other machine before. There were remains from other file systems on them and for unknown reasons mdmadm did not write the new superblocks properly.
I created the RAID in the GUI, started copying my files and after the first reboot the RAID disappeared... Very annoying...
Wipe your disks first (be aware, that all data on the disks will be lost!),
then recreate your RAID in the GUI or in shell. Doublecheck the mdmadm.conf for an existing array, reboot and your RAID will (hopefully) consist permanent.
Re,
There were remains from other file systems on them and for unknown reasons mdmadm did not write the new superblocks properly.
Yeah. That's a bug ... well known for me.
dd if=/dev/zero of=/dev/sdX bs=1M (replace X with the target drive letter)
Better use:
dd if=/dev/zero of=/dev/sdX bs=4096 count=16 (Blocksize is better for 4Kn-drives and 16x4KiB-Blocks will overide any GPT Informations)
But if you zero the drive, you have to add it to the array again ...
Sc0rp
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!