NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
Issues: ReadyNAS keep freeze when trying access the local IP it doesn't show the login so i have to manual hold the button to reset it
What is use for: Storage Data for IP Cameras
Raid 6
6x3TB
Firmware 6.10.8
ReadyNAS Pro 6
4GB ram
Q6600 CPU
System
- Disk 1 has 5 Command Timeouts
- Disk 2 has 3 Command Timeouts
- Disk 3 has 1 Command Timeouts
- Disk 4 has 2 Command Timeouts
- Disk 5 has 3 Command Timeouts
- Disk 6 has 20 Command Timeouts
Logs
- 2023-02-27 18:21:46: general protection fault: 0000 [#2] SMP
- 2023-02-27 18:21:46: RIP [] __fget+0x39/0x65
- 2023-02-27 18:21:34: general protection fault: 0000 [#1] SMP
- 2023-02-27 18:21:34: RIP [] __fget+0x39/0x65
sys.log
Feb 27 18:21:28 NASV2842021 msmtpq[7007]: mail [ 1 ] [ 2023-02-21-09.47.32 ] from queue ; couldn't be sent - host not connected
Feb 27 18:21:29 NASV2842021 snapperd[3559]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Feb 27 18:21:29 NASV2842021 snapperd[3559]: reading failed
Feb 27 18:22:30 NASV2842021 snapperd[3559]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Feb 27 18:22:30 NASV2842021 snapperd[3559]: reading failed
Feb 27 18:23:30 NASV2842021 snapperd[3559]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Feb 27 18:23:30 NASV2842021 snapperd[3559]: reading failed
Feb 27 18:23:37 NASV2842021 clamd[29103]: SelfCheck: Database status OK.
76 Replies
Next time see if it responds to ping before you reboot it. I also suggest enabling SSH, as that might respond when the web interface doesn't.
Are the command timeouts increasing?
How full is the OS partition?
How full is the OS partition? Currently 4.70TB Free 6.19TB Every Month i delete last month
SSH is enabled
Are the command timeouts increasing? what do you mean this? THROW: open failed path:/data/Reolink errno:2 (No such file or directory)?
`
Sys.log in PDF Today 3/3/2023 AUS time
Will see when it happen again
What command do i run when it happen on SSH?
ninjasniper85_ wrote:
How full is the OS partition? Currently 4.70TB Free 6.19TB
No, that's not the OS partition - it's the data volume.
- Download the full log zip file from the logs page.
- Open Volume.log
- Scroll down to the section that starts with === df -h ===
- Look at the line for /dev/md0
You'll see something like this
=== df -h === Filesystem Size Used Avail Use% Mounted on udev 10M 4.0K 10M 1% /dev /dev/md0 4.0G 1.1G 2.7G 30% / ...Let us know what's in the Use% field.
ninjasniper85_ wrote:
do you mean this? THROW: open failed path:/data/Reolink errno:2 (No such file or directory)?
No, I'm talking about these:
ninjasniper85_ wrote:
System
- Disk 1 has 5 Command Timeouts
- Disk 2 has 3 Command Timeouts
- Disk 3 has 1 Command Timeouts
- Disk 4 has 2 Command Timeouts
- Disk 5 has 3 Command Timeouts
- Disk 6 has 20 Command Timeouts
All your disks are timing out to some SATA commands. That can be due to a disk problem, or the SATA controller in the NAS. It's hard to say, since a disk can lock up the SATA bus, which will create timeout messages for other disks. It could also potentially be a result of your forced shutdowns.
Whatever the cause, you should be looking in the log zip file to see if there is any evidence these counts are going up.
ninjasniper85_ wrote:
Logs
- 2023-02-27 18:21:46: general protection fault: 0000 [#2] SMP
- 2023-02-27 18:21:46: RIP [] __fget+0x39/0x65
- 2023-02-27 18:21:34: general protection fault: 0000 [#1] SMP
- 2023-02-27 18:21:34: RIP [] __fget+0x39/0x65
What apps (if any) are tunning on the NAS? Is it possible you are running SickBeard?
Here is the sys.log
The Reolink errors are flooding the log.
I am seeing this
Mar 07 07:22:34 NASV2842021 mdadm[2943]: RebuildStarted event detected on md device /dev/md0, component device resync Mar 07 07:22:34 NASV2842021 mdadm[2943]: NewArray event detected on md device /dev/md1 Mar 07 07:22:34 NASV2842021 mdadm[2943]: NewArray event detected on md device /dev/md127But nothing after that on either md127 (your data volume) or md0 and md1.
What are you seeing on the volumes and shares pages of the NAS web ui?
The Reolink is flooding the log i think cause i setup a FTP for my 5 POE Camera to send the picture and video in the NAS for storage cause the inbuilt MircoSD card only 128GB and it doesn't hold a month of video only a week.
will that crash/freeze the NAS?
it is sending data to the NAS when motions detect and it will write data
Ok i swap ram
The last one was in there lasted 14 days Ish+This one last it 5 hours đ
so one of the ram is faulty and maybe a hardware is faulty for the https://community.netgear.com/t5/ReadyNAS-Storage-Apps-Current/Downgrade-to-RAIDiator-x86-from-ReadyNAS-OS-notsupported/m-p/859412/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExHR0tNSUFRR09BRjc1fDIzMDczNTB8U1VCU0NSSVBUSU9OU3xoSw#M2683
is there a video for this? cause my learning styles is different and i am not studying into networking i have a IT Technology and Telecommunications Technology background this is way out of my zone đ
going switch the ram again
ninjasniper85_ wrote:
is there a video for this?
Not sure what you are asking for - do you want instructions on downgrading back to 4.2????
Sandsharksaid
"
That's a Pro Business Edition (ProBE), then, not a Pro6. Pro6 models are -200's. Same motherboard, different processor. Though, of course, you've updated yours, anyway.
With that BIOS version, I'm surprised your NAS is booting at all. I have always believed that the fastest processor that can be used with that old version of the BIOS is an E6600. I guess I was mistaken that it won't boot with a faster processor, but I do suspect that has a lot to do with your problems.
Frankly, the easiest way to update the bios is to use a spare drive in place of your current drive set to convert the unit back to RAIDiator 4.2.x, then use the Bios update add-on, then revert back to OS6. That was true even before Debian Jessie became unsupported and you could still easily get the necessary tools to manually update using apt."
cause my 10/03/2008 FLAME6-MB V1.6 BIOS is this
well did the Ram testing i don't know if it still hardware issues cause of one the ram last 14+ days and the other last it 5 hours
My thinking process is getting new/second hand ram stick and test them or just updating the bios cause that the longest i seen it run for awhileif they like a instructions on downgrading back to 4.2 video about it would be great
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
