![]() ![]() “mdadm: cannot open /dev/sdc1: Device or resource busy” Mdadm –create /dev/md6 –level=5 –raid-devices=6 /dev/sd1 I even tried overwriting all of those harddrives with zeroes, which worked but didn’t help at all with the creation of the array afterwards. I can dd from and to the harddrives, I can create and delete partitions but I cannot create an md raid array out of them, IĬannot create a physical volume or format them with a filesystem. ![]() Well, I proceded without this array, and after it booted I connected the array of 6 hard disks again. “dracut-initqueue: Warning: dracut-initqueue timeout – starting timeout scripts” I don’t know, if it helps but before that I had two screens full of: If I unplug those drives and boot again, it all works. (Those drives can be pretty slow when writing, dd showed about 30 MBps, the write cache is off.) “A start job is running for dev-mapper-vg0\vice (13s / 1minĬan it be just some kind of a scan, which takes so long? The current throughput based on time (16 h) and capacity (3 TB) would be about 50 MBps. That would unexpectably prevent the system from booting past something like (I copied it from the working setup), I ran it over night, so it was actually about 16 hours: Now I added 6x 500 GB platters from an old server running Debian 8 Jessie with software RAID of a similar fashion as well. I have already been running a RAID1 (mdraid, lvm2) for the system and some oVirt 4.1 testing. I am evaluating oVirt and a storage-ha as part of my bachelors thesis. I have a workstation for testing, running latest CentOS 7.3 AMD64. I have never experienced this problem with hard disk management before and cannot explain it to myself on any rational basis. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |