Re: ReadyNas 516 More Command Timeout Headaches 2

I accidently Closed the post so I am reposting this due to my Nightmare-

ReadyNas516, Latest Firmware/software- 6 disk NAS with 5 12TB Seagate

Just Got done replacing 2 drives to get completely rid of my disks that had command timeouts, all was well with no command timeouts or errors whatsoever. Then came a power outage!! After the NAS rebooted, it was unable to mount the drives and showed them in red, it also said it could not mount the drives, and did not know what type of raid this was.

I then rebooted the unit again, and it was able to mount the drives, but now I HAD 15 COMMAND TIMEOUTS on one disk, and none on the rest. It said it mounted home, but the area was not empty.

At this point, I am going to replace the disk with the 15 timeouts (now about 3-4 day later, I have another disk with 1 command timeout.)

The first question, is this somewhat normal or not?

The second question, when I replace the disk, do I have to replace the disk in the same slot, I remove it from? In other words, pull out disk 2 andd replace it in another open spot, say disk 6, or must it return to the bay it came from.

I have done a disk test.

Hopefully I will replace my bad disk with the 15 command timeouts, and and hopefully the disk with 1 command timeout will not increment.

Thanks for all the help in advance-

Jeff

Sandshark-

It is best to re-insert in the same slot, but you don't have to.

The command timeouts are not normal. It is possible you just got some bad drives, but that behavior does raise an alarm about a potential problem with the NAS itself, possibly the power supply.

Message 2 of 7

Then Sandshark-

Netgear does not offer repair service out of warranty, so that's not an option. If it were the power supply, I'd expect that you would see at least some warnings in the log about one or more voltage being out of spec unless it is just at spin-up, before the OS is loaded and can look for such things.

Do you happen to know if the timeouts you had on the other drives were also coincident with a power cycle?

What specific model(s) of Seagate drives do you have installed?

Message 5 of 7

Then Me-

The Drives I have are 12TB Iron Wolf ST12000VNZ008, clueless on the other info.

Getting Ready to change out the 15 Timeout Drive, I am going to power off the nas first,

reboot, then when I am back up check timeouts, and probably at that point change out the drive. The timeouts have stayed the same for about 3 days. However the NAS seems quite slow.

Message 6 of 7

I just rebooted the system and now saw this:

Disk 2 has 19 Command Timeouts
Disk 4 has 1 Command Timeouts

It did increment on Boot uP!!

Still lost? Any Ideas

Any Help or Testing Ideas could help me?? It was sensative to reboot??

StephenB
Apr 08, 2021
Maxpower411 wrote:

Stephen - I guess the goal is to delete this admin directory?? Will this fix my problem?

Isn't the dir required, or will it build a new one?

Let me try again to explain this.

/home is a linux mount point. The system normally will remount /data/home onto /home. This is done with the same command you used to mount / onto /mnt.

/home itself is supposed to be empty. The NAS software has an error check for that, and in your case the error is triggering.

The only way to make the error go away is to delete all the files and folders in the original /home. Once the system is running, the remount of /data/home means you can't just go into /home to do that. I had you mount / onto /mnt, because /mnt will doesn't include the remounts.

The error is only a concern because of the space taken up by the spurious files and subfolders. It sounds like that is neglible in your case, but it would be good to clean it up.

So the system won't rebuild the folder, and it isn't needed. The real folder is /data/home/admin, and that won't be affected by the deletion in /mnt/home. Deleting /home/admin when the system is running would be a big mistake, as that is the same as /data/home/admin.

Maxpower411 wrote:

I belive it is possible that the admin directory cant be deleted until we delete the hidden dir, and the hidden file-just my best guess.

I don't think so, but I'm not certain what the problem actually is. I am wondering if it's actually a btrfs subvolume (which would be very odd, but conceivable). Let's wait until the resync is finished, and then pick it up again.

25 Replies

StephenB
Guru
Apr 04, 2021
Maxpower411 wrote

Disk 2 has 19 Command Timeouts
Disk 4 has 1 Command Timeouts

Are these the same bays that had the timeouts before?

You might try swapping disk 1 and disk 2, and see if the problem moves with the disk, or if it stays with the bay. Maybe label them as you move them, so you can put the disk back later (w/o losing track).
- Maxpower411
  Aspirant
  Apr 04, 2021
  Stephen- So I should shut down the Nas, Mark all Drives, then switch drive 1 and drive 2,
  and turn it back on. Will this cause a resync, or will the nas figure it out?
  I will wait for your OK before I actually do this. I still have a new drive that has not been used.
  Thanks Again- Jeff
  - Maxpower411
    Aspirant
    Apr 04, 2021
    I didn't wait I did try it-
    Stephen-
    I was quite nervous about doing this but I did, and here are
    the results: (never changed positions before this)
    With Disk 2 in #1 Position
    ---------------------------
    Disk 1- 19 Command TimeOuTs (No Change)
    Disk 2- 8 Command TimeOuts (this had been previously 0)
    Disk 3- 0 Command Timeouts (No Change)
    Disk 4- 1 Command Timeouts (No Change)
    Disk 5- 0 Command Timeouts (No Change)
    I had seemed to notice from the past, that drive 2 always
    seemed to have the highest count, however this unit, stays on 24/7
    and usually does not power down. So I never noticed drive incrementing.
    So The Command timeouts stayed with Drive Bay 2. (or caused incrementation)
    That Being said-Tell me what you think should be my next step?
    My best guess- only a guess- Put Disk 2 in the Drive Bay that is
    open for drive 6?
    Should this be done while running? Again this is
    only my guess.
    Jeff
    For the record, I was only going to have 5 Disks in the Raid

Forum Discussion

Re: ReadyNas 516 More Command Timeout Headaches 2

25 Replies

Related Content

Accessing journalctl command on ReadyNAS 102

packet loss and headaches

Command line help

BTRFS command not found

ReadyNas 516 More Command Timeout Headaches

NETGEAR Academy

ProSupport for Business