Mogo
-
Posts
115 -
Joined
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Mogo
-
-
8 hours ago, johnnie.black said:
If the server reboots during a check you very likely have some hardware problem, make sure it's not overheating and then test with hardware, like a different PSU, etc
The temps for the hard drives are between 26-35 °C (as reported by unraid). Unless the system is getting really hot and unraid doesn't have a display for it, I assume the temps are ok? What I did find was an external ssd drive was corrupted somehow. It has auto mount/share. I was able to do an xfs repair on it. I'm not sure if that might contribute to the problem.
Unfortunately I do not have an extra power supply. I am trying to run the parity check again after fixing the drive above to see if the unclean shutdown happens again. If I do replace the power supply, is there any recommendation for one that supports the Norco RPC-4224 case and all those hard drives?
-
On 3/1/2020 at 10:26 AM, david11129 said:
After it finishes, I would run it again and make sure it's 0 again. I've had them pop up when writing during an unclean shutdown before. As long as the error count is fixed and stays 0 on the next check, I wouldn't worry about it.
So I can't seem to run a parity check. The parity check finished with the same amount I mentioned earlier. Every time I run a parity check everything is ok for the first hour or so. Then for some reason the server gets rebooted and it goes into an unclean shutdown state and the parity check never continues or completes.
-
Just started a monthly parity check and I noticed 33% of the way in this:
- Sync errors corrected:14006
Prior to starting the parity check there was an unclean shutdown as the server tried to reboot I think. The parity check is still going, would the diagnostic file help even though it's in the middle of a parity check.
-
@Jhp612 I believe I solved the issue with my P2200 card and asrock motherboard in general. Going through all my bios options I noticed that the Primary Graphics Adapter was set to pcie. I changed it to use the onboard vga and now the system will boot with the P2200 installed. I'm pretty sure that I had it at onbaord vga before. Perhaps my cmos battery is dying. I don't know but periodically the bios settings will revert back to default settings. Hopefully this helps you as well.
On another note, I have an issue that's been reported in the general forum about the upgrade to 6.8.1. I get the line 164 error on unraid boot up for the nvidia 6.8.1 plugin. Since there seems to be no current solution, how can I go back to nvidia 6.8.0 plugin? I can only get into unraid when I boot in safe mode with no plugins. Thanks as always for any help.
-
I'm having the same issue as reported by fainttrace. The only difference is that I upgraded to the nvidia 6.8.1 plugin. When I choose to launch safe mode with no plugins, unraid boots fine, otherwise I get that line 164 error.
-
1 hour ago, saarg said:
If you can't boot and it stops before unraid is loaded, the issue is not unraid. If your bios is from 2016 it is about time you update it.
Then how did it work before on the nvidia 6.8.0 plugin? (Prior to going from nvidia plugin 6.8.0 to nvidia plugin 6.8.1, it booted with the video card in the system) I tested limetech 6.8.0 and nvidia plugin 6.8.0 when i rolled back. In both instances the server will not boot when the video card is in there now. I would assume that I would of had this issue from the very beginning when I installed the video card and not after the upgrade.
Anyways if anyone has any other ideas about what could have happened, let me know. If not I will try a bios upgrade tomorrow.
-
2 hours ago, Jhp612 said:
I am experiencing the same issue. I have an asrock board with 2 x P2000's installed
with the previous 6.8.1 drivers (prior to today) everything worked fine. I updated again to make sure I had the latest goodies and can not boot anymore either. I will have to wait until Friday when im back to triage. looks like someone had success with physically removing his video cards for the time being so I may give that a go
My motherboard is also an asrock. I didn't have much time today. I ran some tests and could not get it to boot with the P2200 even when I reverted back to the 6.8.0 nvidia plugin. For now the video card is not in the system. That's the only way I can get it to boot. My bios is quite old I think from 2016. Asrock has the latest one listed from 2018 ( there's 3-4 bios revisions). I'm thinking of trying to upgrade the bios. Don't know why nothing will work with the video card now. Currently I'm on 6.8.1 but from limetech.
-
So saarg's comment about hardware issues got me thinking. I took the Quadro P2200 video card out of the system, now the system boots. Does that mean I need to revert back to 6.8.0 to use the graphics card? It was working before with the video card in the system prior to this update.
-
5 hours ago, saarg said:
If system initializing comes before the unraid boot menu it could be that your USB isn't chosen in the bios as a boot device. Or it could be hardware failure.
You can try to check the USB drive in windows and try to run the make boot able script again.
I put the usb drive into the windows system and at fist it said there were issues do you want to fix etc.. after the scan was complete it said there were no errors found and windows was able to load the usb drive. I then copied the folder to my desktop like you mentioned as a backup. I also ran chkdsk from the command prompt and it came back with no errors.
So I put the usb back into the system and it still is stuck on system initializing. Unfortunately the motherboard only has 4 usb 3.0 slots. I even tried to plug the usb drive into the case slots (not sure if those are 2.0/3.0) and that did not work either.
5 hours ago, saarg said:If system initializing comes before the unraid boot menu it could be that your USB isn't chosen in the bios as a boot device. Or it could be hardware failure.
You can try to check the USB drive in windows and try to run the make boot able script again.
Yes the system initializing is showing before unraid boot. It's the first thing that show's when the system is turned on. I guess I have to take the usb drive out and try and get into the bios? Since it won't even give me the option to enter the bios. If it's a hardware failure, how can a software update do that?
3 hours ago, sjaak said:you can use a Linux live boot usb to gain access to the drives, i'm not sure how to do it when you have disk encryption...
(or remove it from the server and mount it to an another linux system)
best tip i can give: ALWAYS make a backup before upgrading and safe the backup somewhere else...
(you can create a full backup through the GUI.)
Thanks noted for future. I've never had issues with unraid updates (os or otherwise). This last month it seems everything is breaking for me. I have to say that everyone on the forum have been very helpful.
-
17 minutes ago, trurl said:
Do you have a backup of your flash drive?
I'm going to say no. I had one of those ca plugins that did weekly backups, however, the folder it backs up to is a share on the array which I don't have access to now. I assume that ca plugin did a flash backup.
-
I just upgraded to the 6.8.1 nvidia plugin from 6.8.0 nvidia plugin. Now the server will not boot. On the screen it keeps saying system initializing and stays like that forever. I tried a hard power off multiple times and even unplugged/turned off the power supply and the issue is the same. I really would appreciate any help since I do not know what else to do. Thanks.
-
Been having this error for awhile (a few months actually). Can't seem to find any solutions, however, I've seen similar questions posted. Almost all torrents will now say Tracker Status: Error: Permission Denied. If the same torrent is loaded into another application it works fine. The odd torrent does work. The container path is /data with a host path of /mnt/user/d and in the actual application it has /data/c and /data/i for complete and incomplete respectively. Other that regular os/docker updates the settings haven't been changed. Any ideas? Thanks.
-
@JT24, @alturismo, thanks for the info. I didn't know about turning IPv6 off or about assigning the appdata folder for plex to 1 drive. Krusader I have installed and didn't think about using it that way. Makes it much easier to navigate. When I look at the docker logs for plex it looks like how you have it, however, the database has to be corrupted if I have stuff unavailable. So I will try a db restore and see what happens.
-
One last thing then. I'm going to try restoring from a database backup that plex does every 3 days. Unfortunately that last backup was a year ago. I figure this would save some work and is less time consuming than starting from scratch (As an aside I've read on the net that if the plex db backup's stop, it's probably due to database corruption).
Anyways instructions say to stop plex and basically rename com.plexapp.plugins.library.db-2019-01-01 to com.plexapp.plugins.library.db. If I stop the plex docker then how to I do this, since I can't get into the docker?
-
3 minutes ago, trurl said:
Not a question of which disk appdata is on, but instead how you specify the path in the docker mapping. /mnt/cache/appdata doesn't involve the user shares, /mnt/user/appdata does, even if the share is completely on cache.
So i just checked the Plex docker paths and they are all setup as /mnt/user/xxx
-
2 minutes ago, trurl said:
The reason I ask is because there were reports of database corruption on earlier version, seemed to be related to user shares, since it didn't affect people who had appdata specified with a disk path. Supposedly fixed on 6.8.
I heard something about that. I thought if the appdata folder resided on the cache drive you were ok? Which is how mine is.
Would my solution be to remove the library from plex and then re-add it? trying to scan for new files doesn't seem to work.
-
possible i was on 6.7 went to 6.8 and then nvidia 6.8 all within the last 2 weeks. This issue though could of happened before that or during the os upgrade window not sure.
-
Hey folks I have a question about a library being unavailable. Using the lsio docker in unraid 6.8, not sure when this happened, however, the content for one of my libraries says unavailable. Permissions and paths etc..all match up and the files are still there are work through shares. It was fine before so not sure what's changed or how to fix it. Any ideas?
-
13 minutes ago, Pducharme said:
Hi, did you made sure to "check" the settings inside PLEX settings itself? Especially, in the "transcoder" section :
"Use hardware acceleration if available"
"Use hardware-accelerated video encoding"
If you already check them, it is suppose to use it.
In Plex I have the following checked "Use hardware acceleration when available"
-
drpete I have a Quadro P2200 installed and plex has not crashed. That being said I'm not sure if the encoding/decoding is working correctly for me. Perhaps someone can enlighten me on my setup.
I followed spaceinvaader's video, no issues there. Using the latest unraid/nvidia build 6.8 and lsio plex docker. When I run a sample video transcode test, my 4 core E3-1245 v5 xeon cpu maxes out on load.
This is what's shown on the plex dashboard:
Video- 4K (HEVC Main 10 HDR)
4K (H264)—TranscodeAudioEnglish (TRUEHD 7.1)
EAC3—Transcode- when running the command "watch nvidia-smi" the empty processes box gets populated
Unless I understand it wrong, since it says both video and audio are being transcoded, I should see the hw beside them in plex to show it's being done by the hardware?
- when running the command "nvidia-smi dmon -s u" all 5 columns are zero's
Shouldn't these columns have numbers in them? (gpu, sm, mem, enc, dec)
So I decided to force plex to decode by using this information as the Plex Transcode
#!/bin/sh
/usr/lib/plexmediaserver/Plex\ Transcoder2 -hwaccel nvdec "$@"Now when I rerun the sample, the process gets populated (same as before) but now for the 5 columns, these 3 headings have numbers in them (sm, mem, dec)
Only thing I can think of is that my cpu is not good enough, was hoping that the video card would have helped since I heard of people running like 15 streams with a dedicated video card and I can't even do 1 stream.
-
17 hours ago, itimpi said:
You need to rerun the repair with the -L option added.
Thanks that seem to work. I'm attaching the log output from running the command. Am I all in the clear now? The array gave back online and disk7 looks normal again.
-
So I tried running the check again and it keeps coming back with the same output. Figured I would try the xfs_repair command since that was the next step. Anyways the output is below. Not sure what to do. How do I mount the filesystem and then unmount it?
xfs_repair -v /dev/md7
Phase 1 - find and verify superblock...
- block cache size set to 708168 entries
Phase 2 - using internal log
- zero log...
zero_log: head block 2559054 tail block 2559047
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed. Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair. If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this. -
On 12/17/2019 at 6:45 PM, jonathanm said:
NO!!!! If you format, all your data on any unmountable drive will be erased! If you format a drive, parity will be updated to reflect the format, and rebuilding will result in a freshly formatted drive with no files, just like you told it to do.
https://wiki.unraid.net/index.php/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
So all your drives are being powered by just one string from the PSU? That may well be causing a voltage drop that would cause your symptoms. Ideally you would only use one connector from each cable so you have the most possible wires running from the PSU to the backplane.
So I am trying to fix the drive now. Found a spare cable to have it connected from the power supply to the 3rd backplane. I was following the instructions in the link you provided however, I am not sure what to do next. I'm attaching the output from the test. I do not see anything about corruptions. Can I assume everything is ok and move to the section After the test and repair?
-
16 minutes ago, jonathanm said:
NO!!!! If you format, all your data on any unmountable drive will be erased! If you format a drive, parity will be updated to reflect the format, and rebuilding will result in a freshly formatted drive with no files, just like you told it to do.
https://wiki.unraid.net/index.php/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
So all your drives are being powered by just one string from the PSU? That may well be causing a voltage drop that would cause your symptoms. Ideally you would only use one connector from each cable so you have the most possible wires running from the PSU to the backplane.
Damn. Thanks for letting me know. I'm going to shut down the server and see if I can run more power cables to the backplanes. Then I'll look at those instructions you provided to fix the file system. I'll report back the outcome when it's all done.
5 minutes ago, Michael_P said:This.
I was having problems with drives dropping from the array, replaced HBAs, cables, drives, until I figured out there were voltage drops causing random drives to fall out of the array.
Thanks man, I wouldn't know anything about voltage drops and stuff like that. I see 4 connectors I figure I can connect 4 things.
[Support] Linuxserver.io - Plex Media Server
in Docker Containers
Posted
Have an issue. Hope someone can help. I was on nvidia plugin 6.8.0, however i upgraded straight from the unraid menu to 6.8.3. I removed all the nvidia plugin stuff since I heard that plex has hardware transcoding support now. Plex is also the latest linuxserver version. I can't connect to plex and it has this in the logs:
Starting Plex Media Server.
That line keeps repeating till infinity. I know this means database corruption. Going through the plex forum when I run the commands to check for corruption or run a repair under linux (https://support.plex.tv/articles/201100678-repair-a-corrupt-database/?_ga=2.196733356.1089636088.1584550100-768537819.1565985532) I get this error:
Error: file is not a database
I don't have any backups. The 4 that are listed don't work since this is probably related to that database corruption stuff. Short of deleting the db to fix this issue and re-adding the libraries, is there any way to save and poster info or at the very least save what items were watched or is all that info lost now?