Mdadm: Defaulting to version 1.2 metadata Mdadm: /dev/sdd1 appears to be part of a raid array: Mdadm: /dev/sdd1 appears to contain an ext2fs file system Mdadm: /dev/sdc1 appears to be part of a raid array: Mdadm: /dev/sdb1 appears to be part of a raid array: Mdadm: /dev/sda1 appears to be part of a raid array: Mdadm: /dev/sda1 appears to contain an ext2fs file system Now create the RAID of your choice with mdadm using the partition device files, not the disk devices mdadm -create -verbose /dev/md0 -level=0 -raid-devices=4 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdc /dev/sdc1 /dev/sdd /dev/sdd1 Now you should see both the disk devices and partition devices in /dev ls /dev/sd* The operation has completed successfully. OK writing new GUID partition table (GPT) to /dev/sda. Number Start (sector) End (sector) Size Code Nameįinal checks complete. Partitions will be aligned on 2048-sector boundaries Main partition table begins at sector 2 and ends at sector 33įirst usable sector is 2048, last usable sector is 3907029134 Hex code or GUID (L to show codes, Enter = 8300): fd00Ĭhanged type of partition to 'Linux RAID'ĭisk /dev/sda: 3907029168 sectors, 1.8 TiB Partition each drive with one partition of type fd00, Linux RAID: gdisk /dev/sdaįirst sector (2048-3907029134, default = 2048) or : There's lots of talk about needing to update /etc/mdadm/nf. I used gdisk and assigned it as type fd00, which is a raid partition. The second form requires proper creation of partitions on each disk using gdisk or fdisk. Instead I used the partition device files, like this: mdadm -create -verbose /dev/md0 -level=0 -raid-devices=4 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 I ended up using the UUID, from the created filesystem.Īlmost all the RAID drive setup tutorials on the web are showing the creation of the RAID device using the driver device files like this: mdadm -create -verbose /dev/md0 -level=0 -raid-devices=4 /dev/sda /dev/sdb /dev/sdc /dev/sdd So you cannot just use the device file in the fstab. Mdadm reassigns the device files from /dev/md0 to something like /dev/md127 on the next reboot. Looked all over the net trying to find the answer, and finally coming across this, and still no help. This recipe worked for me after having the same issue. which is interesting because the first listed array does not have the right name. suggested that it was a problem with initramfs but I do not know how to check or correct that. I think the problem is related to the service not starting on boot but I am not experienced enough with Linux services to know how to fix it. I have tried looking at several other similarly named treads on the net but so far I have not found anything that seems helpful. I also tried doing a reinstall then those commands, but still the output is the same. I ran the commands that suggested and this is the output. Processing triggers for initramfs-tools (0.120+deb8u3). Update-rc.d: warning: start and stop actions are no longer supported falling back to defaults Update-initramfs: deferring update (trigger activated) Is this how it should be? None of them say enabled and I would think they should. I don't know exactly if this is bad but it is suspicious looking. The process is not currently active on the system and I have no idea how to tell if it is configured to start on boot, how to start it or configure it to start on boot. I am wondering if the mdadm service is even running. Does anyone have any ideas?įailed to start rvice: Unit rvice is masked. I don't know if I am searching the internet for the right things or even if I am looking in the right log files. I use webmin to create the raid and the nf "looks" ok. I also looked at several other sites all saying the similar things. I found an issue here that seems to have helped other people but I tried it and it did not help. When I reboot the server the raid device md0 is gone. After rebuilding the raid all my files are still there, so that's a good thing. It was working well with no problems for about half a year but then I had a power failure and have been getting the same problem ever since. I can follow instructions very well on the other hand. My troubleshooting ability in Linux is not impressive, just so you know.
0 Comments
Leave a Reply. |