May I ask what you are working on?
Thanks for your help!
I am trying to make wetty plugin support more features of wetty, such as --command option.
Beiträge von libook
-
-
Hi, I would like to contribute code for core plugins. How can I test or debug them to ensure they are running as expected? Is there any guide?
-
I started using OMV from v5 (or v4, I can't remember). And I have migrate to v6 for many months.
The situation now is:
Storage->Disks: is using label names in Device column;
Storage->S.M.A.R.T.->Devices: is using label names in Device column;
Storage->File Systems: is using label names in Device column;
Storage->Shared Folders: is using UUID in Absolute Path column;
Storage->mergerfs: is using both UUID and ID in Paths column;
Services->SnapRAID->Drives: is using label names in Drive input box for creating or modifying UI.
It's a bit confusing to manage.
Please provide some best practices on whether a single style of description should and can be used consistently.
-
This is a two year old thread. Many things have been fixed/changed since then. Did your pool import into the mergerfs plugin? I need more details.
Sorry, this page is the only one I have gotten from Google with the error message.
It seems that dpkg was executing /usr/share/openmediavault/confdb/create.d/conf.service.mergerfs.sh
Then I got the error:
Code
Alles anzeigenSetting up openmediavault-mergerfs (6.0.14) ... Updating configuration database ... LiNas.nas.libook.com.cn: Data failed to compile: ---------- Rendering SLS 'base:omv.deploy.fstab.15unionfilesystems' failed: Jinja error: 'NoneType' object has no attribute 'get_dict' Traceback (most recent call last): File "/usr/lib/python3/dist-packages/salt/utils/templates.py", line 497, in render_jinja_tmpl output = template.render(**decoded_context) File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1090, in render self.environment.handle_exception() File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 832, in handle_exception reraise(*rewrite_traceback_stack(source=source)) File "/usr/lib/python3/dist-packages/jinja2/_compat.py", line 28, in reraise raise value.with_traceback(tb) File "<template>", line 1, in top-level template code File "/usr/lib/python3/dist-packages/jinja2/sandbox.py", line 465, in call return __context.call(__obj, *args, **kwargs) File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__ return self.loader.run(run_func, *args, **kwargs) File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs) File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as return _func_or_method(*args, **kwargs) File "/var/cache/salt/minion/extmods/modules/omv_conf.py", line 45, in get return objs.get_dict() AttributeError: 'NoneType' object has no attribute 'get_dict' ; line 1 --- {% set config = salt['omv_conf.get']('conf.service.unionfilesystems') %} <====================== {% for pool in config.filesystem %} {% set poolmount = salt['omv_conf.get_by_filter']( 'conf.system.filesystem.mountpoint', {'operator':'stringEquals', 'arg0':'uuid', 'arg1':pool.self_mntentref}) %} [...] --- ERROR: Failed to create the default configuration: Command '['/usr/share/openmediavault/confdb/create.d/conf.service.mergerfs.sh']' returned non-zero exit status 1. dpkg: error processing package openmediavault-mergerfs (--configure): installed openmediavault-mergerfs package post-installation script subprocess returned error exit status 1 Processing triggers for openmediavault (6.0.13-2) ... Updating workbench configuration files ... Restarting engine daemon ... Errors were encountered while processing: openmediavault-mergerfsI didn't remove union filesystem pool before upgrade to OMV v6. So it is still working with the old configuration (I can still access the 'merged' filesystem). It just can't finish the dpkg configuration of the new mergerfs plugin. I can see the web UI of the plugin without any row in the table.
Then, things became different.
I went out for a while. When I came back, problems had been fixed automatically.
In my /var/log/apt/term.log:
CodeSetting up openmediavault-mergerfs (6.0.14) ... Updating configuration database ... Processing triggers for openmediavault (6.0.13-2) ... Updating workbench configuration files ... Restarting engine daemon ...There is no apt execution log in my shell history of that time. I have enabled unattended-upgrades but there is no log of that time either.
I just can't explain this. Sorry for bothering you.
-
As Volker noticed, this is a union filesystems plugin issue. Have you created a union filesystems pool?
@ryecoaaron I have the same problem.
I have created a union filesystems pool during using OMV v5. I upgraded it to OMV v6. The unionfilesystem plugin has been removed. I saw this problem when I was installing new mergerfs plugin.
MergerFS is still working because of fstab.
-
I would replace it immediately
Thanks for your idea!
The new drive is on the way. Hope all data are still fine.
-
please revise attribute 197 & 198:
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 96
and yes, you must consider to replace it. or at least check if grow
Thanks for your analytics!
After reading your comment, I checked S.M.A.R.T. informations of other drives. The RAW_VALUE of these two attributes of other drives are all 0. So the one with value 96 seems being dying.
I 'll replace it soon.
-
There were a red dot on S.M.A.R.T. dashboard. When I place cursor on it, it told me "Device has a few bad sectors.".
So I manually checked the S.M.A.R.T. information of the divice.
The Reallocated_Sector_Ct attribute seems normal:
Code
Alles anzeigenVendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 124749776 3 Spin_Up_Time 0x0003 095 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 811 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 118492584 9 Power_On_Hours 0x0032 049 049 000 Old_age Always - 45007 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 342 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 053 047 045 Old_age Always - 47 (Min/Max 45/53) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 71 193 Load_Cycle_Count 0x0032 050 050 000 Old_age Always - 100343 194 Temperature_Celsius 0x0022 047 053 000 Old_age Always - 47 (0 14 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 96 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 96 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 33468h+10m+04.933s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 45134824293 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 184368737159Then I use openSeaChest tool by Seagate:
The No.5 attribute:
Code5 - Retired Sectors Count Attribute Type(s): Pre-fail Online Data Collection Event Count Self-Preserving Nominal Value: 100 Worst Ever Value: 100 Threshold: 10 Raw Data: 00000000000000hPlease tell me what is going on the disk drive. Should I replace it?
