NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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 ...
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.
Maxpower411 wrote
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).
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
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.
JeffFor the record, I was only going to have 5 Disks in the Raid
It does sound like bay 2 has issues. Power down and move the drive in bay 2 to bay 6. A problem on one slot can affect others when that slot is populated, but not normally when it's not. So, hopefully, this gets you back stable. It's hard to say if this will propagate to other slots without knowing the root cause, which we will likely never know. But you should probably consider that there may be a new NAS in your future.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
