[Plugin] CA Fix Common Problems


Recommended Posts

3 hours ago, ghost82 said:

It's an error in the L1 cache

Oh I see! My CPU is not overclocked, bios is up to date and case is clean and free from dust inside. The PSU may be the problem, I think. It's a cheap PSU that I am using for one month now, waiting my CX600 to come back from service.

Anyway, thank you so much for the time you spent to me. I really appreciate it!
Cheers

Link to comment
49 minutes ago, olschool said:

I can't specifically identify what may be filling my syslog, any expert guidance would be appreciated. 

 

Something is basically continually writing to your flash drive  and the backup feature of MyServers keeps backing up

 

Apr 18 04:41:41 YoungStewtsGen flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
### [PREVIOUS LINE REPEATED 439 TIMES] ###

(one of many many entries)

 

You're going to want to post here: https://forums.unraid.net/topic/112745-stop-useless-backups/#comment-1026238, and read the thread so that you can determine what's going on.  @ljm42 will help out if necessary when you post there.

  • Like 1
Link to comment
  • 2 weeks later...

I just updated to 6.10.2, from 6.9.2

 

I got errors at first (once I was able to fix my docker not working, and that cache drive not being recognized, and there being syntax errors.... etc.....) that my flash drive error'd out, and was READ ONLY. This also caused Fix Common Problems to poop the bed super hard.

 

Following the advice, got a new flash drive, transferred the key over.... FixCommonProblems still hates everything about me, and is throwing the same errors. Is this residual from the previous drive, or is there something in the way I have messed everything which basically wrecks whatever flash drive I put it on?

 

Thanks a ton for all that you do.

unraid-diagnostics-20220601-0830.zip

Link to comment

Hey Squid, i'm getting what appears to be a false positive on a file i created on my USB:
 

/boot/config/usb-rules.cfg corrupted	Your flash drive has possible corruption on /boot/config/usb-rules.cfg.

 

This is the contents of that file (which just maps the zwave and zigbee controller from my HUSBZ-1 to static device entities on boot):

 

SUBSYSTEMS=="usb", DRIVERS=="cp210x", ATTRS{interface}=="HubZ Z-Wave Com Port", SYMLINK+="zwave"
SUBSYSTEMS=="usb", DRIVERS=="cp210x", ATTRS{interface}=="HubZ ZigBee Com Port", SYMLINK+="zigbee"

 

There doesn't appear to be any corruption in the file, i've recreated it just to be sure, so i'm thinking there is some sort of string of characters that the scan is detecting as corruption.

Edited by PhAzE
Link to comment

I had some errors with my hardware and now have Unraid 6.10.2 Stable again, but its show a corrupt file on my Boot USB drive. Not sure I can remove this and it will be recreated. Your flash drive has possible corruption on /boot/config/smart-one-backup.cfg. Post your diagnostics in the forum for more assistance. Diag attached. Any help would be greatly appericated. Thanks in Advance.

unraid02-diagnostics-20220608-1624.zip

Link to comment

Since updating to Unraid Version: 6.10.2 after along time of not updating. I have gotten the "Multiple NICs on the same IPv4 network" with the Fix Common Problems Plugin. However in my network settings its list only one network interface. (Screenshots are attached) Any suggestion you have to resolving this would be appreciated. This was the first time my unraid server has been restarted in some time since it has just been working perfectly since I applied the last update. 

 

I am also unable to use WireGuard now as it doesn't let me access the internet only the unraid server from the peer. This is probably tied to the same issue listed. 

Network Settings

image.thumb.png.6cfe4216b4377de4ca0982c0091fc4c1.png

 

 

Diagnostic report attached below

tower-diagnostics-20220609-1700.zip

Link to comment

You seem to be getting continuous errors along the lines of

 

Jun 10 05:33:01 BIGDADDY kernel: sd 2:0:0:0: [sdb] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
Jun 10 05:33:01 BIGDADDY kernel: sd 2:0:0:0: [sdb] tag#12 CDB: opcode=0x2a 2a 00 0d f0 3f 60 00 00 40 00
Jun 10 05:33:01 BIGDADDY kernel: blk_update_request: I/O error, dev sdb, sector 233848672 op 0x1:(WRITE) flags 0x1800 phys_seg 6 prio class 0
Jun 10 05:33:01 BIGDADDY kernel: BTRFS warning (device sdd1): lost page write due to IO error on /dev/sdb1 (-5)
### [PREVIOUS LINE REPEATED 2 TIMES] ###
Jun 10 05:33:01 BIGDADDY kernel: BTRFS error (device sdd1): error writing primary super block to device 2
Jun 10 05:33:03 BIGDADDY kernel: BTRFS warning (device sdd1): lost page write due to IO error on /dev/sdb1 (-5)

which indicates that there are issues with your cache pool since the sdd and sdb devices belong to it.

 

Not sure of the best way to proceed - maybe @JorgeB might have a view?

Link to comment
2 hours ago, randommonth said:

Any advice appreciated!

One of the cache devices dropped offline:

Jun  8 19:56:06 BIGDADDY kernel: ata1: hard resetting link
Jun  8 19:56:12 BIGDADDY kernel: ata1: COMRESET failed (errno=-16)
Jun  8 19:56:12 BIGDADDY kernel: ata1: reset failed, giving up
Jun  8 19:56:12 BIGDADDY kernel: ata1.00: disabled

 

Check/replace cables, also see here for better pool monitoring for the future.

Link to comment

i had a power failure and my backup n.u.t. didn't do its job properly so i had a hard shutdown 9 days ago.

now i have the same error again

/var/log is getting full (currently 100 % used)

 

image.png.d29edec7b10ff8ae2be1b4f7c36caf0e.png

 

can't even download diagnostics o_O

image.png.9118f27b0a67b1e4336bbd93c9102fcd.png

waiting for over 5 minutes now...

guess i should reboot?

 

already had the same problem some weeks ago. wasn't sure if i should've revived that topic or post here 9_9

Edited by pika
forgot diagnostics
Link to comment

I'm going to reboot now. log shows zillions lines like this:

Jun 13 21:14:44 DataTower nginx: 2022/06/13 21:14:44 [crit] 7671#7671: ngx_slab_alloc() failed: no memory
Jun 13 21:14:44 DataTower nginx: 2022/06/13 21:14:44 [error] 7671#7671: shpool alloc failed
Jun 13 21:14:44 DataTower nginx: 2022/06/13 21:14:44 [error] 7671#7671: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory.
Jun 13 21:14:44 DataTower nginx: 2022/06/13 21:14:44 [error] 7671#7671: *1773828 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost"
Jun 13 21:14:44 DataTower nginx: 2022/06/13 21:14:44 [crit] 7671#7671: ngx_slab_alloc() failed: no memory
Jun 13 21:14:44 DataTower nginx: 2022/06/13 21:14:44 [error] 7671#7671: shpool alloc failed
Jun 13 21:14:44 DataTower nginx: 2022/06/13 21:14:44 [error] 7671#7671: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory.
Jun 13 21:14:44 DataTower nginx: 2022/06/13 21:14:44 [error] 7671#7671: *1773829 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Jun 13 21:14:44 DataTower nginx: 2022/06/13 21:14:44 [crit] 7671#7671: ngx_slab_alloc() failed: no memory
Jun 13 21:14:44 DataTower nginx: 2022/06/13 21:14:44 [error] 7671#7671: shpool alloc failed
Jun 13 21:14:44 DataTower nginx: 2022/06/13 21:14:44 [error] 7671#7671: nchan: Out of shared memory while allocating channel /var. Increase nchan_max_reserved_memory.

 

Link to comment

Does the plugin also inform the user of best practices to prevent common problems?

 

For example:

  • UPS (and configured correctly)
  • Dynamix File Integrity plugin (installed and scheduled)
  • ECC Memory
  • Not sure if I'm missing anything else.  Maybe potential filesystem issues (btrfs vs. xfs recommenations).
Link to comment
15 hours ago, Jaybau said:

Does the plugin also inform the user of best practices to prevent common problems?

 

No - It's a bit out of the realm of what FCP is supposed to do, and not particularly feasible and would be annoying, and there's many counter arguments against all of those examples.

Link to comment
  • 2 weeks later...

Hi guys, following up since my post on June 10 (above). I deleted the docker image and changed to a docker directory. However I just received the same error warning about /var/log filling.

 

It appears I'm getting the same errors as last time, and checking the tip provided by Jorge provides the following:

 

[/dev/sdd1].write_io_errs    0
[/dev/sdd1].read_io_errs     0
[/dev/sdd1].flush_io_errs    0
[/dev/sdd1].corruption_errs  0
[/dev/sdd1].generation_errs  0
[/dev/sdb1].write_io_errs    17381866
[/dev/sdb1].read_io_errs     1092081
[/dev/sdb1].flush_io_errs    615464
[/dev/sdb1].corruption_errs  885679
[/dev/sdb1].generation_errs  0

 

The strange thing here is that sdd1 is an old SSD (6 years?) and old cable, whilst sdb1 is less than a month old, with a new cable. What could cause the new components to have the errors?

 

 

bigdaddy-diagnostics-20220628-1457.zip

Edited by randommonth
Revised the request
Link to comment
17 minutes ago, Digaumspider said:

I've been getting an error message daily of a plugin not being compatible with unraid 6.10, but it's still working just fine, while I wait for the update.

Any way to suppress only this message?

 

"* docker.folder.plg Not Compatible with Unraid version 6.10.3"

 

Thanks!

Click ignore.

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.