× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

ReadyNAS Pro 6 crashed again

tony359
Apprentice

Re: ReadyNAS Pro 6 crashed again

Thanks.

 

Well the NAS crashed again so not sure what to do next now. I guess I could go with plan B, remove the drives and test with a couple spare drives to see if it disappears again. 

 

I was aware of the VGA header, would it be worth connecting it to a monitor? Does it show a real time log or something? It might help in troubleshooting what is going on.

 

I've noticed that if I unplug the network when it's not reachable, the front panel informs me the network has changed so that tells me the kernel is not gone. 

 

I guess I shall try an OS reinstall after all. It can't hurt, right?

 

Sigh, the NAS is pretty important on my workflow. 

Message 26 of 191
Sandshark
Sensei

Re: ReadyNAS Pro 6 crashed again

With ReadyNASOS installed, the only advantage of the VGA header is to see what's happening during boot, before you can start an SSH session, or to make BIOS setting changes.  Once booted. it gives you nothing you don't get from SSH (unless, perhaps, SSH also crashes).

Message 27 of 191
tony359
Apprentice

Re: ReadyNAS Pro 6 crashed again

Yes, SSH crashes 🙂 (Well, the box disappears from the network so I cannot monitor anymore)

What do I get via VGA? a terminal or a live log page? Does that VGA adaptor have a name?

 

Can someone please confirm this is the correct way to enter the boot menu on my Pro6?

 

https://kb.netgear.com/21107/How-do-I-access-the-boot-menu-on-my-ReadyNAS-Ultra-6-Ultra-6-Plus-Pro-6...

 

Thanks

Message 28 of 191
tony359
Apprentice

Re: ReadyNAS Pro 6 crashed again

I've now seen this happening on at least two crash events. nv6lcd is the LCD driver. Does any of this ring a bell?

 

 

Apr 02 15:58:40 Enterprise-NAS kernel: alloc_fd: slot 3 not NULL!
Apr 02 15:58:40 Enterprise-NAS kernel: alloc_fd: slot 4 not NULL!
Apr 02 15:58:40 Enterprise-NAS kernel: general protection fault: 0000 [#1] SMP
Apr 02 15:58:40 Enterprise-NAS kernel: Modules linked in: nv6lcd(O) vpd(PO)
Apr 02 15:58:40 Enterprise-NAS kernel: CPU: 1 PID: 24751 Comm: bash Tainted: P O 4.4.218.x86_64.1 #1
Apr 02 15:58:40 Enterprise-NAS kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080014 07/26/2010
Apr 02 15:58:40 Enterprise-NAS kernel: task: ffff88013c380a80 ti: ffff88008debc000 task.ti: ffff88008debc000
Apr 02 15:58:40 Enterprise-NAS kernel: RIP: 0010:[<ffffffff88134ee0>] [<ffffffff88134ee0>] dup_fd+0x176/0x1e4
Apr 02 15:58:40 Enterprise-NAS kernel: RSP: 0018:ffff88008debfdc0 EFLAGS: 00010206
Apr 02 15:58:40 Enterprise-NAS kernel: RAX: 0000000000000001 RBX: ffff8800ab8b9080 RCX: ffff88009573c808
Apr 02 15:58:40 Enterprise-NAS kernel: RDX: 28e00215ea331f00 RSI: ffff88004b9645e8 RDI: ffff88009573c800
Apr 02 15:58:40 Enterprise-NAS kernel: RBP: ffff88008debfe00 R08: ffff88009ad4a400 R09: ffff88009ad4a400
Apr 02 15:58:40 Enterprise-NAS kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000100
Apr 02 15:58:40 Enterprise-NAS kernel: R13: ffff88008e9aa800 R14: 0000000000000100 R15: ffff8800ab8bb180
Apr 02 15:58:40 Enterprise-NAS kernel: FS: 00007f40de9dc700(0000) GS:ffff88014fc80000(0000) knlGS:0000000000000000
Apr 02 15:58:40 Enterprise-NAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 02 15:58:40 Enterprise-NAS kernel: CR2: 00007ffdc7ac6f78 CR3: 000000004b8ac000 CR4: 0000000000000670
Apr 02 15:58:40 Enterprise-NAS kernel: Stack:
Apr 02 15:58:40 Enterprise-NAS kernel: ffff88009ad4a400 ffff8800ab8bb1a8 ffff88009ad4a400 0000000001200011
Apr 02 15:58:40 Enterprise-NAS kernel: 0000000000000000 ffff88013c380a80 00007f40de9dc9d0 ffff88013c386900
Apr 02 15:58:40 Enterprise-NAS kernel: ffff88008debfec8 ffffffff880625a2 ffffffff88094235 000000008debfe70
Apr 02 15:58:40 Enterprise-NAS kernel: Call Trace:
Apr 02 15:58:40 Enterprise-NAS kernel: [<ffffffff880625a2>] copy_process+0x5b1/0x1611
Apr 02 15:58:40 Enterprise-NAS kernel: [<ffffffff88094235>] ? vprintk_default+0x9/0xb
Apr 02 15:58:40 Enterprise-NAS kernel: [<ffffffff8811fc68>] ? get_empty_filp+0x141/0x185
Apr 02 15:58:40 Enterprise-NAS kernel: [<ffffffff881351e5>] ? __alloc_fd+0x137/0x167
Apr 02 15:58:40 Enterprise-NAS kernel: [<ffffffff88063744>] _do_fork+0x78/0x243
Apr 02 15:58:40 Enterprise-NAS kernel: [<ffffffff8806e9d8>] ? __set_current_blocked+0x3d/0x51
Apr 02 15:58:40 Enterprise-NAS kernel: [<ffffffff8806eb38>] ? sigprocmask+0x5b/0x5f
Apr 02 15:58:40 Enterprise-NAS kernel: [<ffffffff88063981>] SyS_clone+0x14/0x16
Apr 02 15:58:40 Enterprise-NAS kernel: [<ffffffff888e990a>] entry_SYSCALL_64_fastpath+0x1e/0x8e
Apr 02 15:58:40 Enterprise-NAS kernel: Code: 4d d0 e8 f5 fa ff ff 4c 8b 4d d0 4d 8b 6c 24 08 31 c0 45 89 f4 49 8b 79 08 48 89 f9 4c 39 e0 74 32 49 8b 54 c5 00 48 85 d2 74 07 <f0> 48 ff 42 38 eb 15 49 8b 71 18 48 0f b3 06 89 c6 4d 8b 59 20
Apr 02 15:58:40 Enterprise-NAS kernel: RIP [<ffffffff88134ee0>] dup_fd+0x176/0x1e4
Apr 02 15:58:40 Enterprise-NAS kernel: RSP <ffff88008debfdc0>
Apr 02 15:58:40 Enterprise-NAS kernel: ---[ end trace 918f7e9d8e3bfb6b ]---
Apr 02 15:58:41 Enterprise-NAS kernel: general protection fault: 0000 [#2] SMP
Apr 02 15:58:41 Enterprise-NAS kernel: Modules linked in: nv6lcd(O) vpd(PO)
Apr 02 15:58:41 Enterprise-NAS kernel: CPU: 1 PID: 24751 Comm: bash Tainted: P D O 4.4.218.x86_64.1 #1
Apr 02 15:58:41 Enterprise-NAS kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080014 07/26/2010
Apr 02 15:58:41 Enterprise-NAS kernel: task: ffff88013c380a80 ti: ffff88008debc000 task.ti: ffff88008debc000
Apr 02 15:58:41 Enterprise-NAS kernel: RIP: 0010:[<ffffffff8811cabc>] [<ffffffff8811cabc>] filp_close+0x9/0x6f
Apr 02 15:58:41 Enterprise-NAS kernel: RSP: 0018:ffff88008debfba0 EFLAGS: 00010206
Apr 02 15:58:41 Enterprise-NAS kernel: RAX: 0000000000000001 RBX: ffff8800ab8b9080 RCX: ffff88008e9aa800
Apr 02 15:58:41 Enterprise-NAS kernel: RDX: 0000000080000000 RSI: ffff8800ab8b9080 RDI: 28e00215ea331f00
Apr 02 15:58:41 Enterprise-NAS kernel: RBP: ffff88008debfbb8 R08: 0000000000000001 R09: ffffffff88100d00
Apr 02 15:58:41 Enterprise-NAS kernel: R10: ffff88008debfb30 R11: 000000000000000b R12: 0000000000000001
Apr 02 15:58:41 Enterprise-NAS kernel: R13: ffff88013e28f100 R14: 0000000000000000 R15: 000000000000000f
Apr 02 15:58:41 Enterprise-NAS kernel: FS: 0000000000000000(0000) GS:ffff88014fc80000(0000) knlGS:0000000000000000
Apr 02 15:58:41 Enterprise-NAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 02 15:58:41 Enterprise-NAS kernel: CR2: 00007ffdc7ac6f78 CR3: 0000000008cd6000 CR4: 0000000000000670
Apr 02 15:58:41 Enterprise-NAS kernel: Stack:
Apr 02 15:58:41 Enterprise-NAS kernel: ffff8800ab8b9080 0000000000000001 ffff88013e28f100 ffff88008debfbf8
Apr 02 15:58:41 Enterprise-NAS kernel: ffffffff88134fe0 000000010000000d ffff88013c380a80 ffff8800ab8b9080
Apr 02 15:58:41 Enterprise-NAS kernel: ffff88008debfc50 0000000000000001 ffff88009657ea68 ffff88008debfc18
Apr 02 15:58:41 Enterprise-NAS kernel: Call Trace:
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff88134fe0>] put_files_struct+0x65/0xad
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff881350a9>] exit_files+0x3c/0x41
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff88066034>] do_exit+0x3d7/0x8fc
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff880055d7>] oops_end+0x9d/0xa4
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff88005633>] die+0x55/0x5e
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff88003a26>] do_general_protection+0x8f/0x135
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff888eb072>] general_protection+0x22/0x30
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff88134ee0>] ? dup_fd+0x176/0x1e4
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff880625a2>] copy_process+0x5b1/0x1611
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff88094235>] ? vprintk_default+0x9/0xb
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff8811fc68>] ? get_empty_filp+0x141/0x185
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff881351e5>] ? __alloc_fd+0x137/0x167
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff88063744>] _do_fork+0x78/0x243
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff8806e9d8>] ? __set_current_blocked+0x3d/0x51
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff8806eb38>] ? sigprocmask+0x5b/0x5f
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff88063981>] SyS_clone+0x14/0x16
Apr 02 15:58:41 Enterprise-NAS kernel: [<ffffffff888e990a>] entry_SYSCALL_64_fastpath+0x1e/0x8e
Apr 02 15:58:41 Enterprise-NAS kernel: Code: 00 01 00 74 05 b8 02 00 00 00 41 0f ba e0 11 72 03 83 c8 01 48 8d 4d ec 89 45 fc e8 ff e6 00 00 c9 c3 55 48 89 e5 41 55 41 54 53 <48> 8b 47 38 48 85 c0 75 11 48 c7 c7 9f 45 b6 88 45 31 e4 e8 ef
Apr 02 15:58:41 Enterprise-NAS kernel: RIP [<ffffffff8811cabc>] filp_close+0x9/0x6f
Apr 02 15:58:41 Enterprise-NAS kernel: RSP <ffff88008debfba0>
Apr 02 15:58:41 Enterprise-NAS kernel: ---[ end trace 918f7e9d8e3bfb6c ]---
Apr 02 15:58:41 Enterprise-NAS kernel: Fixing recursive fault but reboot is needed!
-- Reboot --
Apr 02 16:13:18 Enterprise-NAS kernel: Initializing cgroup subsys cpuset
Apr 02 16:13:18 Enterprise-NAS kernel: Initializing cgroup subsys cpu
Apr 02 16:13:18 Enterprise-NAS kernel: Initializing cgroup subsys cpuacct
Apr 02 16:13:18 Enterprise-NAS kernel: Linux version 4.4.218.x86_64.1 (root@blocks) (gcc version 8.3.0 (Debian 8.3.0-6) ) #1 SMP Mon Mar 14 21:33:09 UTC 2022
Apr 02 16:13:18 Enterprise-NAS kernel: Command line: initrd=initrd.gz reason=normal BOOT_IMAGE=kernel
Apr 02 16:13:18 Enterprise-NAS kernel: KERNEL supported cpus:
Apr 02 16:13:18 Enterprise-NAS kernel: Intel GenuineIntel
Apr 02 16:13:18 Enterprise-NAS kernel: Disabled fast string operations
Apr 02 16:13:18 Enterprise-NAS kernel: x86/fpu: Legacy x87 FPU detected.
Apr 02 16:13:18 Enterprise-NAS kernel: e820: BIOS-provided physical RAM map:
Apr 02 16:13:18 Enterprise-NAS kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009cbff] usable
Apr 02 16:13:18 Enterprise-NAS kernel: BIOS-e820: [mem 0x000000000009cc00-0x000000000009ffff] reserved
Apr 02 16:13:18 Enterprise-NAS kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Apr 02 16:13:18 Enterprise-NAS kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000afeaffff] usable
Apr 02 16:13:18 Enterprise-NAS kernel: BIOS-e820: [mem 0x00000000afeb0000-0x00000000afebdfff] ACPI data
Apr 02 16:13:18 Enterprise-NAS kernel: BIOS-e820: [mem 0x00000000afebe000-0x00000000afeeffff] ACPI NVS
Apr 02 16:13:18 Enterprise-NAS kernel: BIOS-e820: [mem 0x00000000afef0000-0x00000000afefffff] reserved
Apr 02 16:13:18 Enterprise-NAS kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Apr 02 16:13:18 Enterprise-NAS kernel: BIOS-e820: [mem 0x00000000ffb00000-0x00000000ffffffff] reserved
Apr 02 16:13:18 Enterprise-NAS kernel: BIOS-e820: [mem 0x0000000100000000-0x000000014fffffff] usable

 

 

Message 29 of 191
Sandshark
Sensei

Re: ReadyNAS Pro 6 crashed again

The VGA will give you just a terminal.

 

I'm no expert here, but that sounds like you have a "tainted" kernel.  That the LCD driver is what called it is likely irrelevant except that it is called due to specific actions. The VPD process is also linked, as it lets the OS know which kind of display you have, but I think you'd see a much worse situation if the VPD file were corrupt (NAS would not boot).

 

There may be a way to fix (replace?) the kernel via support mode, but that's not in my wheelhouse.  And I would think an OS re-install would already do that.

 

I was trying to work out a way to do a full OS re-install and retain your data by EXPORTing your volume, using one drive to factory default, importing the original volume (less one drive, so degraded), then DESTROYing the new one.  I did so on a new-to-me RN3220, but the OS and swap partitions didn't propagate to a RAID including all drives, they remained only on the single factory-defaulted drive.  I could manually add the missing ones to the OS RAID via SSH, but not to the swap.  After the DESTROY, there was no longer any swap partition (but the OS expected one) and things got completely locked up.  I had expected the DESTROY to create a swap partition on the remaining drives.  I had to factory default the whole thing just to boot -- an OS re-install wasn't enough.  I plan to try again, disabling the swap partition and trying to add the other drives before the DESTROY.  But with your situation, doing that could make things worse.  And I'm busy doing other things with that NAS now.

Message 30 of 191
tony359
Apprentice

Re: ReadyNAS Pro 6 crashed again

Will I be able to plug a keyboard and use the terminal via VGA? If so, why not.

 

For now, I've unplugged the LCD screen. I also never realised that the flash memory is at the front of the unit and if you unplug both those IDC cables, the NAS won't boot. 🙂

 

I've also stopped nv6lcd. It might be nonsense but my NAS has been doing this for years - only not so frequently. Can I assume the LCD is a USB device? What if it's faulty and it's crashing the system?

 

I'll attempt an OS reinstall - if someone could confirm whether the link I quoted above is the correct procedure as I saw another one online which suggests that holding the reset button for long results in a factory reset... 🙂

 

And no worries @Sandshark, I appreciate the thought. Unfortunately I am not incredibly skilled at Linux so I don't really want to try myself. If I had to factory reset the unit, I would look into an alternative software given that Netgear seems not to be very active with the development.

 

But I'd be very happy to just be able to use the NAS as it is 🙂

Message 31 of 191
StephenB
Guru

Re: ReadyNAS Pro 6 crashed again


@tony359 wrote:

Will I be able to plug a keyboard and use the terminal via VGA? If so, why not.

Yes, you could plug in a USB keyboard.  

 

Message 32 of 191
Sandshark
Sensei

Re: ReadyNAS Pro 6 crashed again

OK.  I thought you'd already tried an OS re-install.  Yes, that should have been the first thing to try.  You will need to have the display re-connected when you do it, though.  While units without a display use the system LEDs to let you choose menu items, those with a screen use only the screen, they don't also use the LEDs.

 

Don't worry about holding in the reset button too long.  On a Pro6, that will make no difference.  On units without a Backup button (rack-mount units), holding it longer makes it look for a USB recovery drive.  But if one's not inserted, then that has no effect, except that it may have to be power cycled to boot (dunno, never tried it).

 

As @StephenB said, you can use a USB keyboard with the VGA display to access the console.  But as I said before, it doesn't gain you a lot in your case.  It's more important if the NAS isn't booting to check BIOS settings and see the boot progress.

Message 33 of 191
tony359
Apprentice

Re: ReadyNAS Pro 6 crashed again

Amazing thanks.

 

If it crashes again I'll surely do an OS reinstall. I'm putting the VGA adaptor together, I know it's a shot in the dark but it might give us more clues as when the box disappears from the network, there is still some activity in it (the "network has changed" message when I plug/unplug the ethernet cable).

 

Finger crossed, I'll keep you posted. Thanks for now.

Message 34 of 191
tony359
Apprentice

Re: ReadyNAS Pro 6 crashed again

And the NAS "crashed" again unfortunately.

 

I went ahead and did an OS reinstall, which I doubt it helps as it looks like the current FW was reinstalled, nothing major.

 

Logs now show this:

 

Apr 03 23:21:42 Enterprise-NAS kernel: general protection fault: 0000 [#1] SMP
Apr 03 23:21:42 Enterprise-NAS kernel: Modules linked in: vpd(PO) [last unloaded: nv6lcd]
Apr 03 23:21:42 Enterprise-NAS kernel: CPU: 1 PID: 2508 Comm: bash Tainted: P O 4.4.218.x86_64.1 #1
Apr 03 23:21:42 Enterprise-NAS kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080014 07/26/2010
Apr 03 23:21:42 Enterprise-NAS kernel: task: ffff8800aba90000 ti: ffff88010ef10000 task.ti: ffff88010ef10000
Apr 03 23:21:42 Enterprise-NAS kernel: RIP: 0010:[<ffffffff88134ee0>] [<ffffffff88134ee0>] dup_fd+0x176/0x1e4
Apr 03 23:21:42 Enterprise-NAS kernel: RSP: 0018:ffff88010ef13dc0 EFLAGS: 00010286

 

Remember I manually unloaded nv6lcd yesterday.

 

I guess my next steps would be

- Try a different PSU. Which can be tricky as I am not sure I have a "known good" one 🙂 Does anybody remember what wattage the internal one is?

- Remove the drives, add a couple of spare, reset and test.

 

This is all very frustrating.

 

 

Message 35 of 191
StephenB
Guru

Re: ReadyNAS Pro 6 crashed again


@tony359 wrote:

- Remove the drives, add a couple of spare, reset and test.

 


I'd try this next.  You haven't definitively ruled out a software issue.

 


@tony359 wrote:

- Try a different PSU. Which can be tricky as I am not sure I have a "known good" one 🙂 Does anybody remember what wattage the internal one is?

 


The hardware manual says 300W.

Message 36 of 191
tony359
Apprentice

Re: ReadyNAS Pro 6 crashed again

I know, it's just that removing my whole storage doesn't appeal me! 🙂 I'll see if I can do a partial backup so I can at least restore my document folder etc.

 

'cause yeah, the NAS has gone offline again, it only lasted a couple of hours. 😞

Message 37 of 191
StephenB
Guru

Re: ReadyNAS Pro 6 crashed again


@tony359 wrote:

I know, it's just that removing my whole storage doesn't appeal me! 😞


I get that, but am thinking that you will either end up with factory default or a new NAS.  Just guessing that a new PSU won't solve it, and you've basically exhausted all the other hardware options.

 

So one way or another, you need to get as much data as you can backed up.

Message 38 of 191
tony359
Apprentice

Re: ReadyNAS Pro 6 crashed again

I can't disagree with you. 

 

This issue has been going on forever, only happening every few months, not hours. A tired PSU could be a good scenario IMHO.

I shall try to populate the NAS with 6 HDD for my test as that would probably stress the PSU as much as my current setup (5 HDDs). 

 

I wished there was an easier way to migrate to a different OS but by looking online I don't see easy paths. 

Message 39 of 191
Sandshark
Sensei

Re: ReadyNAS Pro 6 crashed again

Your problem doesn't seem like a power supply issue to me.  Periodic voltage droops could cause that, but it's just not a common failure mode.  A failing capacitor in the supply might do it, and "bulging" capacitors are a common failure on some supplies, but there are no instances of it on a Pro6 I can recall.

 

The original power supply is 300W.  But if you look at the voltage specs, it has more 12V current available than a typical 300W.  I recommend at least a 350W replacement, and I typically use a 400W.  I generally buy ones that have automatic fan speed control, which tends to keep them more quiet.  You can connect a standard ATX12V supply externally and see if that fixes the issue.  But in your case, you're going to need to run it a while, so be sure to keep the airflow as intact as possible.  Sealing the fan opening for the original supply and the gap where the cables come out with masking tape will accomplish that.

Message 40 of 191
tony359
Apprentice

Re: ReadyNAS Pro 6 crashed again

Thanks,

I am a bit into electronics, I've seen power supplies which look perfectly fine on a scope but after a while would start delivering unstable rails. That usually results in the unit locking though, not in this kind of partial crash. But when power delivery is not great, you never know, anything can happen. 

Indeed before I replace the PSU I'd like to try an ATX power supply I have, I'll see if I can keep the airflow as stock. 

And while testing an alternative PSU, I can put the Netgear PSU under a load and keep an eye on it with an oscilloscope.

It won't take long to be honest: the NAS has been crashing daily for a week now. 

 

The existing PSU was "serviced" some months ago, I fitted a noctua fan and blew the dust off. I do not remember seeing bulged capacitors but this unit is now 15 years old approximately and it's been on 24/7 for many years so I feel there is a chance the PSU is failing. 

 

The other weird thing is that I don't remember the NAS failing while in heavy use. As I said, the NAS is my multimedia centre - I keep a 1:1 ISO copy of my blu rays - so when I watch a movie the NAS is delivering steady 30/40Mbit for a couple of hours non stop. Now I am transferring my Documents folder on my desktop RAID and it's been working fine. I only find it disconnected when it's been idle for a while.

Message 41 of 191
StephenB
Guru

Re: ReadyNAS Pro 6 crashed again


@tony359 wrote:

 

The other weird thing is that I don't remember the NAS failing while in heavy use. 


There are some background processes still running, so that doesn't rule out a software issue.  But it does make your case for the PSU being the culprit less likely.

 

 

Message 42 of 191
tony359
Apprentice

Re: ReadyNAS Pro 6 crashed again

Little "plot twist" - assuming I'm not just being optimistic, the NAS has been up and running for two days now, no issues.

What I did was to disconnect it from the network. How do I know it's still up and running? I use a laptop to connect to it every few hours to see if it still pings - the laptop is otherwise sleeping so the NIC is offline.

 

If it stays online, the next step would be to connect it to the second NIC I have on my main desktop - so I can access it but it's away from my main network and also from the internet.

 

I really don't have much stuff happening on that NAS, it mostly sits there idle. But I have a fixed IP address and the FTP is accessible from the internet via port forwarding. 

I don't know, it wouldn't be the first time someone's hacked into my NAS 🙂 

Any ideas?

 

Oh, if the NAS stays online, then I don't have a hardware issue! 🙂 

Message 43 of 191
tony359
Apprentice

Re: ReadyNAS Pro 6 crashed again

Might need your help please.

 

NAS is on the second NIC of my Desktop PC. It's been up for three days so good news.

From where it sits, there is no access to the internet and even my PC does not really know much about it as it's on a different IP than before so all the mapped drives etc are disconnected.

 

Still, I noticed this:

 

When the NAS is connected to the network, doing nothing, the system temp rise 10C. When I unplug it, it cools down. System, not much the CPU. But the HDDs are really idle. The NAS is sitting on the floor. 

 

What do I get from this?

Message 44 of 191
StephenB
Guru

Re: ReadyNAS Pro 6 crashed again


@tony359 wrote:

 

What do I get from this?


Are you seeing much network traffic in the graphs when the temp rises?

Message 45 of 191
tony359
Apprentice

Re: ReadyNAS Pro 6 crashed again

A little bit - is the attached a lot?

 

Again, the NAS is on a different IP family so anything that is trying to connect to it is looking for the previous IP. And the NAS can't connect to the internet from where it is. 

 

Could that just be the admin page I kept open? Still, that raises the temps by 10C? Maybe this is a red herring but it looks weird.

Message 46 of 191
tony359
Apprentice

Re: ReadyNAS Pro 6 crashed again

I did another test, I left it plugged in but without the UI open.

Network activity stops but the temperatures don't drop. See below, I logged out at 17.30, it's 18.40 now. You can see the activity stopping at 17.30 but temps stay higher. 

 

This is so weird. 

Message 47 of 191
StephenB
Guru

Re: ReadyNAS Pro 6 crashed again


@tony359 wrote:

I did another test, I left it plugged in but without the UI open.

Network activity stops but the temperatures don't drop. See below, I logged out at 17.30, it's 18.40 now. You can see the activity stopping at 17.30 but temps stay higher. 


 There is volume activity (operations per second) that coincides with the all of the rises in temperature. So there is some background activity happening.

 

Message 48 of 191
tony359
Apprentice

Re: ReadyNAS Pro 6 crashed again

and what could that be? As I said, the NAS is on a different IP address so all my network shares point to a different IP. 

 

Is there a way to monitor what is transferring data/accessing the drives via terminal?

 

Edit: it doesn't seem to be that though. See attached: 17:30 is when I logged out, all activity stops. But temps stay high until I physically unplug at 18:30.

 

Do we know where the temperature sensor is? Could that just be the NIC IC warming up a bit because it's being used and the temp sensor happens to be nearby? 

Message 49 of 191
StephenB
Guru

Re: ReadyNAS Pro 6 crashed again


@tony359 wrote:

and what could that be? As I said, the NAS is on a different IP address so all my network shares point to a different IP. 

 


Might not be linked to network activity at all.  There are background processes that kick in from time to time.  If you use indexing, that will get updated periodically, and of course AV (if enabled) will run scans from time to time.  Snapshot processing, and other btrfs stuff might also be kicking in.

 


@tony359 wrote:

 

Do we know where the temperature sensor is? Could that just be the NIC IC warming up a bit because it's being used and the temp sensor happens to be nearby? 


The one that's spiking appears to be the CPU temp, not the system temp.  The CPU sensor is part of the chip. In many intel chips, it is not reliable at low temps - it's purpose to detect high ones.  There are some old posts here from Netgear saying that they clamped low readings for some CPUs, so the spike might not be as big as it looks.  But it's been quite a while (7-8 years ago), so I con't clearly remember the details.

Message 50 of 191
Top Contributors
Discussion stats
  • 190 replies
  • 4249 views
  • 7 kudos
  • 7 in conversation
Announcements