- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
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?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
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?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
@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?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
Hello StephenB
sorry for late response i send a message back but it didn't go through i send it twice yesterday i been busy i check the NAS it still running usually it work for like 1-5 day then it NASV2842021\Reolink say it can't be found on windows 10.
i will wait and see
getting
also netgear,com is slow but i have good internet in Australia don't know why is it doing that
Correct the highlighted errors and try again.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
Sorry but THIS website is making me piss off i post about 10+ times repost but it keep deleting my messages
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
Hi sorry again i wrote a message yesterday about the latest issues it say it posted it but look like it didn't this website is buggy 😐 i check many times to see but it not coming up 😐
so here it is again
=== df -h === Filesystem Size Used Avail Use% Mounted on udev 10M 4.0K 10M 1% /dev /dev/md0 4.0G 1.3G 2.4G 36% / tmpfs 2.0G 0 2.0G 0% /dev/shm tmpfs 2.0G 6.1M 2.0G 1% /run tmpfs 987M 1.4M 985M 1% /run/lock tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup /dev/md127 11T 5.4T 5.6T 49% /Reolink /dev/md127 11T 5.4T 5.6T 49% /home /dev/md127 11T 5.4T 5.6T 49% /apps /dev/md127 11T 5.4T 5.6T 49% /var/ftp/Reolink
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
ok i swear this is a length limit but it keep deleting it
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
Here is the sys.log
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
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/md127
But 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?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
@ninjasniper85_ wrote:
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 shouldn't (famous last words).
The transfers are failing at the moment though, and creating a lot of clutter in the logs.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
ok understand do i have to decrease the write for my IP Camera > NAS?
also
kernel.log
i have access to the folder atm but it stop sending video and frozen up around 4pm
System log in PDF form
i can access the admin page and nas but nothing sending to the nas no error when i am on raidar when i check diagnostics
like you said the transfer are failing
how do i fix it decrease the Max file size (MB) on my camera
2 camera is set for 1024MB
2 camera is set for 100MB
1 camera is set for 50MB
they are all set for Motion Detection
i do have a setting call Transport Mode
honesty it could be this that causing the log to error and the nas to freeze up
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
@ninjasniper85_ wrote:
ok understand do i have to decrease the write for my IP Camera > NAS?
I'm not saying that, just the reolink messages are getting in the way of seeing what is happening. It would be a useful test to simply turn off all the cameras for a couple days, and see if the problem stops (or not). Alternatively, disable the transfers in all the cameras for a couple of days, and just rely on the sd card storage.
There are a lot of log entries for the ftp transfers (which do seem to be succeeding). The errors are actually with the snapshots for that folder
Mar 06 04:40:10 NASV2842021 snapperd[3561]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Mar 06 04:40:10 NASV2842021 snapperd[3561]: reading failed
Are snapshots enabled for the folder? Are you able to access the Reolink share from your PC?
@ninjasniper85_ wrote:
i do have a setting call Transport Mode
honesty it could be this that causing the log to error and the nas to freeze up
No, that's not the problem.
If I were to guess, it would be something like
- failing memory module
- an issue with a disk (all show command timeouts, so hard to say which)
- a corrupted file system on the NAS
- perhaps a failing hardware supply
I suggest running a disk test as a good next step - go to the volumes page in the web ui, and click on the settings wheel. You'll see the option there. That will test all the disks (and it will take a day or so to complete). Hopefully the system won't lock up again before it finishes.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
I will disabled FTP for the Cameras but turning them off require me to disabled the whole System from the POE Switch and that i won't do but i will do Disabled FTP for temporary cause the SD card storage only storage 1 week of footage and the FTP storage 1-3 month
Are snapshots enabled for the folder? snapshot are disabled
Are you able to access the Reolink share from your PC?
Yes \NASV2842021\Reolink (the issues was i think it crash/freeze around 4pm i went on raidar to see what is happen cause it say it couldn't been found went on raidar did say it could not find the NAS and after few retry i had connected back i had issues download the system log.rar had to download it a few times.
a Disk Test i will run i will disabled the FTP for all cameras first then run the disk test
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
@ninjasniper85_ wrote:
a Disk Test i will run i will disabled the FTP for all cameras first then run the disk test
That would be good. Check the command timeouts afterwards, and see if they increase during the test.
@ninjasniper85_ wrote:
Are snapshots enabled for the folder? snapshot are disabled
Ok. Not sure how to fix the snapperd error then.
But if you have enough space, you could try copying the footage to a new share, Then delete the ReoLink share from the web ui, and rename the new one to ReoLink. Make sure you use the same settings for the new share.
If you try this, wait for the disk test to complete (and obviously do it before you start up FTP again).
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
the disk test finish and it passed!
kernel.log
volume.log
sys.log
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
@ninjasniper85_ wrote:
the disk test finish and it passed!
Good.
I suggest creating a new ReoLink share, and see if that removes the snapperd errors.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
will do
it will take awhile to transfer the files over then i will reenabled the camera FTP again to see if that removes the snapperd errors.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
Kernel
System
Part 1
Part 2
Line 174: Mar 12 10:02:42 NASV2842021 snapperd[17923]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Line 175: Mar 12 10:02:42 NASV2842021 snapperd[17923]: reading failed
Line 766: Mar 12 11:02:42 NASV2842021 snapperd[19811]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Line 767: Mar 12 11:02:42 NASV2842021 snapperd[19811]: reading failed
Line 1312: Mar 12 12:02:43 NASV2842021 snapperd[21667]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Line 1313: Mar 12 12:02:43 NASV2842021 snapperd[21667]: reading failed
Line 1813: Mar 12 13:02:43 NASV2842021 snapperd[23496]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Line 1814: Mar 12 13:02:43 NASV2842021 snapperd[23496]: reading failed
Line 2210: Mar 12 14:02:43 NASV2842021 snapperd[25277]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Line 2211: Mar 12 14:02:43 NASV2842021 snapperd[25277]: reading failed
Line 2667: Mar 12 15:02:44 NASV2842021 snapperd[27079]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Line 2668: Mar 12 15:02:44 NASV2842021 snapperd[27079]: reading failed
Line 3099: Mar 12 16:02:44 NASV2842021 snapperd[28859]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Line 3100: Mar 12 16:02:44 NASV2842021 snapperd[28859]: reading failed
Line 3515: Mar 12 17:02:45 NASV2842021 snapperd[30627]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Line 3516: Mar 12 17:02:45 NASV2842021 snapperd[30627]: reading failed
Line 4074: Mar 12 18:02:45 NASV2842021 snapperd[32476]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Line 4075: Mar 12 18:02:45 NASV2842021 snapperd[32476]: reading failed
Line 4628: Mar 12 19:02:45 NASV2842021 snapperd[1967]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Line 4629: Mar 12 19:02:45 NASV2842021 snapperd[1967]: reading failed
Line 4942: Mar 13 08:09:43 NASV2842021 snapperd[3613]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Line 4943: Mar 13 08:09:43 NASV2842021 snapperd[3613]: reading failed
Line 4998: Mar 13 08:10:51 NASV2842021 snapperd[3613]: THROW: open failed path:/data/Reolink errno:2 (No such file or directory)
Line 4999: Mar 13 08:10:51 NASV2842021 snapperd[3613]: reading failed
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
So the old Reolink share has been deleted?
Can you confirm that your volume is named "data"?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
yes the old one has been deleted
don't know why snappered still showing
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
Can you confirm that your volume is named "data"?
Reolink
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
@ninjasniper85_ wrote:
Can you confirm that your volume is named "data"?
Reolink
Ok. The snapperd error is because the system trying to access a share on /data - which doesn't exist on your system.
Likely fix is to find and delete a config file in /etc/snapper/configs
Are you familiar with the linux command line?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP
Are you familiar with the linux command line?
hmmm
i will say no
i did some python coding at College
Please guide me