So I am running 5 Beta 14, and have been for about 3 months now. No issues at all to report, except for yesterday when I went to install a fourth drive. I ran through the preclear_disk.sh with it, and then proceeded to add it to the array. It then was labeled as Disk Disabled after stopping the array, adding it, starting the array and formatting it. So I looked through the forums and tried another preclear_disk.sh on it. I created a new config (which wiped a Drive so I lost 2 TB worth of Data which I am not rebuilding).

 

The issue I am having now is that I have pre-cleared Disk 4 again, and it is still labelled as Disk Disabled. What I am also running into now is that Disks 1 and 3 are running fine, but my Parity and Disk 2 spin down all the time, and Disk 2 doesn't seem to want to be written to (it still says 2TB free even though a lot of stuff has been downloaded). The Array only seems to be focused on Disks 1 and 3.

 

I have attached my System Log, but I am in desperate state now as I do not want to lose anything else. Please help!

syslog.txt

So I am running 5 Beta 14, and have been for about 3 months now. No issues at all to report, except for yesterday when I went to install a fourth drive. I ran through the preclear_disk.sh with it, and then proceeded to add it to the array. It then was labeled as Disk Disabled after stopping the array, adding it, starting the array and formatting it. So I looked through the forums and tried another preclear_disk.sh on it. I created a new config (which wiped a Drive so I lost 2 TB worth of Data which I am not rebuilding).

 

The issue I am having now is that I have pre-cleared Disk 4 again, and it is still labelled as Disk Disabled. What I am also running into now is that Disks 1 and 3 are running fine, but my Parity and Disk 2 spin down all the time, and Disk 2 doesn't seem to want to be written to (it still says 2TB free even though a lot of stuff has been downloaded). The Array only seems to be focused on Disks 1 and 3.

 

I have attached my System Log, but I am in desperate state now as I do not want to lose anything else. Please help!

Disks are immediately disabled when "writes" to them fail.

 

They are then "simulated" by use of all the other disks in the array. 

 

Once you fix the reason the disk was disabled (typically a loose cable, or in some cases, a defective drive) you can

1. stop the array

2. un-assign the drive

3. start the drive with it un-assigned

    (this will cause unRAID to forget the model/serial number of the disk, so it will be treated as its own replacement)

4. stop the array once more

5. re-assign the drive

6. Start the array once more, let unRAID re-construct the drive by reading all the other drives in combination with parity.

 

 

Thanks Joe, I will try that and post back.