This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
This unit has been humming along for several years when this error started to pop up following the 6.10.7 upgrade.
I am able to access via ssh but the management service is not running. The web server is and I do make a connection to the web server. It is just that frontview is not running.
Network shares are available.
I did physically re-seat the memory to no effect.
I am able to download the log package via RAIDar.
The results of diagnostics via RAIDar are cryptic. It lists these two system errors:
Disk 1 has 8 Current Pending Sectors
Volume root is degraded
And nothing in the logs section.
This leads me to believe that perhaps something in front view is broken? Is there a way to restart the management service via the cmd line?
As a last resort I will offload the data and factory default the unit. I would just rather not lose all that time as it has 12-10TB drives and moving data is a job.
Thank you in advance for any help you can give. It is much appreciated.
The results of diagnostics via RAIDar are cryptic. It lists these two system errors:
Disk 1 has 8 Current Pending Sectors
Volume root is degraded
The second error suggests something is wrong with RAID array for the OS (and the first says that you are seeing disk errors on disk 1).
I'd try powering down, removing disk 1, and then try rebooting the NAS as read-only. If that results in normal access to the nas admin ui, then I'd test the disk with vendor tools. Personally I run both the full read test and a full write zeros/erase test.
Replaced the disk located in channel 1 and the "8 pending sectors" message is now gone. While the messages "Volume root is degraded" (existing) and "Volume Data is degraded" (new) do appear I am fairly confident that they will no longer appear once the array completes resyncing. That process will take more than 24 hours so I will post the results here upon completion.
I have downgraded to v6.10.5 and the management interface appears to be more stable. It has been up continuously for 24 hours (usually failed after a few hours) however I still have these messages in the diagnostic output. Any thoughts would be appreciated.
I have downgraded to v6.10.5 and the management interface appears to be more stable. It has been up continuously for 24 hours (usually failed after a few hours) however I still have these messages in the diagnostic output. Any thoughts would be appreciated.
2022-04-18 13:57:42: enclosure_monit[5053]: segfault at 30 ip 00007f594f448950 sp 00007f5941586ae8 error 4 in libapr-1.so.0.5.1[7f594f42b000+32000]
This is an apache library, so likely linked to the failure of the web ui. It might be useful to run the diagnostic again, and see if it gives the same result.
The entries in the diagnostic output are unchanged after executing the commands and rebooting. However there are no new entries regarding the library file post downgrading to 6.10.5
I would expect that the first log message indicating 11 out of 12 devices was the result of replacing drive 1
I do not understand the Volume root is degraded message and I hesitate to use the tools available because of my unfamiliarity with front view and how it is integrated into the system.
Clamav is not updating (a known issue with 6.10.5. I am wondering if it is something in the configuration, the actual program or it's interface to front view. Can that be updated from the command line? Will that solve the virus definition file issue?
The entries in the diagnostic output are unchanged after executing the commands and rebooting. However there are no new entries regarding the library file post downgrading to 6.10.5
Right. Those two log errors are from 4/18, so they aren't a result of running the diags.
I do not understand the Volume root is degraded message and I hesitate to use the tools available because of my unfamiliarity with front view and how it is integrated into the system.
Understood. As I said, I don't think it is critical. But somehow that volume is still including a disk that you replaced. There is no way to fix that from the admin web ui.
Clamav is not updating (a known issue with 6.10.5. I am wondering if it is something in the configuration, the actual program or it's interface to front view. Can that be updated from the command line? Will that solve the virus definition file issue?
I don't think you can fix that from the command line. You could try 6.10.6, which has the fix for it.
Yes, that's "grow" to actually shrink it, but that's the right keyword. It would definitely work if you were really reducing it from 13 to 12 drives, so I think it should also work to eliminate your "phantom" drive.
