Tetsuo
-
Posts
14 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Tetsuo
-
-
Will Change the powersupply tomorrow.
Just ordered a new one for my main rig (that i wanted to upgrade anyway) and will transfer the "old" one over to the Unraid server.
Will report back if that helped. -
Im confident that temperature is not an issue as i cleaned everything when i added 2 more disks just a few weeks ago.
CPU heatsink is a beefy Noctua NH-U12S and disk fans are Noctua PPC 140s in a Fractal R5.
CPU and disk temps are always in the mid 30s. Maybe low 40s when it´s boiling hot in the summer.Memtest it is i guess.
-
So this essentially could be anything really?
Probably a Memtest would be the first course of action then. -
Already had that running fortunately. The last unexpected reboot occured some time between the 8th and 9th of July.
I noticed the sd 10:0:2:0: attempting task abort!scmd errors that seem to be related to some issue with the HDD Temp Docker (according to another support thread).
Things i´ve changed since the last unexpected reboot:
* disable the HDD Temp Docker
* disable spin down (for now)
-
I´m having a hard time finding the culprit of this issue atm.
My Unraid box will reboot unexpectedly/sporadically.
It has done this at least 4 times over the course of the last 4 weeks.
Diagnostics attached.
Would appreciate some help to drill down on this issue.
-
FWIW i found that using this command (add your claim token of course)
curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=claim-xxxxxxx'directly in the Unraid web terminal works in claiming the server.
Before that i also tried it via the variable in the dockers settings but that wouldn´t work.
I have it, sort of, back up and running now. Access via the local web app works. Access remotely via my Phone on mobile network works as well. What´s still weird is that access via the official webapp (app.plex.tv) doesn´t work for now claiming it can´t establish a secure connection.-
2
-
-
15 minutes ago, wgstarks said:
Just from curiosity, did y’all use the sign out all devices option when resetting the password? From my reading it’s supposed to be very important to success.
sure did. now still wrangling to get it up and running again
-
Doesn´t work unfortunately.
There is no Server entry in the sidebar when going to the settings.
And yes, i´m using the local plex app via https://<mylocalserverip>:32400/web
It´s also on the same subnet.
Addtionally, adding PLEX_CLAIM as a variable with a newly generated Claim key doesn´t work either. Also no errors showing up in the docker log.
EDIT: Tried to follow the stuff mentioned in your second link (thanks for that one).
Removed the mentioned lines in the preferences file added the CLAIM variable with a fresh claim key and restarted the container.
Now i can´t access the local web interface anymore
"ERR_EMPTY_RESPONSE"
Which seems to be another problem....argh -
Same issue here after changing my PW. Can´t get the Claim to work.
Server just shows up as "not authorized". -
The link itself does, right. But the next "hop" via "Re-enable the drive" does not. it just goes back to the Troubleshooting category. Thus i couldn´t link it directly.
FWIW i found it by just putting "re-enable" in the search box.So i should just go ahead with "Rebuilding a drive onto itself" described in the documentation i guess as. at least to me, the drive itself looks fine.
-
This article has a link to Re-enable a drive.
this is then empty though
-
I´m in need of a little assistance I´m afraid.
I today had one of my drives going in disabled state with the following erros in the Disk log.
Nov 5 12:25:21 Skynet kernel: blk_update_request: I/O error, dev sdj, sector 8594112800 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 5 12:25:21 Skynet emhttpd: read SMART /dev/sdj Nov 5 12:25:21 Skynet kernel: sd 1:0:3:0: [sdj] tag#1307 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Nov 5 12:25:21 Skynet kernel: sd 1:0:3:0: [sdj] tag#1307 Sense Key : 0x2 [current] Nov 5 12:25:21 Skynet kernel: sd 1:0:3:0: [sdj] tag#1307 ASC=0x4 ASCQ=0x0 Nov 5 12:25:21 Skynet kernel: sd 1:0:3:0: [sdj] tag#1307 CDB: opcode=0x8a 8a 00 00 00 00 02 00 3f c1 20 00 00 00 08 00 00 Nov 5 12:25:21 Skynet kernel: blk_update_request: I/O error, dev sdj, sector 8594112800 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0The disk was running fine until today and i haven´t touched or moved the unraid machine in months. Last time i did some upgrades and recabling is also 2 years back.
I was about to try to just re-enable it and do a rebuild (which i think i need to do, right?) but couldn´t find the information on how to do it.
The respective page about re-enabling in the docs seems to be empty.I suppose the drive is fine and it can still be used. if not, that´wouldn´t be the end of the world as i was about to swap in 2 14TB drives to replace the parity and one of the 3TB ones. At least that was the plan.
I got one 14TB already here, the other on is on order and should arrive mid next week.How to move forward here? Any advice is appreciated
Attached my diagnostics for good measure.
-
@escocrx jup. had the same issue. Wouldn´t connect to VPN anymore. I also had to downgrade to 2.3.9-1-07
Unraid 6.12.2 rebooting sporadically
in General Support
Posted
FWIW i removed the Nvidia Quadro P600 that was still in, but which i wasn´t using for anything anymore, and didn´t have an unexpected reboot since.
Either the Card went south or this was some unexpected behavior after the Update to 6.12.2 as i never had any issues on 6.11.
Will still change the power supply for a bigger more efficient one.