ReadyNas Ultra 6 stuck on READYNAS logo

StephenB Sandshark 

Hi StephenB 

Many thanks for coming back and I was thinking that its at risk.

---

StephenB wrote:

Overall, I am guessing that you have two issues - I am thinking that

• the power supply in the ultra 6 failed, perhaps due to the extended scrub
• Likely a disk is failing (which was why the scrub took so long). 

The power supply in the Ultra 6 can be replaced.

I thinking that the power supply is fine as it is currently running as normal with the HDD's I swapped with the issued HDD's. Basically I swapped NAS's between each set of Drives. The NAS which had the drives when Scrubbing is now running normally with other HDD's inserted - no issues.

So basically it must be a disk failing in some way. I can get a Windows laptop - Obviously I have the HDD's labelled 1,2,3,4,5 & 6 - so using a HDD cradle connected to the PC and run the software you suggested to test the drives.

If its only one drive (fingers crossed) that is faulty and as I am running RAID5 on all NAS's I could just replace that drive and rescue data.

The drives in this particular NAS with the issue are IronWolf (I think) so would have to get same as replacement if that's the root we are taken.

All my other NAS drives I have WD Red HDD's.

Also the reason that the PU must be ok is that I have the drives in another NAS and get the same response. The only NAS I got a different response was the Ultra 6 Pro which booted up to the % booting and getting to 39% before shutting down and re-starting. I wonder if I should try that again to see if it boots up now that that NAS has been running for 24 hours as was not used for sometime before that.

Regards

N

---

niallryan wrote:

 

The drives in this particular NAS with the issue are IronWolf (I think) so would have to get same as replacement

---

The current WD Red drives are all SMR (shingled magnetic recording) - which is not a good technology choice for ReadyNAS.  The WD Red Plus disks are good choices.

You can mix and match. Most of my disks are WD Red Plus (though many were branded as WD Red at the time of purchase), but I have mixed in some Ironwolf.  I've found them both to be pretty reliable. Currently I compare Ironwolf and WD Red Plus prices, and get whichever is cheapest.  

---

niallryan wrote:

I thinking that the power supply is fine as it is currently running as normal with the HDD's I swapped with the issued HDD's. Basically I swapped NAS's between each set of Drives. The NAS which had the drives when Scrubbing is now running normally with other HDD's inserted - no issues.

 

---

Ok, I must have missed that.  Obviously let the scrubbing complete on that NAS.

---

niallryan wrote:

The only NAS I got a different response was the Ultra 6 Pro which booted up to the % booting and getting to 39% before shutting down and re-starting. I wonder if I should try that again to see if it boots up now that that NAS has been running for 24 hours as was not used for sometime before that.

 

---

I don't think that will work.  You could try the boot option to skip the file system check - but I am not sure if OS-6 will pay any attention to that boot option (as it doesn't exist on the newer NAS).

FWIW, the OS-6 NAS have a "read-only" boot option instead, which would have allowed for some more experimentation.  But not the Ultra and Pro ReadyNAS.

StephenB Sandshark 

Hi StephenB 

I was reading back over to see if I read something you said correctly and it made me think....

---

StephenB wrote:

 

There might also be a PC shop nearby that could test the drives for you. If you can identify one that is misbehaving, then you could install the other 5 in the Pro 6, which could get you past the startup problem there. 

---

Is the following possible or maybe I am reading your above statement slightly extended 🙂

Insert all 6 HDD's in the correct order. Them remove one HDD at a time and boot up. eg Remove HDD 1 from slot 1 and boot up and see if this gets me past the Hanging Logo and if not then re-insert HDD 1 and remove HDD 2 and so on. ?

OR

Is what you mean that in testing each HDD that I find the faulty 1 and insert the remaining 5 and boot = do I insert the remaining 5 in to their original slots ? or insert remaining 5 into slots 1 to 5 ?

Granted I am inclined to go with the former thinking as I presume that all HDD's must be in their original slots for it to work

Regards

N

---

niallryan wrote:

I presume that all HDD's must be in their original slots for it to work

 

---

The NAS should assemble them in any order.  However, it is easier to troubleshoot problems if you know the original slot order.  

---

niallryan wrote:

 

Insert all 6 HDD's in the correct order. Them remove one HDD at a time and boot up. eg Remove HDD 1 from slot 1 and boot up and see if this gets me past the Hanging Logo and if not then re-insert HDD 1 and remove HDD 2 and so on. ?

 

---

I was actually thinking that if you knew for sure which disk was bad, then you could just boot up the NAS w/o it.

Your idea would be safe in a a native OS-6 NAS because you can boot up those NAS read-only.  If somehow the NAS did write something with only 5 disks installed, then the data volume would be out-of-sync.  Repeating this several times could increase the risk of data loss.

So there would be some risk with your idea.  It might turn out to be the only practical option, but it'd be good to expllore other possibilities first.

Hi StephenB and Sandshark 

Its been a few weeks but had a lot going on and got back to this issue and managed to get a windows pc and downloaded and installed the software you recommended to test the HDD's (also to note there is a Mac version 🙂 )

Anyways I started with the Seagate software and ran the Long Test (no mention of destructive btw). So the following is the results with this software up to present time.

HDD 1 - Passed

HDD 2 - Passed

HDD 3 - Passed

HDD 4 - Passed

HDD 5 - Currently testing

HDD 6 - Immediately Failed

In case you're wondering how I know this.... lol - I could not unscrew HDD 5 from the cradle (well 1 crew in particular) so jumped to HDD 6 as it takes about 12-14 hours to test a drive.

When I inserted the drive into the caddy and turned it on the software immediately came up with the exclamation mark and when I tried all the various tests it failed after about 5-10 seconds of starting.

I am just wondering - there is a Fix All option in the software - any good to run this with that drive ? or would it destroy the data on it eg (RAID5 system)

Also, If this being the issue (fingers crossed) can I boot up the NAS with just the 5 HDD's in it or should I wait until I get a replacement drive.

Many thanks

N

You can try booting up with just the 5 drives and see if it comes up with a degraded (non-redundant) volume.  It's possible that the one bad drive was affecting the entire SATA subsystem, so it's your only problem.  But it's not that likely.  There is no "fix all" because there are too many things that can go wrong.  StephenB can help you with the commands needed to try and assemble the volume once he gets a look at your logs.  

---

niallryan wrote:

 

I am just wondering - there is a Fix All option in the software - any good to run this with that drive ? or would it destroy the data on it eg (RAID5 system)

 

---

My experience with that feature in the past was never good, so I don't use it.

Generally once a drive starts to fail, it rapidly gets worse.  So the track sparing in the software doesn't seem to help for long.

---

niallryan wrote:

 

Also, If this being the issue (fingers crossed) can I boot up the NAS with just the 5 HDD's in it or should I wait until I get a replacement drive.

 

---

You can boot with 5 drives.  The array should mount, and should be marked as degraded.

Hi StephenB 

Many thenks for coming back to me.

 

My experience with that feature in the past was never good, so I don't use it.

 

Generally once a drive starts to fail, it rapidly gets worse.  So the track sparing in the software doesn't seem to help for long.

---

 I was thinking the same thing to be honest.

---

You can boot with 5 drives.  The array should mount, and should be marked as degraded.

---

Yes again was thinking the same thing. With the degraded the NAS would still work but slower than normal. Also would I be able to add to the NAS while in degraded mode?

Kindest Regards

N

---

niallryan wrote:

Also would I be able to add to the NAS while in degraded mode?

 

---

Yes. 

Though I do recommend updating (or creating) your backup, as you would lose all your data if a second disk fails.

Good morning StephenB Sandshark 

I re-inserted HDD5 after it passed the HDD test. Then powered on the NAS without HDD6 inserted and it booted up. Everything was normal as in the NAS was not displaying any issues on its display when I was expecting to see a notice of it saying that the system is degraded. So I went on my laptop and logged into the readynas Home Screen.

When. I logged in there was a message at the top but it wasn't a system degrading message. It was a message saying to remove the necessary drives BECAUSE when I clicked on Volumes icon all the drives are RED and it is saying that the NAS is FULL = zero space available.

I wonder if this has anything to do with the initial process it was doing as I am only 90% sure it was completed before the power was interrupted.

Will the NAS recover to normal when I insert a replacement drive into bay 6 ?

Kindest reagrds

N

No, it will not self-repair when you replace Drive 6.  It does appear the death of drive 6 caused a problem on the SATA bus, but did so during a write.  So data on one or more other drives is corrupt or out of sync.  Hopefully, you can now download the log .zip and StephenB can use that information to better diagnose the specifics of your issue and help you at least get the volume mounted so as to allow you to get your backup up to date before factory defaulting the NAS with a new drive.

---

niallryan wrote:

 

I wonder if this has anything to do with the initial process it was doing as I am only 90% sure it was completed before the power was interrupted.

 

Will the NAS recover to normal when I insert a replacement drive into bay 6 ?

 

---

The volume is probably out of sync.  Download the full log zip file from the logs page.

I can take a look at that for you if you like.  Just upload it to cloud storage (Dropbox, google drive, etc), and send me a download link in a PM (private message).  Use the envelope link in the upper right of the forum page.

I will be traveling this week, so it might take me a couple days to get to it.

Hi Sandshark 

It doesn't sound good does it really ?

However I shall continue until otherwise. Will see if I can download logs and also if logs are downloaded - will they give us anything to go on.

Thanks

N

Hi StephenB 

Many thanks for this and I will upload the logs if I can download them as stated there to Sandshark 

Just give me a min or so.

Regards

N

Hello again StephenB Sandshark 

Just logged in and took a screenshot of the Volumes screen - see below

Just in case this gives you an idea of what's gone on since being able to boot up

Regards

N

Please send your PM on the location of the logs to StephenB, not me.  I'm really mainly a hardware guy, but I've also run a lot of experiments on ReadyNAS to learn its ins and outs and have seen a ton of messages here in the forum about volume issues.  But when it comes to diagnosing and repairing BTRFS and MDADM issues, StephenB has far more experience than I.

The screen shot really doesn't clear things up except to say that there is something more wrong than just a missing drive, as I had already surmised.  There are a lot of things that can go wrong and result in that display, thus the need to upload the logs to see which problem yours is.

Sandshark 

My apologies and I have done so. Many thanks for all the advice and help as always. You and StephenB really show what a community stands for. Many thanks for this and everything else in the past.

I reckon it is going to be a long road ahead and expensive by the sounds of what StephenB has been correlating to me.

StephenB has already told me that the logs indicate that the RAID is in sync and it is more of a file system issue. So hence a long road ahead.

Kindest regards

N