JorgeB
-
Posts
67,521 -
Joined
-
Last visited
-
Days Won
707
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by JorgeB
-
It's strange, max speed with all drives active on the second LBA is low and about what you're getting during the rebuild, that would suggest the controller is not linking at full speed/with, but that doesn't explain the low single disk speeds, in any case check HBA link speed.
-
See here: https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309
-
Even single disk performances are way of.
-
I would say that helium level below 100 is bad, it means it's leaking.
-
Reboot in safe mode and post new diags if still slow.
-
When it happens again, and before rebooting, download and post the diagnostics.
-
Run an extended SMART test on all disks.
-
This time you did reboot, though log spam already started again, you should check what's causing that, likely a docker or plugin, but probably unrelated to the low speed, nothing else jumps out on the syslog, start by doing a disk speed test to check all disks are performing as expected.
-
This is one way: https://forums.unraid.net/topic/93846-btrfs-error-with-new-system-m2-ssd/?tab=comments#comment-867992
-
There's filesystem corruption in the pool, best bet it to backup and re-format the pool.
-
Please post the diagnostics: Tools -> Diagnostics
-
Difficult to say without seeing the rest of the log, log spam makes some info not appear. Reboot.
-
Syslog starts on September 23rd and ends on the 24th, and is also full of spam.
-
Glad you find the problem, but we still don't recommend using SATA port multipliers, and you might see similar errors in the near future, though they do work for some.
-
Unraid won't disable a disk because of SMART, if it's disable it means there was a write error, and looking at SMART the disk is really failing, probably because all the helium leaked out, you'll need to replace it.
-
Those are without rebooting first.
-
Looks more like a power/connection issue, also a good idea to update the LSI's firmware, since it's very old.
-
Cancel that and re-enable parity.
-
Don't use controllers with or connected to SATA port multipliers.
-
Diags are after rebooting son not much to see, re-sync parity.
-
Log is being spammed with nginx errors, reboot and post new diags after the check is running for 5 minutes.
-
There's something still using the array, if you can't find what it is force a reboot.
-
Errors copying files to share, sometimes it just stops
JorgeB replied to Holo's topic in General Support
Use as simple LAN config as possible, and if needed try with different hardware if available. -
Looks like a connection problem, replace both power and STA cables. Next time please post complete diags: Tools -> Diagnostics
-
Syslog is just after rebooting so not much to see, next time grab and post the complete diagnostics after a disk gets disable, disks look fine, CRC errors are usually a connection problem, most times a bad SATA cable.
