jowy_ham
-
Posts
18 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by jowy_ham
-
-
24 minutes ago, JorgeB said:
If this started out of the blue without any changes it sounds more like a hardware issue, but you can try enabling the syslog server and post that after a crash in case there's something visible there.
Syslog enabled.
Sep 15 11:52:44 Tower sSMTP[8441]: Creating SSL connection to host
Sep 15 11:52:45 Tower sSMTP[8441]: SSL connection using TLS_AES_256_GCM_SHA384
Sep 15 11:52:48 Tower sSMTP[8441]: Sent mail for [email protected] (221 2.0.0 closing connection j5-20020a17090aeb0500b0026b4ca7f62csm1999412pjz.39 - gsmtp) uid=0 username=root outbytes=910
Sep 15 12:10:59 Tower emhttpd: spinning down /dev/sdg
Sep 15 12:11:02 Tower emhttpd: read SMART /dev/sdg
Sep 15 12:41:02 Tower emhttpd: spinning down /dev/sdg
Sep 15 12:41:05 Tower emhttpd: read SMART /dev/sdg
Sep 15 13:11:06 Tower emhttpd: spinning down /dev/sdg
Sep 15 13:11:09 Tower emhttpd: read SMART /dev/sdg
Sep 15 13:41:10 Tower emhttpd: spinning down /dev/sdg
Sep 15 13:41:13 Tower emhttpd: read SMART /dev/sdg
Sep 15 14:11:13 Tower emhttpd: spinning down /dev/sdg
Sep 15 14:11:15 Tower emhttpd: read SMART /dev/sdg
Sep 15 14:41:16 Tower emhttpd: spinning down /dev/sdg
Sep 15 14:41:19 Tower emhttpd: read SMART /dev/sdg
Sep 15 17:46:05 Tower file.activity: Starting File Activity
Sep 15 17:46:05 Tower emhttpd: Starting File Activity...
Sep 15 17:46:05 Tower file.activity: File Activity inotify starting@17:46, the system was forced resetted
Nothing much was logged prior to that
-
Recently my UnRAID system has been crashing randomly.
Can't find any errors in syslog. System was still working fine at 11+am then suddenly, unable to access web and SSH in at 5pm.
Only task it was doing was preclearing 1 x 12TB HDD, nothing intensive was performed during this period.
I have the following running (24x7):
1 x piHole
1 x Linux for torrenting
1 x Windows 2019 for DHCP services
These crashes will rendered the server unresponsive:
- No display output (most of the time, the system runs headless). I have tried to connect up a monitor when it crashes. but nothing shown (black screen)
- Keyboard not responding (Alt+Ctrl+Del) but Caps lock lights up
- web interface not accessible
- SSH not accessible
And after hard resetting the system, I would encountered random disks having disk errors (during auto parity checks upon array restarted) and these errors will disappear upon another reboot (I will shutdown the array and reboot the system again) without meddling with any HW connections.
And sometimes 1 or 2 disks will be disabled due the errors, thus it will trigger a RAID rebuild which is .......
Attached is my diagnostic logs, hope experts can help
-
Tried to preclear my shucked 14TB WDC_WD140EDGZ, only managed to precleared once successfully.
Is the drive bad (twice failed at post-read verification) ? Attached are the logs
tower-smart-20220208-1934.zip tower-syslog-20220208-1142.zip
-
Thanks to all.
The issue has been resolved. Re-do both the SATA and power cables
-
41 minutes ago, trurl said:
Connection problems on disk 4, check connections, both ends, SATA and power, including splitters.
Why do you have 50G docker.img? 20G is often more than enough.
Even more, why 100G libvirt? I don't think anyone has ever needed more than default 1G for that.
At which log/area did U find that it is disk4 that is give the issue ? so that I may learn how to troubleshoot the issue in the future
For issue 2 & 3, how do I fix those "oversized" issue ? Do I have to recreate ?
-
Previously I won't have any parity check sync errors for months. But lately, after I replaced 1 x HDD (faulty) and 1 x 8087 cable (replaced cable due to UDMA CRC error count). Sync errors have been popping up. Is that a cause for concern ?
For example, I did a parity check on :
24-Jan-2022, there were 766 sync errors
31-Jan-2022, there were 272 sync errors
01-Feb-2022, there were 128 sync errors
I'm in the progress of my 4th parity checks, and there are still 128 sync errors
Can experts please kindly advise on what I should do ?
Attached is the diagnostics ZIP for your reference.
By the way, in the event that I need to replace a current HDD (8/10TB) with a higher capacity HDD (14TB), what's the correct procedure ?
Is it use new 14TB HDD to replace either 1 of the parity HDD, then use the replaced parity HDD as normal data HDD
-
Stop & Restart ARRAY does not "remove/clear" the disk errors. Have to reboot the whole machine.
Reason for wanting to remove/clear disk errors is daily health check of array (email notification) will report as FAIL cos disk have errors.
-
3 minutes ago, JorgeB said:
SMART test passed so disk is OK for now, recommend replacing/swapping cables just to rule them out and keep monitoring.
Noted. But how do I clear away the "ERRORS" ? No way except to reboot the server ?
-
Attached is the SMART extended test results
-
Parity check completed without no errors
-
2 minutes ago, John_M said:
Be aware that once your parity check is complete a bug in Unraid 6.9.1 will allow the disks to spin down even if a SMART self-test is in progress. You ought to set the spin-down delay to "Never" until the check is over.
Thanks for the tip.
-
1 minute ago, JorgeB said:
SMART extended test takes several hours, and it can't make much progress while the disk is being used.
Noted (1st time running SMART extended test)
Will just have to wait it out. Thanks
-
3 minutes ago, JorgeB said:
It's logged as a disk problem, run an extended SMART test on that disk.
I'm running a SMART extended self-test now, but as Parity checking is in progress, it is really slow. 5 mins still 10% complete. <- is this progress speed normal ?
-
Hi All,
1 of the disk in my UnRAID server of 8+2 disks encountered read errors while doing a parity check (parity check still in progress at the moment.
Any cause for concern ? Need HDD replacement ?
Attached is the Diagnostics ZIP for your reference.
Appreciate it greatly for any advice in regards to the issue encountered
UnRaid system crash randomly (version 6.9.2)
in General Support
Posted
I have just turn on syslog mirroring to flash (USB), hope that will capture more info.
Cos previous logs were logged to a share folder on the ARRAY, so I guess when the ARRAY crash, the logs can't be logged