ReadyNAS Pro 6 not rebuilding raid after entering new disk

"I will do so however this was a live disk in my PC when I took it out for replacing the broken one"

I've had issues in the past when using a drive that was in use on my PC and attempted to place it in a ReadyNAS.  I suggest you delete all partitions on the HDD using your PC using diskmanager or whatever and then put it back in the ReadyNAS.  That has always worked for me.

Hope that helps.

- AJ

That's definitely worth a try. It is best practice to delete the partitions off a used disk before trying to add it to your NAS.

I will try so straight away and comeback on the result

I added a new disk straight out of the packaging to the setup. Same problems remain. The system tells me in the log the disk passed the test and the volume is being rebuild. However the frontview and raidar tell me the system is Not Reduntant and no rebuilding seems to happen...

---

JS78 wrote:

I added a new disk straight out of the packaging to the setup. Same problems remain. The system tells me in the log the disk passed the test and the volume is being rebuild. However the frontview and raidar tell me the system is Not Reduntant and no rebuilding seems to happen...

---

If you hover the mouse over the disks and volume icons in frontview (bottom of the page) does it give you any status indication that the volume is building?

---

StephenB wrote:

---

JS78 wrote:

I added a new disk straight out of the packaging to the setup. Same problems remain. The system tells me in the log the disk passed the test and the volume is being rebuild. However the frontview and raidar tell me the system is Not Reduntant and no rebuilding seems to happen...

---

If you hover the mouse over the disks and volume icons in frontview (bottom of the page) does it give you any status indication that the volume is building?

---

No I does not. It keeps saying "C is not Redundant"

Perhaps send a fresh set of logs to mdgm-ntgr

---

StephenB wrote:

Perhaps send a fresh set of logs to mdgm-ntgr

---

I did do a quick check of the logs myself. All the same error messages as I've been getting mentioned at the beginning of my post. So I thinking of clearing the entire setup and go to OS6 and see if that solves some of the issues

---

JS78 wrote: ...So I thinking of clearing the entire setup and go to OS6 and see if that solves some of the issues

Certainly an option, assuming the chassis is healthy.  Let us know how that goes if you take that path.

---

StephenB wrote:

---

---

Certainly an option, assuming the chassis is healthy.  Let us know how that goes if you take that path.

---

Anyway to test chassis health?

---

JS78 wrote: Anyway to test chassis health?

---

There is a memory test and a disk test built into the boot menu.  In your case you might want to run the disk test - which should also exercise the SATA hardware in the chassis.

I have two WD red 8TB disk laying around, shoud I put these in before or after the update to OS6?

---

JS78 wrote:

I have two WD red 8TB disk laying around, shoud I put these in before or after the update to OS6?

---

I'm not sure.  There is a lot of resync time if you add them incrementally (either before or after conversion), and expansion will likely fail if you add them before.

I'm temped to modify the usual instructions to power down after installing r4tor6 bin installing the r4tor6 bin, and then put in the disks you want and power up.  I think that will build the new data volume just once.  But of course the r4tor6 process needs to complete (so perhaps leave disk 1 alone).

But wait and see if mdgm-ntgr chimes in - he might have different advice.

The weirdest thing just happened I entered one of my new 8TB drives instead of the one I'd already tried replacing of the same make and type. All of a sudden the rebuilding of the raid array started again....

very strange...

---

JS78 wrote:

 All of a sudden the rebuilding of the raid array started again....

 

---

Good news, though it does point towards an issue with the replacement drive.

I just tried to run the update to OS6. I am getting a checksum error on the second payload (R4toR6_6.6.0.bin). Any ideas what that might be?

Try the download again from here: https://www.readynas.com/contributed/mdgm/r4tor6/

You might as well use R4toR6_latest.bin as all these images look like mdgm updated them to installl 6.6.1.  He usually does that every new firmware release.

Please download the R4toR6 image again and try it again.

All the R4toR6 images in that directory at this time point to the same R4toR6 image.

When making the R4toR6 6.6.1 image I accidentally put the R4toR6 header for 6.6.0 on it. That's why the checksum didn't match. I have just fixed that by preparing a new image.

And we are all up and running on the new OS!

Building the array now