Sirkyle

Been having some issue lately with the cache dropping offline sometime through the night, but when i get up in the morning it seems connected and online but my Dockers are a mess and if i try to reboot it gets done as unclean. Attached Diagnostics, anything look awry? tower-diagnostics-20240104-0701.zip

got it, any way for me to get the array safely stopped to replace it?

Seems to be getting hung trying to stop the array through the web GUI.

Having issues again with dockers dropping off and user shares disappearing. Had issue on Sunday that was resolved by repairing the cache drive. Happened again last night. Diagnostics attached. tower-diagnostics-20230630-0647.zip

Ran test, errors present. Ran XFS Repair with -L, repaired with no issues. thanks for the help

Correct, apologies. I should have caught that. Properly attached now tower-diagnostics-20230625-1925.zip

Getting frequent interruptions on docker where most my user shares disappear. Usually cannot stop array after this happens and unclean shutdown occurs. Parity rebuilds fine after. Diagnostics attached. domain.cfg cache.cfg docker.cfg smb-extra.conf super.dat network-rules.cfg ident.cfg share.cfg network.cfg go.txt disk.cfg ST2000DM008-2FR102_ZFL1H7M6-20230625-1925 cache (sdd).txt Hitachi_HUA723020ALA641_YGG2V01A-20230625-1925 disk11 (sdf).txt ST4000DM004-2CV104_ZFN0GP64-20230625-1925 disk5 (sdn).txt WDC_WD40EZRZ-00GXCB0_WD-WCC7K4AVFN9V-20230625-1925 disk16 (sdm).txt ST2000DL004_HD204UI_S2H7J9GC308116-20230625-1925 disk15 (sdb).txt ST4000VN008-2DR166_ZGY94JW6-20230625-1925 parity2 (sdc).txt ST2000DL004_HD204UI_S2H7J9FC303171-20230625-1925 disk2 (sdi).txt Kingston_DataTraveler_2.0_5B740F869B3B-0-0-20230625-1925 flash (sda).txt ST4000DM004-2CV104_ZFN2YN1D-20230625-1925 disk1 (sdt).txt ST3000DM008-2DM166_W502ANJE-20230625-1925 disk9 (sds).txt WDC_WD40EZRZ-00GXCB0_WD-WCC7K3LFV7T1-20230625-1925 disk13 (sdr).txt ST4000DM004-2CV104_ZFN1W8L7-20230625-1925 disk8 (sdl).txt ST2000DL004_HD204UI_S2H7J9FC303182-20230625-1925 disk4 (sdj).txt ST4000DM000-1F2168_S301K226-20230625-1925 disk12 (sdh).txt ST4000DM000-1F2168_Z3061TEZ-20230625-1925 parity (sdq).txt TOSHIBA_DT01ACA200_23HM07RGS-20230625-1925 disk14 (sdo).txt ST4000VN008-2DR166_ZGY953K3-20230625-1925 disk3 (sdg).txt ST4000DM004-2CV104_ZFN1VH48-20230625-1925 disk6 (sdk).txt ST4000DM004-2CV104_ZFN0QK24-20230625-1925 disk10 (sdp).txt ST3000DM008-2DM166_Z504J69T-20230625-1925 disk7 (sde).txt cmdline.txt drm.txt plugins.txt motherboard.txt iommu_groups.txt ethtool.txt folders.txt lsmod.txt lsscsi.txt loads.txt memory.txt lspci.txt meminfo.txt lsusb.txt urls.txt top.txt ps.txt vars.txt lscpu.txt lsof.txt df.txt ifconfig.txt dhcplog.txt syslog.last200.txt docker.txt syslog.txt unraid-6.11.5.txt appdata.cfg tv.cfg m----s.cfg services.cfg S-----e.cfg shareDisks.txt d-------s.cfg l--------d.cfg

Afternoon, Im getting a problem with my radarr docker not loading the webui. Checking the log I see this error. [v4.0.5.5981] System.IO.InvalidDataException: Failed to load configuration from file '/config/config.xml'. Ive tried force updating, deleting the old image and nothing seems to be working. Any clues?

switched to a new bay. diagnostics attached tower-diagnostics-20211001-1417.zip

So each column of 8 bays is supported by a Molex plug and no other drives in the column are having issues. I’ll try a diff bay

It’s on a set of brand new cables albeit it runs into a backplane. Doesn’t ever seem to be a problem until a parity check occurs. Should I just swap bays?

So been awhile, replaced the cache with a new drive and things had been running fine all month. when parity check ran last night for the first of the month, it completed this morning with 0 errors, but seems like cache is offline again? No dockers available. user shares were offline. grabbed diagnostics before rebooting. I'll hold off rebooting. tower-diagnostics-20211001-1301.zip

Got it, thanks guys, will report back in a few days

Ok, parity check finished with no errors, no user shares are currently mounted. And a new cache drive is on the way. diagnostics attached. tower-diagnostics-20210909-0545.zip

In the meantime ill go back to running the non correcting parity check