March 28, 200917 yr Hi All - Im not sure what to do here... This is my setup: Parity: 501Gb Disk1: 120Gb Disk2: 500Gb So Disk 2 failed. I have another disk that I bought today, but its a 1Tb disk. How do I install it so that I don't lose data? It seems on the surface like I cant - from what I understand I would have to buy another 500Gb HDD to restore the protected array, then make the 1Tb drive my parity. I don't want to have to buy a 500Gb drive just for this though - and if I install the 1Tb drive as parity then move the current parity to disk 2 I'll lose data. Help! Thanks -Jordan
March 29, 200917 yr This is a standard feature of unRAID. Here is a reference in the official unRAID documentation on how to do this ... http://lime-technology.com/wiki/index.php/UnRAID_Manual#Replace_a_failed_disk
March 29, 200917 yr Author Ok - I should be fine then. About 2 months ago I bought a new HDD and replaced the smallest disk in the array. unRaid came up and said that since the new drive was bigger than the existing parity, it had to be my parity drive. So I swapped the new HDD and the parity drive and started the array just like it suggests in the manual you linked to. I noticed that day that most of my newer albums were suddenly half-complete (i.e. about half the mp3 would be randomly missing). I chalked it up to unRaid not being able to handle the swap, which is why I decided to ask first this time.
March 29, 200917 yr About 2 months ago I bought a new HDD and replaced the smallest disk in the array. unRaid came up and said that since the new drive was bigger than the existing parity, it had to be my parity drive. So I swapped the new HDD and the parity drive and started the array just like it suggests in the manual you linked to. I noticed that day that most of my newer albums were suddenly half-complete (i.e. about half the mp3 would be randomly missing). I chalked it up to unRaid not being able to handle the swap, which is why I decided to ask first this time. That should not have happened, and as far as I can remember, I have never heard another report like that. There was a bug (now fixed) in this procedure in an earlier unRAID version, of an operational nature, but no report of data loss. Let us know if you see anything missing, and we will try to figure out what happened, as well as help you recover.
March 29, 200917 yr Ok - I should be fine then. About 2 months ago I bought a new HDD and replaced the smallest disk in the array. unRaid came up and said that since the new drive was bigger than the existing parity, it had to be my parity drive. So I swapped the new HDD and the parity drive and started the array just like it suggests in the manual you linked to. I noticed that day that most of my newer albums were suddenly half-complete (i.e. about half the mp3 would be randomly missing). I chalked it up to unRaid not being able to handle the swap, which is why I decided to ask first this time. This is a very different question that you asked before. Whenever I see a first time poster asking a newbie question I post the newbie answer. The way unRAID does this rebuilding is by copying the disk a sector at a time (like a disk IMAGE), not a file at a time. It is an all or nothing operation, unless it errored out at some point in the process (power failure?). If that happened, it is extremely unlikely that you'd see 1/2 the files in your music directories. Most likely the newest files added to that disk would be gone. If the rebuild didn't complete your array would be horribly unprotected. I suggest you run a parity check to just make sure that your array is healthy. If you ever see this type of behaviour repeat, follow the troubleshooting link in my sig and post a syslog.
Archived
This topic is now archived and is closed to further replies.