Re: All disks DEAD - Everything works .... ReadyNAS Ultra 6 Plus
You are saying that everything works - including access to the web ui and the shares?
If that's correct, then the first thing to do is create (or update) your backup.
Then power down the NAS, and remove the disks (labeling them by slot). Then test them in a windows PC using LifeGuard. You can connect them with either SATA or a USB Adapter/Dock.
If you have a spare disk (not in the array), you can also try doing a factory install in the NAS while the disk tests are running. If that is successful, then try powering up the NAS with that disk in each of the 6 slots. That will test the SATA interfaces in the chassis.
Re: All disks DEAD - Everything works .... ReadyNAS Ultra 6 Plus
While I never had them all do it at once, I had a Pro6 with a mix of 7200 and 5900 RPM drives running OD4.2.something that would occasionally have one or more go "dead" even though all were actually fine. I would remove each, renisert, let it re-sync, and all was fine for a while; then it would happen again. I turned off drive spin-down, and it fixed the problem. I later upgraded to OS6.0, and had no problems, even with spin-down enabled.
I came to the conclusion that differing spin-up times were confusing the NAS; but I dont have hard evidence, just circumstantial.
Re: All disks DEAD - Everything works .... ReadyNAS Ultra 6 Plus
Yes, I meant OS4.2, not OD. That's the firmware family for legacy Intel NASes. I switched to OS6 well before the version you are on. I noticed the drive speed difference from the screen capture you provided, which is why I offered my experience of something perhaps similar.
Yes, you should remove and replace the drives one at a time with power on. Give the NAS time to report the removal before re-inserting. Each will need to re-sync, so total time is going to be a lot.
Actually, you can switch to OS6 on an Ultra6. You have to re-format the drives and you lose any Netgear support (including paid support), but not forum support. There are a lot of positives about switching to OS6. It's more modern and kept up to date and has fewer expansion limitations. A big one is if your NAS dies, or you just want to upgrade to something faster, you can move the drives right into a new OS6 based NAS and just keep trucking. No having to transfer the data because of the different file system (you already had to do that to upgrade to OS6).
It's a good idea to bump the memory up to at least 2GB before switching to OS6, but memory for an Ultra 6 is quite inexpensive these days.
Re: All disks DEAD - Everything works .... ReadyNAS Ultra 6 Plus
Hi again, thanks for helping me with valuable info!
This evening I will try to resync disk 1 (i try the newest disks first) then 2-3-4-5
I have all data backed up on Jottacloud, so I may manage a restore, but jottacloud makes a zip file to download, and that may cause problem since zip + extracted is bigger than the NAS capasity.
Is there a setup page how to install OS6 on my nas?
I will try to remove on HDD at a time, see whats happening. This shall be done with power on?
Not 100% sure if @Sandshark's answer is right for you.
If your goal is just to diagnose the status, then you could power down the NAS, remove drive 1, and reboot. Then power down again, replace drive 1, remove drive 2 and power up. If you don't write anything to the NAS, then that process will avoid the resyncs.
If you do this with the NAS powered up, then it will have to resync.
As far as mixed drive speeds go, I also had them running on my Pro-6 for some years. The only time had an issue with a drive being declared dead was when a drive actually failed. Hot-insertion of the replacement didn't work, as the disk drivers had shut down the SATA port when the first drive failed. Rebooting the NAS solved that particular problem. So I didn't see the issue that @Sandshark had.
One problem i found is that in Win 7 file explorer Network dont show the NAS. Is there some tuning i have missed?
That's a common problem (both with 4.2.x and 6.x), and I haven't seen a sure fire solution for it.
You should be able to access the NAS shares anyway by entering \\nas-host-name or \\nas-ip-address in the file explorer address bar (using the real hostname or ip address of course).
So try that, and let us know if that works or not.
When i write in explorer \\Modesty i dont get access
Try opening the windows credential manager. Delete any credential that might be in there for Modesty. Then add a new credential (using a NAS username and it's password).
If you want to test this first, run CMD (from the windows search bar). Then enter
net use * /delete
net use t: \\Modesty\sharename /user:username userpassword
The first command terminates any open SMB sessions. If it prompts, let it proceed. The second attempts to mount the share as drive letter T.
Be careful on the typing - particularly spaces and slash direction.
When i write in explorer \\Modesty i dont get access
"Try opening the windows credential manager. Delete any credential that might be in there for Modesty. Then add a new credential (using a NAS username and it's password).
If you want to test this first, run CMD (from the windows search bar). Then enter
net use * /delete
net use t: \\Modesty\sharename /user:username userpassword
The first command terminates any open SMB sessions. If it prompts, let it proceed. The second attempts to mount the share as drive letter T.
Be careful on the typing - particularly spaces and slash direction."
Thanks
I changed \\Modesty to \\NASip, then it mounted
In WIN7 should i use switch /persistent for the net use command.
Is it posible to reach share from WAN side like a remote mounted drive?
(NAT in router is configured with open ports/forward)
If you want to test this first, run CMD (from the windows search bar). Then enter
net use * /delete
net use t: \\Modesty\sharename /user:username userpassword
The first command terminates any open SMB sessions. If it prompts, let it proceed. The second attempts to mount the share as drive letter T.
Be careful on the typing - particularly spaces and slash direction."
Thanks
I changed \\Modesty to \\NASip, then it mounted
Do you mean with the net use commands, or in file explorer? The net use commands were suggested as a test - to check if CMD also had a problem resolving the NAS name. Though of course you can use them routinely if you like.
There's no sure-fire method I know of to get name resolution to always work. You can just use the IP address, or add an entry to the hosts file on the PC. Those of course are just workarounds.
