cmarshall85

Thank you. Should I preclear the new drive first?

Honestly I think this disk is probably cooked, it's really old, so at this point I would probably just move forward with replacing it. Is that possible to move forward with from here, and what steps should I take? Thanks!

Thank you for your response. Replaced the SATA cable and started the array. New diagnostics are attached. tower-diagnostics-20240911-1340.zip

Ok so I have my first disk failure and want to make sure I do everything correctly, so would appreciate some help to confirm the steps I need to take moving forward. Diagnostics are attached My setup is: 12TB Parity 12TB Drive (used for media) 2TB Drive (older drive that I was using to sync files to from my seedbox, organize them, and move them to the media drive) The 2TB started throwing errors so I took the array offline. It says this drive is being emulated on the Main page. I have a 12TB to swap it out with. What's the process moving forward? Should I swap out the bad drive with the new, larger size drive? Should I preclear the new drive before doing anything to rebuild the array? If somebody could show me what I need to do from here, I would really appreciate it. Thanks! tower-diagnostics-20240905-0127.zip

Thank you! All working now.

There used to be a clipboard feature in the upper right corner where I could add links to copy and paste into the WebGUI. Did the feature move somewhere else in an update? I see the option to toggle the clipboard obeserver in the toolbar, but that doesn't get the links from my OS into the app in the browser.

Something very strange started happening with my license file. My license is good until Jan of '23 and I had it working fine since I renewed this past January. All of a sudden a couple days ago I started getting errors that the license was invalid. I checked and the license file is still there, but it's now a 4kb file (instead of the normal 670 bytes) that I can't open in a text editor. If I replace the file it will work for like a day or less before magically getting converted into the 4kb file again. As you can see in the attached screenshot, license.psm is 4096 bytes. The FileBot_License.... file is a copy I just started keeping in there so I didn't have to keep re-downloading the license. You can see it's the normal 670 bytes. I've tried restarting the docker container, restarting the UNRAID server and doing a parity check, and deleted and reinstalled the docker container to no avail. Anybody have any idea what might be causing my license file to become corrupted? Thanks!

Ok I checked out syslog.txt from the diagnostics and included relevant log entries below. It looks like on April 17th the Hardware Error occurred: Apr 17 21:30:26 Tower kernel: mce: [Hardware Error]: Machine check events logged Apr 17 21:30:26 Tower kernel: [Hardware Error]: Corrected error, no action required. Apr 17 21:30:26 Tower kernel: [Hardware Error]: CPU:0 (17:71:0) MC27_STATUS[-|CE|MiscV|-|-|-|-|SyndV|-]: 0x982000000002080b Apr 17 21:30:26 Tower kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001 Apr 17 21:30:26 Tower kernel: [Hardware Error]: Power, Interrupts, etc. Extended Error Code: 2 Apr 17 21:30:26 Tower kernel: [Hardware Error]: Power, Interrupts, etc. Error: Error on GMI link. Apr 17 21:30:26 Tower kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout) FCP logs this every day when it runs the daily scan: Apr 18 04:40:08 Tower root: Fix Common Problems: Error: Machine Check Events detected on your server Apr 18 04:40:08 Tower root: mcelog not installed On April 22nd I installed mcelog. From April 23rd to present, FCP logs it slightly different on its daily scan. Apr 23 04:40:08 Tower root: Fix Common Problems: Error: Machine Check Events detected on your server Apr 23 04:40:08 Tower root: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Apr 23 04:40:08 Tower root: CPU is unsupported This thread I found explains why the log is slightly different once mcelog was installed (mcelog doesn't work with AMD). My questions are as follows: Is that initial error anything to worry about if it just occurred once? Do I keep getting the FCP popup notification about a hardware error, even after I told it to ignore it, because that error from the 17th still exists in the system log and FCP keeps detecting it when it runs the daily scan? If I just reboot the server, and the error from the 17th doesn't happen again, will I not get that FCP popup notification anymore because the syslog will be erased on reboot and will no longer contain that error from the 17th?

Bumping this. I edited OP with a new diagnostic report since I got the error notification again after I installed mcelog. Any insight would be greatly appreciated. Thanks!

I got the following alert from Fix Common Problems. I did not have mcelog installed at the time I received this message. It's installed now, although I haven't received the notification again since I installed. I have attached my diagnostics for further assistance. Thanks in advance! Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the unRaid forums. The output of mcelog (if installed) has been logged EDIT: Updated Diagnostic report with mce log

+1 for this! As a web developer, I would love to be able to help with this to move it forward if the unRAID ppl are interested in implementing this.

+1! Would be awesome if they worked like Desktop/OS notifications where I can just click on them and it will take me to the relevant page in the GUI.

There's this sale going on right now as well. https://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=6335460&CatId=234

I'm curious about this as well. Also, I've read a handful of people say that they prefer APC over CyberPower UPS's. A couple people said their CyberPower UPS caught fire or started smoking, but some of them sounded like negligence on their end (waiting too long to change battery, dust accumulation in the unit, etc.)

@Derek_ did you ever figure this out? I am having the same issue. When I run lftp, any folders/files it creates are root:root and i need it to be nobody:users. Thanks!