-
BTRFS error, Docker won't Start
I'm back after replacing the ram for My last issue, it seams that their were multiple sticks that had issues, even though all but one Passed Memtest86 tests, I was still getting a General Protection Fault error, so I switched for a known working set I borrowed of a friend but now I've got a new issue tower-diagnostics-20230818-1657.zip
-
Multiple Call Trace Issues, General protection fault, CPU Stalls
good Call, It was indeed a Faultily Ram Stick
-
-
Multiple Call Trace Issues, General protection fault, CPU Stalls
I've Had CPU Stalls in the past, But wasn't able to log them due to some Checksum issues, preventing me to set the mirror to flash for the syslog it took me over 20 tries of "long formatting" the USB & reinstall from a backup image, to get the checksum error to go away, which made me think that their was something wrong with the USB Drive Tried Backup a Drive, had the Same Issue, Sometimes it didn't even load properly stuck on the Unraid Boot Selection Screen, Tried booting Windows, It Froze during loading, which made me think I either had a memory issue or a CPU Issue, so I Performed a Memtest (motherboard doesn't support legacy boot so had to use memtest86 v6.20 from a different flash drive) which passed, Then Strangely booted into windows successfully, so I tried Unraid again which Worked for 2 Days (during which I set the Syslog to mirror to Flash & run a Diagnostics, seetower-diagnostics-20230725-1551.zip) it the disconnected from the network today (its connected via ethernet over Power) Check the monitor Won't Display Any text, Forced Shutdown, Check the Syslog on the Flash, nothing interesting as it purged it for being too long. Reset Working for about 30mins, Noticed it Hangs on the Docker Selection Screen, which is something that almost never happens Disconnects Again, Monitor Shows Multiple Call Trace Issues (See Attached Photos), at this point I Power it Off & Check the Syslog which captured some of the call Trace Issues, See syslog.txt I should probably setup a syslog server to monitor the Unraid server in the future
-
Cannot access my server, remotely or localy
This is not a new setup, I've been able to access it previously for months, ever since the "my servers plugin" was released. The error I'm getting is "ERR_NAME_NOT_RESOLVED" I can share my hashed link if required diagnostics Attached tower-diagnostics-20230205-1511.zip
-
No space left on Device Error (SOLVED)
That solved it thank you
-
No space left on Device Error (SOLVED)
Theirs 4.40TB free but logs report that theirs No space left on Device. I can still put files on some shares (Videos), but not on others (Torrents) it reports "Not Enough Space". I cannot create a new share either (No space left on Device). The shares are set correctly to use all drives I don't have a cache drive I have 2 drives that are failing. replacements on the way diagnostics: wooby6-diagnostics-20210901-1740.zip
wooby6
Members
-
Joined
-
Last visited