ehbush Posted January 9, 2020 Share Posted January 9, 2020 Hey all, Just as of recently (today), am getting the following when updating plugins (and actually spotted when trying to switch to next version instead of stable, was only on stable as this was a fresh reinstall from a few weeks ago). Error I was getting was something similar to "plugin: run failed: /bin/bash retval: 1" but specific to the enhanced.log plugin. After searching the interwebs, and the forums here, saw a number of callouts about not enough RAM (I have 64GB of RAM) or full disks (I do not, as far as I can tell) Filesystem Size Used Avail Use% Mounted on rootfs 32G 1.3G 31G 4% / tmpfs 32M 588K 32M 2% /run devtmpfs 32G 0 32G 0% /dev tmpfs 32G 0 32G 0% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 128M 284K 128M 1% /var/log /dev/sda1 7.3G 468M 6.8G 7% /boot /dev/loop0 9.0M 9.0M 0 100% /lib/modules /dev/loop1 5.9M 5.9M 0 100% /lib/firmware tmpfs 1.0M 0 1.0M 0% /mnt/disks So then I went to remove said plugin, and that failed as well (I think?) plugin: removing: enhanced.log.plg ----------------------------------------------------------- Plugin enhanced.log has been removed. Version: 2019.12.26 ----------------------------------------------------------- Warning: rename(/boot/config/plugins/enhanced.log.plg,/boot/config/plugins-removed/enhanced.log.plg): Read-only file system in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 358 plugin: removed I have attached the diagnostics, but any guidance or assistance would be very much appreciated. I am seeing a lot of errors in the syslog, examples: Jan 8 20:53:15 unraid root: cp: cannot create regular file '/boot/config/secrets.tdb': Read-only file system Jan 8 20:53:19 unraid emhttpd: error: put_disk_settings, 3547: Read-only file system (30): fopen: /boot/config/disk.cfg Jan 8 21:15:23 unraid kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 01095fd6) Thanks in advance! Any and all help is greatly appreciated! unraid-diagnostics-20200108-2115.zip Quote Link to comment
ehbush Posted January 9, 2020 Author Share Posted January 9, 2020 (edited) I should note, the array starts fine (which makes sense if the flash drive is read-only, yeah?) - and I believe this issue began after an unclean shutdown due to a brief power loss earlier today. Edited January 9, 2020 by AccurateAesthetics answering my own questions, potentially :) Quote Link to comment
ehbush Posted January 9, 2020 Author Share Posted January 9, 2020 (edited) I may have just found a potential solution from Squid in another thread...specifically, for a very similar error he said: Quote Corrupted flash drive. Shut down, toss it into a Windows / Mac box and run the file system checks on it. I will wait to hear back since I already opened this thread before proceeding further, but I imagine that will be the recommendation... Edited January 9, 2020 by AccurateAesthetics Quote Link to comment
JorgeB Posted January 9, 2020 Share Posted January 9, 2020 Flash drive problems: Jan 8 20:53:10 unraid kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 33d7450f) Jan 8 20:53:10 unraid kernel: FAT-fs (sda1): Filesystem has been set read-only Jan 8 20:53:10 unraid kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 33d7450f) Jan 8 20:53:10 unraid kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start d46b0a5a) Run chkdsk on it Quote Link to comment
ehbush Posted January 9, 2020 Author Share Posted January 9, 2020 Thanks for the quick response! It is fixed now 😄 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.