> Ok. Those four drives cut out within a few milliseconds of each other. So I checked the enclosure’s PSU voltages, and it looks like the +5V rail was running at around +3V and the +12V rail at almost +8V under load. So I think your original theory of there being a power issue is correct. It’s a bummer, because I have 2 of these Rosewill 8-bay enclosures, and they both show that same issue. This is very likely why they’ve been discontinued. Granted the speed on them is 1.5Gbps total per channel, but it’s really just for movies, so I’m not concerned about high speed read and writes. I’ll just have to McGuyver it and use different PSUs than the ones they came with. I would imagine, that after about 500GB worth of data being transferred, all the writing caused those drives to get pretty hot, making the PSU that much more likely to cut power. http://www.newegg.com/Product/Product.aspx?Item=N82E16816132016 > Because I do all such maintenance as root. In an ubuntu system, use > "sudo su -" to get a full root console. Ah, gotcha! > Also, in the future, turn off word wrap when pasting. :-) Boom! Done deal, there was a setting in my Apple Mail application under Mail -> Preferences -> Fonts & Colors -> “Use fixed-width font for plain text messages”. I think this might fix this word wrap issue, so my apologies. It’s either that, or the fact that I copied and pasted directly from my Terminal application, and it converted the email to HTML, which changed the format. Now, onto the butter. I tried what you told me, and it showed that the devices were busy: ==================================================== cisco@DoctorBanner:~$ sudo mdadm -Afv /dev/md127 /dev/sd[b-h] mdadm: looking for devices for /dev/md127 mdadm: /dev/sdb is busy - skipping mdadm: /dev/sdc is busy - skipping mdadm: /dev/sdd is busy - skipping mdadm: /dev/sde is busy - skipping mdadm: /dev/sdf is busy - skipping mdadm: /dev/sdg is busy - skipping mdadm: /dev/sdh is busy - skipping ==================================================== So I continued to stop the array: ==================================================== cisco@DoctorBanner:~$ sudo mdadm --stop /dev/md127 mdadm: stopped /dev/md127 ==================================================== Then I tried it once again, but it seems that because they’re displaying that the Events are out of sync, that it’s not able to start the array. Any ideas? ==================================================== cisco@DoctorBanner:~$ sudo mdadm -Afv /dev/md127 /dev/sd[b-h] mdadm: looking for devices for /dev/md127 mdadm: /dev/sdb is identified as a member of /dev/md127, slot 3. mdadm: /dev/sdc is identified as a member of /dev/md127, slot 4. mdadm: /dev/sdd is identified as a member of /dev/md127, slot 5. mdadm: /dev/sde is identified as a member of /dev/md127, slot 0. mdadm: /dev/sdf is identified as a member of /dev/md127, slot 1. mdadm: /dev/sdg is identified as a member of /dev/md127, slot 2. mdadm: /dev/sdh is identified as a member of /dev/md127, slot -1. mdadm: added /dev/sdf to /dev/md127 as 1 mdadm: added /dev/sdg to /dev/md127 as 2 mdadm: added /dev/sdb to /dev/md127 as 3 (possibly out of date) mdadm: added /dev/sdc to /dev/md127 as 4 (possibly out of date) mdadm: added /dev/sdd to /dev/md127 as 5 (possibly out of date) mdadm: added /dev/sdh to /dev/md127 as -1 mdadm: added /dev/sde to /dev/md127 as 0 mdadm: /dev/md127 assembled from 3 drives and 1 spare - not enough to start the array. ==================================================== Thanks again, Cisco---- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
