XDUDE3D

I just deleted the container by mistake, I reinstalled and it will not launch. The container starts but the GUI will not load. I made sure the ports were not conflicting with other containers but still nothing. UPDATE: just needed to remove the "s" from the URL for the "WebUI:" so it was not trying to use SSL. (http://[IP]:[PORT:6080]/vnc.html?resize=remote&host=[IP]&port=[PORT:6080]&autoconnect=1)

While I have been on unraid for awhile now, I have just recently run into the 1 array (30 drive) limit. Pools are great for some things but the whole point of why I picked UNraid was to not be locked in a raid. When I bought my license, they advertised unlimited drives, not 1 array 30 drives. I'm really upset.

Of 23 drives, 7 of these are ST8000VN004 mentioned in the OP, only 1 has been showing errors. All on LSI cards. Set it to no spin down since it's only 1 drive acting up. Hope this is addressed in a more refined fix as this server has been rock solid for years, until this. Thanks to JorgeB for helping confirm it was errors on spin up and pointing me to this post as the likely culprit.

While I would be happy to have an answer, kinda sucks that seagate/lsi are acting up... My server has been rock solid for years, now 7 of my drives & 3 of my HBAs are on the list of potential issues......... I set the one drive that has been throwing errors to no spin down to test this out. I hope a update comes to undo/fix this, as editing each drives power settings (at least what I understood from the linked topic) does not sound like something i wanna do just for fun. Just not sure why only 1 drive is acting up out of 7 of those same drives... Must be the wrong FW on that one maybe. Maybe I'll just grab a 9300 16i card and make sure all the seagates are on it, idk. Ok...I'll do some tinkering and report back/close this topic.

Totally agree on the memory. I have a good stick that I am swapping out one stick at a time till i find the bad one. I thought it saying "MC4 Error (node 1)" it would be stick 4 on CPU 1, so swapped it but error remains. So will just swap them till i find it. Will running the mem test in the boot menu tell me more exact location of the bad stick? Sounded logical to me that a memory issue could cause issues elsewhere, just was not sure it could cause hard drive errors or not. I already moved the drive to another bay, so it is not the cables or hotswap issue.

sovereign-diagnostics-20231214-1606.zip

Hey everyone! I have a drive that keeps getting read errors but I have run the smart tests (short and long) and it passed. Attached the smart file. Also, I have a ram stick (error from log below) that I'm trying to pinpoint as well to replace, could that be causing my read errors if the drive is fine? I normally dive into things and figure them out on my own, but I'm a new dad and have a lot less time to troubleshoot and look over things, so any help would be much appreciated! kernel: mce: [Hardware Error]: Machine check events logged kernel: [Hardware Error]: Corrected error, no action required. kernel: [Hardware Error]: CPU:8 (15:2:0) MC4_STATUS[-|CE|MiscV|AddrV|-|CECC|-]: 0x9c31c00001080a13 kernel: [Hardware Error]: Error Addr: 0x000000070ab8eeb0 kernel: [Hardware Error]: MC4 Error (node 1): DRAM ECC error detected on the NB. kernel: [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: RD, part-proc: RES (no timeout) Edit: I just noticed this might be posted in the wrong section, sorry if it is. ST8000VN004-2M2101_WSD9W4HN-2023-08-31 disk6 (sdo).txt