<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thanks for answers. As i said, I don't need space for recordings, only
<br>for media (pictures, avis, mp3:s etc). My recordings are on separate<br>disk, and I don't care loosing them if disk crashes.<br><br>As everybody says, there seems to be no other way than LVM or Raid. I<br>decided to go with Raid5. This was also my original plan, but after
<br>building an array, I did some testing with bad results;<br><br>- I plugged one sata disk off when array was running. It behavied<br>correctly since I rebooted, simulating disk change. After that I could<br>not activate array anymore, I couldnot remove "broken" disk and couldnot
<br>add new disk. So I lost array contents.</blockquote><div><br>I have removed disks from linux software arrays dozens of times (a lot of this was with testing) and even hot added new ones back never loosing any data or having any difficulty at all getting the array back up. If you need help with that please post the error messages and exactly what commands you have tried.
<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">After that I built new array, with --force, (I noticed, that mdadm<br>creates one failed device as default)
</blockquote><div><br>This is not by default but it can if you specify so. I mean if you say 4 disks and add 3 drives + 1 missing it will add a failed drive.<br> <br>John<br></div></div>