Readynas Ultra 6 (RNDU6000) After Memory Test and rebooted Error " No Disks Detected"

[thekidbass]

Hopefully this time it's posted on the Readynas community webstie.I

have an Readynas Ullra 6 (RDNU6000) with 6x3TB installed. RAIDiator ver 4.2.31. Flex-RAID level-0. After viewing post from Mook1 "Ultra 6 Memory Upgrade Verification", post 1125490,  I wanted to upgrade the Ram from the original 1GB to 2x2GB, which is the max for this unit I backed up all my media prior to trying this upgrade. I have physical raw Hard Drives backups for all my media. I purchased the same Ram with specs as User "sotrack" had posted photos of the RAM he uploaded. I ran the "Memory Test".  After 5 hrs the display showed results "PSS-2, Error-O". Since I was unable to exit the memory test mode (didn't really know how to), I powered down the unit. After powering it back up, it is still in the Boot menu mode.The display shows "Boot menu". I pressed the back-up button to select "Normal" mode. I then pressed the reset button to reboot in "Normal".mode It reboots and now getting a display message "Error, no disks detected". I don't know what to do from here. Any suggestions would be apprecitated.

[StephenB · Accepted solution]

---

@thekidbass wrote:

When this Ultra wipe out all the media I had in it (18TB), I already had it all backed up on raw HDs stored in my closet. 

---

It is of course best practice to have a backup of the data even with X-RAID, since RAID redundancy isn't enough to keep it safe.

When you do have backup(s), the downsides of RAID-0 are just an inconvenience, since you can recreate the volume and restore the data from the backup if it fails.  Time-consuming, but not a disaster.

[Sandshark]

It could be an independent failure, but it's doubtful.  I suggest you go back in and see if you left something disconnected or poorly connected when you upgraded the RAM.  

[thekidbass]

I was thinking the same thing. I'm going to pull out the motherboard again and take a look at the connectors. But when I initially changed the RAM, I was able to remove the original RAM stick and install the replacements WITHOUT disconnecting anything. What I noticed was after I restalling the MOB and covers, when I went to reset the nas, depressed the reset button with the paper clip, I DID NOT hear a click. I'm speculating that when I went to slide the MOB back in place, it may have not centered in the small hole properly, even though can clearly see it centered from the outer back plate. When I turned the power switch on in the back, above the power cord, it was already in the Boot menu. After I powered down the nas to stop the memory test (5hrs), when it rebooted, it went right back to the Boot menu. I press the back button to select "Normal" boot and press the reset button to confirm but it did not exit the Boot Menu. 

[thekidbass]

I just took off the covers of the NAS to double check that the connections on the MOB where not loose. The connections were fine. I brought over the NAS to my work bench to make certain I was able to hear the click sound when I pressed the reset button. It  was able to this time hear the click. I held the reset button and then powered on the NAS and select ed "Normal" boot. It did reboot but STILL GAVE ME THE SAME ERROR MESSAGE "NO DISKS DETECTED".  I have nearly 16TB of media in this NAS. The only positive side is that I have everything backed up on physical raw hard drives in my closet. From this point, I don't know what else to troubleshoot. Any suggestions and or tips  is highly appreciated. It has been a very strenuous 2 days with this problem.

[thekidbass]

My sole reason for upgrading the memory was to prepare for the upgrade to OS6. But now that's on hold with the problem I'm having with the NAS. Is there a way to test each hard drive that's in the NAS on a PC? And will it be recognized in Windows 10? All 6 hard drives were working prior to the memory upgrade. I'm thinking if I can reformat all 6 drives on the PC, then load them back on the Ultra 6 and if it will be recognized again, then I can try to upgrade to OS6. Please, any help would be appreciated.

[Sandshark]

The drive format on the NAS will not be recognized by Windows, but the vendor's tools for testing hard drives don't require that it does.  A USB dock for the drives (one at a time) and the manufacturer's test tool are the best, though SeaTools seems to work pretty well for any brand.

Also, formatting on Windows is not what you want to do -- you want to "unformat" them (remove all partitions).

But it is unlikely all drives went bad at the same time and this most likely is a hardware problem, not a software/firmware one.  If you have a spare SATA drive (of any size, not containing anything about which you care), you can use that drive alone in slot 1 and see if it's recognized, then rotate through the rest of the slots.  If it's recognized in slot 1, then go ahead and let the NAS create a volume before you rotate it through the other bays (with power off).

[thekidbass]

As far as the vendr's tool for testing, will that tool be able to "unformat" each drive within windows? Since windows will not natively recognize it. The suggestion about using a spare drive to test in the NAS, one slot at a time, do I have to first "unformat it" within Windows as well? And as far as hardware failure, I had two volumes on the Ultra 6 (3 HD each volume). If iinfact it was a hardware failure in only one of the volumes, which I won't know until I run the Vendor's test, wouldn't a least the other HD's be detected?

[StephenB]

---

@thekidbass wrote:

As far as the vendr's tool for testing, will that tool be able to "unformat" each drive within windows? Since windows will not natively recognize it. 

---

Seatools has an erase / write zeros destructive test ("advanced"), which will remove all formatting from the drive.

Also, Windows Disk Manager will "see" the drive, and let you remove the partitions (disk manager calls them "volumes") - even though Windows won't mount the drives.

---

@thekidbass wrote:

The suggestion about using a spare drive to test in the NAS, one slot at a time, do I have to first "unformat it" within Windows as well? 

---

If the drive isn't formatted, then the NAS will automatically do a factory install.  If it is formatted, you can also do a factory default using the boot menu.

---

@thekidbass wrote:

If iinfact it was a hardware failure in only one of the volumes, which I won't know until I run the Vendor's test, wouldn't a least the other HD's be detected?

---

Yes, normally you'd expect that.  But I suggest working systematically through the possibilities, and not making assumptions on what might be wrong.

[thekidbass]

Please correct me on this order if it is not correct.

The correct order should be:

1. Run the Vendor's Tools software on my PC and do a diagnostic scan on all 6 HDs

2. If test deems the Drives are good, then use the same Vendor tool to remove all formatting and/or through Disk Manager 

3. Install all drives that are good/or a spare drive and see if  the NAS will recognize it and an auto factory install will be done.

[StephenB]

---

@thekidbass wrote:

Please correct me on this order if it is not correct.

The correct order should be:

1. Run the Vendor's Tools software on my PC and do a diagnostic scan on all 6 HDs

2. If test deems the Drives are good, then use the same Vendor tool to remove all formatting and/or through Disk Manager 

3. Install all drives that are good/or a spare drive and see if  the NAS will recognize it and an auto factory install will be done.

---

This is reasonable.

[thekidbass]

I've read quite of number of posts concerning these  Readynas Units that I and other users have had issues with. You have given your expert assistance and advice to us.. Thank you StephenB. Highly appreciated. I will start the process and will post the results and/or issues along the way.

[thekidbass]

This is the current update. (01) I first took all 6 3TB NAS drives individually to my PC. Checked each drive via "Disk Management". All 6 drives showed "healthy". I then ran the WD Dashboard utility software tool and it scanned each drive. Hard drive number 4's test "Failed with error code 7". Photos below.

(02) I tried Sandshark's suggestion on taking a spare SATA  drive and loading it in slot 1 to see if it is recognized. I first deleted the partitions on the spare SATA drive then placed it in slot 1 and powered the NAS. It gave me the same error message- "No Disks Detected". I sequentially tried it on all the other 5 slots but getting the same error message.

(3) This NAS had two Volumes. Drives 1-3 when I first purchased the NAS. Then I added 3 more drives for the 2nd Volume. Since Hard Drive #4 was the drive that failed the test and was part of the 2nd Volume. I purposely didn't delete the partitions on drives 1-3 to test if  it would be recognized. But I got the same error message as well. Aside from the failed drive, there must be another issue with the NAS. Speculating software/firmware.

[StephenB]

---

@thekidbass wrote:

I tried Sandshark's suggestion on taking a spare SATA  drive and loading it in slot 1 to see if it is recognized. I first deleted the partitions on the spare SATA drive then placed it in slot 1 and powered the NAS. It gave me the same error message- "No Disks Detected". I sequentially tried it on all the other 5 slots but getting the same error message.

But I got the same error message as well. Aside from the failed drive, there must be another issue with the NAS. Speculating software/firmware.

---

Unfortunately it sounds like hardware to me - the SATA interface in the chassis might have failed, or perhaps an issue with power.

[thekidbass]

Oh boy. I was hoping it was something that could be repairable. Any other steps I can test before I send it to it's resting place?

[StephenB]

---

@thekidbass wrote:

Oh boy. I was hoping it was something that could be repairable. Any other steps I can test before I send it to it's resting place?

---

It'd be good to hear from @Sandshark.  It is possible to replace the power supply, but I don't think there's much you can do on the SATA interface. 

[thekidbass]

Well, I do have a power supply tester. I can pull out the PS and it test, to elimante that out of the equation if it is good.

[Sandshark]

Most power supply testers are mostly worthless, as they don't test under load.  If you have a "spare" ATX power supply, using it externally to power the NAS is a better test.

The Ultra6 does have a header on the motherboard for a VGA connector.  If you connect one and a USB keyboard, you can see if the BIOS sees the drives.  If it doesn't, it's not a software/firmware issue (which I very much suspect is the case).

[thekidbass]

I'll see if I have an extra ATX Power Supply and try that.

StephenB mention a possible SATA interface issue. Can that be tested?

[Sandshark]

Using the spare drive was the test of the SATA interface.  Of course, if the drive isn't getting proper power, then it would also fail.

Did you verify that when you re-installed the motherboard that you put it back with the SATA daughterboard fully engaged an no debris in the connectors? 

[thekidbass]

When I replaced the memory, I didn't have to "disconnect" any connections at all. I just slid the MOB out enough to gain acces to the RAM Sticks, with the connectors intact.

[thekidbass]

Once I recieved the iniitial Error message "No Disks Detected", I took off the chasis covers again to re-confirm the connections.

[thekidbass]

Can you indicate where the VGA header is on this photo.

I can't seem to identify it. Thanks

[StephenB]

---

@thekidbass wrote:

Can you indicate where the VGA header is on this photo.

---

Not something I've used myself, but I believe it is here:

[thekidbass]

I don't use it either but Sandshark suggested I connect a monitor to the VGA header and with an ATX Power Supply, connect that to the MOB PS connector and see if the BIOS recognizes the test Hard drive.

[thekidbass]

That's to test the PSU that's in the Readyas. That may be a potential cause of the problem with my NAS.